Your App Works Fine in Development Mode — Then You Switch to Live Mode and Everything Breaks
Developers run into this constantly. Permissions that worked perfectly during testing suddenly stop working for real users. Logins fail. Data stops flowing. The mode toggle in the App Dashboard just broke your app — here is exactly why, and what actually needs to happen before going live.
Development Mode is a sandbox: your app can use all permissions and features, but only for users who have an assigned role on the app (Admin, Developer, Tester, Analytics User). Live Mode opens your app to everyone — but only permissions explicitly approved through Meta App Review are active. Flip that toggle before App Review is complete and every unapproved permission stops working for all users, including your own developer account.
What Changes Between Development Mode and Live Mode
Development Mode
All permissions and features work automatically. Access is restricted to role users only. App is hidden from public search. Data generated is private — visible only to role users. Up to 25 active test users allowed.
Live Mode
App is publicly accessible. Only App Review-approved permissions are active for all users, including role users. Unapproved permissions fail. Data from Development Mode testing becomes visible to all users once you switch.
Why the Switch Is Harder Than It Looks
No Approved Permissions = Broken App
Switching without completing App Review means any permission above basic public data scopes fails silently — even for your admin account. The toggle does not grant approval; it removes the Development Mode safety net.
Role Users Also Get Locked Out
Developers assume their admin account bypasses Live Mode restrictions. It does not. If a permission is not approved through App Review, even Admin and Developer role users cannot grant it once the app is live.
Test Data Becomes Public Instantly
Posts, comments, and any data created during Development Mode testing become visible to all users the moment you switch to Live Mode — no warning, no staging period.
Consumer Apps Have an Extra Restriction
Consumer-type apps in Live Mode still restrict Standard Access permissions to role users only. Most useful permissions require Advanced Access approval — a separate, higher bar in App Review that many developers miss.
The Correct Sequence (High Level)
Build and test entirely in Development Mode
Use test user accounts with assigned app roles. Test every permission and feature your app needs, running the exact user flows a real user would follow — login, consent screen, permission grant, data usage.
Identify every permission and feature that requires App Review
Check the Meta Permissions Reference for each scope your app requests. Permissions above Standard Access and features with advanced access levels each require separate App Review approval.
Submit App Review for every required permission
Prepare a screencast showing the complete user flow for each permission — including login, the permission consent screen, and how data is used. Reviewers test with their own test accounts, not your admin login.
Wait for all required permissions to be approved
Review timelines vary. Rejections require corrections and resubmission. Only after every required permission is approved is it safe to switch to Live Mode — switching earlier causes the breakage most developers experience.
Switch to Live Mode and maintain ongoing compliance
Once live, Meta may conduct periodic audits for apps with Advanced Access. If Meta restricts or disables a live app, switching modes will not fix it, so read what enforcement means and how to appeal. Keeping access active requires continued compliance with Meta Platform Policies — this is not a one-time process.
Common Reasons the Mode Switch Fails
- Switching to Live Mode before App Review is complete — unapproved permissions fail for all users immediately
- Assuming admin or developer accounts bypass Live Mode permission restrictions — they do not
- Missing screencasts for one or more permissions — reviewers cannot approve without a working demo of the complete user flow
- Submitting App Review for permissions that do not match the actual app use case — reviewers reject on use-case mismatch
- Requesting Standard Access permissions for Consumer apps in Live Mode when Advanced Access is what is actually required
- Not anticipating that Development Mode test data becomes publicly visible after the switch
What a Clean Development to Live Mode Transition Looks Like
Every permission the app needs is approved through App Review before the switch. Screencasts, privacy policy URL, and use-case justifications are prepared and accepted by Meta reviewers. The reviewer completed the full test flow with a test account. The app behaves identically in Live Mode as it did in testing — because the approved permission set exactly matches what was built, demonstrated, and reviewed.
If your app is stuck after switching modes — permissions failing in Live Mode, App Review rejected, or unsure which permissions need review — our Facebook App Review Service covers the full submission preparation. Learn more about Meta Advanced Access and why it affects Live Mode permission behavior, or explore common Meta App Review rejection reasons and how to fix them. New to the platform? Start with what the Meta API is and how App Review fits in.