-
Notifications
You must be signed in to change notification settings - Fork 529
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
API 29 / AndroidX FragmentManager.isDestroyed() crash #485
Comments
Facing same error suddenly. |
Facing same error after updating to androidx.appcompat:appcompat:1.1.0. The problem seems to be what @btraas said. |
Guys, here is the solution for the issue being face. |
You can get solution from here |
No need to implement new SDK. Just remove onDetach() method from CaldroidFragment.java, if you have already moved code to androidx. That's it. Check stackoverflow answer:- https://stackoverflow.com/a/56925799/2598244 |
Hello,
I'm getting a crash on API 29 when the androidx fragment is destroyed by android.
This SO question suggests removing the deallocation via reflection in CaldroidFragment.onDetach:
https://stackoverflow.com/questions/56925777/boolean-androidx-fragment-app-fragmentmanagerimpl-isdestroyed-on-a-null-obje
Removing the onDetach() method fixes the crash for me. Should maybe check if API < 29 before deallocating via reflection?
The text was updated successfully, but these errors were encountered: