Error Code

Common WaterFall error code description

Code call

Developers canoneLayerLoadFailed obtain the TPAdError object in the listening callback

Taking the rewarded video type as an example, to obtain the reason why the advertising source failed to load, the code is as follows:

tpReward.setAllAdLoadListener(new LoadAdEveryLayerListener() {
	@Override
	public void oneLayerLoadFailed(TPAdError adError, TPAdInfo adInfo) {
		Log.i(TAG, "oneLayerLoadFailed: The error code is " + adError.getErrorCode() + "， and the error message is " + adError.getErrorMsg());
	}		
});

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. It is necessary to check (1) whether the adUnitId is filled in correctly, for example: there are spaces before and after the adUnitId setting; (2) Check whether the corresponding advertising source is configured in the TradPlus background; (3) The configuration is normal and the network status is normal. For example: If it is an overseas Bidding source, network problems will also cause the pull to fail. Overseas IP is required. For more information, please refer to Test Mode； (4) Check whether obfuscation is added according to the integration document, and whether the obfuscation is effective.
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.

Bidding error message

Code call

Developers canonBiddingEnd obtain the TPAdError object by listening to the AdLoadListener callback.

Taking the rewarded video type as an example, to obtain the reason why the advertising source failed to load, the code is as follows:

tpReward.setAllAdLoadListener(new LoadAdEveryLayerListener() {
	@Override
	public void onBiddingEnd(TPAdInfo tpAdInfo, TPAdError adError) {
		Log.i(TAG, "onBiddingEnd: The error code is " + adError.getErrorCode() + "， and the error message is " + adError.getErrorMsg());
	}
});

Error code ErrorCode	Error messageErrorMsg	illustrate
0	Bidding Success	-
21	Bidding request parameter error	Contact TP
22	Bidding Bidding No advertising source found	-
23	Bidding Bidding Unavailable Buyeruid	Buyeruid is used to obtain the token for this auction advertisement.
204	Bidding request third party is not filled	Three-party NOFILL
30	Bidding Bidding request to third party failed	Try several times
31	Bidding request three-party timeout	Try several times, or switch network conditions
32	Bidding request is successful, resp.SeatBid is empty	Contact TP
34	Bidding request is successful, resp fails to parse json	Contact TP
35	Bidding was discarded: this bid is lower than the last bid
36	Bidding request is successful but adm or price is wrong	Contact TP
37	Bidding three-party thread goRoutine timeout	-
38	Bidding three-party request timed out, notice sending failed	Contact TP
39	Bidding notice Price decryption failed	Contact TP
40	Bidding was discarded because the price was lower than the floor price or exceeded the reserved number of bidding ad sources.	-