-
Notifications
You must be signed in to change notification settings - Fork 343
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
Container is null in performControllerChange when back button is pressed #337
Comments
Infact, we are only seeing this issue in the version that upgraded from 2.1.3 to 2.1.4 |
I'm seeing the same issue, but I am messing about with the instance state of the backstack (related to #316 ). Below is another stacktrack, which originates from the same place in my code, and seems to have relevance to this issue:
|
Same issue here. |
Does anyone have more info on this? A way to reproduce it would be great. |
This issue is returned back in version |
It is happening for me as well and it is very easy to reproduce (for me at least).
Expected Actual I am pretty sure this has to do with Conductor's router keeping the wrong state and assuming it can re-use what it already has, but some things are null / were cleared up, something like that. Is there any way to clear the cache or re-create the router? I am using 3.0.1-SNAPSHOT version. Thanks. |
@danielocampo2 |
@PaulWoitaschek tdigging into the demo and comparing I realized it was actually a DI issue. Thanks! |
We are getting a unreproducible crash report in our app that's difficult to find the cause of.
It appears the container is null when performControllerChange is called in Router.java:
Full stack trace:
I can't seem to reproduce it, so I suspect it occurs during some weird state where the back button is pressed while the container view isn't quite ready. Strangely, it gets past your containerFullyAttached check.
Have you got any idea about what state the app has to be in to cause this issue? I know changes have been made recently in this part of the library, so this may be related to #287 #285 and this commit.
The text was updated successfully, but these errors were encountered: