Hello,
I’m using dhis2 version 2.41.3.
There’s a bug in the Android app from versions 3.0 to 3.1.1.1.
If a DataSet is set to be entered within a specific (data input periods),
when accessing that data packet from the app, it stops responding.
This has been tested on the dhis2 Play platform, and the issue persists.
I don’t know why the latest dhis2 update has encountered so many problems.
Video to illustrate the issue (A bug in adnroid App with data set.mp4 - Google Drive)
Hi @Eng.Ali_Hameed I am sorry for the issues you are experiencing, could you perhaps add some more details on your specific use case / configuration to help troubleshoot and replicate the issue?
The app seems to be freezing when accessing the report periods… what kind of periods do you have configured?
Also if you are able to, could you share through DM a testing server with credentials to further test this that would be great.
Regards,
Xavi
Hi @Xavi
the problem is clear and simple,
the data input period I chose (2025 - January)
when I choose a data input periods the android app crashes.
and when I remove these data input periods the problem resolves.
and you can test it in dhis2 play you’ll see same issue.
Regards
Thank you for the report. This is fixed in the 3.2 version - you can test it out in your instance by downloading the APK from this link: Beta Testing - DHIS2
Hi @nancyesp
Thank you for clarifying this.
and there are some program rules does not work on latest version of android app and works on version 3.0.1
Hi
Good to know that @nancyesp 's post solves the issue.
For these other issues, would you please create a separate topic with the explanation?
Thanks!
Hi @nancyesp
I installed the Android 3.2 beta app, and when I logged in, the app suddenly crashed. I tried logging in several times, but it still crashed.
To clarify, I deleted the previous version of the app and then installed the beta version.
This is an illustrative screenshot.
If you have any test environment please share credentials (direct message) with me and I will create a ticket to review it.
Thank you
I’ve shared it with you.
Thanks
Good morning @Eng.Ali_Hameed
We’ve checked the crash you reported when logging into the beta testing version 3.2 of the App and we’ve found the issue. On one hand we’ll fix the SDK to prevent the hard crash from happening and getting the app being stuck. On the othe hand, the error was being caused by a faulty configuration of the Android Settings Web App, where a mandatory parameter is missing (completion spinner). This shouldn’t happen since currently the Android Settings Web App makes sure the parameter is filled. We are not sure about what caued this, maybe it was generated during a server update.
In any case, this should be fixed by following the steps below:
This way the parameter would be included and potential errors will be prevented.
Thank you very much for your time testing the App, we hope you find less issues in the future!
Hi @Daniel_Tari
Thank you ,
I followed the steps you mentioned and the issue was resolved in the release 3.2dev.
Hi @Eng.Ali_Hameed
I’m also facing the same issue that you had faced. I followed same steps shared above but still the issue persist. I’m attaching the screenshot of the error for more clarity.
Regards,
Mohd Nawaz
Hi @Mohd_Nawaz,
looking at the build version, it shows “nep_2.7”, which means that it is a custom application based on the official capture app. The official Android Capture app would show a version such as 3.1.1 or 3.2-DEV (for the beta version).
As it is a custom application, it is hard to know the reason of the error because if could be originated by code we are not aware of.
