Search...
Menu
Error code
Note:
You can use the Error's Domain field to determine whether the error is thrown by the TopOn SDK (anythink) or a third-party ad network. If thrown by a third-party SDK, please click the links below to navigate to the corresponding ad network's documentation for error troubleshooting.
1. TopOn Error Code Information
When debugging your own placement configuration, please note:
The TopOn SDK debug mode code should be removed.
You should wait for the dashboard configuration changes to take effect (5-15 minutes), and clear the sandbox cache on the local device (you can delete and reinstall to clear it).
The following is a summary of error codes:
| Error Code | Note |
|---|---|
| 2001 | (GDPR not set) GDPR consent not set. Suggestion: Since you are in a data protection region (EU, etc.), please set the data collection consent before initialization. Refer to the GDPR documentation. |
| 1001 | (Invalid policy) Placement strategy invalid. Suggestion: 1. Check whether the ad source is enabled, and check whether the appId, appKey, and placement ID passed during TopOn initialization match. 2. After verifying the parameters, delete and reinstall before attempting to retrieve the policy again. |
| 1003 | The ad load failed. There are two possible scenarios: Suggestion: 1. Waterfall ad configuration — see the dashboard log analysis for details. If it is during the development phase, see Log Output. 2. If the error msg contains Bid request have failed — the bidding failed. For details, implement the bidding delegate to check didFailBiddingADSourceWithPlacementID. |
| 1005 | (No ad display) No ad found when trying to show ad. Suggestion: Before calling the ad display, please first check whether the placement is ready. You can check the corresponding ad type's judgment API. |
| 1006 | (Display too frequent) Ad show too frequent. Suggestion: Please try displaying again later. You can set a display interval to avoid this issue, or use the Mediation Management in the TopOn dashboard to set the display interval. |
| 1007 | (Display has exceeded the maximum number of impressions within the same hour) Ad show too many times within the same hour. Suggestion: During testing, you can increase the number of impressions per hour. If the app has been released, this code is considered normal. |
| 1008 | (Display has exceeded the maximum number of impressions within the same day) Ad show too many times within the same day. Suggestion: During testing, you can increase the number of impressions per day. If the app has been released, this code is considered normal. |
| 1009 | (The corresponding Adapter is not imported) The adapter not found. Suggestion: Please integrate the corresponding ad network's adapter based on the information printed in the log. |
| 10010 | (Ad load timeout) Ad loading timeout. Suggestion: Please change the test device's network and try loading the ad again. |
| 1013 | (The third-party platform's SDK is not imported or the wrong version is imported. The AnyThink iOS and sub-package versions must correspond.) Third party SDK not imported or wrong version's being used. Suggestion: Please refer to the download page in our dashboard and 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: 1. Please verify that the above information is correct and accurately filled in for initialization and ad loading. 2. Please verify that the SDK has been initialized before initiating an ad load. |
| 1015 | (Ad delivery is not enabled for the placement) Ad delivery not turned on for the placement. Suggestion: Please enable the corresponding placement in the TopOn dashboard management system. |
| 1017 | (The placement policy does not contain any ad sources) The placement strategy does not contain any ad sources, please check the mediation configuration in TopOn. Suggestion: Please add the desired ad sources to the corresponding placement, create ads in the ad network's dashboard, and fill the ad ID into the placement. |
| 1018 | (Ad sources have been filtered) Ad sources are filtered, no ad source is currently available. Suggestion: 1. The ad sources have been filtered. They may have been added to the filtering API during initialization. Check whether they have been added. 2. No ad source is enabled in the dashboard. |
| 1019 | (Requests are too frequent within the period after the last load failure) The placement ID load too frequently within the specified time period after the previous load failure. Suggestion: Please wait at least 10 seconds or more after the last request failure before initiating a new request. |
| 1020 | (The placement has been loaded too many times within the specified time period) The placement load too many times within the specified time period. Suggestion: Please adjust the number of times the placement is loaded to avoid excessive loading within a period. |
| 1029 | (Debug mode: the placement policy does not contain any ad sources. Please check the debug mode configuration.) The placement strategy does not contain any ad sources, please check the debugger configuration in [ATAPI setDebuggerConfig]. Suggestion: You can check whether the passed IDFA is the device's IDFA, and then check whether the debug mode platform used is incorrect. If none of the above is the issue, you can provide feedback to us for troubleshooting. |
| 1030 | (The ad source has been filtered and there is no fill.) Ad source not filled, caused by customize filter. Suggestion: The ad from this ad source was set to be filtered by the custom filter configuration, resulting in no load fill. You can check the custom filter settings during initialization. |
| 10004 | Server returns invalid response, code:10004, msg:Invalid placement. Suggestion: 1. AppID must correspond to PlacementID. 2. The SDK in the Podfile should use the matching version generated from the SDK Download Center. |
2. Third-Party Ad Network Error Codes & FAQ
| Common Error | Solution |
|---|---|
| 1001 - No Fill | No fill. The most common reason is 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 site when testing your mobile site. |
| 1000 - Network Error | Network issue. Check whether the proxy is working. |
For more Facebook error information, see: Facebook Error Codes
AdMob
| Common Error | Solution |
|---|---|
| 0 | 1. Use TopOn dashboard placements and test using debug mode. 2. Check whether the proxy is working. |
| 1 | Invalid ad request. Check the ad source parameter configuration. |
| 2 | Ad request failed due to network connection. Check whether the proxy is working. |
| 3 | The ad request was successful, but no ad was returned due to a lack of ad inventory. Use TopOn dashboard placements and test using debug mode. |
For more AdMob error information, see: AdMob Error Codes
Pangle (China)
| Common Error | Solution |
|---|---|
| 40029 | Check the rendering type of the Pangle ad unit. The configuration of the Pangle ad source in the TopOn dashboard must match the configuration in the Pangle dashboard. |
| 40025 | Download the SDK from the Pangle dashboard and replace the Pangle SDK provided by TopOn. |
| 40019 - Media configuration adtype does not match the request | TopOn dashboard Pangle ad source configuration issue. |
| 40018 - Media package name does not match the registered one | The package name configured in the code does not match the one in the Pangle dashboard. |
| 40016 - The slot_id and app_id mapping is invalid | TopOn dashboard Pangle ad source configuration issue. |
| 40006 - Invalid placement ID | TopOn dashboard Pangle ad source configuration issue. |
| 102 - No matching main template: The main template was not downloaded locally. Occurs occasionally on the first ad request; this is normal. | Try requesting the ad multiple times. |
| 103 - No matching sub-template: Occurs occasionally during the initial integration phase, caused by not matching a template. Will not occur after the SDK has successfully downloaded the template. | Try requesting the ad multiple times. |
| 107 - Template rendering timed out without a callback. Possible reasons: 1. Network issue or 2. Hardware issue, causing the rendering to fail. You can try changing the phone or network environment for testing. | Try requesting the ad multiple times. |
For more Pangle (China) error information, see: (Login required) Pangle Error Codes
Pangle
For Pangle error information, see: Pangle Error Codes
Mintegral
| Error Code | msg | Description | Solution |
|---|---|---|---|
| -1 | EXCEPTION_RETURN_EMPTY | No ad fill. Possible reasons: 1. The ads you obtained during testing are all Mintegral's live ads, which are affected by algorithmic intelligent optimization. If a large number of ads are loaded and displayed over a period of time, it may cause no ad fill after a while. | China version: 1. Ensure that Accept APK Ad Delivery is enabled under App Settings in the Mintegral dashboard. Overseas version: 1. Check whether the proxy or VPN is connected to the US region. If the issue persists after the above checks, use TopOn dashboard placements and test using debug mode. |
| -1201 | EXCEPTION_UNIT_NOT_FOUND | The unitID does not exist / is filled in incorrectly. | TopOn dashboard Mintegral ad source configuration issue. |
| -1203 | EXCEPTION_UNIT_NOT_FOUND_IN_APP | The appID and unitID do not match. | TopOn dashboard Mintegral ad source configuration issue. |
| -1205 | EXCEPTION_UNIT_ADTYPE_ERROR | The passed unitID's ad type does not match. | TopOn dashboard Mintegral ad source configuration issue. |
For more Mintegral error information, see: Mintegral Error Codes -> Interface Status Return Instructions
Tencent Ads
| Error Code | Description |
|---|---|
| 4013 | System not supported. Native video template ads only support iOS 9 and above. |
| 4020 | Window is null. You need to add the window property in AppDelegate. |
| 5006 | Package name verification illegal. The package name configured in the code does not match the one in the Guangdiantong dashboard. |
| 6000 | Unknown error. Contact a Tencent Ads commercial colleague for assistance in troubleshooting. |
For more Tencent Ads error information, see: Tencent Ad Error Codes
AppLovin
| Common Error | Solution |
|---|---|
| 204 | No fill. You can try adjusting the phone's region to the United States and proxying the network to the US. |
For more AppLovin error information, see: AppLovin Error Codes
Vungle
| Common Error | Solution |
|---|---|
| Ad not obtained | Enable test mode through the Vungle dashboard for testing. |
| After preloading both Vungle's Rewarded Video and Interstitial ads successfully, playing one of the Vungle ads causes isAdReady() to return false for the other ad. | Vungle's Rewarded Video and Interstitial ads share the same ad source resources. |
For more Vungle error information, see: Vungle Error Codes
Kuaishou
| Common Error | Solution |
|---|---|
| 40003 - Ad data is empty | If it occurs consistently, contact Kuaishou personnel. |
| 310002 - Invalid appId | TopOn dashboard Kuaishou ad source configuration issue. |
| 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 - Invalid posId | TopOn dashboard Kuaishou ad source configuration issue. |
| 330004 - posId does not match the registered appId information | TopOn dashboard Kuaishou ad source configuration issue. |
For more Kuaishou error information, see: (Login required to download) Kuaishou Error Codes
Sigmob
| Common Error | Solution |
|---|---|
| 200000 - No ad fill | Add a test device through the Sigmob dashboard for testing. |
| 500420 - The requested app has closed the ad service | Add a test device through the Sigmob dashboard for testing. |
| 500473 - The requested app does not exist | TopOn dashboard Sigmob ad source configuration issue. |
| 500701 - The app has not opened any ad channels | Check the app status in the Sigmob dashboard. |
For more Sigmob error information, see: Sigmob Error Codes
Baidu
For more Baidu error information, see: (Login required to download) Baidu Error Codes
Bigo Ads
For more Bigo Ads error information, see: Bigo Ads Error Codes
| Common Error | Solution |
|---|---|
| 10102 | No ad fill. Please try changing the proxy network or device and retrying. For bidding ads, check the ads.txt configuration. If necessary, go to the Bigo dashboard to add a test device and wait 30-60 minutes for it to take effect before retrying. |
UnityAds
For more UnityAds error information, see: UnityAds Error Codes
| Common Error | Solution |
|---|---|
| Code=2 - adMarkup is missing | Please check whether "Mediation Partner" under Project Settings → Mediation Partners in the Monetization Dashboard is set correctly. |
Chartboost
For more Chartboost error information, see: Chartboost Error Codes
IronSource
For more IronSource error information, see: IronSource Error Codes
Oneway
For more Oneway error information, see: Oneway Error Codes
StartApp
For more StartApp error information, see: StartApp Error Codes
Ogury
For more Ogury error information, see: Ogury Error Codes
Klevin
For more Klevin error information, see: Klevin Error Codes
InMobi
| Common Error | Solution |
|---|---|
| com.inmobi.ads.requeststatus Code=6 The SDK encountered an internal error. | Network issue. The network is in an invalid region. Solution: Go to the InMobi dashboard to add a test device for testing ads. |
| InMobi test mode did not take effect | Takes 15 minutes to take effect and requires a proxy to request ads. |
For more InMobi error information, see: InMobi Error Codes
Previous
DebugUI Debug Tool
Next
Integration Checklist
Last modified: 2026-07-08Powered 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