Hello,
I have been unable to install any development-signed app on any physical device for five months. Builds succeed, code signing passes locally, but every device rejects the app at install time with:
Failed to verify code signature of .../extracted/MyApp.app :
0xe8008018 (The identity used to sign the executable is no longer valid.)
ApplicationVerificationFailed
The app installs briefly, then iOS immediately removes it.
This started right after my account (Team ID MB4DXDTDMT) was reinstated following a duplicate-account flag. Background: I had a personal account that was converted to a business account (Wakeout LLC), then created a new personal account, which Apple flagged as a duplicate and later reinstated. The signing failure began immediately after that reinstatement.
Isolation already done (this is not a local-setup problem)
I have run the full isolation sequence — including every step DTS typically asks for — and the result points squarely at the account/team, not my machine:
- New blank Xcode project, automatic signing, new bundle ID → same
0xe8008018. - Brand-new macOS user account → same failure.
- Multiple Macs, fresh Xcode installs → same failure.
- Multiple iOS devices (iPhone 17 Pro, iPhone 15 Pro, others) → same failure.
- Different Apple ID / different developer team on the same Mac + same device → installs fine. This is the decisive one: the local environment is healthy; only Team
MB4DXDTDMTis rejected. - Xcode Cloud builds for this same team install fine. Apple's cloud signing trusts
MB4DXDTDMT; the device-verification backend does not. That gap can only exist server-side.
I have also: revoked/regenerated all certificates multiple times, deleted/recreated all provisioning profiles, cleared ~/Library/MobileDevice/Provisioning Profiles, cleared DerivedData and CoreDevice, removed device pairing records, re-paired devices, confirmed Developer Mode and correct system time. Simulators work. codesign --verify --deep --strict passes. Profile certificate SHA-1 matches the signing cert exactly. Entitlements match.
Why I'm posting here
This is the same failure documented in thread 755762, where Quinn concluded:
"this seems to be tied to your primary developer account and only DevPrograms has access to those details."
That matches my evidence exactly: the problem isolates cleanly to one team, and only DevPrograms can see the account-side state.
I've already gone through Developer Support on this — an open case has been with them for about five months without a resolution, which is what convinced me the fix isn't something I can reach from the support side. I'm posting here in case a DTS engineer can confirm the diagnosis and point me to the right path.
Question for any DTS engineer: given that the failure isolates to a single team — different teams sign and install fine on the same Mac and same device, and Xcode Cloud builds for this same team install fine — can you confirm this is an account-side signing-trust state that has to be reset by Apple, and what's the most direct way to get that reset actioned?
Happy to attach a sysdiagnose, full console output, or codesign -dvvv dumps on request.
Thank you.