In Capture Android App v3.0 thumbnail images were available:
Images are configured in the Capture Web App
Tracked Entity Attribute Value type set to “image”
In the Tracked Entity Type the TEA for the image is listed as the first entry
The TEI is marked as “Display in list”
After migrating to v3.1.0.1 the thumbnail images no longer appear. Instead the icon selected in the Tracker program is shown for all TEIs. If I remove the icon, an empty circle with a “?” is displayed instead of the icon.
I note that the same issue occurred last year after migrating from v2.9 to v3.0.
Can anyone help, has the required configuration changed or is this a bug?
Hi @George_McGuire it is indeed a bug that we detected during in 3.1.0.1
I believe we saw it was not working as expected while developing another issue as I can’t find the specific jira ticket where it was fixed in the patch.
I have, however, verified that it is working as expected in both 3.1.1 and 3.1.1.1,
I would recommend updating to latest release (3.1.1.1). As it is a patch it has no major changes other than many bug fixes that improve the stability of 3.1.0.1.
Hi Xavier, thanks for the detailed answer. I have upgraded to v3.1.1.1 but still do not see the thumbnails. I then uninstalled and reinstalled the Capture app v3.1.1.1 dated 31.01.2025 but still do not see the thumbnails. Have you confirmed that the thumbnails are visible to you?
Hi @George_McGuire I verified that they were visible both in tei dashboard and tei list screen, it could be possible that we are missing this fix somewhere else… Where exactly is it that you cannot see the thumbnail? is it in the stock management module? could you share a screenshot of where you are having this issue so that I can troubleshoot the issue?
Thanks in advance!
Ok I thought there weren’t any thumbnail images but just wanted to verify, maybe there was a screen I knew nothing about hidden around there somewhere .
Ok I think I have figured out the issue. First I had misunderstood the issue and I had tested that when you add an image from the app that it is displayed correctly, and it is, at least in 3.1.1
After your detailed message I understand that the issue is that the images that are already saved in the server are not being downloaded.
you can set the size permitted to download files, as it is 0 by default, I believe that is the reason why no files are being downloaded.
in your ASWA you can see that the value is 0
In the later versions of the ASWA, the default value is null rather than 0 which does not set any restriction when downloading unless specified, however when the value is 0 it will not download any files.
So in order to solve this problem you can either increase the file download size limit from the ASWA you have currently have installed, or update the ASWA to the latest version.
I tried modifying this in the demo server you facilitated to test this but the user did not have permissions to do change sync settings.
Let me know if any of the two provided solutions work!
All the other configuration in the maintenance app looks ok!
Hi @Xavi, thanks so much, changing the download limit resolved the issue instantly, I am thrilled! Also the enlarged image pop-ups when tapping on the image are back.
I will make sure to include this in our documentation. Indeed difficult to keep track of all the little changes. I call this a DHIS2 “charming trap”, a setting which seems insignificant but can make a large difference. I had not considered that, obviously, images have to be downloaded and therefore this restriction applies.
Thanks again a million!
George
Hi @George_McGuire that’s what we’re here for! Yes it is very difficult to keep track of all new functionalities and small configuration changes through out the different teams and version changes.
I would say it is one of the things that we have the most trouble with, especially when implementing new features, there is often some use case or configuration that slips through our test cases and generates some unexpected bug, we are continuously working with the development team and QA to improve this, but I’m afraid final “fire proof” testing is ultimately done by the community .
Regardless of this, I am glad this worked!, as usual, don’t hesitate to reach out if you encounter any other problem.
.
.