-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[in_app_purchase] Enable -Werror for Android #3403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Overriding version/changelog: the non-test-file changes are exclusively:
both of which are dev-only changes, thus exempt by policy even though the tooling can't detect that. |
| private HashMap<String, SkuDetails> cachedSkus = new HashMap<>(); | ||
| // TODO(stuartmorgan): Migrate this code. See TODO on querySkuDetailsAsync. | ||
| @SuppressWarnings("deprecation") | ||
| private HashMap<String, com.android.billingclient.api.SkuDetails> cachedSkus = new HashMap<>(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having to inline namespaces everywhere is the most annoying part of the change, but having -Werror is more important IMO. And all of this will go away when the code is migrated to v5.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v5 of what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v5 of the Google Play Billing Library, which this plugin wraps.
[in_app_purchase] Enable -Werror for Android
Enables the
-Werrorflag on the Java compilation step, fixing and suppressing the existing issues.Unlike most other packages where we've enabled this, this consists almost entirely of sweeping suppressions (specifically,
deprecation), since the package was updated to the v5 billing library but still uses many APIs from v4 that are deprecated in v5. While this is more suppression than we would normally want to do, it still sets us up to catch other kinds of warnings going forward. It may also help when the full migration to v5 API is done, since just removing the deprecation suppressions will make it easy to find all of the code than needs to be updated. Given that, I believe this is still a net improvement over having-Werroroff.Part of flutter/flutter#91868
Pre-launch Checklist
dart format.)[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style.///).