In Firebase Analytics, when passing parameters to logPurchase, the signature allows for nullable values (Map<String, Object?>?). However, down the line, there is a method called _assertParameterTypesAreCorrect that asserts value types but ignored null values, creating a runtime issue.
More details in #12790
Related Issues
Fixes #12790
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.
[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
Description
In Firebase Analytics, when passing
parameterstologPurchase, the signature allows for nullable values (Map<String, Object?>?). However, down the line, there is a method called_assertParameterTypesAreCorrectthat asserts value types but ignorednullvalues, creating a runtime issue.More details in #12790
Related Issues
Fixes #12790
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process. Updating thepubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?