Super Mario Run: comprehensive list of issues (and possible fixes) [Android and iOS]

Super Mario Run

Super Mario Run – Comprehensive list of issues and possible fixes (Android)

On March 23rd, Nintendo finally launched Super Mario Run on Android, the very first Mario game on smart devices. In this post, we are going to list the various issues encountered by players, as well as potential fixes.

If you see an issue is missing, or if you have a fix to share, make sure to let us know in the comments or on Twitter! If you do so, make sure to give as many details as you can: device used, OS (rooted or not, custom OS or stock), what you were doing or trying to do when the issue occured, etc.. That way, it will be easier for us and other users to determine what is causing it!

If the fixes listed below don’t work for you, you might have to contact support. Also Don’t forget that Nintendo will release Software updates, so make sure you have the latest version if you’re having any trouble with the game.

If you have any issues with the game, make sure to check out the official FAQ first: chances are, the solution to your problem can be found there! Don’t forget to download the latest Software update if you haven’t already!

Issue #1A – Game crashes at launch on non-stock ROM / rooted devices (added on March 22nd)

  • Devices impacted: devices running non-stock Android ROMs and/or rooted devices
  • Cause: Nintendo’s security check (SafetyNet)
  • Fix: use tool to bypass Nintendo’s security check

If your device is using a non-stock Android ROM and/or if your device is rooted, chances are Super Mario Run will simply crash at launch. Unfortunately, there’s no official fix for that, as this is a security measure put in place by Nintendo to prevent hackers/cheaters from ruining the fun of others.

In order to fix this issue, you can look for tools to bypass Super Mario Run’s security check.

Issue #1B – Error 804-5100 (added on March 23rd)

  • Devices impacted: devices running non-stock Android ROMs and/or rooted devices
  • Cause: Nintendo’s security check
  • Fix: use tool to bypass Nintendo’s security check

If your device is using a non-stock Android ROM and/or if your device is rooted, chances are Super Mario Run will return an error code (Error 804-5100). Unfortunately, there’s no official fix for that, as this is a security measure put in place by Nintendo to prevent hackers/cheaters from ruining the fun of others.

In order to fix this issue, you can look for tools to bypass Super Mario Run’s security check.

NB: this issue is tied to Issue 1A. It gets a separate listing because the error doesn’t happen the same way (with 1A, the app crashes after the Nintendo logo; with 1B, you get Error 804-5100 after the title screen, and the app doesn’t crash).

Issue 2 – Cannot purchase the full game (support code 804-9174) (added on March 23rd)

  • Devices impacted: all devices
  • Cause: Google Account required
  • Fix: create a Google Account

This issue is probably not going to impact many users, since you do need a Google Account to download the game from the Play Store.

Issue 3 – Cannot log in to a Nintendo Account (support code 804-3904) (added on March 23rd)

  • Devices impacted: all devices
  • Cause: unknown
  • Fix: clear the cache of your browser

This issue is probably not going to impact many users, since you do need a Google Account to download the game from the Play Store.

Issue 4 – Cannot re-link a Nintendo Account (support code:804-3905) (added on March 23rd)

  • Devices impacted: all devices
  • Cause: unknown
  • Fix: link your account after a fresh install.

Issue 5 – Cannot run the game because the User Agreement or Privacy Policy has changed (support code 804-3400) (added on March 23rd)

  • Devices impacted: all devices
  • Cause: new User Agreement / Privacy Policy
  • Fix: Click here to log to your Nintendo Account, and then accept the new User Agreement and/or the new Privacy Policy.

More on Super Mario Run:

***
***

Super Mario Run – Comprehensive list of issues and possible fixes (iOS)

On December 15th, Nintendo finally launched Super Mario Run on iOS, the very first Mario game on smart devices. Unfortunately, it looks like some issues came uninvited, and could be ruining the fun of hopeful plumbers who simply want to go on a run. In this post, we are going to list the various issues encountered by players, as well as potential fixes.

NB: this page is still being updated with more details and/or fixes. If you see an issue is missing, or if you have a fix to share, make sure to let us know in the comments or on Twitter! If the fixes listed below don’t work for you, you might have to contact support. Don’t forget that Nintendo will release Software updates, so make sure you have the latest version if you’re having any trouble with the game.

If you have any issues with the game, make sure to check out the official FAQ first: chances are, the solution to your problem can be found there! Don’t forget to download the latest Software update if you haven’t already!

[Fixed] Issue #1 – Game crashes when linking Facebook account (added on December 15th, updated on December 20th)

  • Devices impacted: all devices
  • Cause: trying to link a Facebook account when none of your Facebook friends have linked theirs
  • Fix: update to Ver. 1.0.1.1099

If you’re trying to link your Facebook account to Super Mario Run in order to find friends, the game may crash. The source of this crash is a glitch that occurs if none of your Facebook friends have linked their account to Super Mario Run. To fix this issue, update to Ver. 1.0.1.1099.

Issue #2 – Game crashes at launch on Jailbroken devices (added on December 15th)

  • Devices impacted: jailbroken devices (even clean devices that are not jailbroken anymore, as long as they were previously jailbroken)
  • Cause: Nintendo’s security check
  • Fix: use tool to bypass Nintendo’s security check

If your device is or was jailbroken at one point, chances are Super Mario Run will simply crash at launch. Unfortunately, there’s no official fix for that, as this is a security measure put in place by Nintendo to prevent hackers/cheaters from ruining the fun of others… too bad if that does not apply to you, and you simply want to have fun and play fair.

In order to fix this issue, you can look for tools to bypass Super Mario Run’s security check (tsProtector is one of them). Unfortunately, you will most likely have to wait until an update for said tools is available!

Issue #3 – Game crashes at launch (added on December 15th)

  • Devices impacted: all devices?
  • Cause: unknown
  • Fix: none at the moment

Some users have reported that Super Mario Run crashes at launch (not on a jailbroken device, or a previously jailbroken device). The cause for this is currently unknown, and no fix is available. Make sure that you have the latest version of iOS and Super Mario Run. Try clearing cache and/or re-installing the app.

Issue #4 – My Nintendo fails to load in-game (added on December 15th)

  • Devices impacted: all devices?
  • Cause: servers overloaded
  • Fix: try clearing the cache and history of your web browser, and disabling any content blocker you might have (Adblock, NoScript, etc.)

Some users have reported that My Nintendo failed to load in-game (sometime resetting the game altogether). This is most likely the servers being overloaded at launch, and there doesn’t seem to be anything to do but wait. Alternatively, you can try try clearing the cache and history of your web browser, and disabling any content blocker you might have (Adblock, NoScript, etc.).

Issue #5 – Error during purchase (Support Code: 804-4174) (added on December 15th)

  • Devices impacted: all devices?
  • Cause: servers overloaded?
  • Fix: none

Some users have reported errors during the purchase of the full game. This doesn’t seem to be a widespread issue, though. Try again later, or try contacting Apple.

Issue #6 – “Find an area with a better signal” error (Support Code: 804-1000) at launch (added on December 15th)

  • Devices impacted: all devices?
  • Cause: insufficient signal
  • Fix: get closer to the access point and/or connect via WiFi if you can

Some users have reported getting the “Find an area with a better signal” error at launch.

If you get this, you simply need to do what the message says: find an area with a better signal. Alternatively, you can connect to a WiFi access point if possible. If you’re still getting the error despite your connection being good, then there is definitely an issue, so you should try again later. Unfortunately, you need an internet connection at all time to play Super Mario Run.

Issue #7 – “A communication error has occured. Please try again later (Support Code: 804-1200)” (added on December 15th)

  • Devices impacted: all devices?
  • Cause: communication error
  • Fix: try again later

Some users have reported getting the “A communication error has occured. Please try again later (Support Code: 804-1200)” error while playing. Unfortunately, there doesn’t seem to be anything to do but try again later.

Issue #8 – Super Mario Run cannot be used with Family Sharing (Added on December 16th)

  • Devices impacted: all devices
  • Cause: Family Sharing does not apply to IPA
  • Fix: none. But there is a work-around: account sharing.

Family Sharing does not apply to IAP. Unfortunately, with Super Mario Run, the full game is bought via IAP, which means that Family Sharing does not apply. If you don’t want to pay for the full game several times (for your wife/husband/kids), there’s a work-around… good ol’ account sharing! Click here for more details.

Issue #9 – Cannot link Nintendo Account on second device (Added on December 16th)

  • Devices impacted: all devices
  • Cause: unknown
  • Fix: re-install the game on the second device and link it to your Nintendo Account.

If you’re trying to use Super Mario Run on a secondary device (same user), you need to re-install the game on it and link it to your Nintendo Account. Note that you cannot have the same user play the game at the same time on two devices.

[Fixed?] Issue #10 – “Waiting for purchase to be authorised” loop (Support Code: 804-4105) (Added on December 16th, Updated on December 23rd)

  • Devices impacted: all devices
  • Cause: bug?
  • Fix: use the same Nintendo Account on both devices

If you try to validate a Family Sharing request (and get an error with your payment card), then Super Mario Run will get stuck in a “Waiting for purchase to be authorised” loop (Support Code: 804-4105). Even changing the payment card or user, re-installing/re-downloading the app, or rebooting your device does not seem to work.

It turns out the solution is pretty simple: use the same Nintendo Account on both devices. Here’s what you have to do:

  1. Delete the app on the child device.
  2. Install the app on the parent device and link it to a Nintendo account during the initial setup process (the account you will use/have already used on the child device). If you don’t link during the initial setup and you’ve already linked on the child device, you’ll have to delete and reinstall.
  3. Proceed with the purchase on the parent device.
  4. Reinstall the app on the child device, linking it to the same Nintendo account as you used in step 2.

Thanks Steven and Joe for reporting this, and thanks Jon for providing a solution.

***

More on Super Mario Run:


Facebooktwittergoogle_plusredditmail
Lite_Agent

About

Founder and main writer for Perfectly Nintendo. Tried really hard to find something funny and witty to put here, but had to admit defeat. Also known as Maintenance Guy by some. Twitter: @lite_agent