Xcode 27.2 beta resolves three StoreKit testing problems that could make subscription and purchase tests behave differently from their configuration. The fixes cover introductory-offer eligibility, storefront changes, and error dialogs that appeared even when a test session asked Xcode to suppress them.
Apple lists the changes in its Xcode 27.2 beta release notes. They apply to StoreKit Testing in Xcode, which lets developers exercise in-app purchase behavior with local configurations and the SKTestSession API before using a live App Store environment.
What Xcode 27.2 fixes
- Calling
SKTestSession.clearTransactions()now resets introductory-offer eligibility immediately. - Changing a test session’s storefront or locale now propagates through
Storefront.updates. - Failed test purchases no longer show error dialogs when
dialogsDisabledis set to true.
Each correction removes a source of misleading test results. A stale introductory-offer state can make a new-customer flow difficult to repeat, while an unreported storefront change can hide regional behavior. Unexpected dialogs can also interfere with automated tests that deliberately simulate failed purchases.
Don’t miss the best of The Mac Observer
Set us as a preferred source and our Apple reporting ranks higher in your Google Search results and Discover feed — one tap, no account changes.
One subscription bundle issue remains
Apple also documents a remaining known issue. When a developer makes an in-app test purchase for a subscription that belongs to a subscription bundle, the test environment may incorrectly allow the user to unbundle it instead of throwing an error. Apple provides no workaround in the notes.
These entries describe the Xcode test environment, not a confirmed change to purchases made by customers through the App Store. Developers should rerun affected test cases after installing Xcode 27.2 beta, but they should not treat a passing local test as the only validation required for billing logic.
Apple’s broader 2027 SDK submission deadline gives development teams another reason to validate projects with the new toolchain. Xcode 27.2 remains beta software, so production teams should keep reproducible test configurations and compare results with a stable Xcode release where practical.
Discussion