fix: app crash due to IllegalArgumentException in SearchFragment #1394
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.
Fixes: #1383
Changes:
does not exist in the bundle with which it is initialised in its 'fromBundle' method. Now a null value is passed and hence the crash
does not occur.
The code in SearchFragmentArgs that was throwing the exception is :
if (bundle.containsKey("@string/saved_date")) {
// code that inserts it in arguments, redacted for simplicity
} else {
throw new IllegalArgumentException("Required argument \"@string/saved_date\" is missing and
does not have an android:defaultValue");
}
After adding the
android:defaultValue="@null"
property to thenavigation.xml
file, this IllegalArgumentException statement appears to have gone from the generated fileScreenshots for the change: