Menu

Error code

1. Taku error code information description

The following is a summary of the error code:

Error codeNote
2001(GDPR is not set) GDPR consent not set
Suggestion:
Due to the data protection area (EU, etc.), please set the data before initialization To collect opinions, please refer to GDPR document
1001(Invalid strategy) Placement strategy invalid
Suggestion:
Check Taku Do the appid, appkey and placement id passed in during initialization match?
1003Ad loading fails, there will be two situations:
Suggestion:
1. Waterfall ad configuration - details Please check the background log analysis. If it is in the development stage, please check log output
2. error msg contains Bid request have failed ——The bidding failed. For details, please implement the bidding agent to view didFailBiddingADSourceWithPlacementID
1005(No ad display) No ad found when trying to show ad
Suggestion:
Before calling the display ad, please first determine whether the ad slot has been prepared. You can check the judgment API of the corresponding ad type to judge
1006(show too frequently) Ad show too frequent
Suggestion:
Please try to display again later. You can set a display interval of a little time to avoid this problem. You can also use the aggregation management in the Taku background to set the display interval.
1007(display within hours Maximum number of impressions) Ad show too many time within the same hour
Suggestion:
In the case of testing, you can increase the number of impressions per hour. If it has been published, the code is considered normal. Case.
1008(Show more than the maximum number of impressions in a day) Ad show too many time within the same day
Suggestion:
In the case of testing, you can increase the number of impressions per hour, if you have If released, this code is considered normal.
1009(The corresponding Adapter is not imported) The adapter not found
Suggestion:
Please integrate the adapter of the corresponding advertising platform according to the information printed in the log
10010(Ad loading timeout) Ad loading timeout
Suggestion:
Please change the network of the test device and try loading ads again
1013(The SDK of the third-party platform is not imported or the wrong version is imported. Please correspond to AnythinkiOS and sub-package versions) Third party SDK not imported or wrong version's being used
Suggestion:
Please refer to our background download interface to select the corresponding adapter version for integration
1014(Invalid App ID, App Key Or Placement ID) Invalid parameters encountered (App ID, App Key or Placement ID being nil)
Suggestion:
Please check whether the above information is correct and accurately fill in the initialization and ad loading
1015(Ad delivery not turned on for the placement) Ad delivery not turned on for the placement
Suggestion:
Please open the corresponding advertising slot in the Taku backend management system
1017(advertising position strategy The placement strategy does not contain any ad sources, please check the mediation configuration in Taku.
Suggestion:
Please add the media to be loaded in the corresponding ad slot Ad source, create an ad in the background of the advertising platform, and fill in the ad id into the ad slot
1018 (Ad sources have been filtered)Ad sources are filtered, no ad source is currently available
Suggestion:
The advertising source has been filtered. It may be filled in the filtering API during initialization. Check whether it is filled in
1019(The placementID load too frequently within the specified times period after the previous load failure
Suggestion:
Please wait at least 10s after the previous request failed before making a new request
1020(During the specified time period, ads The placement load too many times within the specified time period
Suggestion:
Please adjust the number of times the ad slot is loaded to avoid excessive loading within a period of time
1029(Debug mode, the placement strategy does not contain any ad sources, please check the debugger configuration) The placement strategy does not contain any ad sources, please check the debugger configuration in [ATAPI setDebuggerConfig]
Suggestion:
You can check whether the incoming ifa is the idfa of the device, and secondly check whether the debugging mode platform used is wrong. If there is no problem above, you can give us feedback and we will investigate.
1030(Ad source is filtered and not filled) Ad source not filled, cause by customize fillter.
Suggestion:
The ad source ad is set to be filtered by the custom filter configuration, resulting in no padding being loaded. You can check the settings of the initialized custom filter

2. Network platform error code

Three-party platform error code instructions

Previous
Third-party AD error code
Next
Integration Checklist
Last modified: 2025-05-30Powered by