[camera, google_sign_in, espresso] Bump guava to version 33.3.1
.
#7773
+18
−6
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 flutter/flutter#155458
Fixes flutter/flutter#154586
Bumps Guava to
33.3.1
, as from what I can tell we were essentially hitting google/guava#7397, from a comment on the issue:I believe this maintainers suspicions were warranted, as it seems AGP was complaining in our case!
That issue was fixed in version
33.3.1
of Guava. Verified that I could re-create the failure in the first issue, and then verified that it was fixed with no additional proguard rules by upgrading the Guava version used by thegoogle_sign_in
plugin. Decided to make the upgrade everywhere we use guava, so we don't hit it in another plugin later.Pre-launch Checklist
dart format
.)[shared_preferences]
pubspec.yaml
with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.md
to add a description of the change, following repository CHANGELOG style, or this PR is exempt from CHANGELOG changes.///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.