Error Handling
Your ad display delegate or callback interface receives a call if an ad fails to load or fails to display. This call is accompanied by an error code. This page describes these error codes.
Error Object
The error that you receive in your callback is a first-class error object. This object has three properties:
error["code"]- the error code, which you can find in the table below
error["message"]- a human-readable message that describes the error
error["adLoadFailureInfo"]- a description string that, when present, contains error codes and reasons why each mediated network failed to load an ad
MAX Error Codes
| Code | Description | Load / Display |
|---|---|---|
| 204 | No ads are currently eligible for your device (no fill). MAX returned no eligible ads from any mediated networks for this app/device. | L |
| −1 | 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 |
| −23 | You are attempting to show a fullscreen ad (interstitial or rewarded) while another fullscreen ad is still showing. | D |
| −24 | You are attempting to show a fullscreen ad before it has loaded. | D |
| −1000 | The ad request failed due to a generic network error. See the message field in the error object for more details. | L |
| −1001 | The ad request timed out due to a slow internet connection. | L |
| −1009 | The ad request failed because the device is not connected to the internet. | L |
| −5001 | 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 adLoadFailureInfo field in the error object for more details. | L |
| −5201 | The internal state of the SDK is invalid. There are various ways this can occur. | L |
| −5205 | The adapter did not have an ad ready when attempting to display. | L |
| −5209 | Unspecified internal error. | L |
| −5601 | The SDK failed to load an ad because it could not find the top Activity. | L |
| −5602 | The SDK failed to display an ad because the user has the “Don’t Keep Activities” developer setting enabled. | D |
| −5603 | The SDK failed to load an ad because the publisher provided an invalid ad unit identifier. Possible reasons for an invalid ad unit identifier:
| L |
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:
- BidMachine (Android) & BidMachine (iOS)
- Chartboost
- DT Exchange
- Google Bidding and Google AdMob (Android) & Google Bidding and Google AdMob (iOS)
- InMobi
- ironSource (Android) & ironSource (iOS)
- Liftoff Monetize
- Line (Android) & Line (iOS) (also)
- Maio (Android) & Maio (iOS)
- Meta Audience Network
- Mintegral
- MoPub
- Ogury — interstitial ads (Android) & Ogury — interstitial ads (iOS)
- Ogury — opt-in video ads (Android) & Ogury — opt-in video ads (iOS)
- Ogury — banner ads (Android) & Ogury — banner ads (iOS)
- Pangle (Android) & Pangle (iOS)
- Tencent (Android) & Tencent (iOS)
- Unity Ads (Android) & Unity Ads (iOS)
- Yandex
- YSO Network (Android) & YSO Network (iOS)