Treating this as a potential proposal and for team's tracking.

We have a design doc for this that, currently blocked on in_app_purchase plugin migrating to Swift.

See also https://flutter.dev/go/ios-plugins-swift-migration and comment in that doc.

@cyanglaz I don't see an open GitHub issue tracking this work, are you aware of one?

@cyanglaz I don't see an open GitHub issue tracking this work, are you aware of one?

No, I think we can use this one.

Where exactly is the starting point to get the ball rolling on supporting StoreKit 2? How can the community help? It has been 2 years and supporting subscriptions with in_app_purchase is more painful than it should be.

We definitely hear you that this is still really painful to use and that it has been for a few years.

There are three pieces to this:

• Migrate the plugin from Objective-C to Swift as the StoreKit2 APIs are Swift-only. That work is tracked in [in_app_purchase] iOS Swift migration #119106. We recently turned on swift-format in our CI to make these plugin migrations a little less fraught (note this StoreKit work wasn't blocked on that, just mentioning it 🙂 ). This work is planned for the near future.
• Migrate this plugin to pigeon so we're not passing type-unsafe maps around. This isn't strictly required, but the Objective-C -> Swift migration will be so much easier when this work is done as we'll be dealing with strongly typed classes, and we'll be able to more easily validate and test behavior isn't regressed. This work is being done in [in_app_purchase] Convert to Pigeon #117910 and this is actively being worked on [in_app_purchase] Convert storefront(), transactions(), canMakePayment(), and addPayment() to pigeon packages#5910 (part 1) Convert startProductRequest(), finishTransaction(), restoreTransactions(), presentCodeRedemptionSheet() to pigeon packages#6032 (part 2) [in_app_purchase] Convert refreshReceipt(), startObservingPaymentQueue(), stopObservingPaymentQueue(), registerPaymentQueueDelegate(), removePaymentQueueDelegate(), showPriceConsentIfNeeded() to Pigeon packages#6165 (part 3) as we decided to do this before the Swift migration. Due to the nested complexity of the objects we receive from Apple's APIs, this was one of the most challenging plugins to migrate to pigeon.
• Swap the APIs from StoreKit to StoreKit2. This may be done as part of the Swift migration (harder to validate regressions), or we may do it as a separate step (which would cause the SK1 Swift code to be throw-away).

The community can help us by testing these incremental changes and filing issues so we can fix them asap.

@jmagman Thank your update.
Is there any schedule, roadmap for these task?
We are waiting long time. StoreKit2 can help us improve some payment issue. It is good for app developer.

I can't give you a schedule, but you can track our progress in #119106, #117910, and this issue. For example flutter/packages#5910 had updates 15 minutes ago.

We certainly know it is a good thing to do for app developers. 🙂 Further commenters please review Do not add "me too" or "same" or "is there an update" comments to bugs and When will my bug be fixed? in our wiki, let's keep comments focused on meaningful content. Thanks!

Really need the isEligibleForIntroOffer in StoreKit 2.

I really hope this feature can be implemented soon.

https://developer.apple.com/documentation/storekit/product/subscriptioninfo/3791958-iseligibleforintrooffer

flutter/packages#7473
Support for basic function product fetching and app store checking has been merged.
The next pr will be for purchasing and transactions.

It's actively being worked on, there's no need to comment that it's important.

This big one landed just last week:
flutter/packages#7887

As of these three PRs, the base in_app_purchase_storekit plugin has been updated to be able to use Storekit 2 APIs! Right now this is experimental and you can enable it by calling it enableStoreKit2(). You can try this out in the example project. With this base laid down, it should be much easier to add StoreKit2 functionality in the future, such as subscription management. Please be noted that Storekit2 is only available for devices running iOS 15 and above.

We encourage you to try it out and report any issues you encounter, or any important StoreKit 2 functionality that is important to you. I’ll add these to this umbrella issue as they come in. You guys are also welcome to tag me directly! We also love contributions, like this great PR to add the expiration date!

Once any major bugs have been ironed out, StoreKit 2 will be on by default for devices above iOS 15, while devices below will fall back to the original StoreKit API.

Thank you for your patience everyone! :)

This issue is assigned to @LouiseHsu but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

This issue is assigned to @LouiseHsu but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!