The following is a summary of the error code:
Error code | Note |
---|---|
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 TopOn Do the appid, appkey and placement id passed in during initialization match? |
1003 | Ad 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 TopOn 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 TopOn backend management system |
1017 | (advertising position strategy The placement strategy does not contain any ad sources, please check the mediation configuration in TopOn. 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 |
Common mistakes | Solution |
---|---|
1001 - No Fill | No padding. The most common reasons are that the user is not logged into the Facebook app when testing your mobile app, or the user is not logged into the Facebook mobile website when testing your mobile website |
1000 - Network Error | Network problem, check whether to circumvent the firewall |
For more Facebook error messages, please see: Facebook error codes
Common errors | Solutions |
---|---|
0 | 1. Use TopOn background advertising space and use Debug mode for testing 2. Check whether the wall is bypassed |
1 | Invalid ad request; check ad source Parameter configuration |
2 | The ad request failed due to network connectivity. Check whether to circumvent the wall |
3 | The ad request was successful, but no ads were returned due to lack of inventory. Use TopOn background advertising slots and use Debug mode for testing |
For more Admob error messages, please see: Admob error code
Common Errors | Solutions |
---|---|
40029 | Check the rendering type of the Pangolin code bit. The configuration of the TopOn background pangolin advertising source needs to be consistent with the Pangolin background The configuration remains consistent |
40025 | Go to the pangolin backend to download the SDK and replace the pangolin SDK provided by TopOn |
40019 - The media configuration adtype is inconsistent with the request | TopOn background pangolin advertising source configuration problem |
40018 - The media package name is inconsistent with the entry | The package name configured in the code is inconsistent with the Pangolin backend |
40016 - The corresponding relationship between slot_id and app_id is illegal | TopOn background pangolin advertising source configuration Problem |
40006 - The advertising slot ID is illegal | TopOn background pangolin advertising source configuration problem |
102 - not matched Main template: The main template is not downloaded locally. It is normal to occasionally request ads for the first time | You can try to request ads a few more times |
103 - Subtemplate not matched: Occasionally, in the early stage of access, the template is not matched. It will not appear after the SDK downloads the template successfully. | You can request a few more ads to try |
107 - Template rendering times out without callback. Possible reasons are 1. Network reasons or 2. Hardware reasons. Therefore, the rendering fails. You can change the mobile phone or test the network environment. | You can request a few more ads to try |
For more pangolin error information, please see: (login required) TT(CSJ) error code
For Pangle error information, please check: Pangle error code
Error code | msg | Description | Solution |
---|---|---|---|
-1 | EXCEPTION_RETURN_EMPTY | No ad filling, which may cause Reasons: 1. The advertisements you obtain during the test period are all official advertisements of Mintegral, so they will be affected by the intelligent optimization of the algorithm. If a large number of advertisements are loaded and displayed for a period of time, there may be no advertisements filled after a period of time. | Domestic version: 1. Make sure Mintegral background-application settings is turned on Whether to accept apk advertising Overseas version: 1. Check whether to bypass the wall or VPN to the United States Above If there is still a problem after checking, use TopOn background advertising slot and use Debug mode to test |
-1201 | EXCEPTION_UNIT_NOT_FOUND | The unitID does not exist/entered incorrectly | TopOn background Mintegral advertising source configuration problem |
-1203 | EXCEPTION_UNIT_NOT_FOUND_IN_APP | The appID and unitID do not match | TopOn background Mintegral advertising source configuration problem |
-1205 | EXCEPTION_UNIT_ADTYPE_ERROR | Incoming The unitID advertising type does not match | TopOn background Mintegral advertising source configuration problem |
For more Sigmob error information, please see: Mintegral error code
Error code | Description |
---|---|
4013 | The system does not support it. Native video template ads only support iOS 9 and above systems |
4020 | window is empty, you need to add the window attribute in AppDelegate |
5006 | Illegal package name verification The package name configured in the codeis inconsistent with the backend of Guangdiantong |
6000 | Unknown error, contact Tencent Advertising Business colleagues for assistance in troubleshooting. |
For more Tencent advertising error information, please see: Tencent Ad error code
Common mistakes | Solution |
---|---|
204 | No padding, you can open the test mode through the Applovin background for testing |
For more AppLovin error information, please see: AppLovin error codes
Common mistakes | Solution |
---|---|
Cannot get ads | Enable test mode through Vungle background for testing |
After preloading Vungle's rewarded videos and interstitial ads successfully, one of the Vungle ads was played, and the isAdReady() of the other ad returned false | Vungle's rewarded videos and interstitial ads share the same advertising source resources |
For more Vungle error messages, please see: Vungle error code
Common mistakes | Solutions |
---|---|
40003 - Advertising data is empty | If necessary, please contact us Kuaishou related personnel |
310002 - appId is invalid | TopOn background Kuaishou advertising source configuration problem |
310004 - packageName and registration Inconsistent packageName | Package configured in code NameInconsistency with Kuaishou backend |
330002 - posId is invalid | TopOn background Kuaishou advertising source configuration problem |
330004 - posId is inconsistent with the registered appId information | TopOn background Kuaishou advertising source configuration issue |
For more Kuaishou error messages, please check: (requires login to download) Kuaishou error code
Common mistakes | Solutions |
---|---|
200000 - no ad filling | Add test device through Sigmob backend for testing |
500420 - The requested app has turned off advertising services | Add test device for testing through Sigmob background |
500473 - Requested app Does not exist | TopOn background Sigmob advertising source configuration problem |
500701 - app has not opened any advertising channels | Check Sigmob background application status |
For more Sigmob error information, please see: Sigmob error code
More Baidu Please check the error message: (Requires login to download) Baidu error code
For more Bigo_Ads error information, please see: Bigo_Ads error code
For more UnityAds error messages, please see: UnityAds error code
More Chartboost errors For information, please see: Chartboost error codes
More For more Ironsource error messages, please see: Ironsource error codes
For more Oneway error messages, please see: Oneway error code
More For StartApp error messages please view: StartApp error code
For more Ogury error messages, please see: Ogury error codes
For more You Keying error messages, please see: Klevin error code