Android: android.view.ViewParent android.view.View.getParent()' on a null object reference

[melkayam92]

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.

[WoLewicki]

Are you using "@react-navigation/native-stack": "^5.0.5",? The supported version of native-stack is taken from react-native-screens/native-stack. Does this issue happen there? If so, please provide a reproduction of this crash so we can work on it.

[lampn9397]

This issue occur also with me on Android devices.
"react-native-screens": "2.10.1"

[WoLewicki]

@lampn9397 could you provide a repo with a reproduction of the issue then?

[melkayam92]

I can confirm that downgrade the library to 2.5.0 didn't help.

Looks like it's related to saveInstanceState..

[melkayam92]

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.

[handipriyono]

i also experienced this issue recently,
details:

• "react-native-screens": "^2.9.0",
• "react-native": "0.63.2",
• "@react-navigation/stack": "^5.7.1",

it seems that the Author has mentioned it in their ReadMe.md file. about how to solve this issue.
For most people using an app built from the react-native template, that means editing MainActivity.java, likely located in android/app/src/main/java//MainActivity.java

You should add this code, which specifically discards any Activity state persisted during the Activity restart process, to avoid inconsistencies that lead to crashes.

  @Override
   protected void onCreate(Bundle savedInstanceState) {
       super.onCreate(null);
   }

[handipriyono]

sorry, i think the solution above still not resolved.
i still getting crash
Android: android.view.ViewParent android.view.View.getParent()' on a null object reference

[WoLewicki]

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 ViewParent screenStack = getView() != null ? getView().getParent() : null; and see if it fixes the issue?

[handipriyono]

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?

[WoLewicki]

You can use patch-package until the version with a fix is released to automatically apply the change to your code.

[handipriyono]

@WoLewicki , thank for the solution, 👍🏼
unfortunatelly, this crash-case is random, so i can not make sure that that solution is working.,
but i still investigating into this issue,, and re-check my sentry if the crash still exist or not

[melkayam92]

I can confirm that disabling the animation "fixes" the issues.

[WoLewicki]

@melkayam92 can you check if having the animation and applying #671 fixes the bug?