Fixes Issue 6436: getString(...) must not be null #6474
Merged
+42
−10
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.
Description (required)
Fixes #6436
What changes did you make and why?
The
getString()
method was changed to allow returning a null value upon failure. This prevents the NPE.Then, usages of
getString()
were modified to handle potential null value returns. IfgetString()
returned null and a non null String was required, the empty string was used instead (this can be changed to throw an exception if needed).Tests performed (required)
Tested ProdDebug on Android Studio Emulator with API level 36.
Reproducing the original issue is tricky, but this is probably the simplest way:
On main, the issue will reproduce with an NPE. On this branch, there will be no crash.
If step 1 is skipped, the app may crash with #6464, but not #6436 according to the logs.