We are seeing a consistently reproducible StoreKit Sandbox issue involving Apple’s refund request sheet.
Our app uses:
Transaction.beginRefundRequest(for:)
The refund sheet is successfully presented, but instead of loading the refund reason form, the Apple-provided sheet consistently displays:
“Cannot Connect”
This prevents the Sandbox refund request from being submitted.
Environment:
App: BTY Norebang Admin iOS: 26.6.1 Physical iPhone StoreKit environment: Sandbox Product type: Consumable Product: BTY Room – 1 Hour Development-signed build
We have confirmed:
Normal consumable purchase succeeds Transaction retrieval succeeds beginRefundRequest successfully presents Apple’s refund sheet App Store Server API calls succeed App Store Server Notifications V2 TEST delivery succeeds Get Test Notification Status reports sendAttemptResult = SUCCESS The problem persists after rebooting the device The problem persists after signing out and back into the Sandbox Apple Account Different network conditions have been tested The issue reproduces in an isolated Xcode/StoreKit test project with no BTY backend, authentication, or app networking dependency
Expected behavior:
The Sandbox refund request sheet should load the refund reason selection and allow the refund request to be submitted.
Actual behavior:
The Apple-provided refund sheet opens but displays “Cannot Connect.”
No refund is submitted and no App Store Server Notification V2 REFUND event is generated.
Feedback Assistant report:
FB24527792
The Feedback Assistant report includes sysdiagnose and relevant diagnostic logs.
This is currently the only remaining external blocker preventing us from completing full and prorated Sandbox refund end-to-end validation before enabling Production App Store Server Notifications.
Could an Apple StoreKit / App Store Commerce engineer confirm whether this is a known Sandbox issue or advise whether any additional configuration or diagnostic information is required?
We can provide a focused reproduction Xcode project, additional sysdiagnose logs, and Sandbox transaction details if needed.