Hey @Elliot_L and @wesleyb, there's a fix coming for Scanner V2, the fix has been implemented and is ready to go. We'll be submitting the new release to both Apple and Google for approval shortly. Once it's approved, it will be available in the App Store / Play Store. Unfortunately, we don't have an exact timeline since the approval process is controlled by Apple and Google, but we'll keep you posted as soon as it goes live! 
@ChiEn I replaced the control with the v2 scanner. It took care of the black screen problem and is much more responsive than the previous version, but I am still having a problem on Android devices. Only about 1 out of 4 barcodes will scan and those take a long time. I experimented with larger barcodes and less information in them with no better results. Then I tried changing the barcode types and found that was the problem. Our bin labels use PDF-417. I tried printing labels using DataMatrix, Code 128 and Code 39 and all of those scan perfectly on Android devices! Is there a possibility of getting this fixed soon? I do not want to go to the trouble of replacing thousands of bin labels just so I can use this app.
Here’s some more information on this: I tried scanning PDF-417 codes printed from two different online generators and they scan perfectly with Retool on Android. I am looking into the possibility that there is a bug in the code generator we have been using for 16 years with no other issues, or if tweaking the parameters in that software makes the codes more readable in Retool. Any advice would be appreciated.
I can follow up internally, @wesleyb! As far as I know, this isn't something that we've specifically seen before.
Hey @Elliot_L and @wesleyb, good news!! 
We've rolled out a new iOS architecture update to users, bringing improvements to Scanner V2. Just update the Retool app to version 3.380.0 in the App Store to get the latest. Let me know how it goes!
We are still experiencing problems scanning with Android devices. The codes scan perfectly in Retool on Apple devices as well as in other scanner software on Android. I will be happy to send samples or give more information if that would be helpful. My app is basically useless to us if we can not use it on all devices.
Thanks for reporting this. Yes please, if you could send some samples @wesleyb, let me bring this up to our engineering team!
Hey @wesleyb, thanks for your samples codes over the dm, we tested it out, our latest updates address this issue, we're planning to release next week! I will keep you updated!
Any update on this?
Hey @wesleyb Thanks for checking in. We're still working on this, there's a more critical fix we need to ship first, but we're hoping to start rolling it out this week. We'll keep you posted here once we have more to share. Appreciate your patience! 
Hey @wesleyb, the fix is live on Android version 4.8.0, currently rolling out in phases, so it may take a little while to reach you. iOS 4.8.0 is still in progress, will update when it's ready!
Hey @wesleyb, Android 4.11.0 is now at 100% rollout, so everyone should have the fix. If you are still experiencing problems scanning with Android devices, try updating the app.
iOS fix is still in progress, I'll follow up here once that's live! 
Hello again @wesleyb, quick update: iOS 4.8.0 has now completed its rollout, and like I mentioned before, Android 4.11.0 is at 100% rollout as well, so the Scanner V2 fix should be available for all at this point. Let me know if you're still running into issues after updating! 
@ChiEn, we are still having problems. Testing with 4.16.0 on Android, pdf-417 labels read very slowly or not at all. Code 39 labels read instantly. With iOS 4.8.0 both types read reliably.
Hey @wesleyb, thanks for testing and reporting back! I've filed this with our engineering team and will keep you updated here. In the meantime, if anything changes on your end, do let me know!
The Android device we tested on was a Samsung Galaxy s24 ultra. I only tried on one device this time, but we had previously tested on at least two others.
Thanks for the additional info, I passed it along! @wesleyb