-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[in_app_purchase_storekit] Make Storekit 2 the default #9178
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
I saw you requested review but it's still "Draft" mode. is it ready to review? |
@@ -1,3 +1,7 @@ | |||
## 0.3.23 | |||
|
|||
* **BREAKING CHANGE:** StoreKit 2 is now the default for all devices that support it. |
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.
should this be 0.4.0
instead? iirc breaking change should be major bump, but this is still 0.
version, so a minor bump?
(cc @stuartmorgan-g for advice)
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.
Yes, breaking changes need a "major" (which for pre-1.0 is the second number, per Dart convention) version bump.
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.
ooh makes sense. Ive changed it.
Now it is! Just had to make sure the tests were passing |
...ages/in_app_purchase/in_app_purchase_storekit/lib/src/in_app_purchase_storekit_platform.dart
Outdated
Show resolved
Hide resolved
} | ||
|
||
/// Call this before `registerPlatform` to re-enable StoreKit1 | ||
static bool enableStoreKit1() { |
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.
should we also deprecate this with a message that storekit 1 will be removed in the future (if that's the plan).
Was this intended to be split into two separate PRs? The changelog says "Updates |
flutter/packages@6a28ad9...2e166de 2025-05-12 louisehsu@google.com [in_app_purchase_storekit] Make Storekit 2 the default (flutter/packages#9178) 2025-05-12 engine-flutter-autoroll@skia.org Roll Flutter from 992ad74 to 54de32d (7 revisions) (flutter/packages#9243) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
I might be misunderstanding? I thought I updated the pubspec to 0.4.0 here https://github.com/flutter/packages/pull/9178/files#diff-0c8b2973edeea37bde2da4d9d3c56b3754745fcf2bb2462dde0ac17d37b2343d |
This PR created version 0.4.0 of I would expect a release of |
ohhhhhhhh. 🤦♀️ so sorry, let me open a seperate pr for that. |
Make Storekit 2 the default. Fixes flutter/flutter#159871 ## Pre-Review Checklist
Make Storekit 2 the default. Fixes flutter/flutter#159871 ## Pre-Review Checklist
Make Storekit 2 the default. Fixes flutter/flutter#159871
Pre-Review Checklist
[shared_preferences]
pubspec.yaml
with an appropriate new version according to the [pub versioning philosophy], or I have commented below to indicate which [version change exemption] this PR falls under[^1].CHANGELOG.md
to add a description of the change, [following repository CHANGELOG style], or I have commented below to indicate which [CHANGELOG exemption] this PR falls under[^1].///
).