ESP32 Forum

Hi,

There are some bugs I want to address in both the IOS and Android versions of the Rainmaker app.

1. There is a major bug in refreshing the data in IOS and Android versions of the app. In IOS, the data is automatically refreshed upon receiving updates. By data, I am referring to dropdown values (add/remove values), text input, and hidden ui, etc. In Android, you always have to refresh the page (drag down) to have the latest values. This is incredibly confusing because the user does not know when to refresh to get a new layout/data. The workaround is to keep the entire configuration (values, ui elements, etc.) even though half of it is not used, creating a complete mess.

I think this is fairly easy to solve, simply update the Android app to refresh when data is received simillar to the IOS one.
I have created several posts, but got no answer for such an important issue: viewtopic.php?t=47184

2. During the SoftAP provisioning, the IOS app shows a wrong and stuck "Sending Wi-Fi Credentials" page with "Failed to connect device SoftAp" error, even though we are connected successfly. After 5 seconds, it automatically goes to the "Select Wi-Fi Network" page, and the provisioning runs fine after that. The Android app goes directly to the "Select Wi-Fi Network", and no error is shown. I think this is an issue in the IOS app, which is simply showing the page "Sending Wi-Fi Credentials" when it is not needed, or the error is shown as the default. This creates some confusion among users who assume something is wrong.

Hi,

Regarding the 2nd point about SoftAP provisioning on iOS, can you please provide the following details:
- what firmware version are you using
- what app version you are using
- what are the exact steps taken in order to reproduce the issue.
These details will help us accurately reproduce the issue on our end and work towards a quick resolution.

Hi,

I am using IOS app v3.6.2 (3e47dbd), esp_rainmaker 1.6.1, rmaker_common 1.4.12 and esp idf 5.5.1.

As for the steps, nothing unusual. Start from an erased board, connect to PROV_, go to the Rainmaker app, add a SoftAP device, and the error appears already.

The code is looking as follows (I tried to put all the code in one function, but normally it is split between different modules and interfaces, so I hope I combined them correctly) :

Is someone able to give a proper statement regarding the bugs and limitations that we identify and post on this forum?

I posted several times the issues related to the difference between IOS and Android, which, for me, is a major bug in not having a common data/layout refresh behaviour. Still, I get no answer, not even something like "stick with it, this is currently not in our use case".

I will ever be fixed, or should I consider moving to a separate app?

Also, is it possible to have a proper widget that controls one of the elements inside a device, rather than having a shortcut to it? Or at least a shortcut to a Scene would be great.

Hi @Dorian ,

Sorry for the delay in following up on this issue, and thank you for your patience.

A fix for the SoftAP provisioning issue on iOS has been released in the latest ESP RainMaker iOS app.
iOS App Version: 3.7.1
Release Notes
Fixed an issue during SoftAP device setup where a misleading “Failed to connect” message could appear even when provisioning was proceeding correctly.

We're also improving how app-related feedback is tracked and reviewed to help ensure reported issues receive quicker visibility and follow-up.
Please update to the latest version from the App Store and let us know if you continue to experience any problems.

Thanks for your feedback and support.