Error 701 on upload looks alarming, but it is one of the most fixable problems in the whole submission flow. It is not a review rejection and it is not a problem with your code. It means the build you are uploading has a bundle identifier that does not match any app record in App Store Connect. Almost always, the record either does not exist yet or the identifier does not line up. Here is what it means and how to clear it.
Short answer
App Store Connect error 701, "no suitable application records were found," means the bundle identifier in your build does not match an app record in App Store Connect. The usual cause is that the app record was not created yet, or the bundle ID differs, including a case mismatch, from the registered App ID and the record. It is an upload-time configuration error, not a problem with your code or a review rejection. Fix it by creating the app in App Store Connect with the exact matching bundle ID, registering the App ID, and confirming your account has access, then re-upload.
What you should know
- It is an upload error: 701 happens before review, when the build cannot be matched to an app record.
- The bundle ID is the link: the build's identifier must match a record in App Store Connect.
- The record may not exist: forgetting to create the app is the most common cause on a new account.
- Case matters: the bundle ID must match exactly, including capitalization.
- It is not your code: nothing about the binary itself is wrong; the mismatch is in configuration.
What does error 701 actually mean?
It means the upload tool could not find an app in App Store Connect whose bundle identifier matches the build you sent. When you upload, App Store Connect looks for an app record tied to the build's bundle ID, and if none exists or none matches, it returns 701 with the message that no suitable application records were found and asks you to verify your bundle identifier. This is a lookup failure at upload time, well before any review, so it has nothing to do with your app's content, design, or quality. The fix is to make the record and the identifier agree. Because it is a lookup, the error is fully deterministic: the same build keeps failing until the record and the identifier match, and it succeeds the moment they do, which is why methodically checking each link beats re-uploading and hoping.
What are the common causes?
A short list covers nearly all of them. The table pairs each with its fix.
| Cause | Fix |
|---|---|
| No app record exists in App Store Connect | Create the app with the matching bundle ID |
| Bundle ID mismatch, including capitalization | Make the build's bundle ID match the record exactly |
| The App ID is not registered | Register the identifier in Certificates, Identifiers and Profiles |
| Your role lacks access | Use an account or role that can see and manage the app |
| Uploading to the wrong team or account | Upload to the team that owns the app record |
The first two account for most cases: a new app that was never created, or a bundle ID that does not line up character for character.
How do you fix it, step by step?
Make the record and the identifier match, then retry:
- Create the app in App Store Connect if it does not exist, using the exact bundle ID your build uses.
- Compare the bundle ID in your project against the app record and the registered App ID, and make them match exactly, including case.
- Register the App ID in Certificates, Identifiers and Profiles if it is missing.
- Confirm your account has access: a Developer-only role may not be able to see or create the app, so check your role and team. If you cannot create the app yourself, an Admin or Account Holder on the team may need to create the record or grant you access first.
- Re-upload, and if it fails once, try again or use Transporter, which often reschedules and succeeds on a retry a minute later.
Why does the bundle ID have to match exactly?
Because it is the only link between your build and its store record. App Store Connect identifies which app a build belongs to by its bundle identifier, so even a small difference, a changed prefix, an extra segment, or a difference in capitalization, breaks the match and produces 701. The identifier is case-sensitive, so com.Example.App and com.example.app are two different IDs as far as the lookup is concerned. Treat the bundle ID as a fixed key that must be identical in your project, your registered App ID, and your App Store Connect record.
What to watch out for
The first trap is a capitalization difference you cannot see at a glance, so copy the bundle ID rather than retyping it. The second is uploading under the wrong team when you belong to several, which makes the record genuinely absent from that account's view. The third is the propagation delay right after creating an app, where a retry a minute later succeeds. Error 701 is a configuration and account issue rather than a security finding, so it sits apart from a pre-submission scan; once the upload goes through, a scan such as PTKD.com (https://ptkd.com) reads the compiled binary against OWASP MASVS for the actual binary-level checks, which is a separate step from getting the build accepted.
What to take away
- Error 701 means your build's bundle ID does not match an app record in App Store Connect; it is an upload error, not a rejection.
- The most common causes are a missing app record and a bundle ID mismatch, including a difference in capitalization.
- Create the app with the exact bundle ID, register the App ID, confirm your account has access, and re-upload.
- The bundle ID is case-sensitive and must be identical across your project, App ID, and record; once uploaded, run a pre-submission scan such as PTKD.com for the binary checks.
