IMPORTANT: Chrome 148 update affecting date pickers in DHIS2 - here is what you need to know

400x33

Dear DHIS2 Community,

We want to give you a heads-up about a known issue affecting date pickers and calendar components across multiple DHIS2 apps for users who have recently updated their Chrome browser version.

What you’ll see:
Depending on which app and which date input you’re using, you may experience one of the following:

  • The month name in a calendar header always displays “January” regardless of which month you’re viewing (In apps such as Capture, Metadata Management, Data Quality)
  • The year/month dropdown in context selectors (such as the period selector in the Data Entry app) shows only the year (Eg “2026”) instead of the month name

In all cases, the underlying date selection still works correctly, this is a display-only problem.

Affected browsers:

  • Google Chrome/Microsoft Edge 148 (latest version launched yesterday 11/05/2026)

Not affected:

  • Chrome/Microsoft Edge 147 and earlier
  • Firefox
  • Safari

Workaround in the meantime
To help prevent this issue from affecting additional users, we recommend not updating your Chrome/Edge browser until a fix is released.

The simplest immediate workaround is to either install an older version of Chrome or use Firefox or Safari for any data entry or reporting tasks that involve date or period selection.

If switching/installing different browsers is not practical, users can still work around the display problem in most cases, since the underlying data selection works correctly even when labels display incorrectly. We recommend paying close attention to the actual date shown in the input field (In Capture, etc.) to confirm you have selected the right value. In the period context selector in Data Entry, however, you would not be able to see the selected period even after selection.

When will this be fixed?

We are working on a patch to our calendar component, after which updated versions of affected apps will be released. We will update this post when the fix is available.

JIRA ticket: DHIS2-21475

Thank you to alert community members for helping us identify this issue quickly!

Best regards,
DHIS2 Core Team

9 Likes

any idea of the impact for older/unsupported dhis2 versions ?

1 Like

Update: This seems to be due to a bug in Chrome itself, which has been reported here: Chromium (feel free to click “+1” in the top right to illustrate its impact – this requires logging in with a Google account). The bug has been triaged and assigned urgent priority.

In the mean time, versions of Data Entry and Capture have been released with workarounds that work with Chrome as it is now:

  • Data Entry v102.0.5
  • Capture v106.2.1

You can upgrade to those versions using the App Management app.

3 Likes

This is impacting also analysis Apps (Data Visualizer, Line-listing) in case they are considered to have versions with workarounds as well

1 Like

Hi @acasrod,

We have not seen the issue yet in our analytics apps - would you let us know what DHIS2 version and app version you are on?

Thanks so much,
Karoline

1 Like

There are also updated versions of the following apps with workarounds for the issue:

  • Metadata Management v0.153.1
  • Approvals v100.1.6
  • Data Exchange: v100.11.7

You can upgrade to those versions using the App Management app.

2 Likes

I thought I was the only one who noticed this. Thank you for the quick update. We will try use the workaround during this time.

2 Likes

@Karoline

I should have tested in the last app versions. This was fixed in our instance (40.9) when moving from:
Data Visualizer 101.3.7 → 101.6.0
Line Listing 102.1.0 → 102.4.0

4 Likes

Great to hear that updating the apps worked! Do not hesitate to let us know if you see the issue other places.

Best,
Karoline

2 Likes

Thanks for the heads up. We also observed this on v41. Any support to align?

1 Like

Hi @kpvandivier! The new released version of the Capture App v106.2.1 resolve the problem of the Calendar, reported by me in the JIRA ticket: DHIS2-21475.
As the Microsoft Edge Browser is also Chromium, is is also affected!
Thanks @Karoline to reported the issue on the coomunity.
I clicked +1 to the Chromium issue too, The today subversion of Chrome don’t resolve the problem, so it is important to upgrade to the new version of the Capture and other App using the Calendar component.
Thanks for all your work!

3 Likes

Thank you @kpvandivier, @tzemp @Karoline and @acasrod for mentioning this. I have tried it out, and it has worked for me. @macheng I am not sure if this could help your case. This is how I resolved it.

Before:
Blank Periods where present

1. DHIS2 Blank

Steps Taken

  1. Go to the App Management

2. App Hub

  1. Install the new Data Visualizer app available

3. App Hub

  1. Do not forget to clear your browser cache using the Browser Cache Cleaner

After

  1. Go to your Data Visualizer, and you should be able to see the periods

4. Data Vis

3 Likes

Thanks to @Karoline @kpvandivier and all the staff for the quick and risolutive update of the Capture App and all other affected.
The * Capture v106.2.1 fix the bug reported in the JIRA ticket: DHIS2-21475.
bot for the latest update of Google Chrome and Microsoft Edge.

2 Likes

Hi Team,

I am using DHIS2 version [2.40.4.1]

I am facing an issue in the filter section. Under the “Fixed Period” filter, I selected “Month” from the dropdown, but it is displaying with a year symbol instead of the month format.

For reference, I have attached the screenshot.

Could you please help me understand why this issue is occurring and how to resolve it?

Thank you.

Hi @venkatesh.bojja : sorry for the problems here.

This is due to an underlying bug in the latest versions of Chrome. More information about this bug is available in this CoP post: IMPORTANT: Chrome 148 update affecting date pickers in DHIS2 - here is what you need to know

To workaround the bug, you can:

  • update the app where you have problems to the latest version (via the App Management app). The latest version should have workarounds for this bug.
  • use Firefox, which does have the underlying bug.

Please also let us know which app (including version number you are using). You can find this information by clicking on your initials/avatar in the header bar:

4 Likes

Thank You Thomas for the detail information.

2 Likes

Here’s another update:

The Chromium fix for this is released on v150, which is in Canary now – I just tested it out and verified it’s fixed by testing these pages in Data Entry, Capture, and the UI library (choose iso8601 as the calendar) with the Canary version of Chrome

v150 with the fix will be released publicly on June 1, at which point this can be fixed by updating browsers to the latest stable version :slight_smile:

2 Likes

Aaand one more update: the Chrome fix for this is now live! :tada:

It’s available on version 148.0.7778.179, and this fix has been verified in the affected apps :slight_smile:

How to update Chrome:

  1. Go to “About Chrome” in the settings: the “three dots” menu at the top right > Settings > About Chrome
  2. Check the Chrome version – viewing this page will trigger a check for updates
  3. If an update is available, click the option to apply it
6 Likes