5.1. Error Location
5.1.1 Error Code List
Reminder: To get ad SDK logs, use the following commands to enable SDK logs, then filter by ADSDK after entering the scenario to get logs
adb shell setprop log.tag.ADSDK DEBUG
adb logcat | grep ADSDK
adb shell setprop log.tag.AD_NET_LOG DEBUG
adb logcat | grep AD_NET_LOG
| Error Code | Description | Troubleshooting Direction |
|---|---|---|
| 9000 | Network exception | Check device internet connection |
| 9003 | Ad unit ID configuration error | Contact operations personnel (server did not match ad data) |
| 9009 | Ad unit unavailable | Please clear app cache, ensure internet connection for cloud configuration pull success, or contact operations to confirm if ad unit is enabled |
| 9031 | Network request timeout | Check device internet connection |
| 9035 | Request successful but no ad fill | 1. Ensure device VPN is working, try triggering ad requests multiple times. 2. If Facebook and Admob ads consistently don't show, try different device and ad unit, as alliances have restrictions on frequent formal ad testing |
| 9041 | Invalid AppID | Ensure initialization in main thread, confirm AppID correctness with operations personnel |
| 9042 | Cloud control unavailable | Please clear app cache, ensure internet connection for cloud configuration pull success, or contact operations to confirm if ad unit is enabled |
| -10000 | Unknown error code | Please try getting test ads or change device to request again |
| 20001 | No ad currently available | Please try getting test ads or change device to request again |
| 20002 | No ad currently available | Please try getting test ads or change device to request again |
| 20004 | Fill failure due to no network | Check device internet connection |
| 30001 | Third-party ad source initialization failed | Contact operations personnel (check if app ID or ad unit ID is valid) |
| 30002 | Third-party ad source request timeout | Please try getting test ads or change device to request again |
| 30003 | Third-party ad source request failed | Please try getting test ads or change device to request again |
| 30004 | Material loading failed | Please try getting test ads or change device to request again |
| 30005 | Request object destroyed by media | Check destruction logic |
| 40001 | No ads to display with network available | Please try getting test ads or change device to request again |
| 40002 | No offline ads to display without network | Please try getting test ads or change device to request again |
| 50001 | Ad display failed | Please try getting test ads or change device to request again |
| 60001 | SDK initialization failed, no available AppID | Contact operations personnel |
| 60002 | Object already destroyed | Check if API call is correct |
| 60003 | Splash ad display parameter exception | Check API call, check if parameters are correct |
| 60004 | SDK internal logic exception | Output complete logs, submit to ad SDK developers |
| 60005 | Native ad display parameter exception | Check API call, check if parameters are correct |
| 60006 | Ad loading error because current ad is being displayed | Please request ad again |
| 60007 | Display error, current scenario has sensitive content, ad cannot be displayed | Please try getting test ads or change device to request again |
| 70001 | Request mediation SDK cloud control timeout | Check device internet connection |
| 70002 | Cloud control request exception: request exception | Please try getting test ads or change device to request again |
| 70003 | Cloud control request exception: app ID does not exist on platform | Contact operations personnel |
| 70004 | Cloud control request exception: package name and app ID don't match | Contact operations personnel |
| 70005 | Cloud control request exception: OS mismatch | Contact operations personnel |
| 70006 | Cloud control request exception: app closed on platform | Contact operations personnel |
| 70007 | Cannot query ad unit ID information | Please go to Frequently Asked Questions |
| 70008 | Daily ad display count reached limit | Contact operations personnel |
| 70009 | Hourly ad display count reached limit | Contact operations personnel |
| 70010 | Display interval time not met, cannot request | Need to meet interval time requirement |
| 70011 | No ad sources configured for current ad unit | Contact operations personnel |
| 70012 | API used doesn't match current ad unit type | Contact operations personnel |
| 70013 | Ad unit has been closed | Contact operations personnel |
| 70014 | Ad request failed | Please try getting test ads or change device to request again |
5.1.2 Admob Ad Loading Failure Platform Reference Table
| Error Code | Error Type | Description |
|---|---|---|
| 0 | ErrorCode.ERROR_CODE_INTERNAL_ERROR | Internal error. For example, received invalid response from ad server. |
| 1 | ERROR_CODE_INVALID_REQUEST | Ad request invalid. For example, ad ID incorrect. |
| 2 | ERROR_CODE_NETWORK_ERROR | Ad request unsuccessful due to network connection. |
| 3 | ERROR_CODE_NO_FILL | Ad request successful but no ad returned due to lack of ad inventory. |
| 8 | ERROR_CODE_APP_ID_MISSING | Ad request not made due to missing app ID. |
| 10 | ERROR_CODE_REQUEST_ID_MISMATCH | Request ID not found in ad string. |
| 11 | ERROR_CODE_INVALID_AD_STRING | Ad string invalid. For example, no request ID in ad string. |
| 512 | MAX_CONTENT_URL_LENGTH | Maximum content URL length. |
5.1.3 Applovin Error Code Reference
5.1.4 Pangle Error Code Reference
5.1.5 Inmobi Error Code Reference
5.1.6 Mintegral Error Code Reference
5.1.7 Vungle Error Code Reference
5.1.8 Bigo Error Code Reference
5.1.9 Media Viewing Main Process Logs
Reminder: To view ad SDK main process logs for ad requests, use the following commands to enable SDK logs
adb shell setprop log.tag.Hisavana_Log DEBUG
adb logcat | grep Hisavana_Log