Blog'a Dön
BLOG

Fix EAS Submit and API Key Errors After an iOS App Transfer

19 Kasım 2026 6 dk okuma
Fix EAS Submit and API Key Errors After an iOS App Transfer

Fix EAS Submit and API Key Errors After an iOS App Transfer

Your transferred app appears in the receiving developer account, yet submission fails. Often the app is fine: the submission API key still belongs to the previous team. This guide provides a safe, verifiable troubleshooting sequence.

Why does submission fail after a successful app transfer?

An iOS app transfer moves the App Store record to a receiving developer organization, but it does not automatically migrate every API credential held by a build or submission service. A project may successfully compile while its submission integration still authenticates against the previous organization.

Treat the failure as an authorization and configuration investigation first. Do not change the app bundle identifier or create a duplicate store record simply because upload failed.

Understanding “application identifier was not found”

The message “App Store Connect app for application identifier ... was not found” can indicate that the credential used by the submission service cannot see the app in the intended organization. It does not, on its own, prove that the app is missing from App Store Connect.

If the error lists other applications accessible to the key but excludes the target app, inspect the owning team of the key before rebuilding the application.

App Store Connect app for application identifier 1234567890 was not found.
Verify that the App Store Connect API key has access to the application.

Five identifiers you must not confuse

The Bundle ID (such as com.example.parent) identifies the iOS package. The numeric Apple ID, used as ascAppId, identifies the App Store Connect app record. Apple Team ID identifies the developer organization. Key ID identifies an API key. Issuer ID identifies the App Store Connect organization for a team-scoped API key.

Team ID and Issuer ID are not interchangeable. A transfer does not call for changing the existing app’s Bundle ID or numeric App Store ID.

Step 1 — Verify the transferred app record

Select the receiving organization in App Store Connect. Open Apps → Your App → General → App Information. Compare the Bundle ID and numeric Apple ID with the app configuration and the ascAppId entry in eas.json.

If the transferred app appears in the recipient account, do not create a second app record with the same bundle identifier. The presence of an Identifier in the developer portal does not mean the submission API key has access.

Step 2 — Enable App Store Connect API access

Open Users and Access → Integrations → App Store Connect API. If the screen states “Only the Account Holder can request access,” the receiving organization’s Account Holder must request initial API access. After approval, an authorized person can manage Team Keys.

The same email address may hold roles in two developer organizations, but this does not grant one organization’s API key access to another organization’s applications.

Step 3 — Create a new API key in the receiving organization

Create a Team API key with a role suitable for the required upload operations. Retain its Key ID, Issuer ID, and private .p8 key securely. The private key download may only be offered once.

Team keys include an issuer identifier; individual keys have a different authentication structure. Do not commit .p8 credentials to source control, send them in support chats, or paste them into build logs.

Step 4 — Inspect the credentials associated with EAS

Run eas credentials --platform ios in the project and select the production build profile. Compare the Apple Team shown under App Store Connect API Key with the team shown for the Distribution Certificate and Provisioning Profile.

An old-team API key paired with new-team signing assets is a strong indication of mismatched submission credentials. Do not delete valid certificates simply to resolve an API access problem.

eas credentials --platform ios

Step 5 — Replace the project’s API key association safely

Open App Store Connect: Manage your API Key. Add the new key or select a correctly saved key, then verify that the project’s app integration uses it. The message “API Key already set up” reports the existence of a configuration, not whether it points to the correct organization.

If deletion fails because an API key is used by an App Store Connect App Integration, update or remove the integration association first. Never blindly delete an account-level key that other applications may still need.

Step 6 — Explicitly configure submission in eas.json

As a project-specific alternative, set ascApiKeyPath, ascApiKeyId, and ascApiKeyIssuerId under submit.production.ios. Use the existing app’s numeric ID for ascAppId and the recipient developer team for appleTeamId.

Preserve the remaining eas.json profiles and keep the .p8 file outside Git. The relative path must resolve in the environment where submission runs.

{
  "submit": {
    "production": {
      "ios": {
        "ascAppId": "1234567890",
        "appleTeamId": "RECIPIENT_TEAM_ID",
        "ascApiKeyPath": "./private-keys/AuthKey_EXAMPLE.p8",
        "ascApiKeyId": "NEW_KEY_ID",
        "ascApiKeyIssuerId": "NEW_ISSUER_ID"
      }
    }
  }
}

Step 7 — Validate signing and decide whether to rebuild

Apple requires new provisioning profiles in the receiving developer account after an app transfer. Confirm that the certificate and profile are valid, match the bundle identifier, and belong to the new team.

If only submission authentication was wrong, a valid existing build may be resubmitted. If its signing is no longer suitable for the receiving team, create a new production build using the recipient credentials.

eas build --platform ios --profile production
eas submit --platform ios --profile production --latest

Frequently asked questions

Is Key ID alone sufficient? No. A team API key also needs its issuer ID and private .p8 key. Does deleting an API key delete the app? No, but it can interrupt all integrations depending on that key.

Why is a new bundle ID missing from the menu? The identifier may not have been registered under the selected team. Register an Explicit App ID under Certificates, Identifiers & Profiles → Identifiers for a genuinely new app—not a transferred app.

Does a successful submission mean release? No. The build must still be processed and can subsequently proceed to TestFlight or review.

Final checklist for a safe transfer

Confirm the app exists in the recipient organization; Bundle ID and numeric Apple ID match; API access has been approved; the API key belongs to the recipient team; the project integration selects that key; distribution signing assets are correct; and the submitted build reaches processing in App Store Connect.

Following this sequence avoids unnecessary duplicate records, accidental credential revocation, and preventable deployment interruptions.