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

Android IterableApi.inAppConsume null pointer exception #547

Open
dwxw opened this issue May 1, 2024 · 1 comment · Fixed by Iterable/iterable-android-sdk#738
Open

Comments

@dwxw
Copy link

dwxw commented May 1, 2024

We're seeing a significant number of crashes from our Android users, Firebase reports:

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.iterable.iterableapi.IterableInAppMessage.getMessageId()' on a null object reference
       at com.iterable.iterableapi.IterableApiClient.inAppConsume(IterableApiClient.java:325)
       at com.iterable.iterableapi.IterableApi.inAppConsume(IterableApi.java:778)
       at com.iterable.reactnative.RNIterableAPIModule.inAppConsume(RNIterableAPIModule.java:390)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
       at com.facebook.jni.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:958)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
       at android.os.Looper.loopOnce(Looper.java:230)
       at android.os.Looper.loop(Looper.java:319)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
       at java.lang.Thread.run(Thread.java:1012)

We're using the latest react-native-sdk (1.3.17) with RN 0.72.

Any suggestions? Thanks.

@jena-chakour
Copy link

Hey @dwxw thanks for sharing this. After reviewing the log above, I think we can better assist via a support ticket (please feel free to open one at https://support.iterable.com/!); can you please share the device details from the user reports? Ex. always seeing this on Android 12+ etc.

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

Successfully merging a pull request may close this issue.

2 participants