Mobile v3.355 Breaks my app

💬 Mobile
1
  1. My goal: Users who have had retool update to 3.355 report major issue with our app not displaying their tickets
  2. Issue: Queries appear to run ok, but the collection is not displaying the ticket data which is in a localstorage object
  3. Steps I've taken to troubleshoot: tested on a working android tablet that is still on v3.332, tested on an iOS iphone that is v3.332. App functions normally on any device running 3.332. App does not display the ticket data on samsung android tablets running 3.355. App works normalling in editor and mobile view
  4. Additional info: Tablets i tested on are samsung galaxy tab active4 pro running android v14
1 Like
3

+1

4

This seems to happen every few months when retool pushes an update to Android.

Moral of the story is don't use Retool if your user base is primarily Android and your app is mission-critical.

5

The jump from 3.332 → 3.355 included changes to how the Retool mobile app sandboxes storage on Android. On Samsung devices running Android 14 specifically, there are reports of localStorage reads returning null or empty objects even when the data was previously written — the app itself doesn't throw an error, which is why your queries appear to run fine but nothing renders.

some things you could try out…

  • Switch from localStorage to a Retool state variable or localStorageState. Retool's own localStorageState component is more reliable across versions than raw JS localStorage calls, and it handles the Android WebView sandboxing differences better.

  • Add a null-check + fallback in your transformer. If your query or transformer reads from localStorage, wrap it:

js

   const data = JSON.parse(localStorage.getItem('tickets') || '[]');
   return data.length ? data : [];

This at least prevents a silent render failure and can help confirm whether the read is returning null.

  • Force a re-read on component mount. Some users have worked around this by triggering the localStorage query via an onSuccess chain from a dummy query that runs on page load, rather than relying on the initial load order.
  • Test with window.localStorage explicitly. On some Android WebView builds, localStorage and window.localStorage behave differently. Worth a quick swap to confirm.
1 Like
6

Yikes. Thats problematic since I’m calling localstorage quite a lot throughout the app. I’ll try and test a few things out like you suggested, but it will be a huge hassle to have to change from localstorage throughout my app.

7

Thanks for flagging this @Peter_Kunz ! I just wanted to share an update that our mobile eng team has identified the issue and is working on releasing a fix for this ASAP. As soon as we have any more updates, we will share them here!

2 Likes
8

Hey everyone, just wanted to share another update here. We have just released v3.362.0 of the Retool mobile app in the Google Play Store. This version addresses the localStorage issues mentioned above, so please update whenever possible and let us know if everything is working as expected!

9

Thanks for the update, but I still appear to be having issues on my samsung tablet. I had another user test with a pixel 10 pro, and they don’t seem to be having issues on 3.362, but my samsung galaxy tab running android v15 is not displaying the collection that pulls from localStorage. I have tried restoring app defaults, and uninstalling and reinstalling.

One other odd thing I noticed is that on the galaxy tab, if you try and view the retool app version, its just a blank box

image
image1458×911 65.6 KB

10

Hey @Peter_Kunz - we'll try to reproduce this on Samsung hardware and give you an update as soon as we can.

11

I made a copy of the app and tried to replace localstorage with variables to see what might be failing, but I’m struggling with the limitations of the debug console in the mobile app. Queries that have never used localstorage are failing, and I can’t tell why.

12

This is concerning. We are in the middle of switching all of our apps from another frontend to Retool. We have a large mixture of iOS and Android out in the field and if there are issues with Android we could have line down situations constantly. Yikes!

14

We’ve noticed that with the latest Retool version 3.362 on a tablet, the resource query is returning a failure status even though the data itself is valid. This issue did not occur in the previous version.

Are you aware of any changes or issues in version 3.362 that might be impacting resource queries? Also, when is the next release expected?

Additionally, where can we find information about releases and updates?

For reference, the device being used is an Android Galaxy Tab A9+ (SM-X210).It seems more timing issues with resource querys

15

Is this similar to the behavior that you're seeing, @Peter_Kunz? It's interesting that you're both on Samsung tablets. We haven't been able to replicate these issues. :thinking: Can one or both of you share a JSON export of the app you're working with?

16

I sent you an export in a separate message

1 Like
19

Hey all - the 3.367.0 release is slated to include a fix for the issue causing certain queries to fail despite returning valid data.

To add some context, version 3.355.0 represented a fairly significant re-architecture of the mobile app and brought a much needed performance boost - along with some bugs, unfortunately. I expect everything to be considerably more stable going forward, but I appreciate the patience!

1 Like
20

3.366.0 version number 3545 has blank screen issues for us (Android). When will 3.367.0 be available?

2 Likes
21

I'm having the same problem.

22

We're digging into it right now! Thanks for reporting an issue.

23

Same here

24

We are having the same issue here, since updating the Android app to 3.366 the 6th click on an application navbar will systematically render a blank screen requiring a complete restart.