Your ad display delegate or callback interface will receive a call if an ad failed to load or failed to display. This call will be accompanied by an error code. This page describes the error codes you may see.
Error Object and MAX Error Codes
The error that you receive in your callback is a first-class error object that implements
MaxError. This object has the following methods:
- Returns the error code, which you can find in the table below.
- Returns a human-readable message that describes the error.
- Returns the mediated network’s error code for the error. Available for errors returned in ad display failure callbacks only.
- Returns the mediated network’s error message for the error. Defaults to an empty string. Available for errors returned in ad display failure callbacks only.
- Allows you to see the information about the current waterfall for an ad that has loaded or failed to load. The network responses provide the ad load state, latency, credentials, and mediated network information for each ad in the waterfall. If an ad in the waterfall fails to load, the network response provides error information. You can find out more about this method in Advanced Settings: Waterfall Information API.
MAX Error Codes
|Code||Constant||Description||Load / Display|
||The system is in an unexpected state. This error code represents an error that could not be categorized into one of the other defined errors. See the message field in the error object for more details.||L/D|
||No ads are currently eligible for your device (no fill). MAX returned no eligible ads from any mediated networks for this app/device.||L|
||The ad failed to load due to no networks being able to fill. MAX returned eligible ads from mediated networks, but all ads failed to load. See the
||The ad request failed due to a generic network error. See the message field in the error object for more details.||L|
||The ad request timed out due to a slow internet connection.||L|
||The ad request failed because the device is not connected to the internet.||L|
||You are attempting to show a fullscreen ad (interstitial or rewarded) while another fullscreen ad was still showing.||D|
||You are attempting to show a fullscreen ad before it has been loaded.||D|
||The internal state of the SDK is invalid. There are various ways this can occur.||L|
||The adapter did not have an ad ready when attempting to display.||L|
||Unspecified internal error.||L|
||The SDK failed to load an ad because it could not find the top
||The SDK failed to display an ad because the user has the “Don’t Keep Activities” developer setting enabled.||D|
Error Codes from Various Networks
To better understand the error codes that various ad networks return, see the error documentation pages published by those networks:
- DT Exchange
- Google bidding and Google AdMob
- Meta Audience Network
- Nend — banner ads
- Nend — icon ads
- Nend — video ads
- Nend — native ads
- Ogury — interstitial ads
- Ogury — opt-in video ads
- Ogury — banner ads
- Unity Ads