I’m trying to diagnose a StoreKit issue with an auto-renewable subscription in my iOS app. The subscription is called “Lighthouse Plus” and is $9.99/month. The app is currently being tested through TestFlight. When the user taps the Lighthouse Plus subscription button, the app begins the purchase process/loading state, but the Apple purchase sheet never appears. The UI then remains stuck loading indefinitely. This has continued across multiple TestFlight builds, including our current Build 11. What happens: Install/open the app through TestFlight. Sign into the app. Navigate to Lighthouse Plus. Tap the subscription/purchase button. The app enters a loading state. No Apple purchase confirmation sheet appears. The loading state never resolves. We have also been investigating Restore Purchases and Manage Subscription behavior as part of the same StoreKit implementation. The subscription product has been configured in App Store Connect and associated with the app. We have repeatedly tested new builds while trying to determine whether the failure is in our StoreKit implementation, product configuration, TestFlight sandbox environment, or communication with the App Store. The particularly difficult part is that we are not receiving a visible StoreKit error on the device — the purchase attempt appears to wait indefinitely rather than returning a clear success, cancellation, or failure. I do not currently have access to a Mac for direct Xcode/StoreKit Console debugging, so I am trying to determine the best way to diagnose exactly where this transaction is stopping from a TestFlight device. Questions: What would cause a StoreKit subscription purchase request to remain pending/loading without ever presenting Apple's purchase sheet? Is there a way to retrieve useful StoreKit/TestFlight transaction diagnostics without access to Xcode on a Mac? Are there specific App Store Connect subscription states/configuration issues that can cause this behavior without StoreKit returning an obvious error? What StoreKit transaction/product logging should we add to the app itself so the next TestFlight build can identify exactly where the request is failing? Should the purchase call have an explicit timeout/error path if StoreKit never returns? I can provide the product identifier, relevant StoreKit implementation/code, App Store Connect configuration screenshots, and additional diagnostics if needed. Any guidance on isolating whether this is an App Store configuration issue versus an implementation issue would be greatly appreciated.