Closed Maatteogekko closed 1 year ago
Hello, thanks for the report !
Can you please paste the output of flutter doctor -v
?
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)
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 NSInternalInconsistencyException
.
This is fixed as of version 1.4.0 by cleaning up all stream handlers when the plugin is detached from the engine and try
/catch
ing the event sending logic.
Closing this for now, please update to motion: ^1.4.0
and let me know if the issue persists, in which case we can reopen it.
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