Tips:
To quickly pinpoint the cause of an issue, it is recommended to obtain all error information via
AdError#getFullErrorInfo().Copy"code[ " + code + " ],desc[ " + desc + " ], platformCode[ " + platformCode + " ], platformMSG[ " + platformMSG + " ]" code: TopOn SDK error code desc: TopOn SDK error message platformCode: Third-party ad network error code (the error code to check when an ad has no fill) platformMsg: Third-party ad network error message (the error message to check when an ad has no fill)
| Error Code | Description |
|---|---|
| 10001 | App ID or App Key is incorrect. Please check the App ID and App Key passed when initializing the TopOn SDK. |
| 10003 | 1. App ID is incorrect. Please check the App ID passed when initializing the TopOn SDK. 2. The TopOn placement ID does not match the App ID. Please check the Placement ID passed when calling the load method in your code. |
| 10004 | The TopOn placement ID is incorrect. Please check the Placement ID passed when calling the load method. |
| 9999 | 1. A network request error occurred. Check whether the network status is normal. 2. An error message appeared: chain validation failed. Please check whether the test device's system time has been adjusted. |
| 9990 | The HTTP interface request returned a status error. You need to contact a TopOn colleague to view the error information. |
| 9991 | A business code error was returned by the interface request. You need to contact a TopOn colleague to view the error information. |
| 9992 | The GDPR level is set too low. Check whether the FORBIDDEN level has been manually set. |
| 2001 | Ad load timed out. Check whether the current test ad source is an overseas network and whether the phone's network has been proxied. |
| 2002 | The TopOn SDK package is incomplete, missing the Adapter package for a third-party ad network. Confirm that the required third-party SDK packages for mediation have been imported as instructed. |
| 2003 | The current placement has reached its impression cap. You need to confirm whether the TopOn dashboard configuration limits the number of impressions for this placement. |
| 2004 | The current placement is in a non-display time period. You need to confirm whether the TopOn dashboard configuration limits the display interval for the placement. |
| 2005 | This placement is in the loading phase. After a request is initiated for the same placement, before receiving the load success or failure callback, the placement cannot initiate the next load. Please wait for the load success or failure callback. |
| 2006 | Check whether the imported third-party ad network SDK packages are complete. If they are complete, check whether the imported version matches the version specified on GitHub. If not, the third-party SDK packages need to be completed. |
| 2007 | This usually occurs when an ad load is initiated immediately in the load failure callback. Initiating an ad load immediately in the load failure callback is prohibited. A certain time interval must elapse since the last load failure for this placement before an ad load can be initiated. Please delay the call to load the ad. |
| 2008 | After a load failure for the same placement, calling the load method immediately in the load failure callback for a retry is prohibited. Please delay for at least 2 seconds before retrying. |
| 2009 | The number of loads for the placement has reached the cap within a certain time interval. |
| 3001 | Policy fetch error. 1. Check whether the network is normal. 2. Check whether the appId, appKey, and placementId used are matching. 3. Check whether the appId, appKey, and placementId in the code are correct and matching (no spaces allowed). |
| 3002 | One of the passed appId, appKey, or placementId is an empty string. Please check these parameters. |
| 3003 | The placement does not match the API being called. For example, a Banner placement ID was used to call the Rewarded Video API to load an ad. |
| 4001 | This usually occurs when a third-party ad network returns an error resulting in no ad fill. You can obtain the full error information via AdError.getFullErrorInfo(), and view the ad network's error code and error message using platformCode and platformMsg. Please check the third-party ad network error codes for troubleshooting. |
| 4002 | The Context has been destroyed. You need to recreate the corresponding ad type object and re-initiate the ad load. |
| 4003 | The status of this placement is closed. Check whether the status switch for this placement is turned on in the TopOn dashboard. |
| 4004 | No ad source information has been configured for this placement in the TopOn dashboard. You need to go to the TopOn dashboard - Mediation Management to add third-party ad network ad sources for the placement. |
| 4005 | All ad sources under the placement have been filtered. Possible reasons are as follows: 1. Check whether the impression cap or impression interval has been set for the ad sources in the TopOn dashboard. 2. If only header bidding ad sources are configured, they will be filtered when the bidding fails. |
| 4006 | Video playback failed. Refer to Error Code 4001 for troubleshooting. |
| 4007 | Ad source bidding failed. Refer to Error Code 4001 for troubleshooting. |
| 4008 | The ad source was filtered due to custom filtering logic in the developer's code. If the filtering does not match expectations, please troubleshoot the custom filtering logic. |
| 4009 | In debug mode, no ad source information has been configured for this placement. |
| ● AdMob | ● Meta | ● Mintegral | ● Pangle |
|---|---|---|---|
| ● Huawei | ● AppLovin | ● Unity Ads | ● Digital Turbine(Fyber) |
| ● Chartboost | ● ironSource | ● Liftoff(Vungle) | ● InMobi |
| ● Ogury | ● Maio | ● Nend | ● Yandex |
| ● Bigo |