-
-
Notifications
You must be signed in to change notification settings - Fork 518
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
Android: android.view.ViewParent android.view.View.getParent()' on a null object reference #646
Comments
Are you using |
@lampn9397 could you provide a repo with a reproduction of the issue then? |
Also, I forgot to say, I did use the "animationEnabled" for my navigator in this version. I will try to see what happens if I revert it to false. |
i also experienced this issue recently,
it seems that the Author has mentioned it in their ReadMe.md file. about how to solve this issue.
|
sorry, i think the solution above still not resolved. |
Can you try and change https://github.com/software-mansion/react-native-screens/blob/master/android/src/main/java/com/swmansion/rnscreens/ScreenStackFragment.java#L157 to |
i'll try, @WoLewicki , but, btw, if i change / modif in node_modules react-native screens repo, it means that, for the production-App, i have to clone that repo and use my repo instead of using from react-native-screen? |
You can use patch-package until the version with a fix is released to automatically apply the change to your code. |
@WoLewicki , thank for the solution, 👍🏼 |
I can confirm that disabling the animation "fixes" the issues. |
@melkayam92 can you check if having the animation and applying #671 fixes the bug? |
Hi,
Since I upgraded from 2.5.0 to 2.10.* I'm getting a lot crashes in production saying:
"android.view.ViewParent android.view.View.getParent()' on a null object reference" - NullPointerExecption
"FragmentManager has been destroyed" - IllegalStateException
"@react-navigation/native": "^5.7.3",
"@react-navigation/native-stack": "^5.0.5",
"@react-navigation/stack": "^5.9.0",
"react-native": "0.63.2",
Now I downgraded to 2.5.0, will update here if the issue really stops.
ALSO - it's not related to the issue that the activity is killed in the background, I checked and it works fine there with the onCreate(null) solution.
The text was updated successfully, but these errors were encountered: