If Dragon Ball Z Dokkan Battle refuses to load and throws an unauthorized error the moment you open the app, you are not banned in most cases. The game has simply flagged something in your network or device setup and stopped the session as a precaution.
Quick answer
Turn off any VPN or proxy, connect through normal mobile data or home Wi-Fi, and reopen the app. The unauthorized error in Dokkan Battle is usually triggered by VPN traffic, an emulator, a rooted or jailbroken device, or a modified APK. Play on a clean, official install on a standard connection and the error clears.
| Error snapshot | |
|---|---|
| Exact error code | Unauthorized |
| Error message | An unauthorized operation was detected. The application will now close. |
| Applies to | Dragon Ball Z Dokkan Battle on Android and iOS |
| Environment | Mobile app, also seen on emulators and rooted devices |
| Severity level | Medium blocks login but rarely a permanent ban |
| Quickest fix | Disable VPN or proxy, switch to normal data or Wi-Fi, then relaunch. |
What the error actually means
In plain English
Dokkan Battle ran a quick security check at launch, decided your connection or device looked non standard, and shut the app down rather than let the session continue. It is a gatekeeper message, not a verdict that your account is gone.
The word unauthorized here points at the environment the game is running in, not your account credentials. Bandai Namco uses checks that look for signs of tampering or traffic rerouting. When a VPN funnels your connection through a data center IP, or when the app detects an emulator, root access, or a repacked APK, it treats the session as untrusted and closes it.
This is why the same account can work perfectly on one phone and fail on another. The account is fine. The device or the route the traffic takes is what trips the flag.
Before you start
Prerequisites and warnings
- Only ever install Dokkan Battle from the official Google Play Store or Apple App Store. Sideloaded or modified APKs are the single most common cause of this error.
- Make a note of your transfer code in advance from the in game menu, so you can move your account safely if you reinstall.
- Do not factory reset your phone to fix this. It is almost never necessary and you risk losing local data.
Step by step fixes
Work through these in order. Most players are back in after the first two steps.
| # | Step |
|---|---|
| 1 | Turn off VPN and proxy. Fully disable any VPN app, private relay, or proxy. iOS users should also turn off iCloud Private Relay for the app. VPN exit nodes use data center IP ranges that the game flags as suspicious. |
| 2 | Switch your connection. Toggle from Wi-Fi to mobile data, or vice versa, then relaunch. A restrictive school, office, or public network can route traffic in ways the game does not trust. |
| 3 | Force close and reopen. Swipe the app away from recents and open it fresh. A stale session left open through a network change can carry the unauthorized state with it. |
| 4 | Confirm you are on the official build. If you installed from anywhere other than the official store, uninstall it. Reinstall the genuine version from Google Play or the App Store, then sign back in with your transfer code or linked account. |
| 5 | Avoid emulators and rooted devices. If you play on an emulator or a rooted or jailbroken device, that is the trigger. Play on a standard, unrooted phone for this account, or expect the check to fire. |
| 6 | Update the app and the OS. Install any pending Dokkan Battle update and any pending system update. Older builds sometimes mishandle the security handshake after a server side change. |
| 7 | Free up storage and reboot. Low storage and long uptime can cause odd launch failures. Clear a little space, restart the device, and try once more. |
The technical context (the why)
Live service mobile games carry valuable accounts and in game currency, which makes them targets for cheating tools, automation, and account theft. To protect that, the client runs integrity checks at startup. These checks ask a simple question: does this look like a normal phone on a normal connection, running the real app?
A VPN answers that question badly because it hides your real network behind a shared data center address that thousands of other sessions also use. Root access answers it badly because it gives software the ability to read and rewrite the game in memory. The unauthorized message is the safe default the game falls back to when the answer is no.
Key points to remember
- A VPN or proxy is the most common trigger, so disabling it is always the first move.
- Rooted, jailbroken, and emulated devices will keep tripping this check by design.
- The error targets the device and network, not your account, so your progress is safe.
- Always reinstall from the official store, never a third party APK site.
Still broken? Your safety net
If you are on a clean official install, no VPN, a standard phone, and a normal connection, and the error still fires, the issue may be a temporary server side check or an account flag that needs a human to review. Contact Bandai Namco support with your friend code and a screenshot of the exact message.
Bandai Namco supportMore Error Fix guides
Was this fix helpful?
Yes, it workedNot yet
Your feedback helps us keep these guides accurate and updated.
Related error fixes
- “Operation could not be completed (0x00000709)” printer error
- ChatGPT “Error 429: Too Many Requests”
- Peacock “Playback Error”
- PS4 “CE-32895-7” connection error
- DoorDash “Error validating basket”
- Google Gemini “Something went wrong (1101)”
- Darktide “Error Code: 5002”
- Easy Anti-Cheat “Error 30005 (CreateFile failed with 32)”
- Steam “Error Code 50”
- Xbox “Error code 0x87e5002c”
- FreeStyle Libre 3 “Sensor Error”
TLDR
- Disable VPN, proxy, and iCloud Private Relay first.
- Switch between Wi-Fi and mobile data, then relaunch.
- Reinstall only the official store version if you sideloaded an APK.
- Rooted, jailbroken, and emulator setups will keep triggering the check.
- Your account is safe, so save your transfer code and contact support if a clean setup still fails.
Written and maintained by: Freddy John , founder of Wings Infotech and editor at Seminarsonly. This guide is reviewed and updated as vendors ship new patches. Last reviewed: 26 June 2026.
