Hello, I’m encountering a persistent code-signing verification failure when installing a development build on a registered physical iPhone. The project builds and signs successfully in Xcode, and the .app is transferred to the device. However, the installation fails when installd verifies the app’s signature. The relevant error is: Failed to verify code signature of Runner.app: 0xe8008018 The identity used to sign the executable is no longer valid.
Domain: MIInstallerErrorDomain Code: 13 LegacyErrorString: ApplicationVerificationFailed
Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: The app cannot be installed because its integrity could not be verified. Environment macOS: 26.6.2 (25G83) Xcode: 27.0 (27A266a) iOS: 26.6.2 (23G90) Device: iPhone15,4 Architecture: arm64 Installation method: Xcode Run on a registered physical device Signing type: Apple Development Provisioning: Development provisioning profile Important account history Our Apple Developer Program account was previously suspended and was later reinstated by Apple. Apple Developer Support has checked the account and stated that the membership account currently appears normal. However, development builds signed by this Team are still rejected by the device with 0xe8008018. This makes us suspect that the membership itself was restored, but some signing-related backend state may not have been fully restored or propagated, such as:
- Development certificate trust or revocation state
- Registered-device installation authorization
- Provisioning-profile validity
- A restriction or risk flag associated with the previous suspension
- Synchronization between the Developer account system and Apple’s device-side certificate trust services
What I have verified
- The Apple Developer Program membership is active.
- The physical iPhone is registered with the Developer Team.
- The Bundle ID matches the provisioning profile.
- The build uses an Apple Development certificate and a development provisioning profile.
- The application builds successfully.
- Xcode completes the signing phase successfully.
- The resulting app contains an embedded provisioning profile.
- The app is successfully transferred to the device.
- The failure occurs during device-side signature verification, not during compilation or transfer.
- Cleaning and rebuilding the project produces the same result.
- The original missing-product-path issue has been resolved; Xcode is now installing the correct Runner.app.
I have also reviewed Apple’s certificate documentation and discussions involving the same 0xe8008018 error. Some developers report that the same device accepts an app signed with another Apple ID or Team while rejecting builds signed by the affected paid Developer Team. I also found reports involving Sideloadly where forcing a different installation mode once and then returning to Apple ID signing caused the signing flow to recover. That exact workaround is not applicable here because this is a normal Xcode development build, not third-party IPA sideloading. However, it suggests that refreshing signing state on Apple’s side may affect the result. Questions
- Can a Developer Program membership appear active while the Team’s development certificates are still treated as revoked or invalid by device-side trust services?
- After a previously suspended account is reinstated, is there a separate process for restoring or resynchronizing development-signing privileges?
- Is there a way to determine whether this Team still has a backend restriction or stale certificate-revocation state?
- Has anyone resolved this without switching to a different Apple ID or Developer Team?
- What diagnostic files would be most useful for confirming whether this is a Team-level backend issue?
Apple Developer Support case reference: 102975363424. I can provide an .xcresult, signed IPA, embedded provisioning profile, certificate details, and complete installation logs privately if requested. Thank you.