-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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 Production App - java.lang.IllegalStateException #24287
Comments
Same issue here with the production app.
|
The logs are helpful - by any chance are you able to reproduce this/know what sequence of events lead to this crash, or are these just coming in from analytics from your users? |
It looks like this can be caused when the Activity's onCreate gets called without a call to the Application's onCreate. I think @jason-simmons or @matthew-carroll might know more about how the Android lifecycle could result in this - my rough understanding is that we're getting into a state where the Application is maintained but the Activity is lost (and so is FlutterMain). When the Activity is re-launched, it doesn't find settings and thinks things have gone out of order. Check was introduced by flutter/engine#5614 but not a ton of context there :( |
Do you know what version this was working on? |
@dnfield I don't think its possible for an Activity to be created before the Application class. The Application class is the closest thing in Android to a representation of the process....if the process exists then so does the Application class. I agree that the error seems to point to initialization not happening. We've seen some reports of this before. But I don't think we were able to root cause the previous instances of this. @sroddy does this issue only occur on a fresh launch of an app? only on a relaunch of an app? or both? Are you working with a pure Flutter app, or did you add Flutter to an existing app? |
Could something be causing the activity to be created a second time, but the application didn't stop running? |
similar to #14513 |
Did flutter/engine#5614 fix this? |
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away! |
This crash is still recorded by Google Play Console.
Logs
|
Also happening on HWDRA-MG on Android 8.1 (#26997) |
I can't reproduce this error with my own devices. Got the following error report from Google Play ANRs & crashes reports @ 2019/05/29:
|
Same problem. |
Having same problem in Google Play crashes reports. Cannot preproduced it myself.
|
I have the same problem. Any updates for it? |
The issue was closed already due to lack of information. But it seems like no one here has reproduced it other than the logs on Google Play Console. Someone should get one of the devices where the issue occurs or ask someone who has such a device, and do some testing and getting more info. |
Same issue Device list
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Steps to Reproduce
We have a crash on our production app that started to surface after updating flutter to v0.10.2
It is happening on both android 8.0 and 8.1 on the following devices:
P20 (HWEML)
Mate 20 lite (HWSNE)
FIG-LX1 (HWFIG-H)
Mate 10 Pro (HWBLA)
Logs
The text was updated successfully, but these errors were encountered: