-
-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on iOS with the latest version (3.4.x) #720
Comments
Looking at it now.. |
Thanks for your quick changes, but even by setting IPHONEOS_DEPLOYMENT_TARGET to 15, I have the following error:
|
I just experienced this as well, luckily in development. Runner | +0xe3253c | MobileScanner.start (MobileScanner.swift:224)
EXC_BREAKPOINT I'm not sure if it the same issue, but iOS is crashing. Edit: The |
Hi @vlazdra, I'm also using latest version 3.4.1 and few days ago I encounter the crash maybe same with this on my firebase craslytics My case the crashing line is It's same with your detecting. |
@binhvtKova what was your fix/workaround for this. Did you just end up reverting versions. I'm getting the exact same crash as you.
|
+1
|
I think I know what the problem is here. As indicated, there is a problem with
specifically Will fix this soon. |
Hi all, could anyone verify if #781 fixes the issue?
|
@navaronbracke Just tested your fix multiple times, my app is no longer crashing. Before it was constantly crashing after scanning anything with the error message |
@gabrielyea Thanks a lot for confirming! |
We've been encountering a substantial number of crashes on Firebase Crashlytics related to this bug in the latest release, version 3.5.2. Has anyone else noticed the same thing?
|
@radivojeostojic That seems to point to https://github.com/juliansteenbakker/mobile_scanner/blob/master/ios/Classes/MobileScanner.swift#L223 Could you file a different issue for this? Including the full stacktrace would be helpful. |
Hi everyone,
On iOS, I have the following crash when returning to a Flutter application:
The text was updated successfully, but these errors were encountered: