4.3.1 - Android 12 crash on RN 0.68.1 (java.lang.NullPointerException)

[jonesaustindev]

Hello! Right now I am getting the error below on Android 12 with RN 0.68.1 using 4.3.1 of this library

com.wix.reactnativenotifications.core.notification.PushNotificationProps.asBundle
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.os.Bundle.clone()' on a null object reference

com.wix.reactnativenotifications.core.notification.PushNotificationProps.asBundle PushNotificationProps.java:26
com.wix.reactnativenotifications.core.notification.PushNotification.notifyOpenedToJS PushNotification.java:210
com.wix.reactnativenotifications.core.notification.PushNotification.dispatchImmediately PushNotification.java:127
com.wix.reactnativenotifications.core.notification.PushNotification$1.onAppVisible PushNotification.java:36

Seems to be the same as seen in #835

[jonesaustindev]

Does there happen to be any info or movement made around this issue?

[KimJeonghun91]

I am also it. It happened When I clicked the android notification alert.

[gabrielbezerra81]

Same behavior here, I cant open push notifications in background. This is blocking us from bumping compileSdkVersion to 31.

[walterholohan]

I just got this error from a user too. Users device info below and it was using version 4.2.4

[simona-iuliana]

same error with RN 0.68.2 using 4.3.1 of this library, any updates on this?

[pepf]

Try https://github.com/wix/react-native-notifications/issues/835#issuecomment-1152155685 :)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jonesaustindev]

Not stale, still very much an issue on the latest version 4.3.1

[jonesaustindev]

@DanielEliraz would you or someone else have a clue on this one by chance?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[pepf]

Please keep this issue open 🙏🏼

On Thu, Aug 11, 2022, 17:34 stale[bot] @.***> wrote:

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

— Reply to this email directly, view it on GitHub https://github.com/wix/react-native-notifications/issues/864#issuecomment-1212153843, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJU6G4KROQKLJ4DN46T2FDVYUMRBANCNFSM5USXXHNQ . You are receiving this because you commented.Message ID: @.***>

[PROda221]

I am facing the same issue

[ernstmul]

Yep, also facing this issue!

[gabrielbezerra81]

anyone tried another alternative? I tried notifee but couldn't make it work.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[walterholohan]

@gabrielbezerra81 what issue did you have with Notifee, i migrated our app over to use a combination of notifee and firebase messaging. Both libraries are maintained by the same company

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale[bot]]

The issue has been closed for inactivity.