There is no official time limit for an Apple Developer account investigation, and that is the hard part. Apple does not publish a service level for these reviews, so a case can take anywhere from a few days to several months, and a small number of accounts sit in limbo for six months or more. While the account is under investigation, Apple pauses review of everything you submit, so new apps and updates simply wait. The realistic move is to respond to Apple quickly, keep a single account, and document every message.
Short answer
An Apple Developer account investigation has no published deadline. Most cases resolve within a few days to a few weeks, but reviews involving the Developer Code of Conduct, fraud signals, or identity checks can run for months, and Apple pauses your app reviews the whole time. Apple notifies you in Resolution Center when it finishes, as part of the review process described in the App Store Review Guidelines. You cannot force a timeline, but you can respond fast and avoid the actions that extend it.
What "under investigation" actually means
"Under investigation" means Apple has flagged your Apple Developer Program account for a closer look and has paused review of your submissions until it finishes. This is an account-level hold, not a normal app rejection, which is why resubmitting a build does nothing. Apple's App Store Review Guidelines tie most of these holds to the Developer Code of Conduct in section 5.6, which covers honesty, account integrity, and manipulation. The guidelines are blunt about the stakes: if Apple decides you tried to cheat the system or manipulate ratings and discovery, the response "may include expelling you from the Apple Developer Program."
Two things follow from that. First, the hold is deliberate rather than a glitch, so waiting it out is part of the process. Second, the outcome is a real decision, which means the clarity and tone of your response, and the evidence you can provide, genuinely matter.
How long does it take?
Plan for days to weeks, and prepare for the possibility of months. Apple gives no guaranteed window, so any single figure is an average reported by other developers, not a promise. On the Apple Developer Forums, developers describe accounts held under investigation for weeks, and some report cases that dragged on much longer with little communication. The table below sets rough expectations by scenario.
| Scenario | Typical wait | What it usually means |
|---|---|---|
| Enrollment identity verification | Days to 2 weeks | Apple is confirming who you are before activating the account |
| App-level code of conduct review | Days to a few weeks | A submission triggered a closer policy look |
| Fraud or manipulation investigation | Weeks to months | Apple is examining ratings, installs, or account behavior |
| Account linked to a terminated one | Weeks to months, often ends in removal | Apple associates you with a previously banned account |
These ranges are directional, not guarantees. The same trigger can clear in three days for one developer and stall for two months for another, mostly depending on Apple's queue and how quickly you supply what it asks for. What shortens a case is a fast, complete response to Apple's requests. What lengthens it is missing information, a link to a flagged account, or anything that looks like an attempt to work around the hold.
Why did it happen?
Most investigations start from one of a handful of triggers, and none of them require you to be a bad actor. The common ones are a submission that reads as a Developer Code of Conduct issue under section 5.6, signals that look like rating or install manipulation (even from a paid growth service you hired), identity or payment details that do not match during enrollment, an app that resembles a known scam or copycat pattern, or a new account that Apple links to a previously terminated one. Apple's guidelines are explicit that trying to "trick the review process, steal user data, copy another developer's work, manipulate ratings or App Store discovery" leads to removal from the program.
The honest reality is that some flags are false positives. A sudden spike in downloads, a template-heavy app, or reused marketing assets can all look suspicious to an automated signal. That does not mean you are guilty, but it does mean you should be ready to explain your app, your data practices, and your traffic sources clearly.
Linked accounts deserve special mention, because they surprise developers who feel they did nothing wrong. Apple can associate a new account with an older one through payment details, device identifiers, or contact information, so if a previous account was ever terminated, the new one can inherit that history without a fresh violation. If you believe the connection is a mistake, say so plainly and provide the specific details that show the accounts are genuinely separate, rather than hoping the flag clears on its own.
Will resubmitting or a new build change anything?
No, because the hold sits on the account, not on a single submission. Uploading a new build, editing metadata, or resubmitting the same binary does not move an account investigation, and it can waste your daily submission slots. The review queue only resumes once Apple closes the case. The one exception is when Apple explicitly asks you to change something in Resolution Center: in that situation, follow the instructions exactly and reply there. Otherwise, leave your submissions in place, because extra uploads add noise without adding speed.
Can you appeal or speed it up?
You can appeal a decision, but you usually cannot speed up an active investigation. While Apple is still investigating, there is often nothing to appeal yet, because no decision has been issued. Once Apple posts an outcome in Resolution Center, you can respond there, and for guideline decisions you can escalate to the App Review Board through App Store Connect. Contacting Apple Developer Support is worth doing, but keep expectations realistic: developers on the Apple Developer Forums regularly describe appeals and support emails going unanswered for long stretches.
The most useful thing you can do is respond fast and completely whenever Apple asks for information. A calm, specific reply with the exact details requested moves a case faster than repeated follow-ups. Expedited requests exist for time-sensitive app reviews, but they rarely apply to an account that is already under investigation.
What to do while you wait
Focus on the few actions that actually help and avoid the ones that make it worse. The single most damaging mistake is opening a second developer account to get around the hold, because Apple links accounts and a new one can be flagged by association, turning a temporary pause into a permanent ban.
Before you reply to anything, write down a short, factual account of what your app does, where your users come from, and how you handle their data. If a growth campaign or a sudden spike in installs might explain a manipulation flag, name it and be transparent about it. Reviewers respond better to a clear explanation than to defensiveness, and having one ready means you answer within hours instead of days. The table below is the short version of what helps and what hurts.
| Do this | Avoid this |
|---|---|
| Respond to Apple in Resolution Center quickly and completely | Ignoring or delaying Apple's requests for information |
| Keep working with your single existing account | Opening a new Apple Developer account to bypass the hold |
| Document dates, screenshots, and every message | Resubmitting the same build repeatedly to force movement |
| Prepare a clear explanation of your app and traffic sources | Buying installs, reviews, or ranking services |
| Wait within realistic ranges before escalating | Sending duplicate support tickets that reset the queue |
If your app depends on a launch date, tell your stakeholders early that the timeline is outside your control. Planning around a worst case of several weeks is safer than assuming a two-day turnaround, and it keeps a stalled account from derailing a marketing commitment.
Where a pre-submission scan fits
A cleaner, more transparent build lowers the number of red flags that put an account in front of a human reviewer in the first place. Many code of conduct and safety flags trace back to concrete issues in the binary, such as hardcoded secrets, undeclared data collection, misleading permissions, or insecure network settings that read as careless. Scanning the build before you submit lets you find and fix those signals before they shape a reviewer's first impression.
A scanner like PTKD.com analyzes your .ipa or .apk and returns a graded report mapped to OWASP MASVS, so you can clean up the issues that make an app look risky. It is worth being honest about the limit: a scanner cannot lift an active account investigation, resolve an identity or fraud hold, or change Apple's queue. What it does is reduce the avoidable, app-level problems that invite scrutiny, which is prevention before submission rather than a cure once you are already under review.
What to take away
- There is no official deadline; plan for days to weeks and prepare for months, because Apple publishes no service level.
- The hold is account-level, so resubmitting builds does nothing while the investigation is open.
- Respond in Resolution Center fast and completely, and escalate to the App Review Board only after Apple issues a decision.
- Never open a second account to bypass the hold, because linked accounts can turn a pause into a permanent ban.
- Before your next submission, scan the build with PTKD.com to remove the app-level red flags that invite scrutiny.
