-
Notifications
You must be signed in to change notification settings - Fork 22
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
NPE with Activity#isChangingConfigurations #26
Comments
It seems that activity is null while mosby tries to determine whether or
not the controller is destroyed permanently. Just from the exception
stacktrace I can't say much more in detail, nor I think there is much Mosby
can do . Seems more like conductor is clearing out activity reference of
controllers too fast. Is there am example you can provide to reproduce this
issue so that I can try to debug it?
Julien Biral <notifications@github.com> schrieb am Fr., 16. Juni 2017,
20:19:
… When the app is stopped and restarted quickly, I intermittently get into
this state:
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.Activity.isChangingConfigurations()' on a null object reference
at com.hannesdorfmann.mosby3.mvp.conductor.delegate.MvpConductorLifecycleListener.preDestroyView(MvpConductorLifecycleListener.java:73)
at com.bluelinelabs.conductor.Controller.removeViewReference(Controller.java:898)
at com.bluelinelabs.conductor.Controller.detach(Controller.java:886)
at com.bluelinelabs.conductor.Controller$8.onDetached(Controller.java:965)
at com.bluelinelabs.conductor.internal.ViewAttachHandler.reportDetached(ViewAttachHandler.java:103)
at com.bluelinelabs.conductor.internal.ViewAttachHandler.onViewDetachedFromWindow(ViewAttachHandler.java:58)
at android.view.View.dispatchDetachedFromWindow(View.java:16782)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3429)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewGroup.dispatchDetachedFromWindow(ViewGroup.java:3421)
at android.view.ViewRootImpl.dispatchDetachedFromWindow(ViewRootImpl.java:3718)
at android.view.ViewRootImpl.doDie(ViewRootImpl.java:6691)
at android.view.ViewRootImpl.die(ViewRootImpl.java:6668)
at android.view.WindowManagerGlobal.removeViewLocked(WindowManagerGlobal.java:476)
at android.view.WindowManagerGlobal.removeView(WindowManagerGlobal.java:414)
at android.view.WindowManagerImpl.removeViewImmediate(WindowManagerImpl.java:128)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4683)
at android.app.ActivityThread.-wrap7(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1703)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6776)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)
I don't think there is much I can do since it seems to be internal to the
library. Could you please investigate?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAjnri_kNLe5gImoBQZXtLW11A9zTGfeks5sEsckgaJpZM4N8xsz>
.
|
Thanks, I have open the issue on Conductor too. I don't have any good way to repro this, unfortunately. I use MvpController as my base Controller class, and sometimes we've seen this crash. I will keep you updated if I can get to know more about it. |
I have 9 crashes in my Firebase console with exactly this stack trace. I am not able to reproduce this manually either... |
Mosby Conductor version is |
I have the same issue on about 0.5 % of my users in 1 of my apps. I can't reproduce it either. I went through the source code. There is very little Mosby can do here, it seems like am conductor bug but couldn't reproduce it. |
I see, thanks, will folow that issue too. |
When the app is stopped and restarted quickly, I intermittently get into this state:
I don't think there is much I can do since it seems to be internal to the library. Could you please investigate?
The text was updated successfully, but these errors were encountered: