Menu

Error code description

1.Taku error code information description

Error codeDescription
10001Invalid appid or app key, please check
1. AppId or AppKey is wrong, Check the AppId and AppKey passed in when initializing Taku SDK in the code
Call ATSDK.setNetworkLogDebug(true); Filtering in Logcat anythink is possible To view the parameters currently passed into the SDK, please check these parameters
10003Invalid app
1.AppId error, Check the initialization Taku in the code AppId passed in when SDK
2.Taku advertising slot Id does not match AppId, Check The PlacementId passed in when calling load in the code
calls ATSDK.setNetworkLogDebug(true); Filter anythink in Logcat to view the parameters currently passed into the SDK. Please check these parameters
10004Invalid placement
1.Taku advertising slot Id is wrong, Check the PlacementId passed in when calling load in the code
Call ATSDK.setNetworkLogDebug(true); in Logcat Filter anythink to view the parameters currently passed into the SDK, please check these parameters
9999Generally the network An error occurred in the request, check whether the network status is normal
9990The status returned by the Http interface request is wrong. You need to contact your Taku colleagues to check the error information
9991The business code returned by the interface request is wrong. You need to contact your Taku colleagues to check the error information
9992GDPR level has been set Low, check whether the FORBIDDEN level is set manually
2001Ad loading timeout, check whether the current test advertising source is an overseas platform and whether the mobile network has been bypassed
2002Taku's SDK package is incompletely imported and the Adapter package of the third-party advertising manufacturer is missing. (anythink_network_*.aar), confirm whether the SDK package required by the aggregated third party has been imported according to the instructions
2003The number of impressions of the current ad slot has reached the upper limit. You need to confirm whether Taku's background configuration limits the number of impressions of this ad slot
2004The current ad slot is in a non-display period. You need to confirm whether Taku's background configuration limits the ad slot. Display interval
2005This ad slot is in the loading stage. After a request is made for the same ad slot, the ad slot cannot initiate the next load before receiving a callback of successful or failed loading. Please wait for the callback of successful or failed loading
2006 Check whether the SDK package imported into the third-party advertising platform is complete. If it is complete, check whether the imported version is consistent with the version specified on GitHub. Otherwise, the third-party SDK package needs to be completed
2007Usually occurs in callbacks on load failure Immediately initiate ad loading. It is forbidden to initiate ad loading immediately in the callback of loading failure. A certain time interval must be met before the ad loading can be initiated since the last time the ad slot failed to load. Please delay the time of calling ad loading
2008After the same advertisement fails to load, it is prohibited to immediately call the load method in the callback of the failed load to retry. Please delay for more than 10 seconds before attempting again
2009 The number of times the ad slot is loaded reaches the upper limit within a certain time interval
3001Policy 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 (cannot contain spaces)
Call ATSDK.setNetworkLogDebug(true); Filter anythink in Logcat to view the parameters currently passed into the SDK, please check these Parameters
3002One of the passed in appid, appkey, and placementid is a null character
CallATSDK.setNetworkLogDebug(true); Filter anythink in Logcat to view the parameters currently passed into the SDK. Please check these parameters
3003The ad slot does not match the API called. For example: Banner's ad slot calls the rewarded video API to load ads
4001Usually occurs when the third-party advertising platform returns an error resulting in no ad filling: 1. Can Get complete error information through AdError.getFullErrorInfo(), and check the error code and error information of the advertising platform through platformCode and platformMsg. Please check the third-party advertising platform error code & FAQ for troubleshooting. Which advertising platform the advertisement belongs to can be checked through the SDK Log acquisition 2. It is recommended to call ATSDK.setNetworkLogDebug(true); open the SDK log to obtain more detailed information 3. Advertising testing can be carried out through this testing guide
4002Context’s context has been destroyed. You need to re-create the corresponding ad type object and re-initiate ad loading
4003The status of this advertising slot has been closed. Check whether the status switch of this advertising slot is turned on in the Taku background
4004This ad slot does not have advertising source information configured in the Taku backend. You need to go to the Taku backend - aggregation management to add the ad source of a third-party advertising platform to the ad slot
4005Advertising slot All advertising sources under are filtered. The possible reasons are as follows:
1. Check whether the display of the advertising source is set in the Taku background. Upper limit, Display interval
2. If only configured Head bidding advertising source, when the inquiry fails, the head bidding advertising source will be filtered
4006Video playback failed, refer to 4001 error code Conduct troubleshooting
4007Ad source bidding failed, refer to 4001 error code Conduct troubleshooting
4008Advertising sources are filtered due to custom filtering logic in the developer's code. If the filtering does not meet expectations, please troubleshoot the custom filtering logic
4009In debug mode, this ad slot does not have advertising source information configured



2. Third-party advertising platform error Code&FAQ (Frequently Asked Questions)

Meta

(Recommended country with high VPN filling rate: United States)

Common mistakesSolution
1001 - No FillUse Taku's Debug mode (DebuggerConfig) for testing
1000 - Network ErrorCheck whether to circumvent the wall

For more Meta error information, please see: Meta error code


Meta Load Fail can be debugged through the following steps

1. Make sure Facebook is installed on the device and logged in

2 .Add a Meta advertising source of header bidding type

Note: You must use header bidding advertising sources, ordinary advertising sources are not supported

3. Confirm that the introduced Meta version corresponds to the TakuSDK version

4. Confirm the Application number (App ID) and Placement Number (Placement ID) Consistent

The correct configuration example is as follows:

If there is no filling after the advertisement space request, call ATSDK. setNetworkLogDebug (true); Open the Taku log and filter the keyword "anything | HeadBidding" to view the log


If the log format is as follows: facebook_config_guide2 If there is a Meta in the HeadBidding Failure List, it means that the Meta bidding has failed

5. Call the following code to open the Bidding test mode:

//5.9.96 and above versions
//f669f2b7137d82b9 To test the Android ID of the device
ATSDK.setDebuggerConfig(this, "f669f2b7137d82b9", null);

//Below version 5.9.96
//f669f2b7137d82b9 To test the Android ID of the device
ATSDK.setBiddingTestDevice("f669f2b7137d82b9");

If the bidding is successful after turning on the Bidding test mode, and the ad is filled successfully, the Meta ad is successfully connected


Admob

(Recommended country with high VPN filling rate: United States)

Common mistakesSolution Solution
3Use Taku's Debug mode (DebuggerConfig) for testing
2Check whether to circumvent the wall
Check the Taku background Admob ad source configuration
01 , Use Taku's Debug mode (DebuggerConfig) for testing
2. Check whether the wall is circumvented

For more Admob error messages, please see: Admob error code


AppLovin

(Recommended country with high VPN filling rate: United States)

Common mistakesSolutions
204Use Taku's Debug mode (DebuggerConfig) for testing

For more AppLovin error information, please see: AppLovin error code


Mintegral

(Country with high VPN filling rate recommended for foreign versions: the United States)

Common errorsSolutions
EXCEPTION_RETURN_EMPTYChinese version:
1. Ensure Mintegral backend -Whether to accept apk advertising
Non-China version:
is turned on in the application settings 1. Check whether to circumvent the firewall or VPN to the United States

If there are still problems after the above checks, use Taku's DebuggerConfig Test
errorCode: 3507 errorMessage: data load failed, errorMsg is Network error,I/O exception Check whether the proxy is connected and SSL Proxying is enabled, remove it and try again
Check whether it is connected Proxy, and enable SSL Proxying, remove it and try again
EXCEPTION_UNIT_NOT_FOUNDCheck Taku background Mintegral ad source configuration (ad unit id)
EXCEPTION_UNIT_NOT_FOUND_IN_APPCheck the Taku background Mintegral advertising source configuration (ad unit id)
EXCEPTION_SIGN_ERRORCheck the Taku background Mintegral ad source configuration ( AppKey)
EXCEPTION_UNIT_ADTYPE_ERRORCheck the Taku background Mintegral advertising source configuration (ad format does not match)
resource load timeoutCheck whether the network is normal and try again


Q :The video plays with a white screen, or the debug package plays normally, but the release package plays abnormally

A:Check whether resource optimization is enabled during packaging:  shrinkResource=true



Add a keep.xml in the res/raw path with the content Add the following resources to the whitelist for:


Add the following resources to the whitelist:
R.string.mintegral_*
R.drawable.mintegral_*
R.layout.mintegral_*
R.id.mintegral_*

For more Mintegral error messages, please see: Mintegral error code


Tencent Advertising

Common mistakesSolution
6000 - 102006No suitable ads were matched. Retrying is prohibited, otherwise the system policy may be triggered, resulting in a decrease in traffic revenue
Test integration can be tested using Taku's debug mode (DebuggerConfig)
5002 - Video material download errorCheck whether it has been correctly adapted to Android 9 and above systems according to the integration document (network_security_config.xml)
The image in the advertisement cannot be displayedCheck whether it has been correctly adapted according to the integration document Equipped with Android 9 and above systems (network_security_config.xml)
Native advertising video black screen or transparent displayEnable hardware acceleration in AndroidManifest.xml
5004 - No suitable advertisement was matchedIn this case, multiple retries of requesting advertisements are prohibited, otherwise it may affect The system’s evaluation of your traffic affects the monetization effect
Test integration can be tested using Taku’s debug mode (DebuggerConfig)
5004 - No ads1. Check whether it has been correctly adapted to Android 9 and above systems according to the integration document (network_security_config.xml)
2. Check the Taku background Tencent advertising source configuration (whether template rendering 2.0)
5006 - Package name verification error, the package name of the current App is the same as the one filled in when registering media on Guangdiantong official website The package names are inconsistent, so no ads are returnedThe package name configured in the code must be consistent with that of the Guangdian Tong backend
5010 - Advertising style verification failed, please check whether the ad slot and interface usage are consistentCheck the Taku background Tencent advertising source configuration (whether Template rendering, full-screen video, etc.)
2001 - Initialization errorDeveloper self-check parameter issues
1. Do not disassemble the SDK package of Tencent Ads
2. Check the Taku background Tencent Ads advertising source configuration
3. If there is no problem with the parameters, please confirm whether you are using a real machine and do not use the simulator for testing
4004-Open screen ad container is not visible1. Check whether the container is hidden or blocked
2. If you directly execute show in acitvity's oncreate, it will need to be delayed. It is recommended to use the showAd method. Please use the Handler of the main thread. The postDelay delay is 10ms. Try calling the showAd method later
3. Add container.removeAllViews(); call before display
102006-No ads that meet the price or experience requirements were foundIt is recommended to adjust the price settings of the floor price/target price appropriately, or go to the platform Advertising Center Checks and Verifies Blocking Rules

For more error information on Tecent Ads, please refer to:

1、Tencent Ads error code
2、Tencent Ad serror code 6000


Chartboost

(Recommended countries with high VPN filling rate: United States)


Common mistakesSolution
NO_AD_FOUNDTesting with DebuggerConfig from Taku

For more error messages on Chartboost, please check：Chartboost error code

Tapjoy

(Recommended countries with high VPN filling rate: United States)


Common mistakesSolution
Unable to obtain advertisementTesting with DebuggerConfig from Taku

ironSource

(Recommended countries with high VPN filling rate: Israel)


Common mistakesSolution
508 - initISDemandOnly() had failedWhen configuring the Taku backend advertising source, an Instance ID must be configured. Check if the Ironsource backend account has Instance permission. If not, please contact Ironsource personnel
510Contact Ironsource personnel

For more error information on Ironsource, please review：Ironsource error code

UnityAds

(Recommended countries with high VPN filling rate: United States)

For more error information on UnityAds, please refer to：UnityAds error code

Vungle

(Recommended countries with high VPN filling rate: United States)


Common mistakesSolution
NO_SERVETesting with DebuggerConfig from Taku
PLACEMENT_NOT_FOUNDCheck Taku backend Vungle ad source configuration
CONFIGURATION_ERROR1. Check if the network is functioning properly

2. Check Taku backend Vungle advertising source configuration
UNKNOWN_ERRORContact relevant personnel from Vungle
After preloading the incentive video and insert screen advertisement of Vungle and successfully playing one of Vungle's advertisements, the isAdReady() of the other advertisement returned false

Vungle's incentive videos and insert ads share the same advertising source resource

For more error information on Vungle, please refer to：Vungle error code

AdColony

(Recommended countries with high VPN filling rate: Finland)


Common mistakesSolution
onRequestNotFilled!Testing with DebuggerConfig from Taku


Bigo

(Recommended countries with high VPN filling rate: Singapore)


Common mistakesSolution
3507-EXCEPTON_UNIT_BIDDNG_TYPE_ERRORBidding type error, such as loading Bidding ad space using Waterfull advertising code or loading Waterfull ad space using bidding code. Please maintain consistency and check the topon backend configuration and advertising platform configuration. For more details, please consult the advertising platform
1000 - ERROR_CODE_UNINITIALIZEDIndicates that the advertising SDK did not complete initialization when requesting advertising. Please ensure that the initialization of the advertising SDK is completed before initiating the advertising request.
1001 - ERROR_CODE_INVALID_REQUESTThis advertisement request is invalid. Please check if your App Id or Slot Id has been passed in correctly. For banner type advertisements, please ensure that at least one AdSize has been passed in
1002 - ERROR_CODE_AD_DISABLEIndicates that the current advertising Slot Id is not available, which is usually caused by the Bigo Ads platform being configured to disable this advertising location.
1003 - ERROR_CODE_NETWORK_ERRORA network exception occurred during the advertising request process. Please ensure that the current device's network connection is unobstructed.
1004 - ERROR_CODE_NO_FILLThis indicates that the advertisement request was successful, but the advertisement did not fill in the return. If you are using a formal Slot ID, we will not be able to manually fill in the fill rate for this Slot ID. We suggest that you use a test advertisement during the early validation process.
1005 - ERROR_CODE_INTERNAL_ERRORIndicates that some internal errors have occurred, possibly due to the advertising server receiving an invalid request or an unknown exception occurring during the processing of the request.
1006 - ERROR_CODE_ASSETS_ERRORThis indicates that there has been a shortage of advertising material resources or an abnormal situation during the download process.

cjs(Pangle)

(Recommended countries with high VPN filling rate for foreign versions: South Korea, Japan, Singapore)


Common mistakesSolution
4201 - No initializer1. Check if the ABI architecture has been restricted according to the integration document

2. Check if the com. android. support: appcompat v7 dependency or androidx. appcompat: appcompat dependency has been added according to the integration documentation
-7- Open screen advertisement image loading failedCheck if the Android 9 and above systems have been correctly adapted according to the integration documentation（network_security_config.xml）
No result callback after loadingCheck if the Android 9 and above systems have been correctly adapted according to the integration documentation（network_security_config.xml）
The image in the advertisement cannot be displayedCheck if the Android 9 and above systems have been correctly adapted according to the integration documentation（network_security_config.xml）
Black screen during video playbackCheck if WAKE is configured in the Manifest_ LOCK permission
20001The request was not filled due to the lack of suitable advertisement returns, which is a normal situation

Please try changing the device for verification, do not use the emulator for testing, or try again later. If none of the issues can be resolved, please check the error code of the pangolin SDK for troubleshooting or inquire about the bill of lading on the pangolin platform



Testing integration can use the testing mode in Taku backend advertising space - Advanced settings
40029Check the rendering type of pangolin code bits, and ensure that the configuration of the Taku backend pangolin advertising source is consistent with the configuration of the pangolin backend
400251. Check if the system time of the testing equipment is the current correct time

2. Check if the ABI architecture has been restricted according to the integration document

3. If confusion is enabled, please check the confusion rules provided in the downloaded SDK compressed package

4. Download the SDK from the pangolin backend and replace the pangolin SDK provided by Taku (open_cd_sdk_ *. aar)
40021- APK signature sha1 value inconsistent with media platform inputThe signature of the application must be consistent with the signature configured in the pangolin backend. If it has just been configured, please clear the cache and try again in 5 minutes
40019- Media configuration adtype and request inconsistentCheck the Taku backend pangolin advertisement source configuration. If it has just been configured, please clear the cache and try again in 5 minutes
40018- Media package name inconsistent with inputThe package name configured in the code must be consistent with the pangolin backend. If it has just been configured, please clear the cache and try again in 5 minutes
40016- slot_ ID and app_ The ID correspondence is illegalCheck the Taku backend pangolin advertising source configuration for any spaces or special matches
40006- Illegal advertising space IDCheck the Taku backend pangolin advertising source configuration for any spaces or special matches
0 - nullThis error will be reported when the network is weak. Please check the network status or switch networks to try again
There is an issue with the size displayed by the bannerBefore calling load, it is necessary to specify the LayoutParams width and height value of ATBannerView
The motivational video advertisement on the headline has a null pointer during playbackIf multiple dexes will be typed during packaging, please ensure that the class related to the headline is entered into the classs.dex

For more error messages on Pangle, please refer to: (login required) Pangle error code

Uniplay


Common mistakesSolution
3000/3001Contact Uniplay related operations personnel
4006/4007/4008/4009Missing Manifest related configuration for Uniplay
4011Lack of relevant permissions. Please refer to the permissions configured in Uniplay's Manifest for application
AD NOT FOUNDContact Uniplay related operations personnel
There has been no callback when loading Banner advertisementsATBannerView needs to be added to the window first before initiating a load request

For more error messages on Uniplay, please refer to: (login and download required) Uniplay error code

BaiDu


Common mistakesSolution
Unable to obtain advertisement1. Incentive videos require contacting Baidu to open a whitelist

2. Test using the testing mode in Taku backend advertising space - advanced settings
There has been no callback when loading Banner advertisementsATBannerView needs to be added to the window first before initiating a load request

For more Baidu error information, please see：Baidu error code

Nend

(Recommended countries with high VPN filling rate: Finland)


Common mistakesSolution
Unable to obtain advertisementTesting with DebuggerConfig from Taku


KuaiShou


Common mistakesSolution
40003- Empty advertising dataBe sure to contact relevant personnel of Kwai
40004- Video resource cache failureCheck if the Android 9 and above systems have been correctly adapted according to the integration documentation（network_security_config.xml）
Native advertising videos with black screen or transparent displayEnable hardware acceleration in AndroidManifest.xml
0- Network error1. Check if the network is functioning properly

2. Check if the Android 9 and above systems have been correctly adapted according to the integration documentation（network_security_config.xml）
310002- invalid appIdCheck the Taku background Kwai advertising source configuration. If it is just configured, please clear the cache and try again in 5 minutes
310004- The packageName does not match the registered packageNameThe package name configured in the code is inconsistent with the Kwai background
330002- invalid posIdCheck the Taku background Kwai advertising source configuration. If it is just configured, please clear the cache and try again in 5 minutes
330004- posId does not match the registered appId informationCheck the Taku background Kwai advertising source configuration, and whether you have used different appids to initialize Kwai
Abnormal display of native advertisementsSet a fixed width and height value for ATNativeAdView


Q:Video playback with white screen, or debug package playing normally but release package playing abnormally

A:Check if resource optimization is enabled during packaging: shrinkResource=true



Add a keep.xml file under the res/raw path, with the following content：



Add the following resources to the whitelist：
R.string.ksad_*
R.drawable.ksad_*
R.layout.ksad_*
R.id.ksad_*
R.style.ksad_*
R.color.ksad_*
R.attr.ksad_*
R.dimen.ksad_*

For more Kwai error information, please see: (login to download) Kwai error code

Sigmob


Common mistakesSolution
200000- No advertising fillingTesting with DebuggerConfig from Taku
Sigmab has been unable to obtain advertisements since opening the screenDevices above 6.0 require dynamic application for READ_ PHONE_ DATE permission
500701- The app has not opened any advertising channelsCheck the status of the Sigmab backend application
500420- The requested app has disabled advertising servicesCheck the status of the Sigmab backend application
500473- The requested app does not existCheck Taku backend Sigmab ad source configuration
500424/500422/5004821. Devices above 6.0 require dynamic application for READ_ PHONE_ DATE permission

2. Please refer to the Sigmab FAQ on how to fill in advertisements for Android 10 in China容
Android 10 cannot obtain advertisementsReference Sigmab FAQ Content on how to fill in advertisements for Android 10 in China
No playback and subsequent callback after successful advertisement loadingThe callback for Sigmab needs to rely on the LocalBroadcastManager library

Check if the dependency on com. android. support: appcompat v7 has been introduced

(Android x corresponds to androidx. local broadcastmanager: local broadcastmanager)

For more error information on Sigmab, please refer to：Sigmob error code

HMS

Attention: When testing Huawei advertisements in testing mode, Huawei phones must be used and must be crossed over walls. When using Huawei's official advertising space, it is necessary to use Huawei's overseas version of the phone


Common mistakesSolution
3 - NO_ADTesting with DebuggerConfig from Taku
2 - NETWORK_ERRORCheck if the network has climbed over the wall
1 - INVALID_REQUESTCheck the Huawei advertising source configuration in the Taku backend

For more Huawei (HMS) error messages, please check：HMS error code


YouKeYing

Common mistakesSolution
1110- App ID exceptionPlease self check if the AppID and PosID match
1111- Resource bit (PosID) exception, please check if the AppID and PosID matchPlease self check if the AppID and PosID match
1112- Advertising template not matchedSuggest checking if the SDK version supports the requested advertising style

For more information on YouKeYing, please check the error message：YouKeYing error code


QuMeng

Common mistakesSolution
1000001- No more ADs from poolNo ads, try again later, or test on another device
UNKNOWN_ERROR - https:\/\/api.jietuhb.com\/v6\/json1. The package name configured in the code must be consistent with that of Qumeng backend
2. Capture the packet to view the error information returned by the error reporting interface, and conduct troubleshooting based on the error information.

For more information on Qumeng, please check the error message：QuMeng error code

Amazon

Common mistakesSolution
NO_FILL|No Ad returned by AdServer. No ads, try again later

For more information on Amazon, please check the error message：(login required) Amazon error code










Previous
Callback information description
Next
Advanced setup instructions
Last modified: 2025-05-30Powered by