Skip to content
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

NullPointerException when using @oracle/react-native-pushiomanager on Android #72

Open
sorarco opened this issue Oct 22, 2024 · 1 comment

Comments

@sorarco
Copy link

sorarco commented Oct 22, 2024

Issue Description:
We are encountering a NullPointerException when using the @oracle/react-native-pushiomanager module, version ^6.52.2, in our React Native application. This issue is specific to Android devices and may potentially be related to in-app messages.

The error stack trace is as follows:
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.graphics.Bitmap.getWidth()' on a null object reference at com.pushio.manager.r0.F(SourceFile:1) at com.pushio.manager.c0.o(SourceFile:1) at com.pushio.manager.c0.e(SourceFile:1) at com.pushio.manager.c0$a$a.run(Unknown Source:9) at java.lang.Thread.run(Thread.java:1012)

The error seems to be occurring during the handling of a bitmap operation inside the PushIOManager.

Steps to Reproduce:
Install @oracle/react-native-pushiomanager version ^6.52.2.
Set up in-app messaging for the Android platform.
Trigger a push notification or an in-app message on an Android device.
Observe the crash with the aforementioned stack trace.
Expected Behavior:
The push notification or in-app message should be displayed without causing a crash.

Actual Behavior:
The app crashes with a NullPointerException when trying to access a Bitmap object during push or in-app message handling.

Affected Environment:
Library Version: @oracle/react-native-pushiomanager@^6.52.2
Platform: Android
React Native Version: 0.73.8
Device Information: Occurs across multiple Android devices.
Additional Information: We suspect that the issue might be related to handling in-app messages, but further investigation is needed to confirm this.

Please advise if there are any known fixes or workarounds for this issue.
Could this be related to improper bitmap handling in in-app messages?
Any guidance on this matter would be greatly appreciated.

Thank you!

@neerhaj
Copy link
Member

neerhaj commented Oct 23, 2024

@sorarco This issue has been addressed with the latest release - v7.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants