DHIS2 Android Capture App 2.0.0 has been publish in Github for Beta testing prior to the production release in December. This version is compatible with 2.33 comes with a lot of bug fixes (list here) and many new features! You can find an overview of New features with screenshots at the end of this message, and the detailed list in Jira here.
We open in Beta to allow you to test all the fixes and new features. It is very important to give us your Feedback!
Report your issues in Jira before Friday, November 30th
Project: Android App for DHIS2 | Component: AndroidApp
Fix Version: 2.0.0-Beta
The APK is available in Github
You can find the updated documentation here.
Remember that is also a good moment to work on translations for 2.0.0!
Hi @marta, This is great! I installed it on my phone but for some reason I keep getting a login error “No user has been previously authenticated. Cannot login offline.” I only get this when pointing in my instance but not the dhis2 play instances.
Thanks for the tip. Unfortunately I am still getting the same error. I am not sure if it’s an issue but I am using aws ec2 IPv4 Public IP with the port 8080 after it. Could this be the issue?
Dear John,
If you still get same error message, then try to add a new user and assign the Tracker app roles and then try to log in with the newly created usei
I don’t have a tracker program. Is it mandatory to have a tracker program and users assigned to that program? Also, now I am getting a different error:
“Login Error: Something went wrong. Please check that server url, username and password are correct and try again.”
please try to write the URL as you write it to access through the browser and include the folder where you have dhis2 deployed if is not root. In web you are usually redirected but not in Android.
Hi @jesplana. Are you sure you don’t need to include the “s” after the http as a secure connection? Would you mind creating a user in your server and sharing the details via private message so we can try to access?
If on your computer one of the two URLs are working fine, it means the server you’re trying to reach is locally hosted on your computer which makes it inaccessible when out of your computer! (No other device can access that link unless you host it online)