Filed as FB24069273.
Sandbox POST /inApps/v1/notifications/test consistently returns 404 {"errorCode":4040007} for our app (Apple ID 6765662617), although GET /v1/apps via the App Store Connect API confirms both subscriptionStatusUrl and subscriptionStatusUrlForSandbox are set (V2). With the same JWT, sandbox POST /inApps/v1/notifications/history returns 200 with an empty history — so the key and app resolve correctly. No organic sandbox notifications have ever been delivered, despite active TestFlight sandbox subscription activity.
Exhausted remediations (4040007 persists after each, with 30-60+ minute waits):
- Re-saving the URLs in the App Store Connect UI (two locales)
- Deleting and re-adding the Sandbox URL
- PATCH /v1/apps setting the sandbox URL + version V2 twice, with two different valid endpoints (verified by GET each time)
- Removing the Sandbox URL entirely to rely on the documented Production fallback
- Deleting BOTH URLs, waiting a full hour, and re-creating them from scratch
- Testing with both an App Store Connect team key and a freshly generated In-App Purchase key — identical results
Endpoints are publicly reachable (HTTPS, TLS 1.2+, port 443). Production App Store Server API returns 401, which we understand is expected for an app not yet released.
This looks like a desync between App Store Connect metadata and the notification delivery registry consulted by the test-notification endpoint. Any help would be appreciated.
