Repository navigation
fix: skip setRead when the in-app message is no longer queued - #916
Merged
Merged
Conversation
Passing a missing message into the Android SDK crashes the app with a NullPointerException.
|
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
joaodordio
approved these changes
Oct 8, 2026
This was referenced Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Passing a missing message into the Android SDK crashes the app with a NullPointerException.
📝 Summary
Skips setRead if the message is null
🎟️ Jira Ticket: SDK-785
📖 Description
Updates RNIterableAPIModuleImpl to check for message (RNIterableInternal.getMessageById(messageId)) and skip setRead if null.
🧪 How to test?
QA apps
🧾 Changelog