You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have integrated the document scanner and it works fine in debugging release. but when I publish a TestFlight release, it scans for first document. after the successful scan, when I try to open scanner for next scan, it doesn't open camera scanner.
It looks like that Another view is already being presented and this could be why it's not displaying the scanner. It also not throwing any error as well. I have tried customizing the DocScanner.Swift and DocumentScanner.Swift files but it doesn't work fine in Production. Though, it's seamless in Debug mode.
I got the same issue here, so I connected my phone and opened the app in Xcode to investigate. While there were no error logs, I noticed a warning when trying to open the document scanner:
Unbalanced calls to begin/end appearance transitions for <RCTModalHostViewController:>
So this issue might caused by multiple modals being open simultaneously, including the document scanner. however, I add a line of code to close the previous modal still not working, so I add a setTimeout on document scanner code block so it will open after 100ms. and it fix the issue
I have integrated the document scanner and it works fine in debugging release. but when I publish a TestFlight release, it scans for first document. after the successful scan, when I try to open scanner for next scan, it doesn't open camera scanner.
It looks like that Another view is already being presented and this could be why it's not displaying the scanner. It also not throwing any error as well. I have tried customizing the DocScanner.Swift and DocumentScanner.Swift files but it doesn't work fine in Production. Though, it's seamless in Debug mode.
Let me know how I can help further assist with it. It'd be really helpful for any quick response. @dmarcs @mateusz1913 @nicolascavallin @ghorbani-m @brennansaul
The text was updated successfully, but these errors were encountered: