[Android][FirebaseAnalytics] Adds Null Params Handling to Firebase's logEvent #7897
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.
Why
The params parameter of
logEvent
is nullable but it was passed to theMapArguments constructor which expects a non-null map.
This caused a NPE when the Map’s keySet method is invoked.
How
The fix is to simply pass null to Firebase
logEvent
method as thatis handled as in no properties are being passed with the event.
Test Plan
Added an additional test case for logEvent to the test suite and observed it failing without the fix and passing after the change.