Pangle: A global platform dedicated to developer growth.|Integration Docs
Knowledge Center

Error Code

Error code

Instructions

Investigation hint

4000

resources not found, if you use aab please call PAGConfig.setPackageName

If you use obfuscation, please make sure to add Pangle's resources to the whitelist. You can refer to this link for more information: link

Also, if you use Pangle's AAB function, please call PAGConfig.setPackageName and use '.to' to split the base package name and module package name.

10000

Please exec TTAdSdk.init before loading the ad

Initialize the SDK and then initiate an ad request

10002

load time out

The ad object is not returned within the specified time. We do not recommend initiating the request again.

10003

resource error

Resource loading failed due to network and other reasons.

20001

No fill


40001

BadRequest: HTTP request pb error

Indicates that some necessary parameters have invalid values. Please check the integration guideline on the Pangle platform

40004

BadRequest: Empty Slot ID

Indicates that the slotID is null

40005

BadRequest: Invalid Ad Size

Indicates that the AdSize is missing or an unsupported size is passed.

40006

Invalid Slot ID

Indicates that the length of the slot ID is incorrect, or an empty string is passed.

40007

BadRequest: Ad counts error

Indicates that the Ad counts is invalid

40008

BadRequest: Image size error

Indicates that the image size is not supported.

40009

Invalid App ID

Indicates that the app id is invalid or app id is missing

40013

Using App Open Ad's placement to other request methods.

The non-splash ad request method uses the splash ad placement ID. Check whether the ad placement ID used for the requested advertisement is correct, the app open ad placement ID is a nine-digit number starting with 8

40016

BadRequest: Slot ID and App ID is not matched

Indicates that the relationship between App Id and Slot Id is invalid or App Id is missing.

40018

Invalid Package Name

Indicates that the package name of your project does not match the package name you filled in the Pangle platform.

40019

BadRequest: Ad Type and Slot Id are not matched

Indicates that Ad Type and Slot Id are not matched. For example, try to load a rewarded ad with a banner ad slot id.

40021

BadRequest: Invalid SHA1 value

Indicates that the SHA1 is not matched with the SHA1 you entered on the Pangle platform.

There are a situation that may cause ad request issues:

  1. Lack of so library for pangle. Mono cannot be used in Unity, ill2cpp needs to be used, and 64-bit must be checked, and then Android - > Resolve will be executed to download 64-bit so.

40022

BadRequest: Incorrect API method

Indicates that the API method is incorrect

40024

BadRequest: The SDK version is too low

Please update to the latest SDK

40025

BadRequest: verification failed

Update to the latest SDK

40029

BadRequest: Incorrect API method

There are three situations that may cause ad request issues:

  1. IOS ad request method error: When the SDK rendering and self-rendering ad request methods are different, the solution is to use the SDK rendering method with the correct parameters to request the ad.
  2. Ineffective server slotID configuration: If the server slotID configuration is not effective, developers need to wait 2-3 minutes for the new slotID to request the ad.
  3. Low SDK version: When the SDK version is too low (lower than 2.9.5.0), the personalized SDK rendering function is not supported. The solution is to update to the latest version of the Platform SDK.

40034

Incorrect Bidding Ad Placement

  1. Bidding ad placement can not be used in a non-bidding environment
  2. Non-bidding ad placement can not be used in a bidding environment.

50001

Servers error

Server error, if the error could be 100% replicated, please give feedback to us via pangle_support@bytedance.com

-1

Data parsing failed.

For the collection of client code problems, you can first check the following situations: One: the show is called in the child thread. Two: ViewGroup is empty when registering click events. Three: The business logic of the media in the onFeedLoaded callback is abnormal, which causes the SDK to go to the onError callback. If the above ideas still can not solve your problem, you can contact the TS

-2

Network error

This indicates that your network connection is not stable enough.

-16

Prohibit requesting ads

Pangle doesn't have Children ads, you can not get filled when coppa = 1

101

Data parsing failed for template ads

Please update to the latest SDK.

102

Template is missing

Please update to the latest SDK.

103

Subtemplate missing

Please update to the latest SDK.

107

SDK rendering timeout

Please update to the latest SDK.

108

SDK rendering timeout

Please update to the latest SDK.

109

Template loads failed

Please update to the latest SDK.

113

Dynamic-Native 1.0 JS parsing error

Re-request ads

117

Dynamic-Native 1.0 JS parsing timeout

Re-request ads

118

Dynamic-Native 1.0 rendering error

Re-request ads

123

Dynamic-Native 2.0 SDK parsing error

Re-request ads

127

Dynamic-Native 2.0 SDK parsing timeout

Re-request ads

128

Dynamic-Native 2.0 SDK rendering error

Re-request ads

601

Link establishment failed

Check network status and request ads again

602

Link establishment timeout

Check network status and request ads again

603

Ads returned abnormally

Re-request ads

604

Ads parsing failed

Re-request ads

605

Ads parsing failed

Re-request ads

606

Ads parsing abnormally

Re-request ads

607

Ads read and write failed

Re-request ads

608

Ads read and write failed

Re-request ads

609

Ads download failed

Re-request ads

610

Ads download abnormally

Re-request ads

611

Ads request canceled

Re-request ads

612

Image load abnormally

Re-request ads