Hi there!
Our organization has been happy users of retool mobile since launch. However, the last couple months we have been getting a lot of issues, crashing our app in deployment.
The main issue we are facing is unresponsive buttons and the scanner component freezing, forcing us to restart the app to get them to work. When it does crash, we have no error messages indicating what is causing the failure. I have attached
videos to this, demonstrating the most common issues we are getting. Other issues observed have included: “screen going completely white, camera not working, buttons not working, screen going completely black”.
The devices experiencing the issues are all over the board (new& old ios devices, and androids) which makes me think its an issue on the retool side and not our devices.
Would love insight into this, as our retool mobile app is an extremely important part of our production. If we cannot get this solved, we will probably need to move off retool to a custom solution.
Thanks for reaching out, @Ryan_Dale! I'm currently investigating the scanner issue that you've described here and will provide an update as soon as possible.
I'll also make sure that the rest of your feedback gets surfaced internally.
If you're willing to be a bit of a guinea pig, we do have a scannerV2 component that you can try out! In my initial testing it seems to not have the same issue, but I can't guarantee that everything else about it is free of hiccups.
I've raised the necessary feature flag for your org, so you should see it as an option in the mobile IDE. If you do give it a shot, let me know what you find!
Im trying to use this new component, but running into an issue where I cannot close the scanner after successfully scanning a code (essential for our use case). Is there a way to accomplish this?
Yes! You can set up an event handler that fires off scannerName.close() in response to the Capture event. That could easily be a component setting, though - I'll give that feedback to the team.
I tried using the new scanner component for our application but ran into other issues, of the component not grabbing the last scanned code as the latest and causing other issues.
I was wondering if you have any more insight into the performance issues for the v1 scanner? I really like the way it works, but am still experiencing extremely frequent crashes.
I have attached another video, and I want to draw attention to the fact that the whole app locks up when it gets into this state (i.e. even the back button doesnt work)
For some context, this happens roughly every 20 minutes on every device and requires a full app reset. When I have debugging tools open, I can't see any failed queries.
Thanks for the update, @Ryan_Dale. I reproduced the same unresponsive behavior that you're describing when initially testing this, but haven't yet heard back from our Mobile team. I can give them a ping!
If you're able to describe the additional issues that you've seen when using the ScannerV2 component, I can document that feedback at the same time.
Hello,
We're experiencing the same issue, but in our case, we're using an NFC reader. Several team members have reported that the issue tends to occur when the app is left idle but not fully closed. In those situations, the app freezes, and they have to force close it completely before they can use it again.
Hi Darren, the issues with the scannerV2 are a little less obvious to me. I think what was occurring is that even in single scan mode, the previous scan data is being saved and then pulled when referencing the component instead of the new scan data.
Any update on this from the team? Currently these crashes are causing us a 10-20% slowdown in our operation.
