There are various reasons why an ad load could fail. If this happens, the SDK will show the error details in LogCat (go to Android Monitor in your Android Studio).
Also if you’re actively loading, the ad will receive an error in the ad listener through the TappxAdError object.
| Code | Type | Explanation |
| NO_FILL | Notice | This means that at this moment the system is not getting an ad that fits your request. You should try and request an ad again. However, if you keep getting NO_FILL for your ad requests, you may want to use an additional ad network to ensure higher fill rates. |
| DEVELOPER_ERROR | Error | There’s an error with your SDK integration. Check our guides again and make sure you’re using the correct Tappx key. You can find more details in LogCat. |
| NETWORK_ERROR | Error | There’s a network error. This error usually happens when the device doesn’t have an internet connection or the connection is restricted. |
| SERVER_ERROR | Error | There’s a server error. Try again in a few seconds. |
| INTERNAL_ERROR | Error | There’s an internal error while loading the ad. If the error persists, please contact us. |
| UNSPECIFIED | Error | This is a generic error message for errors that don’t match the categories above. |
Simply use the AdRequest object with the loadAd method.
Here’s an example of information you can provide:
AdRequest adRequest = new AdRequest().useTestAds(true);
var adRequest = AdRequest().useTestAds(true)
If you get an error that’s not explained here or if you need help, please contact us