Hi there! I see you're encountering the "Error has occurred" message when trying to log into DRAGON BALL LEGENDS on your iPad. Let's get that sorted out for you.
To start, could you tell me if you're connected to Wi-Fi or using mobile data on your iPad when this happens? Also, have you tried logging in with a different internet connection or restarted the app already? These details help narrow down the cause.
Generally, this kind of error can be due to network issues or app data corruption. Here’s a step-by-step guide to troubleshoot:
1. Switch Internet Connection: If you're on Wi-Fi, try switching to mobile data, or vice versa. Sometimes network restrictions or poor connectivity cause login errors.
2. Restart the App and Device: Close DRAGON BALL LEGENDS completely, then restart your iPad. This refreshes temporary files and connections.
3. Update the Game and iOS: Ensure your game is updated to the latest version from the App Store. Also, check that your iPad iOS 14 is fully updated, as updates can fix compatibility issues.
4. Clear App Cache / Reinstall: If the error persists, try uninstalling the game and reinstalling it from the App Store. Before you uninstall, make sure to back up your account data or link your game to your Bandai Namco ID or social account to prevent data loss. During reinstall, on the initial launch, select 'Data Transfer' to restore your saved data.
5. Check Permissions: Make sure the app has necessary permissions like access to the internet. On iPad, go to Settings > DRAGON BALL LEGENDS and confirm permissions.
6. Confirm Server Status: Sometimes server issues can cause login errors. You can quickly check if others are experiencing problems via official social media or fan community updates.
Please try these steps and let me know how it goes. If the error still appears, we can look into more advanced options or I can help you contact support directly.
Are you comfortable trying these out? Also, did this error happen suddenly or after an update or change? That info might help pinpoint the cause better.
Comments
Frank Taylor
Frank automates deployment pipelines and loves tinkering with container orchestr...
Followed by
Hi there! I see you're encountering the "Error has occurred" message when trying to log into DRAGON BALL LEGENDS on your iPad. Let's get that sorted out for you.
To start, could you tell me if you're connected to Wi-Fi or using mobile data on your iPad when this happens? Also, have you tried logging in with a different internet connection or restarted the app already? These details help narrow down the cause.
Generally, this kind of error can be due to network issues or app data corruption. Here’s a step-by-step guide to troubleshoot:
1. Switch Internet Connection: If you're on Wi-Fi, try switching to mobile data, or vice versa. Sometimes network restrictions or poor connectivity cause login errors.
2. Restart the App and Device: Close DRAGON BALL LEGENDS completely, then restart your iPad. This refreshes temporary files and connections.
3. Update the Game and iOS: Ensure your game is updated to the latest version from the App Store. Also, check that your iPad iOS 14 is fully updated, as updates can fix compatibility issues.
4. Clear App Cache / Reinstall: If the error persists, try uninstalling the game and reinstalling it from the App Store. Before you uninstall, make sure to back up your account data or link your game to your Bandai Namco ID or social account to prevent data loss. During reinstall, on the initial launch, select 'Data Transfer' to restore your saved data.
5. Check Permissions: Make sure the app has necessary permissions like access to the internet. On iPad, go to Settings > DRAGON BALL LEGENDS and confirm permissions.
6. Confirm Server Status: Sometimes server issues can cause login errors. You can quickly check if others are experiencing problems via official social media or fan community updates.
Please try these steps and let me know how it goes. If the error still appears, we can look into more advanced options or I can help you contact support directly.
Are you comfortable trying these out? Also, did this error happen suddenly or after an update or change? That info might help pinpoint the cause better.