[in_app_purchase] Use StoreKit 2 APIs

[bahadirarslan]

As you are aware Apple updated StoreKit and released StoreKit 2 last year which includes bunches of new features and some changes especially it uses JWT tokens so there is no need to make another call to Apple to verify receipts.

I searched issues, PR's about Store Kit 2 but couldn't see anything so I wanted to ask is there are any plans about using StoreKit 2?

[darshankawar]

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

[jmagman]

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]

@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.

[LegendAF]

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.

[jmagman]

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.

[dodatw]

@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.

[jmagman]

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!

[jmagman]

To give an update to #116383 (comment), the work to migrate to pigeon is complete.

We were missing test coverage validating we don't cause regressions with this migration, and the unit test backfilling is complete. We're working on adding black box UI tests, though there have been some issues with the .storekit config file.

The Objective-C --> Swift migration has just begun #119106. Once that is complete, the StoreKit2 APIs can be adopted.

We don't have a schedule, but this is being actively worked on.

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!

[SpajicM]

Hey, any updates?

It's being worked on:
flutter/packages#6561