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 that implements ErrorInfo.
This object has the following API:
Code- The error code, which you can find in the table below.
Message- A human-readable message that describes the error.
MediatedNetworkErrorCode- The mediated network’s error code for the error. Available for errors returned in ad display failure callbacks only.
MediatedNetworkErrorMessage- 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.
WaterfallInfo- Allows you to see the information about the current waterfall for an ad that loads or fails 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 | MaxSdkBase.ErrorCode Constant | Description | Load / Display |
|---|---|---|---|
| −1 | .Unspecified | 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 |
| 204 | .NoFill | No ads are currently eligible for your device (no fill). MAX returned no eligible ads from any mediated networks for this app/device. | L |
| −5001 | .AdLoadFailed | 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 |
| −1000 | .NetworkError | The ad request failed due to a generic network error. See the message field in the error object for more details. | L |
| −1001 | .NetworkTimeout | The ad request timed out due to a slow internet connection. | L |
| −1009 | .NoNetwork | The ad request failed because the device is not connected to the internet. | L |
| −23 | .FullscreenAdAlreadyShowing | You are attempting to show a fullscreen ad (interstitial or rewarded) while another fullscreen ad was still showing. | D |
| −24 | .FullscreenAdNotReady | You are attempting to show a fullscreen ad before it has been loaded. | D |
| −5601 | .NoActivity | The SDK failed to load an ad because it could not find the top Activity. | L |
| −5602 | .DontKeepActivitiesEnabled | The SDK failed to display an ad because the user has the “Don’t Keep Activities” developer setting enabled | D |
| −5603 | .InvalidAdUnitID | 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