Error Codes
1、Error code (Android)#
Developers can obtain the error in callbacks such as OnOneLayerLoadFailed.
| Error code ErrorCode | Error messageErrorMsg | illustrate |
|---|---|---|
| 1 | success | Advertisement loaded successfully. |
| 2 | internal error! | Unknown reason. |
| 3 | load timeout | Ad loading timed out. (1) Check whether the current testing advertising source is an overseas source and whether it is scientifically connected to the Internet; （2）(2) Whether the test machine is equipped with Google Family Bucket (whether it is an overseas version of the mobile phone); (3) Some advertising sources need to be added to the third-party backend Test equipment; (4) Some advertising sources need to be tested with a test ID. |
| 4 | frequency limit | Set a frequency limit under the ad slot to achieve the number of impressions within a limited time. |
| 5 | ad not ready | The ad did not load successfully. It is called when the advertisement is not loaded successfullyshow()，or the third-party advertisement times out. |
| 7 | network not connection | The network cannot be connected. Check network conditions. |
| 8 | has cache,no need to load again | The number of ad caches has reached the configuration limit. |
| 9 | waterfall bean is null | The waterfall delivery configuration is empty. |
| 10 | wrong config | The server returns abnormal data. Please contact a TradPlus colleague to check the cause of the error. |
| 11 | load all adSource failed | All advertising sources under waterfall configuration failed to load. (1) Check whether the current testing advertising source is an overseas source and whether it is scientifically connected to the Internet; (2) Whether the test machine is equipped with Google Family Bucket (whether it is an overseas version of the mobile phone); (3) Some advertising sources need to be added to the third-party backend for testing Equipment; (4) Some advertising sources need to be tested using test IDs; (5) Developers need to filter tradpluslog to determine the reason why each source fails to load. Developers are asked to troubleshoot the specific reasons based on Android FAQ |
| 12 | no config | The waterfall delivery configuration is empty. It is necessary to check (1) whether the network access of the test machine is normal; (2) check whether obfuscation is added according to the integration document, and whether the obfuscation is effective. |
| 13 | adapter not found | The advertising source does not introduce the corresponding Adapter under the advertising slot configuration. Check the ad source configured for the ad slot. Correctly introduce third-party Adapters according to SDK DownLoad Platform |
| 14 | show ad failed | Ad display failed. |
| 15 | load failed interval please try again later | The last load failed, and loading again is prohibited within 10 seconds. |
| 16 | is loading please try again later | The ad is already being requested, please load it later. Loading frequency is too high. |
| 19 | has valid cache but not show | The last successful loading did not show, and loading again is prohibited within 4 minutes. |
| 20 | Context is not Acvitiy context | Check whether Activity is passed in when initializing the ad slot or showAd(). |
| 101 | adContainer is null | Native advertising misses ViewGroup. |
| 102 | adLayout is null | Native banner ads are leaking layout files. |
| 103 | Bidding Failed | There is an advertising source under the advertising space that sets the Bidding mode, when bidding fails. Error 103 will be sent directly. It is necessary to check (1) whether the advertising space is configured with a Bidding advertising source; (2) the configuration is normal. If it is an overseas Bidding source, network problems will also cause the pull to fail. An overseas IP is required. For more information, refer to the Test Mode (3) Check whether obfuscation is added according to the integration document and whether the obfuscation is effective. |
| 104 | Wrong a TPUnitID requested | The created ad type and the requested API are inconsistent. Please check the background, for example, a standard native ad type is created, but the rewarded video API is used to request this ID. |
2、Error code（iOS）#
| Error Code | Error Message | Explanation |
|---|---|---|
| 1000 | wrong config | The waterfall configuration sent by the backend is empty or incorrect. 1. Check if the ad placement has configured ad sources in the backend. 2. If using overseas bidding ad sources, check if the current device is using an overseas IP. |
| 1001 | Ad is loading | The loading process is in progress and cannot start a new loading process. |
| 1007 | network not connection | Network connection is not available. |
| 10002 | Not set AdUnitID | Ad unit ID is not set. |
| 10003 | not set renderingViewClass | Native ad is not set with renderingViewClass when displaying. |
| 10004 | not set renderer | Native ad is not set with TradPlusNativeRenderer when displaying. |
| 10005 | not set subView | Native ad is not set with subView when displaying. |
| 10008 | bidding response data error | The returned bidding result data is empty or returns a 204 status. |
| 10009 | bidding response biddingwaterfall error | The waterfall configuration data in the returned bidding result is incorrect. |
| 10010 | not set rootViewController | Interstitial or rewarded video is not set with rootViewController when displaying. |
| 10011 | not set window | Splash or native splash is not set with window. |
| 10012 | post bidding Data error | Data error after bidding. |
| 10013 | Wrong Ad Type | Invalid ad type. |
| 10014 | not set MediaVideo adContainer | No ad container is set for interstitial ads. |
| 10015 | not set MediaVideo ViewController | No view controller is set for interstitial ads. |
| 600004 | frequency limit | Ad placement frequency limit. |
| 600009 | waterfall bean is null | The waterfall configuration sent by the backend does not contain any usable ad source configuration information. |
| 600015 | load failed interval please try again later | Loading too frequently, unable to load again within 10 seconds after a failure. |
| 600019 | has valid cache but not show | Loaded successfully but failed to display an ad within 4 minutes. |
| 600103 | bidding fail no more waterfall | Failed to obtain any third-party bidding source data, bidding and adx failed. |
| 800002 | Third-party error message | Error loading from third-party, returns the third-party error code and description. |
| 800003 | netWork load timeout | Timeout when loading from third-party. |
| 800004 | netWork load limit | Frequency limit from third-party ad sources. |
| 800009 | netWork no ad source | Class name for the corresponding third-party network is empty in the waterfall configuration sent by the backend. |
| 800012 | netWork no config | Configuration for the corresponding third-party network is empty in the waterfall configuration sent by the backend. |
| 800013 | netWork no adapter | No adapter found for the corresponding third-party network. |
| 800017 | netWork adconfig Info error | Configuration error for the corresponding third-party network in the waterfall configuration sent by the backend. |
| 810011 | load Fail, No ad fill | Loading ended without any ads loaded. |
| 810103 | Bidding Fail | Bidding failed. When only bidding ads are configured for the current ad source, the loading ends after bidding fails. |
| 810105 | exclusive Fail | Exclusive bidding failed. |
| 1000004 | frequency limit | Ad placement frequency limit. |
| 1000005 | not any ready ad | No cached ads available. |
| 1100014 | Render Error | Native ad rendering error. |
Bidding Error Messages#
Developers can obtain the error information by monitoring the callback BiddingEnd. The specific information is as follows:
| Error Code | Error Message | Explanation |
|---|---|---|
| 0 | Bidding Success | - |
| 21 | Bidding Request Parameter Error | Contact TP development |
| 22 | No Ad Source Found for Bidding | - |
| 23 | Invalid Buyeruid for Bidding | Buyeruid is used to get the token for this bid ad |
| 204 | Third-party NOFILL for Bidding Request | Third-party NOFILL |
| 30 | Third-party Bidding Request Failed | Try multiple times |
| 31 | Third-party Bidding Request Timed Out | Try multiple times or switch network conditions |
| 32 | Bid Request Succeeded, but resp.SeatBid is Empty | Contact TP development |
| 34 | Bid Request Succeeded, but resp Failed to Parse JSON | Contact TP development |
| 35 | Bid Has Been Discarded: The Bid Price is Lower Than the Previous Bid Price | |
| 36 | Bid Request Succeeded, but adm or price is incorrect | Contact TP development |
| 37 | Third-party Thread goRoutine Timed Out for Bidding | - |
| 38 | Third-party Bidding Request Timed Out and Notice Sending Failed | Contact TP development |
| 39 | Notice Decryption Failed for Bidding | Contact TP development |
| 40 | Bid Has Been Discarded: The Bid Price is Lower Than the Floor Price or Exceeds the Reserve Count of Bidding Ad Sources | - |