react-native-screens: [Android] App crash on start (NullPointerException)
Hi All,
I’m using this library with react-navigation
when enable this library using:
// enable in App.js
import { enableScreens } from 'react-native-screens'
enableScreens() // OK on iOS but crash on Android
Then when I start my app in Android it crashes right at the beginning
Here the error:
--------- beginning of crash
2020-01-11 17:56:41.155 25469-25469/com.myapp E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.meadow9, PID: 25469
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.swmansion.rnscreens.ScreenContainer.isTransitioning()' on a null object reference
at com.swmansion.rnscreens.ScreenFragment.onCreate(ScreenFragment.java:51)
at androidx.fragment.app.Fragment.performCreate(Fragment.java:2586)
at androidx.fragment.app.FragmentManagerImpl.moveToState(FragmentManagerImpl.java:838)
at androidx.fragment.app.FragmentManagerImpl.addAddedFragments(FragmentManagerImpl.java:2100)
at androidx.fragment.app.FragmentManagerImpl.executeOpsTogether(FragmentManagerImpl.java:1874)
at androidx.fragment.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManagerImpl.java:1830)
at androidx.fragment.app.FragmentManagerImpl.execPendingActions(FragmentManagerImpl.java:1727)
at androidx.fragment.app.FragmentManagerImpl$2.run(FragmentManagerImpl.java:150)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
My environment:
- react-native: 0.61.5
- react-navigation: 4.0.10
- react-native-screens: 2.0.0-alpha.22 (Other setups I already follow documents)
Can any help this,
Many thanks
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 19
- Comments: 17 (4 by maintainers)
I can take a look but before I do I’d need to get a minimal repro app where I can see the crash happening. Apparently in this case the stacktrace that’s provided in the issue description does not say much about what could be causing the issue (I see that there one object is null but I wouldn’t expect it to be null at this moment and adding nullability check won’t resolve this problem)