Docs

Error Code Reference

This reference helps you quickly understand error codes returned by the platform, including what each code means, where it comes from, and how to troubleshoot it. Use it to identify common issues across APIs and to find the recommended next step for each error.

Network error codes

Request and downloadFile API

Error code	Error message	Description	Source	Recommended action
HTTP non-2xx status code (such as 401 or 404)	Server error	The request reached the server successfully, but the server returned a non-2xx HTTP status.	Developer	Review the server logs to locate the issue.
10401	Server error	The request finished, but no valid response was returned and no explicit error was provided. This is a fallback error code.	Developer	Verify that the server is running normally, then check the server logs to identify the root cause.
21100	URL not in domain list	The URL’s domain is not included in the trusted-domain whitelist configured in the developer platform.	Developer	Add the domain to the trusted-domain whitelist in the developer platform, or confirm that the URL is spelled correctly.
21101	Destination path has error	The download destination path is invalid because one or more path components are empty.	Developer	Check whether the generated destination path is correct. If the issue comes from an internally generated path, contact the Runtime team for investigation.
21101	Move file failed	Moving the temporary file to the destination path failed.	Developer	Check whether the destination path is already in use, whether the device has enough storage space, and whether directory permissions are correct.
21102	TTNet download progress error	After TTNet creates the download task, the `progress` object is `nil`, so download progress cannot be monitored.	TikTok Client	This is an internal TTNet exception. Retry the download. If the issue continues, contact the Runtime team to investigate TTNet version compatibility.
21103	Request timeout	The request did not receive a response within the specified `timeout` period.	Developer	Check whether the network connection is working properly, consider increasing the `timeout` value, and confirm whether the server is responding too slowly.
21201	Response data error	The download completed, but `filePath` is `nil` and no other error was returned, indicating abnormal response data.	Developer	Retry the download. If the issue persists, it may be caused by an underlying TTNet exception; contact the Runtime team for further investigation.
100000	File path error	The specified `filePath` is not writable because it is not under the `ttfile://user` or `ttfile://temp` directory.	Developer	Make sure `filePath` starts with `ttfile://user` or `ttfile://temp`.
100000	filePath is not supported	A `filePath` parameter was provided, but the current version does not yet support custom download paths.	Developer	Remove the `filePath` parameter and use the default temporary download directory instead. Wait for a later version that supports custom paths.
600003	Network interrupted error	The network was interrupted, or the request or download task was actively canceled (by calling `request.abort` or `downloadFile.abort`).	Developer	Confirm whether your business logic intentionally canceled the request. If the cancellation was not expected, check for network interruptions.
600005	Network argv error	The request parameters are invalid. For example: `url` is not a string, `method` is not a supported value, or `data` is of an unsupported type.	Developer	Check the types and formats of all input parameters. Ensure that `url` is a string, `method` is valid, and `data` is a `string`, `object`, or `ArrayBuffer`.
600009	Invalid URL	The URL is an empty string, is malformed and cannot be parsed, or is missing a scheme.	Developer	Check whether the URL is empty, whether it includes a valid `http://` or `https://` prefix, and whether it contains invalid characters.
600011	URL validation error	The URL scheme is not https (for example, `ftp://` or `file://`).	Developer	Change the URL scheme to https
603301	Exceeded max file size	The downloaded file exceeds the maximum allowed size. The temporary directory limit is 200 MB.	Developer	Make sure the file being downloaded does not exceed 200 MB. If larger files are required, consider downloading them in chunks.

In-App Ads error codes

Init API

Error code	Full error code	Error message	Description	Source	Recommended action
11001	101111001	[Third party] The ad placement ID was empty. Please provide a non-empty ad placement ID parameter.	The ad placement ID is empty, so the request parameter is invalid.	Developer	Check whether the ad placement ID is correct and non-empty.
10001	101310001	Request params error	The ad placement validation request parameters are invalid on server side.	Developer	Check whether the ad placement parameter type and required fields are correct.
20000	101120000 / 101320000	[Server] Minis/ad placement/validation - request failed due to a network issue. Please check your network and try again.	The client failed to request Minis/ad placement/validation, or the validation response did not return a valid RIT.	TikTok Client / TikTok Server	Ask the user to check network status and try again later.
20001	101320001	Ad placement does not exist	The specified ad placement does not exist.	Developer	Go to the portal and verify that the ad placement ID has been created.
20002	101320002	Client key does not match	The ad placement does not match the requested mini game ID.	Developer	Go to the portal and verify that the ad placement belongs to the current mini game.
20003	101320003	Ad placement status is inactive	The ad placement is inactive.	Developer	Go to the portal and activate the ad placement.
20004	101320004	IAA switch is close	The IAA switch is disabled for the current mini game or placement.	Developer	Enable IAA in the portal or confirm the game/placement is eligible for IAA.
20007	101320007	Ad placement type does not match	The ad placement type does not match the ad type requested by the SDK.	Developer	Go to the portal and verify that the ad placement type is correct.
30001	101330001	Ad placement frequency control calibration failure	Requests for the same ad placement are being made too frequently.	Developer	Check whether the current SDK usage is abnormal or whether the IAA API is being called too often.
50000	101150000 / 101350000	Internal error	A client-side IAA environment/state check failed, or the server returned an invalid/unknown validation status.	TikTok Client / TikTok Server	Report the error details to the support team for further investigation.

Show API

Error code	Full error code	Error message	Description	Source	Recommended action
11001	101111001	[Third party] The ad placement ID was empty. Please provide a non-empty ad placement ID parameter.	The passed ad instance ID is empty. Android reuses the invalid ad placement/ad instance scene for this path.	Developer	Verify correct SDK implementation against the official documentation.
11002	101111002	[Third party] Invalid ad instance ID. Please call `createRewardedVideoAd`/`createInterstitialAd` JSB with the same `adUnitId` first.	The ad instance ID does not match any existing ad instances.	Developer	Check for uninitialized ad instances.
11003	101111003	[Third party] Ad instance can only show once. Please call this JSB with another adUnitId.	This ad instance has already been shown and cannot be reused.	Developer	Check for duplicate usage of the ad instance.
11004	104111004	[Third party] Interstitial ad frequency limits reached. Please wait and show it later.	Not enough time has passed since the previous ad impression, so the interstitial ad cannot be shown yet.	Developer	Wait until the frequency-control window has passed before calling show again.
11005	104111005	[Third party] Interstitial ad frequency limits reached. Please wait and show it later.	The interstitial ad impression limit has been reached, so the ad cannot be shown.	Developer	Reduce interstitial show frequency or create a new eligible user flow.
11006	104111006	[Third party] Ads video is currently active. Do not call this JSB multiple times simultaneously.	Another rewarded/interstitial ad is already active, so this show call is rejected.	Developer	Serialize show calls and avoid concurrent invocations.
20000	101120000	Network error.	The client request timed out due to a network issue.	TikTok Client	Try again later.
30001	104130001	[User] User closed the ad within 15 seconds.	The user closed the ad before watching it to completion, so no reward was granted.	User	Treat as user cancellation/no reward and continue the game flow.
50000	101150000 / 102150000	Internal error.	A client-side state check failed, the TT4B ad manager is unavailable, or the IAA SDK threw an internal error.	TikTok Client / TT4B SDK	Forward the error details to the support team.

50000 inner error code details

50000 is a generic IAA internal error returned to the frontend. The exact root cause is reported through inner_error_code and inner_error_msg, so one 50000 full error code may correspond to multiple error messages.

Inner error code	Full error code	Error message	Description
50001	101150000	[Third party] The client key is invalid. Please check the client key.	The mini game client key is invalid.
50002	101150000	[Third party] The ad activity instance is invalid.	The client page/activity instance is unavailable.
50003	101150000	[Server] Minis/ad placement/validation - request failed with an empty rit. Please check your network and try again, or contact support.	The ad placement validation response returned an empty RIT.
50005	101150000 / 102150000	[TT4B] Empty ad manager. Please contact support.	The TikTok for Business (TT4B) ad manager instance is missing.
50006	101350000	[Server] Failed to call API. Please check your network settings and contact support.	The server validation response status is invalid or unknown.
50007	101150000	[Client] PRO client is not supported. Please contact support.	The current client type is unsupported for IAA. On iOS interstitial init this may also indicate an unavailable prewarm environment.
50008	101150000	[Client] Ad operation rejected because the mini game container is still being pre-rendered offscreen.	The call was blocked because the mini game container is still pre-rendering or otherwise unavailable.
50009	101150000	[Client] Env check failed, current env is unavailable for IAA.	iOS interstitial show was called while the environment is unavailable.
50100 + TT4B raw error code	102150000	[TT4B] Internal error.	The TT4B SDK returned an internal error. Check `inner_error_code` and `inner_error_msg` for the SDK-level reason.

Was this document helpful?