5.2 Error Location

5.2.1 Error Code List

Reminder: Record both the error code and error message from callbacks. Start with the Troubleshooting Guide for the complete flow. Use the following commands to enable and filter SDK logs:

adb shell setprop log.tag.ADSDK DEBUG
adb logcat | grep ADSDK

adb shell setprop log.tag.AD_NET_LOG DEBUG
adb logcat | grep ADSDK_N

Mediation SDK Error Codes

Error Code	Stage	Description	Owner	What to Check
-10000	General	Unknown error	SDK Support	Provide the error message and complete incident-period logs
20001	Fill	No ad is currently available	Integrator/Operations	Check test mode, delivery region, ad source configuration, and platform inventory
20002	Fill	The cached ad has expired	Integrator	Load a new ad and do not display an expired ad
20003	Fill	The mediation request reached the cloud-configured timeout	Integrator/Operations	Check the network, placement timeout, and ad source response times
20004	Fill	Fill failed because of a network exception	Integrator	Check device connectivity and request logs
20005	Fill	Bidding completed without an ad fill	Operations	Check bidding ad sources, bids, and delivery configuration
20006	Fill	The device is offline and no offline ad is available	Integrator	Restore connectivity and load again
20007	Fill	The bid price is below the floor price	Operations	Check the placement floor price and bidding configuration
20008	Fill	The ad was filtered because of sensitive content	Integrator/Operations	Check the current scene and brand restriction configuration
30001	Ad Source	Ad source initialization failed	Integrator	Check the corresponding *-lib, platform App ID, Manifest, ProGuard rules, and version compatibility
30002	Ad Source	Ad source request timed out	Integrator/Platform	Check connectivity, platform status, and request-period logs
30003	Ad Source	Ad source request failed	Integrator/Platform	Use errorMessage and the platform error code to diagnose the failure
30004	Ad Source	Ad material could not be obtained	Integrator/Platform	Check material network requests and the platform response
30005	Ad Source	The request object was destroyed	Integrator	Check destroy() timing and do not destroy the object before loading completes
30006	Ad Source	Bidding query failed	Operations/Platform	Check bidding type, placement, and platform bidding configuration
40001	Display Trigger	The device is online but no ad can be displayed	Integrator	Display only after onLoad() succeeds, and check whether the ad expired or was already used
40002	Display Trigger	The device is offline and no offline ad can be displayed	Integrator	Restore connectivity and load a new ad
50001	Display	Ad display failed	Integrator/Platform	Record onShowError() and inspect the platform logs
50002	Display	A required JS Banner element is missing	Integrator/SDK Support	Check Banner rendering parameters and provide logs if it persists
60001	Media Usage	The App ID is invalid	Integrator/Operations	Check the initialization App ID and platform application status
60002	Media Usage	An operation used a destroyed ad object	Integrator	Correct the object lifecycle and do not call destroy() before later operations
60003	Media Usage	Splash display parameters are invalid	Integrator	Check Splash display parameters and the integration example
60004	Media Usage	The SDK cannot obtain the ad handler	SDK Support	Provide the SDK version and complete incident-period logs
60005	Media Usage	Native display parameters are invalid	Integrator	Check the Native container, ad information, and binding parameters
60006	Media Usage	The current ad is displaying and another load cannot start	Integrator	Wait for the ad to close before loading again
60007	Media Usage	The current scene contains sensitive content and the ad cannot display	Integrator/Operations	Check the scene content and brand restriction configuration
60008	Media Usage	The SDK has not been initialized	Integrator	Initialize the SDK and wait for onCloudComplete
70001	Cloud Configuration	Cloud configuration request timed out	Integrator	Check device connectivity and cloud request logs
70002	Cloud Configuration	Cloud request parameters are invalid	Integrator/SDK Support	Check initialization parameters and provide logs if it persists
70003	Cloud Configuration	The App ID does not exist on the platform	Operations	Confirm the platform application and App ID
70004	Cloud Configuration	The package name does not match the App ID	Integrator/Operations	Compare the installed package name with the platform application configuration
70005	Cloud Configuration	The operating system does not match the platform configuration	Operations	Confirm that the platform application is configured for Android
70006	Cloud Configuration	The platform application is disabled	Operations	Enable the application on the platform
70007	Cloud Configuration	No matching local placement configuration was found	Integrator/Operations	Wait for cloud success, then check the placement, region, and cache; see Frequently Asked Questions
70008	Cloud Configuration	The daily impression limit was reached	Operations	Check placement frequency-cap configuration
70009	Cloud Configuration	The hourly impression limit was reached	Operations	Check placement frequency-cap configuration
70010	Cloud Configuration	The display interval has not elapsed	Integrator	Request again only after the configured interval
70011	Cloud Configuration	No ad source is configured for the placement	Operations	Configure and enable an ad source for the placement
70012	Cloud Configuration	The API does not match the placement ad format	Integrator/Operations	Use the correct ad API for the configured placement format
70013	Cloud Configuration	The placement is disabled	Operations	Enable the placement on the platform
70014	Cloud Configuration	Request preparation failed	Integrator/SDK Support	Check request parameters and provide complete incident-period logs

Hisavana SSP Ad Source Pass-Through Error Codes

The following errors originate from the Hisavana SSP ad source and may be returned unchanged through onError():

Error Code	Description	Owner	What to Check
9000	Network exception	Integrator	Check device connectivity and ADSDK_N logs
9003	Placement ID configuration error	Operations	Confirm the Hisavana SSP placement and server configuration
9009	Placement unavailable	Integrator/Operations	Confirm that cloud configuration is current and the placement is enabled
9031	Network request timeout	Integrator	Check network quality and request logs
9035	Request succeeded but returned no fill	Operations/Platform	Verify the path with test ads, then check delivery region and inventory
9041	Invalid App ID	Integrator/Operations	Check the initialization App ID and platform application configuration
9042	Cloud configuration unavailable	Integrator/Operations	Check connectivity, the cloud callback, and platform application status

5.2.2 Admob Ad Loading Failure Platform Reference Table

Error Code	Error Type	Description
0	ErrorCode.ERROR_CODE_INTERNAL_ERROR	Internal error. For example, received invalid response from ad server.
1	ERROR_CODE_INVALID_REQUEST	Ad request invalid. For example, ad ID incorrect.
2	ERROR_CODE_NETWORK_ERROR	Ad request unsuccessful due to network connection.
3	ERROR_CODE_NO_FILL	Ad request successful but no ad returned due to lack of ad inventory.
8	ERROR_CODE_APP_ID_MISSING	Ad request not made due to missing app ID.
10	ERROR_CODE_REQUEST_ID_MISMATCH	Request ID not found in ad string.
11	ERROR_CODE_INVALID_AD_STRING	Ad string invalid. For example, no request ID in ad string.
512	MAX_CONTENT_URL_LENGTH	Maximum content URL length.

5.2.3 Applovin Error Code Reference

5.2.4 Pangle Error Code Reference

5.2.5 Inmobi Error Code Reference

5.2.6 Mintegral Error Code Reference

5.2.7 Vungle Error Code Reference

5.2.8 Bigo Error Code Reference

5.2.9 Media Viewing Main Process Logs

Reminder: To view ad SDK main process logs for ad requests, use the following commands to enable SDK logs

adb shell setprop log.tag.Hisavana_Log DEBUG
adb logcat | grep Hisavana_Log