Issue with Read-Only Access in Android 3.2 App

Hi everyone,

We are currently on 2.39.7.1.

We’ve encountered an unusual behavior (potentially a bug) in the Android 3.2 app.

Issue: Users with read-only access to a tracked entity type are able to modify TEI information. These access settings functioned correctly in version 3.1.1.1 and continue to work properly in both version 3.1.1.1 and the web application. However, this issue appears to be specific to Android 3.2.

We are working on restricting certain user groups from editing TEIs, but this behavior is affecting our ability to enforce those restrictions.

Has anyone else experienced this, or found a possible solution?

Thanks!

1 Like

Hi @m.siusko

Thank you for the report. Just to confirm, the restriction in the configuration only comes by adding “can view only” in the DATA sharing of the Tracked Entity Type, correct?

Hi @nancyesp ,
Thank you for a prompt reply. Yes, you are completely right.
The current settings are the following:

P.S. This approach worked well with 3.1.1.1 and in WEB. At the same time they need to be able to create/update events.
If there is another way to restrict specific user groups from editing TEIs, please let me know.

Hi @m.siusko

Thanks for sharing the details! We were able to replicate the issue on our side and are currently investigating it further. We’ll keep you posted with updates as soon as we have more information or a fix available.

1 Like

Hi, @nancyesp ,
Do you have any updates on it?

Hi @m.siusko

Thanks again for reporting this issue! We’ve identified the cause and already implemented a fix. It will be included in the upcoming version 3.2.1, scheduled for release in July.

1 Like