“sandbox”

Thanks for the clear write-up. Your reading is correct. As of macOS 26, SwiftUI's file modifiers are fileImporter (open, returns URLs), fileExporter (writes a document or Transferable item you supply), and fileMover (moves an existing file). None of them return a bare destination URL the way NSSavePanel does, so there is no SwiftUI equivalent for choosing a save location and getting a URL back. Presenting .fileExporter with an empty placeholder document only to read its URL writes an empty file and works against how the modifier operates, so it is not a substitute. NSSavePanel is the supported way to get that destination URL, and using it from a SwiftUI app is a normal use of AppKit, not a workaround. You present it from your SwiftUI action, read panel.url, and pass that URL to your database. Since you create the file at that location, the sandbox behavior is relevant: the NSSavePanel documentation notes that when someone saves through the panel, macOS adds the chosen file to your app's sandbox

Thanks for the reply — by checks I just meant the standard troubleshooting/verification steps 🙂 Environment: iPhone: iOS 26.5 Xcode 26.5 (17F42), macOS 26.5.1 Flutter 3.44.2 — the app uses firebase_messaging for push. Core issue: a direct FCM test message (Firebase Console → Send test message) to a valid registration token from the device delivers nothing (app killed, lock screen, notification permission fully ON). Verified correct: TestFlight build with aps-environment=production; GoogleService-Info.plist matches the Firebase iOS app (project la-french, sender 649219813428); valid FCM token; APNs Auth Key in Firebase with correct Key ID + Team ID — tried two keys (one Production, one Sandbox & Production), neither delivers. Bundle com.thomasmanfredini.lafrench, Team 7TWV3839F3. Since even a direct FCM test fails with a valid token and correct config, what could prevent APNs from delivering to this app/account? What should I check next? Many thanks for your support> Thomas

Hello - I can confirm that all three of your In-App Purchase subscription products should be available for testing in Sandbox, after successfully loading them through two internal tools available within Apple. For further assistance from Apple, I recommend submitting a new report via the Feedback Assistant. Ideally your submission will include a Sysdiagnose log that captures what happens in your app when trying to load the IAP products. Once you have filed through Feedback Assistant, you can reply to this thread with the ticket/case number assigned by Feedback Assistant and we can follow-up further on our side. Thank you.

Hello, Thank you for pointing me to TN3186. I have reviewed every item. Summary: App: Vytal AI Bundle ID: com.ciborgu.vytalai ASC App ID: 6767160542 Team ID: JZF7CR3W8Z Test environment: TestFlight (build 115, version 1.1.0) Platform: Capacitor + RevenueCat Purchases SDK (@revenuecat/purchases-capacitor) Subscription Product IDs (auto-renewable, subscription group Vytal AI): vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro TN3186 checklist: ✓ Bundle ID matches ASC app record ✓ Explicit App ID (not wildcard) ✓ In-App Purchase capability enabled on App ID ✓ App signed with valid distribution profile via EAS ✓ Active Apple Developer membership ✓ Paid Apps Agreement: Active ✓ Banking and tax: complete ✓ Price and localizations on all 3 subscriptions ✓ No StoreKit Configuration file in project Issue: When calling StoreKit via RevenueCat on a physical iPhone (TestFlight), Product.products / getProducts returns ZERO products for all 3 identifiers. Purchase sheet never appears. In-app diagn

Hello - TestFlight uses the Sandbox environment when testing In-App Purchases. To troubleshoot issues with IAP products in a TestFlight build, please refer to this TechNote and review all of the topics covered to ensure your app and IAP products are correctly configured and ready for testing. If you have addressed everything in the TechNote and are still having problems, please reply again to this thread with any additional details and we will be happy to try and assist further. Thank you.

Hello - TestFlight uses the Sandbox environment when testing In-App Purchases. To troubleshoot issues with IAP products in a TestFlight build, please refer to this TechNote and review all of the topics covered to ensure your app and IAP products are correctly configured and ready for testing. As noted on the linked page, all banking and tax information must be complete. If you have addressed everything in the TechNote and are still having problems, please reply again to this thread with any additional details and we will be happy to try and assist further. Thank you.