5.1 Error location
5.1.1 List of error codes
Reminder: Get the advertising SDK log. Use the following command to open the SDK log. After entering the scene, filter the ADSDK and get the log.
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 abnormality | Check mobile phone network status |
| 9003 | Advertising slot ID configuration error | Contact the operator (the server does not match the advertising data) |
| 9009 | Advertisement space is not available | Please clear the cache of the app and connect to the Internet to ensure that the cloud control configuration is pulled successfully, or contact the operator to confirm whether the advertisement space is enabled. |
| 9031 | Network request timed out | Check the mobile network connection |
| 9035 | The request is successful but there is no ad filling | 1. You can try to trigger the ad request a few more times under the condition that the network of the mobile phone has been bypassed. 2. Facebook and Admob ads have been unable to come out, please change the phone and test the ad space, the alliance has restricted frequent official ad tests. |
| 9041 | Invalid AppId | Make sure to initialize on the main thread and confirm the correctness of the AppID to the operator. |
| 9042 | Cloud Control is unavailable | Please clear the cache of the app and connect to the Internet to ensure that the cloud control configuration is pulled successfully, or contact the operator to confirm whether the advertising space is enabled. |
| -10000 | Unknown error code | Please try to get a test ad or change the device and request again |
| 20001 | No ads currently | Please try to get a test ad or change the device and request again |
| 20002 | No ads currently | Please try to get a test ad or change the device and request again |
| 20004 | Filling fails due to lack of network connection | Check mobile phone network status |
| 30001 | Initialization of third-party ad source failed | Contact the operator (whether the application ID or code position ID is valid) |
| 30002 | Ad request from third-party ad source timed out | Please try to obtain test ads or change the device to request again |
| 30003 | Ad request from third-party ad source failed | Please try to obtain test ads or change the device to request again |
| 30004 | Material loading failed | Please try to obtain test ads or change the device to request again |
| 30005 | The request object was destroyed by media | Check destruction logic |
| 40001 | No ads can be displayed when there is a network connection | Please try to get a test ad or change the device and request again |
| 40002 | No offline ads can be displayed when there is no network connection | Please try to get a test ad or change the device and request again |
| 50001 | Ad display failed | Please try to get a test ad or change the device and request again |
| 60001 | sdk initialization failed, no AppID available | Contact operations staff |
| 60002 | The object used has been destroyed | Check if the API call is correct |
| 60003 | Exception in parameters passed when displaying open-screen ads | Check the API call to see if the parameters are correct |
| 60004 | SDK internal logic exception | Submit the complete log output to advertising SDK development |
| 60005 | When native ads are displayed, the parameters passed in are abnormal. | Check the API to check whether the parameters are correct |
| 60006 | Ad loading error, because the current ad is being displayed | Please request the ad again |
| 60007 | Display error, the current scene contains sensitive content, and the ad cannot be displayed | Please try to obtain a test ad or change the device and request again |
| 70001 | Request aggregation SDK cloud control timeout | Check mobile phone network status |
| 70002 | Request cloud control exception: Request exception | Please try to get test ads or change the device and request again |
| 70003 | Request cloud control exception: The application ID does not exist on the platform | Contact operations staff |
| 70004 | Request cloud control exception: package name and application ID do not match | Contact operations staff |
| 70005 | Request cloud control exception: operating system does not match | Contact operations staff |
| 70006 | Request cloud control exception: The application is closed on the platform | Contact operations staff |
| 70007 | Unable to query ad slot ID information | Frequently Asked Questions |
| 70008 | The maximum number of ad impressions in a single day has been reached | Contact operations staff |
| 70009 | The maximum number of ad impressions in a single hour has been reached | Contact operations staff |
| 70010 | The display interval is not met and the request cannot be made | Need to meet the interval length |
| 70011 | There is no advertising source configured under the current advertising slot. | Contact operations staff |
| 70012 | The API used does not match the current ad slot type | Contact operations staff |
| 70013 | This ad slot has been closed | Contact operations staff |
| 70014 | The ad request failed | Please try to get a test ad or change the device and request again |
5.1.2 Admob cannot load ads platform comparison table
| Error Code | Error Type | Description |
|---|---|---|
| 0 | ErrorCode.ERROR_CODE_INTERNAL_ERROR | internal error. For example, an invalid response was received from the ad server. |
| 1 | ERROR_CODE_INVALID_REQUEST | The ad request is invalid. For example, the advertising ID is incorrect. |
| 2 | ERROR_CODE_NETWORK_ERROR | The ad request was unsuccessful due to a network connection. |
| 3 | ERROR_CODE_NO_FILL | Ad request was successful. However, no ad was returned due to lack of ad inventory. |
| 8 | ERROR_CODE_APP_ID_MISSING | The ad request was not made due to a missing app ID. |
| 10 | ERROR_CODE_REQUEST_ID_MISMATCH | The request ID in the ad string is not found. |
| 11 | ERROR_CODE_INVALID_AD_STRING | The ad string is invalid. For example, there is no request ID in the ad string. |
| 512 | MAX_CONTENT_URL_LENGTH | The 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 view main process log
Reminder: Check the advertising SDK advertising request main process log, and use the following command to open the SDK log
adb shell setprop log.tag.Hisavana_Log DEBUG
adb logcat | grep Hisavana_Log