IOS read-only not working and endless refresh on Android

Dorian
Posts: 20
Joined: Thu May 01, 2025 9:25 am

IOS read-only not working and endless refresh on Android

Postby Dorian » Thu Jun 25, 2026 10:47 am

Hi,

I have identified new bugs related to the RainMaker app for IOS and Android.

1. Parameters created only with PROP_FLAG_READ (so read-only) are still visible with Edit field on the IOS app. This is not reproduced on the Android app, and I know that it worked in the past versions on the IOS app as well. This only happens for text parameters (toggle, for example, is working fine)

2. The refresh on Android is never-ending, so the loading icon stays forever (tested on different phones as well). Also new parameters added using esp_rmaker_report_node_details are not updated automatically on the Android app (on IOS is refreshed automatically annd they are visible)

printscreen.png
printscreen.png (63.94 KiB) Viewed 60 times

Versions:
- esp_rainmaker 1.15.0
- esp_rainmakercommon 1.8.5
- APP version v3.14.0
- IOS version v3.7.1
- esp idf 5.5.1

Thank you

Dorian
Posts: 20
Joined: Thu May 01, 2025 9:25 am

Re: IOS read-only not working and endless refresh on Android

Postby Dorian » Fri Jun 26, 2026 2:16 pm

One more bug I see between IOS and Android apps.

IOS supports having a value as a description of the parameter that is not part of a dropdown list, while on Android, it shows an extra invalid value. This is confusing, and Android should not show that because it is just the description of the dropdown parameter.

Furthermore, on Android, because of that, it shows an empty space in the dropdown value.

Untitled.png
Untitled.png (211 KiB) Viewed 41 times

esp-ajay
Posts: 4
Joined: Fri Apr 10, 2026 10:12 am

Re: IOS read-only not working and endless refresh on Android

Postby esp-ajay » Tue Jun 30, 2026 11:44 am

Hi @Dorian ,

Thank you for reporting these issues.

Regarding the esp.ui.dropdown behavior, the current parameter value must be one of the strings listed in valid_strs. In your case, the parameter reports ✅ Configured while valid_strs only contains ➔ Clear data, so Android correctly marks it as invalid. iOS does not perform this validation, which is why the behavior differs between the two platforms.
To represent a status or description separately from selectable actions, we recommend using a read-only parameter (esp.ui.text) for the status and a separate dropdown or trigger parameter for the actions. Alternatively, if you prefer a single dropdown parameter, all possible status values should be included in valid_strs.
Regarding the extra empty space appearing in the Android dropdown, we have verified the issue and will be addressing it in an upcoming fix.

We have also verified the following issues and will be looking into them shortly:
- Read-only text parameters being shown as editable on the iOS app.
- The Android refresh indicator continuing indefinitely, and newly added parameters not being updated automatically.

We'll work on addressing these issues and provide fixes as soon as possible. We'll keep you updated on the progress.

Thank you.

Who is online

Users browsing this forum: No registered users and 2 guests