[Android][TimePickerDialogModule] IllegalStateException #13831
Labels
Platform: Android
Android applications.
Ran Commands
One of our bots successfully processed a command.
Stale
There has been a lack of activity on this issue and it may be closed soon.
Comments
|
I am getting something very similar :/ |
|
We are also seeing this. Its fairly infrequent (but regularly). I'd say about once or twice every release cycle for just one or two users, tops. I absolutely cannot reproduce it. Here is my stack trace.java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState at FragmentManager.java:1415android.app.FragmentManagerImpl.checkStateLoss FragmentManager.java:1433android.app.FragmentManagerImpl.enqueueAction BackStackRecord.java:687android.app.BackStackRecord.commitInternal BackStackRecord.java:663android.app.BackStackRecord.commit DialogFragment.java:301android.app.DialogFragment.dismissInternal DialogFragment.java:267android.app.DialogFragment.dismiss DialogModule.java:120com.facebook.react.modules.dialog.DialogModule$FragmentManagerHelper.dismissExisting DialogModule.java:126com.facebook.react.modules.dialog.DialogModule$FragmentManagerHelper.showNewAlert DialogModule.java:256com.facebook.react.modules.dialog.DialogModule.showAlert Method.java:-2java.lang.reflect.Method.invoke BaseJavaModule.java:319com.facebook.react.bridge.BaseJavaModule$JavaMethod.invoke JavaModuleWrapper.java:158com.facebook.react.cxxbridge.JavaModuleWrapper.invoke NativeRunnable.java:-2com.facebook.react.bridge.queue.NativeRunnable.run Handler.java:739android.os.Handler.handleCallback Handler.java:95android.os.Handler.dispatchMessage MessageQueueThreadHandler.java:31com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage Looper.java:168android.os.Looper.loop MessageQueueThreadImpl.java:196com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run Thread.java:818java.lang.Thread.runAlso, yes this DOES seem the same as #6228. I am not sure why it is closed by the product team. |
|
Same here (RN 0.42.3) Stacktrace: |
|
+1 |
|
+1 Same stacktrace. Crash on Android 6.0.1 |
|
Also getting this, here is my stack trace. The common theme here seems to be calls to |
|
Same error with |
|
+1 Maybe related to Code Push |
|
@yaronlevi I don't think it is related since we are not using Code Push and we still got the error |
|
A question to those of you who are seeing this error. Are you guys placing ReactRootView on Fragment? |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
stale
bot
added
the
Stale
|
Still getting these in production. Can't reproduce. |
stale
bot
removed
the
Stale
react-native-bot
added
the
Ran Commands
react-native-bot
added
Platform: Android
|
Same here。 Android: 7.1.1 & 7.1.2 |
|
Upgraded to 0.55.4 but still got the error. Android: 7.1.2 |
|
RN version: And on Android 8.0 Any work around or possible reason for crash? |
|
the same error in our production. react-native version: 0.54.2. it happens on Android 6.0.1, 7.0，7.1.2, 8.0, 8.1.0. about 1,671 times on 972 users. most devices on Oppo, and some on Huawei. the others is rarely. stacktrace:
I am sure the |
|
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
stale
bot
added
the
Stale
|
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I've found 50 crashes recently on our product.
I'm not sure it's the same issue as #6228
React-Native: 0.42
Android: 7.0
java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState at android.support.v4.app.FragmentManagerImpl.checkStateLoss(FragmentManagerImpl.java:1527) at android.support.v4.app.FragmentManagerImpl.enqueueAction(FragmentManagerImpl.java:1545) at android.support.v4.app.BackStackRecord.commitInternal(BackStackRecord.java:654) at android.support.v4.app.BackStackRecord.commit(BackStackRecord.java:621) at android.support.v4.app.DialogFragment.show(DialogFragment.java:139) at com.facebook.react.modules.timepicker.TimePickerDialogModule.open(TimePickerDialogModule.java:121) at java.lang.reflect.Method.invoke(Method.java) at com.facebook.react.bridge.BaseJavaModule$JavaMethod.invoke(BaseJavaModule.java:345) at com.facebook.react.cxxbridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:136) at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java) at android.os.Handler.handleCallback(Handler.java:751) at android.os.Handler.dispatchMessage(Handler.java:95) at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31) at android.os.Looper.loop(Looper.java:154) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:196) at java.lang.Thread.run(Thread.java:761)The text was updated successfully, but these errors were encountered: