Provisioning profile expired
Check PB-23 · App Store Review Guideline provisioning · Likely rejection when present · verified 2026-09-16
Why App Review rejects under Provisioning & signing
Signing problems are rejected by the upload pipeline or by App Store Connect processing, not by a human, and the messages are terse. The usual causes: a development or ad-hoc profile in a build meant for the store (get-task-allow = true), an expired profile, a push entitlement without the matching background mode, or a capability entitlement the app never uses. All of it sits in embedded.mobileprovision inside the .ipa.
How to fix it
Create a new provisioning profile in Xcode, re-sign and rebuild. Expo/EAS: run eas build again — EAS renews credentials automatically.
How RejectProof detects it
The scan reads your .ipa in the browser (or locally with npx rejectproof): Info.plist, entitlements, the privacy manifest, embedded frameworks and the executable itself. Check PB-23 reports the exact evidence it found — the key, the symbol, the file or the URL — so you can confirm it in your own project before changing anything. Nothing is uploaded; only a small redacted summary is sent to build the report, and you see it first.