You should check the server url, we have seen other cases like the one you describe.
The link can redirect you to the login screen on web yes, but that does not mean it is the “server url”. The app needs the whole path to where dhis is installed in the server.
If this is caused by the common “bracket problem” (that tomcat 8.0.35 or later does not allow square brackets unless it has been explicitly permitted via a setting in Tomcat’s “server.xml” configuration file), then the problem should appear when opening e.g. Tracker Capture in the web too… Rahul, does Tracker Capture opens normally in your browser?
I’ve rectified the Tracker Capture issue in DHIS 2.30 after going through your shared post. Tracker Capture is now opening with Metadata loading in web but still im facing problem while its connecting to the database through the APP.
Its still stuck at authenticating window.
Kindly check the link again if its opening on your app and advice.
Initial configuration time depends on many factors, in particular how many orgunits the user have access too (it works OK with up to 1,000+ orgunits, but it takes considerable time and there are obviously some limit), the size of your Tracker / Event program and so forth.
I would suggest you experiment a bit - using users with access to one facility and another with access to 1,000, as an example - in order to track down exactly which part of your specific installation that takes too much time to synch. Also do some meta-data and data synching from the settings window, and see if it’s faster (or slower) there.
In all fairness to the developers: it is difficult for them to effectively respond to general requests for “better performance” - much better if you can focus on specific, proven bottlenecks (like “synch time goes up 10 times when the number of stages increases from 1 to 5” - just as a made-up example).
I’ve just downloaded/installed v 1.2.0 myself, and it took around 2 minutes to synch the meta-data plus around 3 min to synch the data (500 cases, 1000 events). That’s more or less as with earlier versions.
Is there a way to control which program cases are downloaded during the data synch? I do have several Tracker Programs on the same system, but with version 1.1.1 and earlier the cases and events downloaded were mostly from the “main” tracker program. With 1.2.0, all cases and events are downloaded from another program that’s seldomly used - AND I cannot figure out how to dump those cases and instead download cases from the “main” Tracker Program… I can open the initial profile form for the “main” program, and it says “enter your search criteria” at the bottom - but the main Case ID field (usually auto-populated with six-digit unique ID) is locked…
I am able to open a new case for the “main” program though, but it seems like some of the erratic program rule behaviour persists… (this is test 1, so will test further and report via Jira)
we will give more control on the data downloaded when we are able to work on this issue (https://jira.dhis2.org/browse/ANDROAPP-1804), concretely in this related one (https://jira.dhis2.org/browse/ANDROAPP-1960) in which we are considering to add a parameter “per program” in the number on TEI’s downloaded (similar to the “per org unit” which is already present). But for now, we are focusing on stabilizing the app and we don’t have a timeline for new features.
In any case, I cannot find a reason for you downloading very different data from one version to another, unless your data has changed (i.e. last updated more recent… enrollments closed… ). If you sync two versions of the app to the same server, do you get different TEI’s downloaded?
The test instance I’m using is exactly the same test instance we used for v 1.1.1 2-3 weeks ago (and which Nancy, Jose, and you have access to) - which is why I find this behaviour so weird. During all those previous tests, the initial synch would result in 500 cases from the “main” Tracker Program being downloaded - now all 500 cases downloaded are from a Tracker Program used as an “archive” that in the test instance have negligible or no data for the last 12 months. (in other words, you have access so you can try yourself).
I am able to capture a NEW case for the main Tracker Program, but not edit any existing one (which is typically what field investigators will be doing). Also, after capturing the profile and stage 1, I cannot get out again - whenever I press the “back” arrow in the profile screen, it jumps forward to stage 1 instead of back to the program&case list. That is “new” behaviour too, it did not do that in 1.1.1