NullPointerException Error: RNBootSplashDialog.show(java.lang.Runnable)

[kf94]

Before submitting a new issue

• [X] I tested using the latest version of the library, as the bug might be already fixed.
• [X] I tested using a supported version of react native.
• [X] I checked for possible duplicate issues, with possible answers.

Bug summary

I am experiencing crashes on Android 14 and earlier versions across various devices with v6.1.3.

Error:

Attempt to invoke virtual method 'void com.zoontek.rnbootsplash.RNBootSplashDialog.show(java.lang.Runnable)' on a null object reference

Stack trace:

java.lang.NullPointerException: Attempt to invoke virtual method 'void com.zoontek.rnbootsplash.RNBootSplashDialog.show(java.lang.Runnable)' on a null object reference at com.zoontek.rnbootsplash.RNBootSplashModuleImpl$3.run(RNBootSplashModuleImpl.java:130) at android.os.Handler.handleCallback(Handler.java:958) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:230) at android.os.Looper.loop(Looper.java:319) at android.app.ActivityThread.main(ActivityThread.java:9063) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:588) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

This seems similar to https://github.com/zoontek/react-native-bootsplash/issues/601

Library version

6.1.3

Environment info

"react-native": "0.73.8"

Steps to reproduce

I am not able to reproduce this, but I can see it is affecting our users via Sentry crash reports

Reproducible sample code

-

[zoontek]

@kf94 Are you using fade: true? Do you have users that report an actual issue or does this only happen when the user kills the app at launch?

[kf94]

Yes, I'm using fade: true. I haven't received any reports from users, only seeing it in Sentry. The crash doesn't seem to occur consistently or after a specific session length.

[zoontek]

Try switching to useHideAnimation with a simple animation on the opacity and see if something change.

[kf94]

I appreciate the suggestion, but it will take some time before I can validate its effectiveness. Could you provide more details on why this approach should mitigate the issue?

[zoontek]

@kf94 Because fading relies on a hack on Android, where it creates a new instance of Dialog (as we cannot set window animations after its creation).

[kf94]

ok, thanks.

[zoontek]

I migrated the Android codebase to Kotlin, and don't perform nullability casts, we should be good now.