-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fatal NSInternalInconsistencyException
when terminating application
#13
Comments
Hello, thanks for the report ! Can you please paste the output of Also, are you experiencing this crash within the sample app our your own app ? |
I am receiving this as a report of my app in production. I haven't tried to replicate it yet (only a few crashes so far) flutter doctor -v
|
Hello, I have the same problem. I received 676 crash reports in 10 days. I was using it for the background to be animated on the homepage, I think that's why I'm getting a lot of crashes. |
Hello everyone, thanks for reporting this bug. According to the crash stacktrace, it is a race between threads after the FlutterEngine has been detached due to the app being closed. Motion events may still be sent to the engine at that point, causing the Flutter framework to throw this This is fixed as of version 1.4.0 by cleaning up all stream handlers when the plugin is detached from the engine and Closing this for now, please update to |
NSInternalInconsistencyException
when terminating application
I am getting this error on iOS. So far got 3 reports, all on the iPhone 12 mini
NSInternalInconsistencyException
Sending a message before the FlutterEngine has been run.
Stacktrace:
02fd7c2211694d7dad91337afbe2d033-symbolicated.crash.zip
The text was updated successfully, but these errors were encountered: