TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer

We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect.

Observed product metadata: build 1.0 (4)

On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation:

Storefront.current.countryCode = CHN
Product.priceFormatStyle.currencyCode = USD
Product.price = 0.99
Product.displayPrice = US$0.99
Product.subscription.introductoryOffer = nil
Product.subscription.isEligibleForIntroOffer = true

The product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI.

For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed.

Subsequent replacement product: build 1.0 (5)

The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group.

The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values.

Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause.

Relevant implementation path

The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here:

// Product loading:
let values = try await Product.products(for: [id])
guard values.count == 1, let product = values.first,
      product.id == id else {
    throw SubscriptionClientError.invalidProduct
}
products[id] = product
// The UI model copies product.displayPrice directly.

// Later, in the purchase method:
guard let product = products[productID] else {
    throw SubscriptionClientError.unavailable
}
return try resolvePurchase(try await product.purchase(confirmIn: scene))

Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture.

What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.

Update — November 13, 2026

We have now independently checked the connected iPad and confirmed that the installed TestFlight app is 1.0 (5), using the replacement subscription product. A fresh, narrowly scoped observation for that product returned:

Storefront.current.countryCode = CHN
Product.priceFormatStyle.currencyCode = USD
Product.price = 0.99
Product.displayPrice = US$0.99
Product.subscription.introductoryOffer = nil
Product.subscription.isEligibleForIntroOffer = true

The configured and returned product identifiers matched. The two diagnostic lines were paired by process and load sequence. Product and Storefront were read sequentially, not as an atomic snapshot. The tester reported that the App page still displayed US$0.99/month. We did not reopen or capture the Apple purchase sheet during this observation; its previously reported correct CNY price and trial remain separate evidence.

A fresh App Store Connect readback showed China-mainland-only availability, a current CNY 6.80 monthly price, and an active two-week free trial with no end date. The paid-apps agreement was active. We have not established a propagation, account-environment, or platform root cause.

Code review also identified a possible application-side race between the displayed product snapshot and a mutable purchase cache, plus a foreground product-refresh gap. We have addressed and unit-tested those locally, but the changes are not installed in this TestFlight build. We have no device trace proving that race occurred, and it does not explain how the raw Product already contains USD 0.99 and no offer. We are not claiming that the local fixes resolve this discrepancy.

Would a sequential, read-only comparison of StoreKit 2 Product.products(for:) and SKProductsRequest, using the same App identity and product with storefront readings before and after each request, be useful? SKProductsRequest is deprecated; we would use it only as a diagnostic control, not as a pricing or purchase fallback. Please advise if a different targeted diagnostic is preferable. No purchase, restore, receipt, or account data is included in this update.

A further controlled comparison is complete. Four observations:

  1. A fresh read-only App Store Connect check confirmed the same monthly product, Ready to Submit, with China mainland as the only selected territory. Current pricing for new subscribers showed CNY 6.80 and two weeks free, one introductory offer, and zero upcoming changes. No settings were changed.
  2. In an internal TestFlight build using the registered app identity, an explicit diagnostic entry ran before constructing the normal app environment or application product cache. One SK2 request followed by one SK1 request returned the matching product with USD 0.99, a one-month period, and no introductory offer in either API. There were no reported request errors.
  3. Four surrounding SK2 storefront reads all reported CHN/CNY. SK1's storefront was initially unavailable, then reported CHN in the remaining three samples. These are sequential observations, not an atomic snapshot.
  4. Earlier, the tester reported that Apple's purchase sheet showed two weeks free followed by CNY 6.80/month. No purchase sheet was opened in this latest run; eligibility, actual charges, and the cause remain unverified.

Two questions:

  • Which smallest supported diagnostic would distinguish a product-catalog/context issue from an application or configuration error here, and does the initially missing SK1 storefront materially change the interpretation?
  • Our small standalone probe has not reproduced this under an independent Bundle ID. What supported identity/signing setup should a minimal reproduction use to access the existing product catalog, or would the probe sources plus a report from the registered-identity shell be sufficient for code-level investigation?

Please file a Feedback report using Feedback Assistant, then post the ID here.