Search...
Menu
Error code description
Tips:
- To quickly locate the cause of the issue, it is recommended to get the full error information through
AdError#getFullErrorInfo()"code[ " + code + " ],desc[ " + desc + " ], platformCode[ " + platformCode + " ], platformMSG[ " + platformMSG + " ]" code: Taku SDK's error code desc: Taku SDK's error message platformCode: The third-party ad platform's error code (the error code to check when no ad fill occurs) platformMsg: The third-party ad platform's error message (the error message to check when no ad fill occurs)
1. Taku Error Code Information
| Error Code | Description |
|---|---|
| 10001 | Incorrect App ID or App Key. Please check the App ID and App Key passed when Initializing the Taku SDK. |
| 10003 | 1. Incorrect App ID. Please check the App ID passed when Initializing the Taku SDK. 2. The Taku Ad Placement ID does not match the App ID. Please check the Placement ID passed when calling the load method in the code. |
| 10004 | Incorrect Taku Ad Placement ID. Please check the Placement ID passed when calling the load method. |
| 9999 | 1. Generally a network request error. Check whether the network status is normal. 2. platformMSG: chain validation failed , check whether the system time has been adjusted. |
| 9990 | HTTP interface request returned a status error. Contact Taku colleagues to check the error message. |
| 9991 | Interface request returned a business code error. Contact Taku colleagues to check the error message. |
| 9992 | The GDPR level is set too low. Check whether the FORBIDDEN level has been manually set. |
| 2001 | Ad loading timeout. Check whether the current tested Ad Source is an overseas platform and whether the phone's network has a VPN enabled. |
| 2002 | The Taku SDK package is not fully imported. The third-party ad vendor's Adapter package is missing (anythink_network_*.aar). Confirm whether all required third-party SDK packages for the Mediation have been imported as instructed. |
| 2003 | The display count for the current Ad Placement has reached the limit. Check whether the Taku dashboard configuration has restricted the display count for this Ad Placement. |
| 2004 | The current Ad Placement is in a non-display time period. Check whether the Taku dashboard configuration has restricted the display interval for the Ad Placement. |
| 2005 | The Ad Placement is in the loading phase. After initiating a request for the same Ad Placement, before receiving the load success or failure callback, this Ad Placement cannot initiate the next load. Wait for the load success or failure callback. |
| 2006 | Check whether the imported third-party ad platform SDK packages are complete. If complete, check whether the imported version matches the version specified on GitHub. If not, the third-party SDK packages need to be supplemented. |
| 2007 | Usually occurs when ad loading is immediately initiated in the load failure callback. Prohibited: Do not immediately initiate ad loading in the load failure callback. A certain time interval must pass since the last Ad Placement load failure before initiating ad loading again. Delay the ad loading call. |
| 2008 | After a load failure for the same Ad Placement, do not call the load method immediately in the load failure callback for retry. Wait for more than 10 seconds before retrying. |
| 2009 | The number of ad placement loads within a certain time interval has reached the limit. |
| 3001 | Strategy acquisition error. 1. Check whether the network is normal. 2. Check whether the AppId, AppKey, and PlacementId used match. 3. Check whether the AppId, AppKey, and PlacementId in the code are correct and match (must not contain spaces). Call ATSDK.setNetworkLogDebug(true); and filter anythink in Logcat to view the parameters currently passed to the SDK. Please check these parameters. |
| 3002 | One of the passed AppId, AppKey, or PlacementId is an empty string. Call ATSDK.setNetworkLogDebug(true); and filter anythink in Logcat to view the parameters currently passed to the SDK. Please check these parameters. |
| 3003 | The Ad Placement does not match the called API. For example: a Banner Ad Placement was called using the Rewarded Video API to load an ad. |
| 4001 | Usually occurs when a third-party ad platform returns an error resulting in no ad fill. You can get the full error information via AdError.getFullErrorInfo(). Use platformCode and platformMsg to view the ad platform's error code and error message. Please check the third-party ad platform error codes for troubleshooting. |
| 4002 | The Context has been destroyed. You need to recreate the corresponding ad type object and then re-initiate ad loading. |
| 4003 | The status of this Ad Placement has been closed. Check whether the status switch for this Ad Placement in the Taku dashboard is enabled. |
| 4004 | This Ad Placement has no Ad Source configured in the Taku dashboard. You need to go to Taku Dashboard - Mediation Management to add a third-party ad platform's Ad Source for the Ad Placement. |
| 4005 | All Ad Sources under the Ad Placement have been filtered. Possible reasons are as follows: 1. Check whether Display Limit or Display Interval has been set for the Ad Source in the Taku dashboard. 2. If only Header Bidding Ad Sources are configured, when the bidding fails, the Header Bidding Ad Sources will be filtered. |
| 4006 | Video playback failed. Refer to Error Code 4001 for troubleshooting. |
| 4007 | Ad Source bidding failed. Refer to Error Code 4001 for troubleshooting. |
| 4008 | The Ad Source has been filtered due to custom filtering logic in the developer's code. If the filtering does not meet expectations, troubleshoot the custom filtering logic. |
| 4009 | In debug mode, the Ad Placement has no Ad Source configured. |
2. Third-Party Ad Platform Error Codes
● Tencent Ads
| Common Error | Solution |
|---|---|
| 6000 - 102006 | No suitable ad matched. Retries are prohibited, otherwise it may trigger system policies leading to decreased traffic revenue. For testing integration, you can use Taku's debug mode (DebuggerConfig) for testing. |
| 5002 - Video creative download error | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| Ad images not displaying | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| Native ad video black screen or transparent | Enable hardware acceleration in AndroidManifest.xml. |
| 5004 - No suitable ad matched | In this situation, retrying ad requests multiple times is prohibited, otherwise it may affect the system's evaluation of your traffic and thus affect monetization. For testing integration, you can use Taku's debug mode (DebuggerConfig) for testing. |
| 5004 - No ads | 1. Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). 2. Check the Tencent Ads Ad Source configuration in the Taku dashboard (whether it is template rendering 2.0). |
| 5006 - Package name verification error. The current app's package name does not match the package name filled in during media registration on the GDT official website, resulting in no ad return. | The package name configured in the code must match the one in the GDT dashboard. |
| 5010 - Ad format verification failed. Check whether the Ad Placement and API usage are consistent. | Check the Tencent Ads Ad Source configuration in the Taku dashboard (whether it is template rendering, whether it is full-screen video, etc.). |
| 2001 - Initialization error | Developer self-checks parameter issues. 1. Do not split the Tencent Ads SDK package. 2. Check the Tencent Ads Ad Source configuration in the Taku dashboard. 3. If parameters are correct, confirm whether a real device is being used. Do not use a simulator for testing. |
| 4004 - Splash Ad container not visible | 1. Troubleshoot whether the container is hidden or obscured. 2. If show is executed directly in the Activity's onCreate, a delay may be needed. It is recommended to use the main thread's Handler to postDelay by 10ms before calling the showAd method and try again. 3. Add container.removeAllViews(); call before displaying. |
| 102006 - No ad found matching the price requirement or experience requirement | It is recommended to appropriately adjust the floor price/target price settings, or go to the platform's ad center to check the blocking rules. |
For more Tencent Ads error information, see: Tencent Ads Error Codes
● Pangle (China)
| Common Error | Solution |
|---|---|
| 4201 - No initializer | 1. Check whether the ABI architecture has been restricted according to the integration documentation. 2. Check whether the com.android.support:appcompat-v7 dependency or androidx.appcompat:appcompat dependency has been added according to the integration documentation. |
| -7 - Splash Ad image load failed | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| No result callback after loading | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| Ad images not displaying | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| Video playback shows black screen | Check whether the WAKE_LOCK permission is configured in the Manifest. |
| 20001 | Request has no fill due to no suitable ad returned. Occasional occurrences are normal. Try switching devices for verification. Do not use a simulator for testing, or try again later. If the issue cannot be resolved, check the Pangle (China) SDK error codes for troubleshooting or submit a ticket to the Pangle platform for inquiry. For testing integration, you can use the test mode in the Taku dashboard's Ad Placement - Advanced Settings. |
| 40029 | Check the rendering type of the Pangle (China) placement ID. The Taku dashboard's Pangle (China) Ad Source configuration must be consistent with the Pangle (China) dashboard's configuration. |
| 40025 | 1. Check whether the system time of the test device is the current correct time. 2. Check whether the ABI architecture has been restricted according to the integration documentation. 3. If obfuscation is enabled, check the obfuscation rules provided in the downloaded SDK package. 4. Download the SDK from the Pangle (China) dashboard and replace the Pangle (China) SDK provided by Taku (open_ad_sdk_*.aar). |
| 40021 - APK signature SHA1 value does not match the media platform entry | The app's signature must be consistent with the signature configured in the Pangle (China) dashboard. If it was just configured, clear the cache and try again after 5 minutes. |
| 40019 - Media configuration adtype does not match the request | Check the Taku dashboard Pangle (China) Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes. |
| 40018 - Media package name does not match the registered one | The package name configured in the code must match the one in the Pangle (China) dashboard. If it was just configured, clear the cache and try again after 5 minutes. |
| 40016 - slot_id and app_id correspondence is invalid | Check the Taku dashboard Pangle (China) Ad Source configuration for spaces or special characters. |
| 40006 - Ad Placement ID invalid | Check the Taku dashboard Pangle (China) Ad Source configuration for spaces or special characters. |
| 0 - null | This error is reported on weak networks. Check the network status or switch networks and try again. |
| Banner display size issue | Before calling load, specify the LayoutParams width and height values for ATBannerView. |
| Null pointer error when playing Pangle (China) Rewarded Video ad | If multiple dex files are generated during packaging, ensure that Pangle (China) related classes are included in classes.dex. |
For more error information, see: (Login required) Pangle (China) Error Codes
● Baidu
| Common Error | Solution |
|---|---|
| Ad cannot be obtained | 1. Rewarded Video takes effect two hours after configuration. 2. Use the test mode in the Taku dashboard's Ad Placement - Advanced Settings for testing. |
| No callback when loading Banner Ad | ATBannerView needs to be first added to the window before initiating a load request. |
For more Baidu error information, see: Baidu Error Codes
● Kuaishou
| Common Error | Solution |
|---|---|
| 40003 - Ad data is empty | If it occurs consistently, contact Kuaishou personnel. |
| 40004 - Video resource cache failed | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| Native ad video black screen or transparent | Enable hardware acceleration in AndroidManifest.xml. |
| 0 - Network error | 1. Check whether the network is normal. 2. Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). |
| 310002 - appId invalid | Check the Taku dashboard Kuaishou Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes. |
| 310004 - packageName does not match the registered packageName | The package name configured in the code does not match the one in the Kuaishou dashboard. |
| 330002 - posId invalid | Check the Taku dashboard Kuaishou Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes. |
| 330004 - posId and registered appId info inconsistent | Check the Taku dashboard Kuaishou Ad Source configuration, and whether a different appId was used to Initialize Kuaishou. |
| Native ad display abnormal | Set fixed width and height values for ATNativeAdView. |
For more Kuaishou error information, see: (Login required) Kuaishou Error Codes
● Sigmob
| Common Error | Solution |
|---|---|
| 200000 - No ad fill | Use Taku's Debug Mode (DebuggerConfig) for testing. |
| Sigmob Splash Ad consistently fails to retrieve ads | Devices on Android 6.0 and above need to dynamically request the READ_PHONE_STATE permission. |
| 500701 - No ad channels have been enabled for the app | Check the app status in the Sigmob dashboard. |
| 500420 - The requested app has closed ad services | Check the app status in the Sigmob dashboard. |
| 500473 - The requested app does not exist | Check the Taku dashboard Sigmob Ad Source configuration. |
| 500424/500422/500482 | 1. Devices on Android 6.0 and above need to dynamically request the READ_PHONE_STATE permission. 2. For Android 10, please refer to Sigmob's FAQ regarding How to fill ads domestically on Android 10. |
| Ads cannot be retrieved on Android 10 | Refer to Sigmob's FAQ regarding How to fill ads domestically on Android 10. |
| After ad loads successfully, there is no playback or subsequent callbacks | Sigmob's callbacks depend on the LocalBroadcastManager library. Check whether the com.android.support:appcompat-v7 dependency is imported (for Androidx, the corresponding one is androidx.localbroadcastmanager:localbroadcastmanager). |
For more Sigmob error information, see: Sigmob Error Codes
● TapTap
| Common Error | Solution |
|---|---|
| 3002 - Network error | Check whether the phone's network environment is normal. |
| 3003 - Interstitial Ad orientation parameter does not match the supported direction of the Ad Placement | Modify the landscape and portrait configuration of the TapTap dashboard Ad Placement. |
| 9999 - Failed to retrieve ad creative: Unknown error | Regular no-fill error. Use Taku's Debug Mode (DebuggerConfig) for testing. |
For more error information, see: TapTap Error Codes
● Jingdong Ads
| Common Error | Solution |
|---|---|
| 2001 - Network error | Check whether the phone's network environment is normal. |
| 2002 - No ad matched | It is recommended to switch to a device registered with a JD account, then initiate the ad request again. |
| 3000 - The tagid and app id fields in the request are inconsistent with the platform configuration | Check whether the placement ID parameters are set correctly. |
| 4041 - Occasional occurrence, retry the request | Occasional occurrence, retry the request. If it occurs frequently, contact JD R&D. |
| 4042, 4043 - Request too frequent, retry the request | No ad matched. It is recommended to re-initiate the ad request. |
For more error information, see: Jingdong Ads Error Codes
● Mintegral
| Common Error | Solution |
|---|---|
| EXCEPTION_RETURN_EMPTY | China version: 1. Ensure that the option Accept APK ad delivery is enabled in the Mintegral dashboard - App Settings. Non-China version: 1. Check whether the VPN is enabled and proxied to the US region. If the issue persists after the above checks, use Taku's Debug Mode for testing. |
| errorCode: 3507 errorMessage: data load failed, errorMsg is Network error,I/O exception | Check whether a proxy is connected and SSL Proxying is enabled. Remove it and try again. |
| Network error,I/O exception | Check whether a proxy is connected and SSL Proxying is enabled. Remove it and try again. |
| EXCEPTION_UNIT_NOT_FOUND | Check the Taku dashboard Mintegral Ad Source configuration (ad unit ID). |
| EXCEPTION_UNIT_NOT_FOUND_IN_APP | Check the Taku dashboard Mintegral Ad Source configuration (ad unit ID). |
| EXCEPTION_SIGN_ERROR | Check the Taku dashboard Mintegral Ad Source configuration (AppKey). |
| EXCEPTION_UNIT_ADTYPE_ERROR | Check the Taku dashboard Mintegral Ad Source configuration (ad format mismatch). |
| resource load timeout | Check whether the network is normal and then retry. |
For more Mintegral error information, see: Mintegral Error Codes
● Huawei
Note: When testing Huawei ads, a Huawei phone or a phone with HMS Core Huawei services must be used.
To test overseas Huawei: A VPN must be enabled.
| Common Error | Solution |
|---|---|
| 3 - NO_AD | Use Taku's Debug Mode for testing. |
| 2 - NETWORK_ERROR | Check whether the network has a VPN enabled. |
| 1 - INVALID_REQUEST | Check the Taku dashboard Huawei Ad Source configuration. |
For more Huawei error information, see: Huawei Error Codes
Previous
How to test ads
Next
Test Tool
Last modified: 2026-07-02Powered by;}.cls-2{fill:%230868f7;}.cls-3{fill:url(%23未命名的渐变_44);}.cls-4{fill:%23333;}%3c/style%3e%3clinearGradient%20id='未命名的渐变_8'%20x1='33.73'%20y1='100.61'%20x2='-0.03'%20y2='-1.06'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20offset='0'%20stop-color='%237ae9fb'/%3e%3cstop%20offset='0.67'%20stop-color='%232b90f8'/%3e%3cstop%20offset='1'%20stop-color='%230868f7'/%3e%3c/linearGradient%3e%3clinearGradient%20id='未命名的渐变_44'%20x1='27.86'%20y1='18.67'%20x2='68.36'%20y2='22.22'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20offset='0'%20stop-color='%235ac7f2'/%3e%3cstop%20offset='1'%20stop-color='%230868f7'/%3e%3c/linearGradient%3e%3c/defs%3e%3cpath%20class='cls-1'%20d='M29,28.74V81.91l-9.51-3.68v0L8.52,74A7.17,7.17,0,0,1,4,67.32V24.54A3.76,3.76,0,0,1,9.08,21Z'/%3e%3cpath%20class='cls-2'%20d='M68.09,78.07a13.15,13.15,0,0,1-17.9,12.06L29,81.91h0V28.74L50.19,37A13.17,13.17,0,0,0,68.08,25.3h0Z'/%3e%3cpath%20class='cls-3'%20d='M68.08,25.3a13.19,13.19,0,0,1-6.73,10.87A13.09,13.09,0,0,1,50.19,37L29,28.74V6A3.76,3.76,0,0,1,34.1,2.52l25.59,9.91A13.22,13.22,0,0,1,68.08,25.3Z'/%3e%3cpath%20class='cls-4'%20d='M129.06,81.76a4.33,4.33,0,0,1-3.19-1.31,4.4,4.4,0,0,1-1.31-3.24V56.86H97.65V77.21a4.36,4.36,0,0,1-1.35,3.2A4.68,4.68,0,0,1,93,81.76a4.32,4.32,0,0,1-3.19-1.31,4.37,4.37,0,0,1-1.32-3.24V27.27A4.58,4.58,0,0,1,89.83,24a4.59,4.59,0,0,1,7.82,3.27V48.15h26.91V27.27A4.58,4.58,0,0,1,125.91,24a4.59,4.59,0,0,1,7.82,3.27V77.21a4.37,4.37,0,0,1-1.36,3.2A4.65,4.65,0,0,1,129.06,81.76Z'/%3e%3cpath%20class='cls-4'%20d='M163.77,81.66c-6.57,0-11.76-1.92-15.44-5.7s-5.54-9.07-5.54-15.74a26.76,26.76,0,0,1,2.09-10.43,17.72,17.72,0,0,1,6.67-8.06,19.15,19.15,0,0,1,10.68-2.95,19,19,0,0,1,10.46,2.8,18.7,18.7,0,0,1,6.55,7.36,22.53,22.53,0,0,1,2.36,10.28A4.51,4.51,0,0,1,177,63.77H152.23a10.8,10.8,0,0,0,3.49,6.65c2,1.68,4.88,2.52,8.66,2.52a22.25,22.25,0,0,0,7.54-1.21c.74-.3,1.55-.67,2.37-1.07a3.75,3.75,0,0,1,1.84-.4,4.09,4.09,0,0,1,3,1.15,4,4,0,0,1,1.12,3,4.38,4.38,0,0,1-2.58,3.82,32.34,32.34,0,0,1-6.36,2.61A28.67,28.67,0,0,1,163.77,81.66ZM172.4,55.9a9.72,9.72,0,0,0-1.63-4.56A9.9,9.9,0,0,0,167,48a10.38,10.38,0,0,0-4.64-1.14,12,12,0,0,0-4.77,1.06,9.54,9.54,0,0,0-4.89,5.66,11.78,11.78,0,0,0-.51,2.3Z'/%3e%3cpath%20class='cls-4'%20d='M193,81.64a4.49,4.49,0,0,1-4.51-4.55V27.28A4.58,4.58,0,0,1,189.84,24a4.48,4.48,0,0,1,3.28-1.36A4.36,4.36,0,0,1,196.35,24a4.46,4.46,0,0,1,1.31,3.31V77.09a4.34,4.34,0,0,1-1.35,3.2A4.67,4.67,0,0,1,193,81.64Z'/%3e%3cpath%20class='cls-4'%20d='M263.79,81.71a5.7,5.7,0,0,1-4.2-1.74,5.76,5.76,0,0,1-1.73-4.19V27.37a4.58,4.58,0,0,1,1.35-3.27A4.59,4.59,0,0,1,267,27.37V72.53h24a4.58,4.58,0,0,1,3.27,7.82A4.66,4.66,0,0,1,291,81.71Z'/%3e%3cpath%20class='cls-4'%20d='M424.48,81.74a4.71,4.71,0,0,1-2.71-.88,5.43,5.43,0,0,1-1-1l-.07-.09-12.41-17-5.41,5v9.44a4.31,4.31,0,0,1-1.36,3.19,4.66,4.66,0,0,1-3.3,1.36A4.29,4.29,0,0,1,395,80.42a4.36,4.36,0,0,1-1.32-3.23V27.37A4.58,4.58,0,0,1,395,24.1a4.52,4.52,0,0,1,6.58.12,4.54,4.54,0,0,1,1.24,3.15V56.31l17.72-16.38.05,0a4.8,4.8,0,0,1,2.94-1.11,4.4,4.4,0,0,1,3.27,1.2,4.57,4.57,0,0,1,1.2,3.27,4.44,4.44,0,0,1-.77,2.33,7.45,7.45,0,0,1-1.43,1.65l-11,9.64,13.34,17.68a5,5,0,0,1,1,2.71,4.12,4.12,0,0,1-1.36,3.24A4.64,4.64,0,0,1,424.48,81.74Z'/%3e%3cpath%20class='cls-4'%20d='M317.93,81.76a21.5,21.5,0,1,1,21.17-21.5A21.37,21.37,0,0,1,317.93,81.76Zm0-34.1a12.61,12.61,0,1,0,12.42,12.6A12.52,12.52,0,0,0,317.93,47.66Z'/%3e%3cpath%20class='cls-4'%20d='M212.18,101.22a4.12,4.12,0,0,1-3.05-1.26,4.17,4.17,0,0,1-1.26-3.1V43.34a4.37,4.37,0,0,1,1.3-3.14,4.26,4.26,0,0,1,3.13-1.3,4.19,4.19,0,0,1,3.1,1.26,4.32,4.32,0,0,1,1.26,3.16,20.77,20.77,0,0,1,13-4.54,21.51,21.51,0,0,1,0,43,20.51,20.51,0,0,1-13-4.57V96.86a4.15,4.15,0,0,1-1.3,3.06A4.5,4.5,0,0,1,212.18,101.22Zm17.43-53.63c-6.23,0-12.93,4.11-12.93,12.72a12.73,12.73,0,0,0,25.46,0A12.71,12.71,0,0,0,229.61,47.59Z'/%3e%3cpath%20class='cls-4'%20d='M365.76,81.76a21.5,21.5,0,1,1,21.18-21.5A21.37,21.37,0,0,1,365.76,81.76Zm0-34.1a12.61,12.61,0,1,0,12.42,12.6A12.52,12.52,0,0,0,365.76,47.66Z'/%3e%3c/svg%3e)
Outline