Fixed
Status Update
No update yet.
Comments
fl...@gmail.com
Since this is happening in Tink, rather than in the AndroidX library, it would be best to open an
fl...@gmail.com
il...@google.com
il...@google.com
ap...@google.com
Tink is the library that does the heavy lifting in Jetpack Security.
And yes, potentially raising that issue with the Tink team directly could help.
il...@google.com
@4 Well why didn't Google offer it there? Crashes are far more important than warning logs...
Here, created it there too:
https://github.com/google/tink/issues/535
Here, created it there too:
Description
this is the first time I file a bug, so I don't really know how to do that properly.
I noticed that if I create a fragment instance in an activity, add it to the container, remove it with the FragmentTransaction's remove method (which destroys the fragment instance) and then later use the same fragment variable in the activity to add it back to the container (which calls onCreate again), no LifecycleObserver can be added in the fragment's onCreate method, because the fragment is still in DESTROYED state.