Hello,
We are trying to back up App Store Connect Analytics data before an app transfer, and we are seeing two different problems with ONE_TIME_SNAPSHOT requests.
Apps
- com.estmob.paprika (App ID: 596642855)
- com.estmob.ios.sendy.app (App ID: 1489041568)
Issue 1: Paprika snapshot exists, but no instances or segments are ever generated
Current snapshot request:
- Request ID: 4a40d802-5cd4-4bb2-ad53-8539f43c9ce2
What we see:
- GET /v1/analyticsReportRequests/4a40d802-5cd4-4bb2-ad53-8539f43c9ce2 returns 200
- The request has a reports relationship
- GET /v1/analyticsReportRequests/{id}/reports returns 127 analyticsReports
- However, for all of those reports, GET /v1/analyticsReports/{reportId}/instances returns no instances
- Therefore there are still no segments and no downloadable raw files
As of May 26, 2026, the state is still:
- reports: 127
- reportsWithInstances: 0
- instances: 0
- segments: 0
Issue 2: Sendy snapshot was deleted, but creating a new snapshot still fails with 409
Previous snapshot request:
- Request ID: d40503ae-7a75-4d88-a8a6-115456c333cc
Current state:
- GET /v1/analyticsReportRequests/d40503ae-7a75-4d88-a8a6-115456c333cc now returns 404
- Listing analyticsReportRequests for the app shows no visible ONE_TIME_SNAPSHOT request
- Only the ONGOING request is visible
However, creating a new ONE_TIME_SNAPSHOT still fails with:
- 409 STATE_ERROR
- "You already have such an entity"
We also found this forum thread, which seems related:
Questions
- For Paprika, does this mean the ONE_TIME_SNAPSHOT is still processing, or is it stuck?
- For Sendy, is this expected behavior due to a cooldown / retention rule after deleting a snapshot request?
- If Sendy is blocked by backend state, how long should we wait before a new ONE_TIME_SNAPSHOT can be created?
- Is there anything else we should check to determine whether the Paprika snapshot will eventually produce instances and segments?
This is currently blocking our analytics backup for app transfer. If needed, I can provide additional request/response details.
Thank you.