RUM-11716: Check for result of activity.intent#2877
Merged
0xnm merged 1 commit intoSep 16, 2025
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2877 +/- ##
===========================================
+ Coverage 70.49% 70.54% +0.05%
===========================================
Files 809 809
Lines 29482 29487 +5
Branches 5054 5056 +2
===========================================
+ Hits 20782 20799 +17
+ Misses 7275 7263 -12
Partials 1425 1425
🚀 New features to boost your workflow:
|
aleksandr-gringauz
approved these changes
Sep 16, 2025
0xnm
deleted the
nogorodnikov/rum-11716/check-for-activity.intent-result
branch
September 16, 2025 07:35
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.
What does this PR do?
There is the following SDK crash reported:
It is not a fault of SDK per se, and probably it is some very rare/weird situation, but we can add a guard by checking the result of
Activity.getIntent().Review checklist (to be filled by reviewers)