1.TopOn error code information description

Error code	Description
10001	Invalid appid or app key, please check 1. AppId or AppKey is wrong, Check the AppId and AppKey passed in when initializing TopOn 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
10003	Invalid app 1.AppId error, Check the initialization TopOn in the code AppId passed in when SDK 2.TopOn advertising slot Id does not match AppId, Check The PlacementId passed in when calling load in the code calls ATSDK.setNetworkLogDebug(true);< /strong> Filter anythink in Logcat to view the parameters currently passed into the SDK. Please check these parameters
10004	Invalid placement 1.TopOn 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
9999	Generally the network An error occurred in the request, check whether the network status is normal
9990	The status returned by the Http interface request is wrong. You need to contact your TopOn colleagues to check the error information
9991	The business code returned by the interface request is wrong. You need to contact your TopOn colleagues to check the error information
9992	GDPR level has been set Low, check whether the FORBIDDEN level is set manually
2001	Ad loading timeout, check whether the current test advertising source is an overseas platform and whether the mobile network has been bypassed
2002	TopOn'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
2003	The number of impressions of the current ad slot has reached the upper limit. You need to confirm whether TopOn's background configuration limits the number of impressions of this ad slot
2004	The current ad slot is in a non-display period. You need to confirm whether TopOn's background configuration limits the ad slot. Display interval
2005	This 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
2007	Usually 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
It is forbidden to load the same ad slot after it fails to load. In the failed callback, call the load method immediately to try again. Please delay for more than 10 seconds before trying again
2009	The number of times the ad slot is loaded reaches the upper limit within a certain time interval
3001	Policy 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
3002	One of the passed in appid, appkey, and placementid is a null character CallATSDK.setNetworkLogDebug(true);< /strong> Filter anythink in Logcat to view the parameters currently passed into the SDK. Please check these parameters
3003	The ad slot does not match the API called. For example: Banner's ad slot calls the rewarded video API to load ads
4001	Usually 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
4002	Context’s context has been destroyed. You need to re-create the corresponding ad type object and re-initiate ad loading
4003	The status of this advertising slot has been closed. Check whether the status switch of this advertising slot is turned on in the TopOn background
4004	This ad slot does not have advertising source information configured in the TopOn backend. You need to go to the TopOn backend - aggregation management to add the ad source of a third-party advertising platform to the ad slot
4005	Advertising 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 TopOn 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
4006< /td>	Video playback failed, refer to 4001 error code Conduct troubleshooting
4007	Ad source bidding failed, refer to 4001 error code Conduct troubleshooting
4008	Advertising 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
4009	In 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 mistakes	Solution
1001 - No Fill	Use TopOn's Debug mode (DebuggerConfig) for testing
1000 - Network Error	Check 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 TopOnSDK version< /p>

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

The correct configuration example is as follows:

Called if there is no filling after the ad space is requested ATSDK.setNetworkLogDebug(true);Open the TopOn log and filter "anythink|HeadBidding"Keyword view log

If the log format is as follows ：

"HeadBidding Fail List" with Meta means that the Meta bidding failed

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

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

//Below version 5.9.96
//f669f2b7137d82b9 is the AndroidID of the test 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 vpn with high fill rate Country: United States)

Common Errors	Solutions
3	Using TopOn's Debugging Mode (DebuggerConfig) Testing
2	Check whether to circumvent the wall
1	Check TopOn background Admob ad source configuration
0	1. Use TopOn's debugging mode ( DebuggerConfig) Test 2. Check whether to circumvent the wall

More Admob Please see the error message: Admob error code

AppLovin

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

Common mistakes	Solutions
204	Use TopOn'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 errors	Solutions
EXCEPTION_RETURN_EMPTY	Chinese 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 TopOn'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_FOUND	Check TopOn background Mintegral ad source configuration (ad unit id)
EXCEPTION_UNIT_NOT_FOUND_IN_APP	Check the TopOn background Mintegral advertising source configuration (ad unit id)
EXCEPTION_SIGN_ERROR	Check the TopOn background Mintegral ad source configuration ( AppKey)
EXCEPTION_UNIT_ADTYPE_ERROR	Check the TopOn background Mintegral advertising source configuration (ad format does not match)
resource load timeout< /td>	Check 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:

<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:tools="http://schemas.android.com/tools"
                tools:shrinkMode="safe" />

：
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 mistakes	Solution
6000 - 102006	No 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 TopOn's debug mode (DebuggerConfig)
5002 - Video material download error	Check 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 displayed	Check 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 display	Enable hardware acceleration in AndroidManifest.xml
5004 - No suitable advertisement was matched	In 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 TopOn’s debug mode (DebuggerConfig)
5004 - No ads	1. 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 TopOn background Tencent advertising source configuration (whether template rendering 2.0)< /td>
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 returned	The 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 consistent	Check the TopOn background Tencent advertising source configuration (whether Template rendering, full-screen video, etc.)
2001 - Initialization error	Developer self-check parameter issues 1. Do not disassemble the SDK package of Tencent Ads 2. Check the TopOn 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 visible	1. 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 found	It 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 Tecent Ads error messages, please see:

1、Tencent Ads error code

2、Tencent Ads error code 6000

Chartboost

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

Common errors	Solution
NO_AD_FOUND	Use TopOn DebuggerConfig carry out testing

For more Chartboost error messages, please see：Chartboost错误码

Tapjoy

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

Common errors	Solution
Can't get ads	Use TopOn DebuggerConfig carry out testing

ironSource

(Recommended country with high VPN filling rate: Israel)

Common errors	Solution
508 - initISDemandOnly() had failed	Instance Id must be configured when configuring the TopOn backend advertising source. Check whether the Ironsource backend account has Instance permissions. If there is no permission, please contact the relevant Ironsource personnel.
510	Contact Ironsource personnel

For more Ironsource error messages, please see：Ironsource error code

UnityAds

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

For more UnityAds error messages, please see:

UnityAds error code

Vungle

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

Common errors	Solution
NO_SERVE	Use TopOn DebuggerConfig carry out testing
PLACEMENT_NOT_FOUND	Check the TopOn backend Vungle ad source configuration
CONFIGURATION_ERROR	1. Check whether the network is normal 2. Check the TopOn background Vungle advertising source configuration
UNKNOWN_ERROR	Contact Vungle relevant personnel
After preloading Vungle's rewarded videos and interstitial ads successfully, one of the Vungle ads is played, and the other ad's isAdReady() returns false.	Vungle’s rewarded videos and interstitial ads share the same advertising source resources.

For more Vungle error information, please see:

Vungle error code

AdColony

(Recommended country with high VPN filling rate: Finland)

Common mistakes	Solution
onRequestNotFilled!	使用TopOn的 DebuggerConfig 进行测试

Bigo

(Recommended country with high VPN filling rate: Singapore)

Common mistakes	Solution
3507-EXCEPTON_UNIT_BIDDNG_TYPE_ERROR	Bidding type error, such as using waterfull advertising code to load Bidding advertising space, or using bidding code to load waterfull advertising space, please keep it consistent, check the topon background configuration and advertising platform configuration, please consult the advertising platform for details

CJS(Pangle)

(For foreign versions, recommended countries with high VPN filling rates: South Korea, Japan, and Singapore)

Common errors	Solution
4201 - No initializer	1. Check whether the abi architecture has been restricted according to the integration document. 2. Check whether the com.android.support:appcompat-v7 dependency or androidx.appcompat:appcompat dependency has been added according to the integration document.
-7 - Failed to load the opening screen advertisement image	Check whether it has been correctly adapted to Android 9 and above systems according to the integration documentation（network_security_config.xml）
No result callback after loading	Check 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 displayed	Check whether it has been correctly adapted to Android 9 and above systems according to the integration document (network_security_config.xml)
Black screen when playing video	Check whether WAKE_LOCK permission is configured in Manifest
20001	The request is not filled due to no suitable advertisement being returned. This is normal. Please try changing the device to verify. Do not use the simulator for testing, or try again later. If it cannot be solved, please check the CJS-SDK error code for troubleshooting or ask the CJS platform for inquiries. To test the integration, you can use the test mode in the TopOn background advertising space-advanced settings.
40029	Check the rendering type of the CJS code bit. The configuration of the TopOn background CJS advertising source must be consistent with the configuration of the CJS background.
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 document 3. If obfuscation is enabled, please check the obfuscation rules provided in the downloaded SDK compressed package 4. Download from the CJS background SDK, replaces the pangolin SDK provided by TopOn (open_ad_sdk_*.aar)
40021 - The apk signature sha1 value is inconsistent with the media platform entry	The signature of the application must be consistent with the signature configured in the CJS backend. If it has just been configured, please clear the cache and try again after 5 minutes.
40019 - The media configuration adtype is inconsistent with the request	Check the TopOn background CJS advertising source configuration. If it has just been configured, please clear the cache and try again after 5 minutes.
40018 - Media package name and entry are inconsistent一致	The package name configured in the code must be consistent with the CJS background. If it has just been configured, please clear the cache and try again after 5 minutes.
40016 - The corresponding relationship between slot_id and app_id is illegal	Check the TopOn background CJS advertising source configuration to see if it contains spaces or special matches.
40006 - The advertising slot ID is illegal	Check the TopOn background CJS advertising source configuration to see if it contains spaces or special matches.
0 - null	This error will be reported when the network is weak. Please check the network status or switch the network and try again.
There is a problem with the size of Banner display	Before calling load, you need to specify the LayoutParams width and height values of ATBannerView.
Toutiao's rewarded video ad has a null pointer when playing.	If multiple dexes will be typed when packaging, please ensure that headline-related classes are typed in classes.dex

For more Pangle error information, please see:

(login required) Pangle error code

Uniplay

Common errors	Solution
3000/3001	Contact relevant Uniplay operations personnel
4006/4007/4008/4009	Uniplay’s Manifest related configuration is missing
4011	Relevant permissions are lacking. Please refer to the permissions configured in Uniplay's Manifest to apply.
AD NOT FOUND	Contact relevant Uniplay operations personnel
There is no callback when loading Banner ads	ATBannerView needs to be added to the window first and then initiate a load request.

For more Uniplay error information, please view: (Requires login to download)

Uniplay error code

Baidu

Common errors	Solution
Can't get ads	1. The rewarded video will take effect two hours after setting. 2. Use the test mode in the TopOn background advertising space-advanced settings for testing.
There is no callback when loading Banner ads	ATBannerView needs to be added to the window first and then initiate a load request.

For more Baidu error information, please see:

Baidu error code

Nend

(Recommended country with high VPN filling rate: Finland)

Common errors	Solution
Can't get ads	Use TopOn DebuggerConfig carry out testing

Yandex

(Recommended country with high VPN filling rate: Russia)

Please check the error message:

Yandex error code

Kuaishou

Common errors	Solution
40003 - Advertisement data is empty	If necessary, please contact the relevant personnel of Kuaishou
40004 - Video resource caching failed	Check whether it has been correctly adapted to Android 9 and above systems according to the integration document (network_security_config.xml)
Native advertising video has a black screen or is displayed transparently	Turn on hardware acceleration in AndroidManifest.xml
0 - Network error	1. Check whether the network is normal 2. Check whether it has been correctly adapted to Android 9 and above systems according to the integration document (network_security_config.xml)
310002 - Invalid appId	Check the Kuaishou ad source configuration in the TopOn background. If it has just been configured, please clear the cache and try again after 5 minutes.
310004 - packageName is inconsistent with the registered packageName	The package name configured in the code is inconsistent with the one in the Kuaishou backend
330002 - posId is invalid	Check the Kuaishou ad source configuration in the TopOn background. If it has just been configured, please clear the cache and try again after 5 minutes.
330004 - posId is inconsistent with registered appId information	Check the TopOn background Kuaishou advertising source configuration to see if you have used a different appid to initialize Kuaishou.
Abnormal display of native ads	Set fixed width and height values for ATNativeAdView

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 turned on when packaging: shrinkResource=true

Add a keep.xml under the res/raw path, the content is:

<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:tools="http://schemas.android.com/tools"
                tools:shrinkMode="safe" />

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 Kuaishou error messages, please see:

(Requires login to download) Kuaishou error code

Sigmob

Common errors	Solution
200000 - No ad fill	Use TopOn DebuggerConfig carry out testing
Sigmob keeps getting no ads when opening the screen	Devices above 6.0 need to dynamically apply for READ_PHONE_STATE permissions
500701 - The app has not opened any advertising channels	Check Sigmob background application status
500420 - The requested app has turned off ad serving	Check Sigmob background application status
500473 - The requested app does not exist	Check TopOn background Sigmob advertising source configuration
500424/500422/500482	1. Devices above 6.0 need to dynamically apply for READ_PHONE_STATE permission. 2. For android10, please refer to the Sigmob FAQ for information on how to fill ads in domestic Android10.
Android10 cannot get ads	Refer to the Sigmob FAQ for information on how to fill ads in Android 10.
After the advertisement is loaded successfully, it does not play and the subsequent callback	Sigmob's callback needs to rely on the LocalBroadcastManager library. Check whether the dependency of com.android.support:appcompat-v7 is introduced (Androidx corresponds to androidx.localbroadcastmanager:localbroadcastmanager)

For more Sigmob error information, please see:

Sigmob error code

Huawei (HMS)

Note: When using the test mode to test Huawei ads, you must use a Huawei mobile phone and must circumvent the wall. When using Huawei's official advertising space, you must use Huawei overseas version mobile phones

Common errors	Solution
3 - NO_AD	Use TopOn DebuggerConfig carry out testing
2 - NETWORK_ERROR	Check whether the network is circumvented
1 - INVALID_REQUEST	Check TopOn background Huawei advertising source configuration

For more Huawei (HMS) error information, please see:

Huawei (HMS) error code

You Keying

Common errors	Solution
1110 - Application ID (AppID) exception	Please check whether the AppID and PosID match
1111 - The resource bit (PosID) is abnormal. Please check whether the AppID and PosID match.	Please check whether the AppID and PosID match
1112 - Ad template not matched	It is recommended to check if the SDK version supports the requested ad style

For more YouKeYing error information, please see:

You Keying error code

Integration Testing