Data Entry Manifest link

Support - Assistance technique
1

Hi everyone
Small quesion
I was trying to check which version of the data entry app I’m using using the below end point added to my DHIS2 instance.
/dhis-web-dataentry/manifest.webapp
The above “structure” works for all other apps except the data entry app. Is there something I’m missing?
Any insight on this would be invaluable.
Thanks!

2

Hi @AllanLusui

To get the version of an app, you can click on the profile picture which will open the menu that has the DHIS2 Instance version, App version as well as if there’s an update available for the app. See screenshot below:

image
image1916×1617 250 KB

3

Dear Gassim,
Thanks for your input, very helpful, Any reason why the manifest link isn’t working for the Data Entry App?

4

Hi Team,

I am suddenly encountering an issue while retrieving the URL from the DHIS2 manifest file. Previously, I was able to access the DHIS service URL using the key activities.dhis.href, which used to resolve correctly. However, it now returns only an asterisk (*) instead of the expected URL.

This functionality was working fine until last month without any changes from our side.

For your reference, I have attached:

  • The DHIS2 system info details
  • A screenshot of the manifest file response

Kindly help investigate and advise on the cause of this issue or if any recent DHIS2 updates might have impacted this behavior.

image
image1017×248 19 KB

image
image1364×513 61.8 KB

5

Hi All,
Could someone please assist me with this?

6

Hi @ravibagul91 and @AllanLusui !

I think this is the same topic so I merged the posts. You can use the direct link to the app instanceURL/dhis-web-aggregate-data-entry/manifest.webapp instead of instanceURL/apps/aggregate-data-entry#/. You can find the direct URL of the app from the Network tab. For example, you can find the manifest.webapp https://play.im.dhis2.org/stable-2-42-1/dhis-web-aggregate-data-entry/manifest.webapp.

7

We have been using the direct app URL (defined in the manifest.webapp file) for several years without any issues. Our application has been submitted to the DHIS2 App Hub and has been actively used by countries through this approach.

However, we’ve recently noticed that the URL specified in the manifest is no longer being returned or recognized as expected. Could you please clarify if there have been any changes to the DHIS2 platform or App Hub processes that might have caused this?

If this behavior is the result of an intentional change, we kindly request:

  • Documentation or release notes detailing the update
  • Guidance on the new recommended approach
  • Any actions we should take (e.g., changes in the manifest structure or app deployment process)

This information is important for us, as we may need to submit an updated version of our application to the App Hub and provide a valid justification for the change to the countries currently using the app.

Thank you in advance for your support.

8

Hi all, thanks for your comments here!

The change to manifest.webapp was unintentional, and we’re aware of it and working on restoring the previous base URL value. You can track progress on this Jira item here: Jira

3 Likes