Dear all,
I have updated my instance to the latest version 2.41, and I first noticed that the lower version of Android Capture is not working with the latest version. I then upgraded DHIS2 Android Capture to the latest version, dhis2-v3.0.0.1, but unfortunately, the data is not synchronizing from the capture to the DHIS2 web instance. I am not sure what might be the issue
Hi @Shapr0019 , I’m sorry you are experiencing problems.
Can you please give us more details on the issue? like, what kind of data are you trying to sync, is there an error message anywhere?. what version of the capture app where you using that didn’t work with v2.41, and what was the error if any was shown?
Thanks in advance! 
1 Like
Hi @Xavi
Thank you for reaching out.
I was using Capture version 2.9.1 for DHIS2 version 2.40, and it was working well. I upgraded DHIS2 to the latest version because I wanted to use the multiple selection option set on a tracker program. Afte upgrading, I designed a new tracker program. Everything worked well on the entry stage, but after capturing the data and trying to send it, the app is not sending the data. It keeps saying “syncing” for more than 10 minutes, even though my internet connection is very good.
There is no specific error showing; the app is just stuck, and nothing is pushed to the server. In terms of the data, I am trying to sync tracker data with many questions involving multiple selections. It’s a general tracker program with fewer than 15 questions. See some attached image
This is the test instance. If you require credentials to test from your side, please reach out.
2 Likes
@Xavi any solution to this
Hi @Shapr0019 thanks for all the info, unfortunately if there is no message we can’t really know what’s wrong (something we should improve on our side), if you could DM me the credentials on slack I could debug a bit and see if we can find out more about what is causing the problem and we can make sure to inform the user what the problem is.
1 Like
@Xavi i have sent the email to you
1 Like
Hi all received well! @Shapr0019 I will try to look into it as soon as possible and get back to you.
2 Likes
@Xavi Thanks
Hi all, this is a follow up to this issue for anyone that is having a similar problem.
From DHIS2 core latest minor patches in v40 and v41 the new tracker importer is being used by default and recommendation.
The new tracker importer greatly improves on sync issues for implementations with large simultaneous amount of data from many users, however, as more people use it we are detecting some fine tuning that still needs to be done. So thank you all for helping detect these issues and improving the product.
The issue in this case was a backend issue where if the org unit the tei belonged to did not have a code, the update job in the back end would fail, but not inform correctly of the sync problem or reason. This is indeed an issue as metadata wise, we allow an empty org unit code, and also user should be informed on what the problem was.
A Jira issue was created to resolve this and has been merged to develop and backported to other versions. It will be available in the next minor patch releases.
Thank you all again for helping us detect these issues and allowing us to keep improving DHIS2.
2 Likes
@Xavi thank you so much Molloy
1 Like