Filed: FB23052931 (Feedback Assistant, 2026-06-10) + Apple Dev Support Case 102913469272.
Question for the community: Has anyone else hit this and resolved it?
TestFlight beta feedback (screenshot submissions) for one of our apps stopped being recorded in App Store Connect at 2026-05-31 17:15:54 UTC. Testers submit screenshot + comment via TestFlight "Send Beta Feedback" — the dialog completes successfully and dismisses with no error — but submissions never appear in the ASC web UI under TestFlight / Feedback / Screenshots or in the App Store Connect API endpoint GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions.
meta.paging.total has been frozen at 882 for 10+ days. Verified live by submitting two screenshots from a current TF build today and confirming the API total did not increment seconds later.
The betaFeedbackCrashSubmissions endpoint is also stale on this app (last entry 2026-05-03), which makes me think it's the whole beta feedback ingestion pipeline for this app record, not screenshot-specific.
Minimal repro: 1) Install a current TestFlight build (any from a current train, processed VALID, internalBuildState IN_BETA_TESTING, delivered to a tester group). 2) Take a screenshot inside the app. 3) From the share sheet, tap "Share Beta Feedback". 4) Add a comment, tap Submit. Dialog completes successfully. 5) Query the App Store Connect API: GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions?limit=200. meta.paging.total is unchanged. data[0].attributes.createdDate is unchanged.
Developer-side causes I've already ruled out:
- Build processing: all 10 most-recent builds are VALID with internalBuildState IN_BETA_TESTING and were delivered to both internal and external tester groups.
- Per-group Tester Feedback toggle: verified ON for both groups in the ASC UI.
- App entitlements / Info.plist: no changes in the 30 days prior to the cutoff.
- Tester membership: verified active. The tester used in the repro is Account Holder on the team.
- ASC API key: the same key successfully retrieves the 882 historical submissions. Read auth is intact; only writes from the device side fail to land.
- App Privacy: configured and submitted.
What I've already filed:
- Feedback Assistant: FB23052931 (filed 2026-06-10, Area: App Store Connect, Incorrect/Unexpected Behavior)
- Apple Developer Support (Distribution / TestFlight email channel): Case 102913469272 (filed 2026-06-10, cross-references FB23052931)
What I'd love to hear from the community:
- Have you seen this exact pattern (sharp cutoff date, total frozen, no error on submission)?
- Did it eventually resolve on Apple's side, and if so what was the rough turnaround?
- Is there anything you tried on the developer side that actually re-enabled ingestion (re-promoting a build to groups, regenerating an ASC API key, anything)?
- Anyone on a thread where an Apple Frameworks Engineer responded to this class of bug?
I'm aware of older threads going back to 2019 (thread 122295) with similar symptoms but no Apple engineer response. Hoping to surface a more recent path forward.
Thanks.