Joseph Leporati

Why Does Our Business App Keep Getting Rejected From the App Store?

Short answer

Most repeat rejections of business apps come from guideline 2.1, App Completeness. The reviewer can't log in, the backend is asleep or blocked, or the app still has placeholder content. Fix it by giving Apple a demo account that never expires and is preloaded with sample data, keeping the backend up during review, writing clear review notes, and testing that exact login from outside your network before every submission.

Abstract phone outline, a closed gate and a key shape, with a looping path passing through on the third try

Apple rejects a lot of apps. By one count, about 2.1 million of the 9.1 million submissions it reviewed in 2025 were rejected. That's roughly one in four (Kealy Studio). A single rejection is routine. Getting rejected again and again for the same reason is different: it means some part of your submission process has no owner.

Business apps run into one pattern in particular. A scheduling app, a field service tool, an ordering app or an employee portal usually sits behind a login. It talks to a backend that a vendor or your IT team runs, and it often has no public content at all. Each of those traits gives the reviewer a way to fail before seeing a single feature.

What App Review actually does with your build

The reviewer installs your build on a clean device on Apple's network and reads your review notes. They aren't on your VPN or in your identity directory, they aren't on your IP allowlist, and they have no saved session. Whatever a stranger would see on first launch is what Apple evaluates.

Apple's App Review Guidelines say submissions should be final versions with placeholder text and temporary content removed. If the app has a login, you should include demo account details and have the backend turned on. The same page tells you to give App Review full access to the app. That means an active demo account or a fully featured demo mode, plus any resources the review needs, such as login credentials or a sample QR code.

Each round costs time. Apple aims to review at least 50% of submissions in under 24 hours and 90% in under 48 hours. You can request an expedited review once the app is already submitted, for a critical bug fix or a release tied to an event. Three avoidable rejections can still burn most of a week, plus engineering time on every resubmission.

Why does Apple reject an app that works fine on our devices?

Your test devices aren't the reviewer's device. Apple has reported that over 40% of unresolved issues fall under guideline 2.1, App Completeness, which covers crashes, placeholder content and incomplete information (Wishkit, citing Apple).

The most common version for business apps is "Guideline 2.1, Information Needed." The reviewer couldn't sign in with the credentials you gave them. Apple asks you to enter demo credentials in the Username and Password fields of the App Review Information section, or to include a demo mode that shows all features. Apple also says it can't use a demo video to continue the review (Adalo forum, quoting the rejection).

Here are the failure modes I'd look for first, in roughly this order:

Failure modeWhat the reviewer seesFix
Review account password expired or rotated by policyLogin failsExempt that one account from rotation until approval
MFA code sent to a phone nobody monitorsStuck at the 2FA promptTurn off MFA for the review account only, and log its use
SSO-only login tied to your company tenantNo way in at allAdd a password login path for the review account
IP allowlist, VPN requirement or geo-restrictionNetwork error or timeoutAllow the review account from any network, or expose a dedicated review environment
Staging torn down, scaled to zero, or database sleepingSpinner, timeout, crashKeep the environment running and warm until approval
Empty account with no recordsBlank screens that look incompleteSeed realistic sample data
Feature needs a scanner, QR code or paired deviceFeature can't be exercisedProvide a sample QR code or a demo mode
Leftover test buttons, lorem ipsum, dead linksPlaceholder contentScrub before every build

If you can't hand Apple an account for legal or security reasons, a built-in demo mode is allowed instead. It needs Apple's approval in advance, and it has to show the app's full features and functionality (appflight.dev). Expect that to take longer than keeping one well-managed review account.

The single most useful habit: test the exact demo account on a device outside your network with no saved session before every submission, including any 2FA prompts or region checks (testscenario.com). A scripted check against the same endpoint the app calls catches most of this in seconds:

# Run from a machine OFF the corporate network and VPN (a phone hotspot works).
# Checks that the review account authenticates and how long a cold request takes.
curl -s -o /dev/null \
  -w "status=%{http_code} total=%{time_total}s\n" \
  -X POST https://api.example.com/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"username":"appreview@example.com","password":"REDACTED"}'

A 200 that takes many seconds still counts as a failure. Serverless backends and free-tier databases can take a long time on the first request after they've gone idle, and the reviewer's first tap is always a cold request. An average response time won't show this, because the slow requests hide in the tail of the distribution; checking p95 and p99 latency is the better test of whether a reviewer will hit a slow screen.

The other guidelines that catch business apps

Most other rejections cluster around a short list of guidelines (CatDoes). Here is how each one tends to show up in a business app:

GuidelineHow it shows up in a business appWhat to do
4.2 Minimum FunctionalityThe app is a web portal wrapped in a shell ("this is just a website")Add native value that matters to users: offline work, push notifications, camera scanning, device integration
2.3 Accurate MetadataScreenshots come from design mockups, or the description promises roadmap featuresUse screenshots from the actual build and describe only what ships
4.3 SpamA vendor submits near-identical template apps for several clients with different logosAsk your vendor how their white-label approach handles this before you sign
5.1.1 PrivacyData collection isn't disclosed, or the app has sign-up but no account deletionMatch the privacy disclosures to the real data flows
3.1.1 PaymentsThe app links out to an external payment page for digital goodsHave your vendor check the payment flow against the guideline text before building it

Two points deserve emphasis. Guideline 5.1.1(v) has required since 2022 that if users can create an account in your app, they must be able to delete it from inside the app (CatDoes). Business apps that added self-service sign-up late often miss this.

Guideline 4.2 is the bigger architectural risk. An app that only renders your existing web portal can fail no matter how polished it is. That decision gets made at the start of the project, which is why the framework and scope choices in native vs. React Native vs. Flutter matter before the first line of code.

Is it our vendor's fault, or something our IT team controls?

Usually both, and repeat rejections tend to happen where their responsibilities meet. The vendor controls the build: crashes, placeholder content, metadata, account deletion, payment flows. Your IT team usually controls identity (SSO, MFA, password rotation), network policy (firewalls, allowlists) and often the hosting budget that decides whether staging stays up. A vendor can't fix a review account that your identity policy disables every 30 days.

Ownership of the developer account is the other piece. My view is that the business should own the Apple Developer account and add the vendor as a user. The vendor shouldn't hold it for you. When a vendor relationship ends, you want the listing, the signing setup and the review history to stay with you. Membership costs $99 a year, at the same price for individuals and organizations. The fee is waived only for eligible nonprofits, accredited schools and government entities, so a city or parish office should check eligibility before paying.

I've shipped five iPhone games and a smart-lighting app that runs on seven Apple surfaces from one codebase. Most review delays I've dealt with were process problems, not code problems. If nobody on your side has authority over both the vendor and the infrastructure, a fractional CTO can cover that gap.

Rejection, Information Needed, or appeal?

"Information Needed" means the reviewer couldn't finish. Most of the time it's the demo account. The fix is often entirely on your side of the server: reset the account, bring the environment up, then reply in the Resolution Center with updated notes. A rejection under a specific guideline means the reviewer evaluated the app and found a problem.

If the Resolution Center exchange doesn't settle it, you can appeal to the App Review Board. Cite the specific guideline you were rejected under and explain point by point how the app meets it. The form covers up to five rejected or removed apps. Appeal when the reviewer misread the app, for example by treating a real offline field tool as a website wrapper. Don't appeal a 2.1 login failure. Fix it.

Pre-submission checklist

  • Dedicated review account, exempt from rotation and MFA, with a named owner on your team
  • Account seeded with realistic records in every main screen
  • Backend, database and any third-party services pinned up until approval
  • Login and core flows tested off-network on a device with no saved session
  • Placeholder content, test menus and dead links removed
  • Screenshots taken from this build
  • In-app account deletion present if sign-up exists
  • Sample QR codes or hardware instructions attached if features need them
  • Review notes written so a stranger could test every feature

A review notes template that covers most business apps:

Demo account: appreview@example.com / [password in the fields above]
Role: Manager (sees all features). No MFA on this account.
Sample data: 3 job sites, 12 work orders, 2 open invoices.
Key flows: Schedule > tap any job > Start > photo > Complete.
Scanning: use the attached sample QR code on the Check-In tab.
Account deletion: Settings > Account > Delete Account.
Backend availability: monitored and kept running through review.

Where to start

  1. Pull every past rejection message and map each one to its guideline number. Repeats point to the gap in your process.
  2. Create the review account and decide who on your side owns it.
  3. Confirm the Apple Developer account belongs to your organization, not your vendor.
  4. Run the off-network login test and time the first request.
  5. If you're vetting a vendor or negotiating who owns the app, the Louisiana Small Business Development Center at the University of Louisiana at Monroe and Louisiana Tech's Technology Business Development Center in Ruston are both nearby resources.

If you'd like a second set of eyes on a rejected submission, email hello@josephleporati.com.

Common questions

Can we send Apple a demo video instead of giving the reviewer a login?

No. Apple's standard 2.1 Information Needed message says it can't use a demo video to continue the review. You need to enter working credentials in the Username and Password fields of App Review Information or provide a demo mode that shows every feature. A built-in demo mode in place of an account needs Apple's approval in advance, so plan for that delay.

Do we need to keep the backend running just for Apple's review?

Yes. Apple's guidelines say the backend service should be turned on if the app includes a login. In practice, that means the environment the build points to can't be torn down, scaled to zero or left to sleep during review. Keep it running until approval and confirm the first request is fast. A slow cold start looks like a broken app to a reviewer.

What does it cost each year to keep a business app on the App Store?

Apple Developer Program membership costs $99 a year and renews annually. Individuals and organizations pay the same price. Apple waives the fee only for eligible nonprofits, accredited schools and government entities. That fee is just for publishing. Hosting, maintenance and the engineering time each resubmission takes are separate, and they depend on your architecture and how often you ship updates.

Should we leave the review account active after the app is approved?

Yes. Every update goes through review again, and Apple's demo account requirement applies to each submission, not only the first. Keep the account active with its sample data in place, keep it out of password rotation, and name someone responsible for it. Deactivating it after launch is a common reason the next routine update gets a 2.1 Information Needed response.

Does Google Play reject apps for the same reasons as Apple?

Not exactly. The guideline numbers here (2.1, 2.3, 4.2, 4.3, 5.1.1, 3.1.1) are Apple's alone, and Google Play publishes its own separate policies. Some habits help on both stores: a working reviewer login, a backend that stays up, accurate screenshots and honest data disclosures. Still, check each store's requirements separately rather than assuming a fix for one covers the other.

Sources

  1. Why did Apple reject my app? - Kealy Studio kealy.studio
  2. App Review Guidelines - Apple Developer developer.apple.com
  3. Request an expedited review - Apple Developer developer.apple.com
  4. App Store Review Guidelines: Why Apps Get Rejected - Wishkit wishkit.io
  5. Adalo forum: Apple rejected my app for being unable to sign in with demo credentials forum.adalo.com
  6. App Store rejection: Guideline 2.1 app completeness - appflight.dev appflight.dev
  7. 18 Reasons Your App Was Rejected by Apple - testscenario.com testscenario.com
  8. Most Common App Store Rejection Reasons and Fixes (2026) - CatDoes catdoes.com
  9. Apple Developer Program Fee Waiver - Apple Developer developer.apple.com
  10. Appeal to the App Review Board - Apple Developer developer.apple.com
  11. Resources - WMWO Chamber of Commerce westmonroechamber.org
  12. Louisiana Tech Enterprise Center (LaTEC) - LED opportunitylouisiana.gov

app store ios app review mobile apps