{"data":{"id":"76251","string_id":"c5Q1nQ","status":"1","parent_id":"76196","slug":"aAjULO","order":"7","name":"Integration Testing","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"1709722539","add_time":"1709721485","update_time":"1783478283","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"parent_name":"SDK Access Guide","parent_type":"1","parent_slug":"cUkkAX","child":[{"id":"76252","string_id":"6orzSN","status":"1","parent_id":"76251","slug":"How-to-test-ads","order":"0","name":"How to test ads","type":"2","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1709722539","add_time":"1709721485","update_time":"1783050423","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"76252","content":"## **1.** SDK Integration Verification\n\n> **Note:** Do not include this API in the build submitted for review, as it may affect the review.\n\n```\nATSDK.integrationChecking(applicationContext);\/\/Check whether the SDK integration of each ad platform is normal based on the output logs.\n```\n\nIn Logcat, filter with the Tag **anythink** to view the logs. Pay attention to whether the **Status** field under each ad platform is **Success**. If it is **Success**, that ad platform is correctly integrated; otherwise, the integration is incorrect and you need to examine each parameter specifically to make the corresponding modifications and supplement the missing integration parts.\n\nThe log output example is as follows:\n\n```\n********************************** Network Integration Status *************************************\n----------------------------------------\nNetworkName: Admob \/\/Name of the mediated ad platform\nSDK: VERIFIED \/\/Verifies whether the Mediation SDK is correct. Displays VERIFIED if correct, otherwise NOT VERIFIED.\nDependence Plugin: VERIFIED \/\/Verifies whether the plugin that the ad platform depends on exists. Displays VERIFIED if correct, otherwise displays the missing configuration.\nActivities : VERIFIED \/\/Verifies whether the ad platform's Activity declaration exists. Displays VERIFIED if correct, otherwise displays the missing configuration.\nProviders : VERIFIED \/\/Verifies whether the ad platform's Provider declaration exists. Displays VERIFIED if correct, otherwise displays the missing configuration.\nStatus: Success \/\/Verifies whether the ad platform is fully integrated correctly. Displays Success if correct, otherwise displays Fail.\n----------------------------------------\nNetworkName: Facebook\nSDK: VERIFIED\nDependence Plugin: VERIFIED\nActivities : VERIFIED\nServices : VERIFIED\nProviders : VERIFIED\nStatus: Success\n********************************** Network Integration Status *************************************\n```\n\n## **2.** SDK Log Switch\n\n> **Note:** The log feature must be turned off before the app goes live.\n\n```\nATSDK.setNetworkLogDebug(true);\n```\n\nAfter enabling the log feature, you can obtain the test device ID:\n\n- Open Android Studio's Logcat, filter with \"anythink\" as the tag, and view the SDK logs.\n- The following log will be printed when the Taku SDK is initialized. You can obtain the device ID from the log.\n\n```\nanythink: ********************************** UA_5.9.96 *************************************\nanythink: OAID: ef7e0bcaf130b9b0 , AndroidID: f669f2b7137d82b9\nanythink: ********************************** UA_5.9.96 *************************************\n```\n\nLog Example:\n\n```\nanythink_network:\n\u2554\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n\u2551 {\n\u2551 \"placementId\": \"b5bbdc725768fa\", \/\/The ad placement ID that initiated the load.\n\u2551 \"adType\": \"inter\", \/\/The ad placement type that initiated the load.\n\u2551 \"mixedFormatAdType\": -1,\n\u2551 \"action\": \"request_result\", \/\/Action after initiating ad loading: request (ad request), request_result (ad request result), impression (ad impression), click (ad click), close (ad close).\n\u2551 \"refresh\": 0,\n\u2551 \"result\": \"fail\", \/\/Result parameter, success or fail.\n\u2551 \"segmentId\": 0, \/\/(Added in v5.7.7) The traffic group where the current Ad Source belongs. 0 indicates the default group.\n\u2551 \"adSourceId\": \"1423289\", \/\/Ad Source ID.\n\u2551 \"position\": 0, \/\/The sorting position of the current Ad Source under the Ad Placement.\n\u2551 \"networkFirmId\": 6, \/\/Taku's unique ID used to distinguish third-party ad platforms. See the mapping at (https:\/\/help.takuad.com\/docs\/2KR6QU)\n\u2551 \"networkName\": \"Mintegral\", \/\/Ad platform name.\n\u2551 \"networkVersion\": \"MAL_16.1.41\", \/\/Ad platform SDK version.\n\u2551 \"networkUnit\": \"{\\\"is_video\\\":\\\"0\\\",\\\"video_muted\\\":\\\"0\\\",\\\"suport_video\\\":\\\"1\\\",\\\"appkey\\\":\\\"ef13ef712aeb0f6eb3d698c4c08add96\\\",\\\"unitid\\\":\\\"1726152\\\",\\\"appid\\\":\\\"100947\\\"}\", \/\/Configuration of this Ad Source in the TopOn dashboard (corresponds to the third-party ad platform's app and placement info).\n\u2551 \"isHB\": 0,\/\/Whether the Ad Source is a Header Bidding Ad Source.\n\u2551 \"msg\": \"code:[ 4001 ]desc:[ Return Ad is empty. ]platformCode:[ ]platformMSG:[ EXCEPTION_UNIT_ADTYPE_ERROR ]\", \/\/If loading fails, the complete error information will be output here.\n\u2551 \"hourly_frequency\": 0, \/\/Number of times displayed in the current hour.\n\u2551 \"daily_frequency\": 0, \/\/Number of times displayed in the current day.\n\u2551 \"network_list\": \"6,6,6\", \/\/The IDs in the current third-party ad platform request list, separated by \",\".\n\u2551 \"request_network_num\": 1, \/\/Indicates how many third-party ad platform Ad Source loads are initiated simultaneously (corresponds to the parallel request count in the Taku dashboard Advanced Settings).\n\u2551 \"handle_class\": \"com.anythink.network.mintegral.MintegralATInterstitialAdapter\" \/\/The class name that calls the ad platform API.\n\u2551 }\n\u255a\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n```\n\n> Note:\n>\n> - If the result field of all action type logs is success, then the ad platform is integrated normally.\n> - If the result field of a certain log is fail, it indicates that an error occurred in that ad behavior. You need to check the content of the msg field in the log, with the following format:\n\n```\n\"code[ \" + code + \" ],desc[ \" + desc + \" ],platformCode[ \" + platformCode + \" ],platformMSG[ \" + platformMSG + \" ]\"\n\ncode: Taku SDK's internal error code.\ndesc: Taku SDK's internal error description.\nplatformCode: The third-party ad platform's error code (the error code to check when no ad fill occurs).\nplatformMsg: The third-party ad platform's error message (the error message to check when no ad fill occurs).\n```\n\nYou can look up the relevant [Taku Error Code](https:\/\/help.takuad.com\/en\/docs\/Error-code-description-ua8l) based on **code and desc**. If **code=4001**, you need to check [Third-Party Ad Platform Error Codes & FAQ](https:\/\/help.takuad.com\/en\/docs\/Error-code-description-ua8l#2.%20Third-Party%20Ad%20Platform%20Error%20Codes) based on **platformCode and platformMSG** for troubleshooting.\n\n## **3.** Testing Ads Using the Test Tool\n\n### 3.1 Test Tool Introduction\n\n- Basic Info: Check app, device, and SDK related information.\n- Taku SDK Settings: Check whether privacy settings and permissions are successfully configured.\n- Integration Check: Check the integration status of third-party platform SDKs and Adapters, testing suggestions, and test ad loading for third-party ad platforms.\n\n> **Note:**\n>\n> - Supports use for checking after integrating the Taku SDK.\n> - The test tool is only for checking SDK integration and cannot replace the app's own ad logic testing.\n> - After testing is complete and before the app goes live, the code that calls the test tool must be deleted.\n> - SDK version requirement: v6.2.70 and above.\n> - Friendly Reminder: Custom Adapter only supports the online ad placement testing feature; other features are not supported.\n\n#### \u25cf Version Notes\n\n| Taku SDK Version | Test Tool Version | Description |\n| ------------------------------- | ------------ | -------------------------------- |\n| **v6.6.21 and above (Recommended)** | v1.1.5 | **Adapted to higher SDK version, optimized known issues.** |\n| **v6.5.50-6.6.21 below (Recommended)** | v1.1.3 | **Adapted to higher SDK version, optimized known issues.** |\n| **v6.2.70-6.5.50 below (Recommended)** | **v1.1.2** | **Adapted to higher SDK version, optimized known issues.** |\n\n> **\ud83d\udca1Tips:** When testing with the test tool, **pay close attention** to the following:\n>\n> 1. **Check whether the ad platform's SDK integration display is correct.**\n> 2. **Check whether the request, impression, and click for each ad platform's formats are normal.**\n\n###\n\n### 3.2 Test Tool Integration\n\n(1) Refer to the [Taku SDK Integration Guide](https:\/\/help.takuad.com\/en\/docs\/cUkkAX) to integrate the SDK.\n\n(2) Import the test tool by adding the reference in `build.gradle`:\n\n```\nrepositories {\n maven {\n url \"https:\/\/jfrog.anythinktech.com\/artifactory\/debugger\"\n }\n}\ndependencies {\n \/\/v6.2.70-6.5.50 below\n implementation 'com.anythink.sdk:debugger-ui:1.1.2'\n \/\/v6.5.50 and above\n implementation 'com.anythink.sdk:debugger-ui:1.1.3'\n}\n```\n\n(3) Launch the test tool:\n\n> **Note:** You must first Initialize the Taku SDK, then call the following method to use the test tool.\n\n```\nATDebuggerUITest.showDebuggerUI(context);\n```\n\n### 3.3 Test Tool Usage\n\n#### 3.3.1 Basic Info\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a4725974accd.png)\n\n\n\n\n\n#### 3.3.2 Taku SDK Settings\n\nTaku SDK Settings consists of two parts: Privacy Settings and Permission Settings.\n\n(1) Privacy Settings\n\n[Restricted device privacy data reporting](\/docs\/wNPGmZ)\n\n(2) Permission Settings: The list of permissions requested by the app.\n\n\n![Article Image](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a4720e74bf4d.png)\n\n\n\n#### 3.3.3 Integration Check\n\n(1) View the integration status of the ad platform list: **Integration Issue, Integration Complete, Not Integrated**.\n\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a47217f2e953.png)\n\n\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a47217180053.png)\n\n\n\n(2) Check the switch to enable debug mode.\n\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a47218b3dc6b.png)\n\n\n\n(3) Select an ad platform to enter **debug mode**, and click the share button in the top right corner to share the ad platform information of the current page.\n\n(4) Select the ad platform's ad format for testing operations.\n\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a4721b50d1d9.png)\n\n\n\n\n#### 3.3.4 Online ID Testing\n\nOnline ID Testing supports testing ads using the Ad Placements configured in the Taku dashboard, and supports filtering Ad Sources under the Ad Placement for testing.\n\n> **Note:** After running Online ID Testing, if you switch back to testing within the developer's app, you need to restart the app to avoid cache issues caused by the in-app test Ad Placement being the same as the test tool's Ad Placement.\n\n**(1) Prerequisites**\n\n- SDK Version: v6.3.68 and above.\n- Test Tool Version: v1.0.5 and above.\n- Set SDK Debug Key: The steps to obtain it are: `Log in to the Dashboard` -> `Account Management` -> `Key` -> `SDK Debug Key`.\n- Debug mode is in the off state.\n\n**(2) Get Started**\n\nSample code:\n\n```\n\/\/1. Initialize SDK\nATSDK.init(context, \"your app id\", \"your app key\");\n\/\/2. Set Debug Key to enter the test tool\nATDebuggerUITest.showDebuggerUI(context, \"your debug key\");\n```\n\n**(3) Online ID List**\n\n- Supports viewing app information: App name, App ID, App package name, SDK version.\n- Supports viewing the list of Ad Placements configured under the app.\n- Supports viewing Ad Placement information: Name, ID.\n- Supports clicking on an Ad Placement to navigate to the Ad Placement Testing page for testing (VAST\/VMAP Ads are not currently supported for testing).\n\n \n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a4721f573301.png)\n\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a4721fd4c4e9.png)\n\n\n**(4) Ad Placement Testing**\n\n- Supports switching traffic groups.\n- Supports bidding and waterfall Ad Sources.\n- Supports filtering Ad Sources: Unchecked Ad Sources will be filtered when initiating a load.\n \n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a47237960447.png)\n\n\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/5expvy\/article\/NL1sTV\/6a47238ab5117.png)\n\n\n## **4.** Testing Ads via Debug Mode\n\n(1) Using debug mode, you can lock onto a single ad platform and use the test Ad Sources pre-configured by Taku to test and verify the ad platform integration.\n\n(2) After testing begins, first enable the SDK's log feature and obtain the test device ID. Then call the API for each ad platform, configure the test device, test ad platform, and test ad type, and enable debug mode. Finally, based on the log output results, make the corresponding adjustments.\n\n(3) Each ad platform has its own specific method, and different ad formats have different parameter configurations. Please select the method to call based on the ad platform and ad format you need to test. For the ad formats supported by each ad platform, refer to: [Mediation Platform Overview](https:\/\/help.takuad.com\/en\/docs\/2KR6QU).\n\n(4) We recommend calling the API to configure before Taku SDK Initialization.\n\n(5) After configuration is complete, all Ad Placements on the test device will only request test Ad Sources of the ad platform specified in the configuration.\n\n> **Note:**\n>\n> - For Bidding Ad Sources, this configuration only supports Taku ADX. Other Bidding Ad Sources cannot be tested using this method.\n\n### 4.1 Ad Platforms Supported by Debug Mode\n\n#### 4.1.1 China Platforms\n\n#### \u25cf Mintegral\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Mintegral_NETWORK) .setInterstitial(Mintegral_INTERSTITIAL_VIDEO).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Mintegral_NETWORK).setNativeType(nativeType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\n Mintegral_NATIVE_SELF_RENDER: Native Custom Rendering\n Mintegral_NATIVE_TEMPLATE: Native Auto Rendering\n```\n\n#### \u25cf GDT (Tencent Ads)\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(GDT_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(GDT_NETWORK).setNativeType(nativeType).setInterstitial(interType).build());\nParameter Description:\nGDT_NATIVE_TEMPLATE: Platform Template Rendering\nGDT_NATIVE_SELF_RENDER: Developer Self-Rendering\nGDT_NATIVE_DRAW_TEMPLATE: Video Patch Ad (Template Rendering)\nGDT_NATIVE_DRAW_SELF_RENDER: Video Patch Ad (Self-Rendering)\ninterType: Set Interstitial Ad type, supports the following types:\nGDT_INTERSTITIAL: Popup Video\nGDT_INTERSTITIAL_FULL_SCREEN: Full-Screen Video\n```\n\n#### \u25cf Pangle (China)\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(TT_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(TT_NETWORK).setNativeType(nativeType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nTT_NATIVE_TEMPLATE: Info Feed Ad + Template Rendering\nTT_NATIVE_SELF_RENDER: Info Feed Ad + Self-Rendering\nTT_NATIVE_DRAW_TEMPLATE: Draw Info Feed Ad + Template Rendering\nTT_NATIVE_DRAW_SELF_RENDER: Draw Info Feed Ad + Self-Rendering\n```\n\n#### \u25cf Baidu\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(BAIDU_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(BAIDU_NETWORK).setNativeType(nativeType).setInterstitial(interType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nBAIDU_NATIVE_SELF_RENDER: Self-Rendering\nBAIDU_NATIVE_TEMPLATE: Template Rendering\ninterType: Set Interstitial Ad type, supports the following types:\nBAIDU_INTERSTITIAL_FULL_SCREEN: Full-Screen Video\nBAIDU_INTERSTITIAL_TEMPLATE: Template Interstitial\n```\n\n#### \u25cf Kuaishou\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(KS_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(KS_NETWORK).setNativeType(nativeType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nKS_NATIVE_SELF_RENDER: Info Feed Ad + Self-Rendering\nKS_NATIVE_TEMPLATE: Info Feed Ad + Template Rendering\nKS_NATIVE_DRAW: Draw Info Feed Ad\n```\n\n#### \u25cf Huawei\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Huawei_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Huawei_NETWORK).setNativeType(nativeType).setInterstitial(interType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nHuawei_NATIVE_VIDEO: Video\nHuawei_NATIVE_IMAGE: Small Image\nHuawei_NATIVE_BIG_IMAGE: Large Image\ninterType: Set Interstitial Ad type, supports the following types:\nHuawei_INTERSTITIAL_IMAGE: Interstitial Image\nHuawei_INTERSTITIAL_VIDEO: Interstitial Video\n```\n\n#### \u25cf Sigmob\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Sigmob_NETWORK).build());\n\n```\n\n#### \u25cf Mimo\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Mimo_NETWORK).build());\n```\n\n#### \u25cf YouKeYing\n\n```\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Klevin_NETWORK).build());\n```\n\n#### \u25cf ADX\n\n```\nString oaid = \"\";\nString aid = \"\";\n\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, oaid, new ATDebuggerConfig.Builder(Adx_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, aid, new ATDebuggerConfig.Builder(Adx_NETWORK).setNativeType(nativeType).setInterstitial(interType).setBannerType(bannerType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\n ADX_NATIVE_EXPRESS_LEFT_PIC_RIGHT_TEXT: Left Pic Right Text\n ADX_NATIVE_EXPRESS_LEFT_TEXT_RIGHT_PIC: Left Text Right Pic\n ADX_NATIVE_EXPRESS_TOP_PIC_BOTTOM_TEXT: Top Pic Bottom Text\n ADX_NATIVE_EXPRESS_TOP_TEXT_BOTTOM_PIC: Top Text Bottom Pic\n ADX_NATIVE_SELF_RENDER: Self-Rendering\ninterType: Set Interstitial Ad type, supports the following types:\n Adx_INTERSTITIAL_FULL_SCREEN: Full-Screen Interstitial\n Adx_INTERSTITIAL_HALF_SCREEN: Half-Screen Interstitial\nbannerType: Set Banner Ad type, supports the following types:\n ADX_BANNER_SIZE_320_50: 320x50 size\n ADX_BANNER_SIZE_320_90: 320x90 size\n ADX_BANNER_SIZE_300_250: 300x250 size\n ADX_BANNER_SIZE_728_90: 728x90 size\n```\n\n### **4.2 Platforms Not Supported by Debug Mode**\n\nFor platforms not supported by debug mode, you can use the Online ID feature of the test tool for testing.\n\n- Based on the output logs, verify the Ad Sources. From the log output in Logcat, you can see the tracking of various ad actions.\n- After calling the API to configure the test rules, you can start performing various ad actions.\n- Based on `placementId`, locate the Ad Placement that needs to be verified.","pure_content":"1. SDK Integration Verification\n\nNote: Do not include this API in the build submitted for review, as it may affect the review.\n\nATSDK.integrationChecking(applicationContext);\/\/Check whether the SDK integration of each ad platform is normal based on the output logs.\n\nIn Logcat, filter with the Tag anythink to view the logs. Pay attention to whether the Status field under each ad platform is Success. If it is Success, that ad platform is correctly integrated; otherwise, the integration is incorrect and you need to examine each parameter specifically to make the corresponding modifications and supplement the missing integration parts.\nThe log output example is as follows:\n********************************** Network Integration Status *************************************\n----------------------------------------\nNetworkName: Admob \/\/Name of the mediated ad platform\nSDK: VERIFIED \/\/Verifies whether the Mediation SDK is correct. Displays VERIFIED if correct, otherwise NOT VERIFIED.\nDependence Plugin: VERIFIED \/\/Verifies whether the plugin that the ad platform depends on exists. Displays VERIFIED if correct, otherwise displays the missing configuration.\nActivities : VERIFIED \/\/Verifies whether the ad platform's Activity declaration exists. Displays VERIFIED if correct, otherwise displays the missing configuration.\nProviders : VERIFIED \/\/Verifies whether the ad platform's Provider declaration exists. Displays VERIFIED if correct, otherwise displays the missing configuration.\nStatus: Success \/\/Verifies whether the ad platform is fully integrated correctly. Displays Success if correct, otherwise displays Fail.\n----------------------------------------\nNetworkName: Facebook\nSDK: VERIFIED\nDependence Plugin: VERIFIED\nActivities : VERIFIED\nServices : VERIFIED\nProviders : VERIFIED\nStatus: Success\n********************************** Network Integration Status *************************************\n\n2. SDK Log Switch\n\nNote: The log feature must be turned off before the app goes live.\n\nATSDK.setNetworkLogDebug(true);\n\nAfter enabling the log feature, you can obtain the test device ID:\n\nOpen Android Studio's Logcat, filter with \"anythink\" as the tag, and view the SDK logs.\nThe following log will be printed when the Taku SDK is initialized. You can obtain the device ID from the log.\n\nanythink: ********************************** UA_5.9.96 *************************************\nanythink: OAID: ef7e0bcaf130b9b0 , AndroidID: f669f2b7137d82b9\nanythink: ********************************** UA_5.9.96 *************************************\n\nLog Example:\nanythink_network:\n\u2554\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n\u2551 {\n\u2551 \"placementId\": \"b5bbdc725768fa\", \/\/The ad placement ID that initiated the load.\n\u2551 \"adType\": \"inter\", \/\/The ad placement type that initiated the load.\n\u2551 \"mixedFormatAdType\": -1,\n\u2551 \"action\": \"request_result\", \/\/Action after initiating ad loading: request (ad request), request_result (ad request result), impression (ad impression), click (ad click), close (ad close).\n\u2551 \"refresh\": 0,\n\u2551 \"result\": \"fail\", \/\/Result parameter, success or fail.\n\u2551 \"segmentId\": 0, \/\/(Added in v5.7.7) The traffic group where the current Ad Source belongs. 0 indicates the default group.\n\u2551 \"adSourceId\": \"1423289\", \/\/Ad Source ID.\n\u2551 \"position\": 0, \/\/The sorting position of the current Ad Source under the Ad Placement.\n\u2551 \"networkFirmId\": 6, \/\/Taku's unique ID used to distinguish third-party ad platforms. See the mapping at (https:\/\/help.takuad.com\/docs\/2KR6QU)\n\u2551 \"networkName\": \"Mintegral\", \/\/Ad platform name.\n\u2551 \"networkVersion\": \"MAL_16.1.41\", \/\/Ad platform SDK version.\n\u2551 \"networkUnit\": \"{\\\"is_video\\\":\\\"0\\\",\\\"video_muted\\\":\\\"0\\\",\\\"suport_video\\\":\\\"1\\\",\\\"appkey\\\":\\\"ef13ef712aeb0f6eb3d698c4c08add96\\\",\\\"unitid\\\":\\\"1726152\\\",\\\"appid\\\":\\\"100947\\\"}\", \/\/Configuration of this Ad Source in the TopOn dashboard (corresponds to the third-party ad platform's app and placement info).\n\u2551 \"isHB\": 0,\/\/Whether the Ad Source is a Header Bidding Ad Source.\n\u2551 \"msg\": \"code:[ 4001 ]desc:[ Return Ad is empty. ]platformCode:[ ]platformMSG:[ EXCEPTION_UNIT_ADTYPE_ERROR ]\", \/\/If loading fails, the complete error information will be output here.\n\u2551 \"hourly_frequency\": 0, \/\/Number of times displayed in the current hour.\n\u2551 \"daily_frequency\": 0, \/\/Number of times displayed in the current day.\n\u2551 \"network_list\": \"6,6,6\", \/\/The IDs in the current third-party ad platform request list, separated by \",\".\n\u2551 \"request_network_num\": 1, \/\/Indicates how many third-party ad platform Ad Source loads are initiated simultaneously (corresponds to the parallel request count in the Taku dashboard Advanced Settings).\n\u2551 \"handle_class\": \"com.anythink.network.mintegral.MintegralATInterstitialAdapter\" \/\/The class name that calls the ad platform API.\n\u2551 }\n\u255a\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n\n\nNote:\n\nIf the result field of all action type logs is success, then the ad platform is integrated normally.\nIf the result field of a certain log is fail, it indicates that an error occurred in that ad behavior. You need to check the content of the msg field in the log, with the following format:\n\n\n\"code[ \" + code + \" ],desc[ \" + desc + \" ],platformCode[ \" + platformCode + \" ],platformMSG[ \" + platformMSG + \" ]\"\n\ncode: Taku SDK's internal error code.\ndesc: Taku SDK's internal error description.\nplatformCode: The third-party ad platform's error code (the error code to check when no ad fill occurs).\nplatformMsg: The third-party ad platform's error message (the error message to check when no ad fill occurs).\n\nYou can look up the relevant Taku Error Code based on code and desc. If code=4001, you need to check Third-Party Ad Platform Error Codes & FAQ based on platformCode and platformMSG for troubleshooting.\n3. Testing Ads Using the Test Tool\n3.1 Test Tool Introduction\n\nBasic Info: Check app, device, and SDK related information.\nTaku SDK Settings: Check whether privacy settings and permissions are successfully configured.\nIntegration Check: Check the integration status of third-party platform SDKs and Adapters, testing suggestions, and test ad loading for third-party ad platforms.\n\n\nNote:\n\nSupports use for checking after integrating the Taku SDK.\nThe test tool is only for checking SDK integration and cannot replace the app's own ad logic testing.\nAfter testing is complete and before the app goes live, the code that calls the test tool must be deleted.\nSDK version requirement: v6.2.70 and above.\nFriendly Reminder: Custom Adapter only supports the online ad placement testing feature; other features are not supported.\n\n\n\u25cf Version Notes\n\n\n\n Taku SDK Version\n Test Tool Version\n Description\n\n\n\n\n v6.6.21 and above (Recommended)\n v1.1.5\n Adapted to higher SDK version, optimized known issues.\n\n\n v6.5.50-6.6.21 below (Recommended)\n v1.1.3\n Adapted to higher SDK version, optimized known issues.\n\n\n v6.2.70-6.5.50 below (Recommended)\n v1.1.2\n Adapted to higher SDK version, optimized known issues.\n\n\n\n\n\ud83d\udca1Tips: When testing with the test tool, pay close attention to the following:\n\n\nCheck whether the ad platform's SDK integration display is correct.\n\n\nCheck whether the request, impression, and click for each ad platform's formats are normal.\n\n\n\n\n3.2 Test Tool Integration\n(1) Refer to the Taku SDK Integration Guide to integrate the SDK.\n(2) Import the test tool by adding the reference in build.gradle:\nrepositories {\n maven {\n url \"https:\/\/jfrog.anythinktech.com\/artifactory\/debugger\"\n }\n}\ndependencies {\n \/\/v6.2.70-6.5.50 below\n implementation 'com.anythink.sdk:debugger-ui:1.1.2'\n \/\/v6.5.50 and above\n implementation 'com.anythink.sdk:debugger-ui:1.1.3'\n}\n\n(3) Launch the test tool:\n\nNote: You must first Initialize the Taku SDK, then call the following method to use the test tool.\n\nATDebuggerUITest.showDebuggerUI(context);\n\n3.3 Test Tool Usage\n3.3.1 Basic Info\n\n3.3.2 Taku SDK Settings\nTaku SDK Settings consists of two parts: Privacy Settings and Permission Settings.\n(1) Privacy Settings\nRestricted device privacy data reporting\n(2) Permission Settings: The list of permissions requested by the app.\n\n3.3.3 Integration Check\n(1) View the integration status of the ad platform list: Integration Issue, Integration Complete, Not Integrated.\n\n\n(2) Check the switch to enable debug mode.\n\n(3) Select an ad platform to enter debug mode, and click the share button in the top right corner to share the ad platform information of the current page.\n(4) Select the ad platform's ad format for testing operations.\n\n3.3.4 Online ID Testing\nOnline ID Testing supports testing ads using the Ad Placements configured in the Taku dashboard, and supports filtering Ad Sources under the Ad Placement for testing.\n\nNote: After running Online ID Testing, if you switch back to testing within the developer's app, you need to restart the app to avoid cache issues caused by the in-app test Ad Placement being the same as the test tool's Ad Placement.\n\n(1) Prerequisites\n\nSDK Version: v6.3.68 and above.\nTest Tool Version: v1.0.5 and above.\nSet SDK Debug Key: The steps to obtain it are: Log in to the Dashboard -> Account Management -> Key -> SDK Debug Key.\nDebug mode is in the off state.\n\n(2) Get Started\nSample code:\n\/\/1. Initialize SDK\nATSDK.init(context, \"your app id\", \"your app key\");\n\/\/2. Set Debug Key to enter the test tool\nATDebuggerUITest.showDebuggerUI(context, \"your debug key\");\n\n(3) Online ID List\n\nSupports viewing app information: App name, App ID, App package name, SDK version.\nSupports viewing the list of Ad Placements configured under the app.\nSupports viewing Ad Placement information: Name, ID.\nSupports clicking on an Ad Placement to navigate to the Ad Placement Testing page for testing (VAST\/VMAP Ads are not currently supported for testing).\n\n\n\n(4) Ad Placement Testing\n\nSupports switching traffic groups.\nSupports bidding and waterfall Ad Sources.\nSupports filtering Ad Sources: Unchecked Ad Sources will be filtered when initiating a load.\n\n\n\n4. Testing Ads via Debug Mode\n(1) Using debug mode, you can lock onto a single ad platform and use the test Ad Sources pre-configured by Taku to test and verify the ad platform integration.\n(2) After testing begins, first enable the SDK's log feature and obtain the test device ID. Then call the API for each ad platform, configure the test device, test ad platform, and test ad type, and enable debug mode. Finally, based on the log output results, make the corresponding adjustments.\n(3) Each ad platform has its own specific method, and different ad formats have different parameter configurations. Please select the method to call based on the ad platform and ad format you need to test. For the ad formats supported by each ad platform, refer to: Mediation Platform Overview.\n(4) We recommend calling the API to configure before Taku SDK Initialization.\n(5) After configuration is complete, all Ad Placements on the test device will only request test Ad Sources of the ad platform specified in the configuration.\n\nNote:\n\nFor Bidding Ad Sources, this configuration only supports Taku ADX. Other Bidding Ad Sources cannot be tested using this method.\n\n\n4.1 Ad Platforms Supported by Debug Mode\n4.1.1 China Platforms\n\u25cf Mintegral\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Mintegral_NETWORK) .setInterstitial(Mintegral_INTERSTITIAL_VIDEO).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Mintegral_NETWORK).setNativeType(nativeType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\n Mintegral_NATIVE_SELF_RENDER: Native Custom Rendering\n Mintegral_NATIVE_TEMPLATE: Native Auto Rendering\n\n\u25cf GDT (Tencent Ads)\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(GDT_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(GDT_NETWORK).setNativeType(nativeType).setInterstitial(interType).build());\nParameter Description:\nGDT_NATIVE_TEMPLATE: Platform Template Rendering\nGDT_NATIVE_SELF_RENDER: Developer Self-Rendering\nGDT_NATIVE_DRAW_TEMPLATE: Video Patch Ad (Template Rendering)\nGDT_NATIVE_DRAW_SELF_RENDER: Video Patch Ad (Self-Rendering)\ninterType: Set Interstitial Ad type, supports the following types:\nGDT_INTERSTITIAL: Popup Video\nGDT_INTERSTITIAL_FULL_SCREEN: Full-Screen Video\n\n\u25cf Pangle (China)\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(TT_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(TT_NETWORK).setNativeType(nativeType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nTT_NATIVE_TEMPLATE: Info Feed Ad + Template Rendering\nTT_NATIVE_SELF_RENDER: Info Feed Ad + Self-Rendering\nTT_NATIVE_DRAW_TEMPLATE: Draw Info Feed Ad + Template Rendering\nTT_NATIVE_DRAW_SELF_RENDER: Draw Info Feed Ad + Self-Rendering\n\n\u25cf Baidu\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(BAIDU_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(BAIDU_NETWORK).setNativeType(nativeType).setInterstitial(interType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nBAIDU_NATIVE_SELF_RENDER: Self-Rendering\nBAIDU_NATIVE_TEMPLATE: Template Rendering\ninterType: Set Interstitial Ad type, supports the following types:\nBAIDU_INTERSTITIAL_FULL_SCREEN: Full-Screen Video\nBAIDU_INTERSTITIAL_TEMPLATE: Template Interstitial\n\n\u25cf Kuaishou\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(KS_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(KS_NETWORK).setNativeType(nativeType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nKS_NATIVE_SELF_RENDER: Info Feed Ad + Self-Rendering\nKS_NATIVE_TEMPLATE: Info Feed Ad + Template Rendering\nKS_NATIVE_DRAW: Draw Info Feed Ad\n\n\u25cf Huawei\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Huawei_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Huawei_NETWORK).setNativeType(nativeType).setInterstitial(interType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\nHuawei_NATIVE_VIDEO: Video\nHuawei_NATIVE_IMAGE: Small Image\nHuawei_NATIVE_BIG_IMAGE: Large Image\ninterType: Set Interstitial Ad type, supports the following types:\nHuawei_INTERSTITIAL_IMAGE: Interstitial Image\nHuawei_INTERSTITIAL_VIDEO: Interstitial Video\n\n\u25cf Sigmob\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Sigmob_NETWORK).build());\n\n\n\u25cf Mimo\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Mimo_NETWORK).build());\n\n\u25cf YouKeYing\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, AndroidID, new ATDebuggerConfig.Builder(Klevin_NETWORK).build());\n\n\u25cf ADX\nString oaid = \"\";\nString aid = \"\";\n\n\/\/ General Settings\nATSDK.setDebuggerConfig(context, oaid, new ATDebuggerConfig.Builder(Adx_NETWORK).build());\n\/\/ Advanced Usage\nATSDK.setDebuggerConfig(context, aid, new ATDebuggerConfig.Builder(Adx_NETWORK).setNativeType(nativeType).setInterstitial(interType).setBannerType(bannerType).build());\nParameter Description:\nnativeType: Set Native Ad type, supports the following types:\n ADX_NATIVE_EXPRESS_LEFT_PIC_RIGHT_TEXT: Left Pic Right Text\n ADX_NATIVE_EXPRESS_LEFT_TEXT_RIGHT_PIC: Left Text Right Pic\n ADX_NATIVE_EXPRESS_TOP_PIC_BOTTOM_TEXT: Top Pic Bottom Text\n ADX_NATIVE_EXPRESS_TOP_TEXT_BOTTOM_PIC: Top Text Bottom Pic\n ADX_NATIVE_SELF_RENDER: Self-Rendering\ninterType: Set Interstitial Ad type, supports the following types:\n Adx_INTERSTITIAL_FULL_SCREEN: Full-Screen Interstitial\n Adx_INTERSTITIAL_HALF_SCREEN: Half-Screen Interstitial\nbannerType: Set Banner Ad type, supports the following types:\n ADX_BANNER_SIZE_320_50: 320x50 size\n ADX_BANNER_SIZE_320_90: 320x90 size\n ADX_BANNER_SIZE_300_250: 300x250 size\n ADX_BANNER_SIZE_728_90: 728x90 size\n\n4.2 Platforms Not Supported by Debug Mode\nFor platforms not supported by debug mode, you can use the Online ID feature of the test tool for testing.\n\nBased on the output logs, verify the Ad Sources. From the log output in Logcat, you can see the tracking of various ad actions.\nAfter calling the API to configure the test rules, you can start performing various ad actions.\nBased on placementId, locate the Ad Placement that needs to be verified.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1709721487","update_time":"1783050423"},"pure_content":"1. SDK Integration Verification\n\nNote: Do not include this API in the build submitted for review, as it may affect the review.\n\nATSDK.integrationChecking(applicationContext);\/\/Check whether the SDK in"},{"id":"76253","string_id":"gbEMW0","status":"1","parent_id":"76251","slug":"Error-code-description-ua8l","order":"0","name":"Error code description","type":"2","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1709722540","add_time":"1709721487","update_time":"1782974885","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"76253","content":"> **Tips:**\n> \n> - To quickly locate the cause of the issue, it is recommended to get the full error information through `AdError#getFullErrorInfo()`\n> ```\n> \"code[ \" + code + \" ],desc[ \" + desc + \" ],\n> platformCode[ \" + platformCode + \" ],\n> platformMSG[ \" + platformMSG + \" ]\"\n> \n> code: Taku SDK's error code\n> desc: Taku SDK's error message\n> platformCode: The third-party ad platform's error code (the error code to check when no ad fill occurs)\n> platformMsg: The third-party ad platform's error message (the error message to check when no ad fill occurs)\n> ```\n\n**1.** Taku Error Code Information\n--------------\n\n| Error Code | Description |\n|---|---|\n| 10001 | Incorrect App ID or App Key. Please **check the App ID and App Key passed when Initializing the Taku SDK**. |\n| 10003 | 1\\. Incorrect App ID. Please **check the App ID passed when Initializing the Taku SDK**. 2\\. The Taku Ad Placement ID does not match the App ID. Please **check the Placement ID passed when calling the load method in the code**. |\n| 10004 | Incorrect Taku Ad Placement ID. Please **check the Placement ID passed when calling the load method**. |\n| 9999 | 1. Generally a network request error. Check whether the network status is normal. 2. platformMSG:\\[ chain validation failed \\], check whether the system time has been adjusted. |\n| 9990 | HTTP interface request returned a status error. Contact Taku colleagues to check the error message. |\n| 9991 | Interface request returned a business code error. Contact Taku colleagues to check the error message. |\n| 9992 | The GDPR level is set too low. Check whether the FORBIDDEN level has been manually set. |\n| 2001 | Ad loading timeout. Check whether the current tested Ad Source is an overseas platform and whether the phone's network has a VPN enabled. |\n| 2002 | The Taku SDK package is not fully imported. The third-party ad vendor's Adapter package is missing **(anythink\\_network\\_\\*.aar)**. Confirm whether all required third-party SDK packages for the Mediation have been imported as instructed. |\n| 2003 | The display count for the current Ad Placement has reached the limit. Check whether the Taku dashboard configuration has restricted the display count for this Ad Placement. |\n| 2004 | The current Ad Placement is in a non-display time period. Check whether the Taku dashboard configuration has restricted the display interval for the Ad Placement. |\n| 2005 | The Ad Placement is in the loading phase. After initiating a request for the same Ad Placement, before receiving the load success or failure callback, this Ad Placement cannot initiate the next load. Wait for the load success or failure callback. |\n| 2006 | Check whether the imported third-party ad platform SDK packages are complete. If complete, check whether the imported version matches the version specified on GitHub. If not, the third-party SDK packages need to be supplemented. |\n| 2007 | Usually occurs when ad loading is immediately initiated in the load failure callback. Prohibited: Do not immediately initiate ad loading in the load failure callback. A certain time interval must pass since the last Ad Placement load failure before initiating ad loading again. Delay the ad loading call. |\n| 2008 | After a load failure for the same Ad Placement, do not call the load method immediately in the load failure callback for retry. Wait for more than 10 seconds before retrying. |\n| 2009 | The number of ad placement loads within a certain time interval has reached the limit. |\n| 3001 | Strategy acquisition error. 1. Check whether the network is normal. 2. Check whether the AppId, AppKey, and PlacementId used match. 3. **Check whether the AppId, AppKey, and PlacementId in the code are correct and match (must not contain spaces).** Call **ATSDK.setNetworkLogDebug(true);** and filter **anythink** in Logcat to view the parameters currently passed to the SDK. Please check these parameters. |\n| 3002 | One of the passed AppId, AppKey, or PlacementId is an empty string. Call **ATSDK.setNetworkLogDebug(true);** and filter **anythink** in Logcat to view the parameters currently passed to the SDK. Please check these parameters. |\n| 3003 | The Ad Placement does not match the called API. For example: a Banner Ad Placement was called using the Rewarded Video API to load an ad. |\n| **4001** | Usually occurs when a third-party ad platform returns an error resulting in no ad fill. **You can get the full error information via `AdError.getFullErrorInfo()`. Use `platformCode` and `platformMsg` to view the ad platform's error code and error message. Please check the third-party ad platform error codes for troubleshooting.** |\n| 4002 | The Context has been destroyed. You need to recreate the corresponding ad type object and then re-initiate ad loading. |\n| 4003 | The status of this Ad Placement has been closed. Check whether the status switch for this Ad Placement in the Taku dashboard is enabled. |\n| 4004 | **This Ad Placement has no Ad Source configured in the Taku dashboard. You need to go to Taku Dashboard - Mediation Management to add a third-party ad platform's Ad Source for the Ad Placement.** |\n| 4005 | All Ad Sources under the Ad Placement have been filtered. Possible reasons are as follows: 1. Check whether **Display Limit** or **Display Interval** has been set for the Ad Source in the Taku dashboard. 2. If only Header Bidding Ad Sources are configured, when the bidding fails, the Header Bidding Ad Sources will be filtered. |\n| 4006 | Video playback failed. Refer to **Error Code 4001** for troubleshooting. |\n| 4007 | Ad Source bidding failed. Refer to **Error Code 4001** for troubleshooting. |\n| 4008 | The Ad Source has been filtered due to custom filtering logic in the developer's code. If the filtering does not meet expectations, troubleshoot the custom filtering logic. |\n| 4009 | In debug mode, the Ad Placement has no Ad Source configured. |\n\n\n\n**2.** Third-Party Ad Platform Error Codes\n-------------\n\n### \u25cf Tencent Ads\n\n| Common Error | Solution |\n|---|---|\n| 6000 - 102006 | No suitable ad matched. Retries are prohibited, otherwise it may trigger system policies leading to decreased traffic revenue. **For testing integration, you can use Taku's debug mode (DebuggerConfig) for testing.** |\n| 5002 - Video creative download error | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| Ad images not displaying | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| Native ad video black screen or transparent | Enable hardware acceleration in AndroidManifest.xml. |\n| 5004 - No suitable ad matched | In this situation, retrying ad requests multiple times is prohibited, otherwise it may affect the system's evaluation of your traffic and thus affect monetization. **For testing integration, you can use Taku's debug mode (DebuggerConfig) for testing.** |\n| 5004 - No ads | 1. Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). 2. Check the Tencent Ads Ad Source configuration in the Taku dashboard (whether it is template rendering 2.0). |\n| 5006 - Package name verification error. The current app's package name does not match the package name filled in during media registration on the GDT official website, resulting in no ad return. | **The package name configured in the code** must match the one in the GDT dashboard. |\n| 5010 - Ad format verification failed. Check whether the Ad Placement and API usage are consistent. | Check the Tencent Ads Ad Source configuration in the Taku dashboard (whether it is template rendering, whether it is full-screen video, etc.). |\n| 2001 - Initialization error | Developer self-checks parameter issues. 1. Do not split the Tencent Ads SDK package. 2. Check the Tencent Ads Ad Source configuration in the Taku dashboard. 3. **If parameters are correct, confirm whether a real device is being used. Do not use a simulator for testing.** |\n| 4004 - Splash Ad container not visible | 1. Troubleshoot whether the container is hidden or obscured. 2. If show is executed directly in the Activity's onCreate, a delay may be needed. It is recommended to use the main thread's Handler to postDelay by 10ms before calling the showAd method and try again. 3. Add container.removeAllViews(); call before displaying. |\n| 102006 - No ad found matching the price requirement or experience requirement | It is recommended to appropriately adjust the floor price\/target price settings, or go to the platform's ad center to check the blocking rules. |\n\n\n\nFor more Tencent Ads error information, see: [Tencent Ads Error Codes](https:\/\/developers.adnet.qq.com\/doc\/android\/union\/union_debug#sdk%20%E9%94%99%E8%AF%AF%E7%A0%81)\n \n\n### \u25cf Pangle (China)\n\n| Common Error | Solution |\n|---|---|\n| 4201 - No initializer | 1. Check whether the ABI architecture has been restricted according to the integration documentation. 2. Check whether the com.android.support:appcompat-v7 dependency or androidx.appcompat:appcompat dependency has been added according to the integration documentation. |\n| -7 - Splash Ad image load failed | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| No result callback after loading | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| Ad images not displaying | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| Video playback shows black screen | Check whether the **WAKE\\_LOCK** permission is configured in the Manifest. |\n| 20001 | Request has no fill due to no suitable ad returned. Occasional occurrences are normal. Try switching devices for verification. Do not use a simulator for testing, or try again later. If the issue cannot be resolved, check the Pangle (China) SDK error codes for troubleshooting or submit a ticket to the Pangle platform for inquiry. **For testing integration, you can use the test mode in the Taku dashboard's Ad Placement - Advanced Settings.** |\n| 40029 | Check the rendering type of the Pangle (China) placement ID. The Taku dashboard's Pangle (China) Ad Source configuration must be consistent with the Pangle (China) dashboard's configuration. |\n| 40025 | 1. Check whether the system time of the test device is the current correct time. 2. Check whether the ABI architecture has been restricted according to the integration documentation. 3. If obfuscation is enabled, check the obfuscation rules provided in the downloaded SDK package. 4. Download the SDK from the Pangle (China) dashboard and replace the Pangle (China) SDK provided by Taku (open\\_ad\\_sdk\\_\\*.aar). |\n| 40021 - APK signature SHA1 value does not match the media platform entry | The app's signature must be consistent with the signature configured in the Pangle (China) dashboard. If it was just configured, clear the cache and try again after 5 minutes. |\n| 40019 - Media configuration adtype does not match the request | Check the Taku dashboard Pangle (China) Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes. |\n| 40018 - Media package name does not match the registered one | **The package name configured in the code** must match the one in the Pangle (China) dashboard. If it was just configured, clear the cache and try again after 5 minutes. |\n| 40016 - slot\\_id and app\\_id correspondence is invalid | Check the Taku dashboard Pangle (China) Ad Source configuration for spaces or special characters. |\n| 40006 - Ad Placement ID invalid | Check the Taku dashboard Pangle (China) Ad Source configuration for spaces or special characters. |\n| 0 - null | This error is reported on weak networks. Check the network status or switch networks and try again. |\n| Banner display size issue | Before calling load, specify the LayoutParams width and height values for ATBannerView. |\n| Null pointer error when playing Pangle (China) Rewarded Video ad | If multiple dex files are generated during packaging, ensure that Pangle (China) related classes are included in classes.dex. |\n\n\n\nFor more error information, see: (Login required) [Pangle (China) Error Codes](https:\/\/www.csjplatform.com\/union\/media\/union\/download\/detail?id=195&docId=27625&locale=zh-CN&osType=android)\n\n### \u25cf Baidu\n\n| Common Error | Solution |\n|---|---|\n| Ad cannot be obtained | 1. Rewarded Video takes effect two hours after configuration. 2. Use the test mode in the Taku dashboard's Ad Placement - Advanced Settings for testing. |\n| No callback when loading Banner Ad | ATBannerView needs to be first added to the window before initiating a load request. |\n\n\n\n\n\nFor more Baidu error information, see: [Baidu Error Codes](https:\/\/union.baidu.com\/docs\/sdk\/AndroidSDK\/10511\/#sdk-%E9%94%99%E8%AF%AF%E7%A0%81)\n\n### \u25cf Kuaishou\n\n| Common Error | Solution |\n|---|---|\n| 40003 - Ad data is empty | If it occurs consistently, contact Kuaishou personnel. |\n| 40004 - Video resource cache failed | Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| Native ad video black screen or transparent | Enable hardware acceleration in AndroidManifest.xml. |\n| 0 - Network error | 1. Check whether the network is normal. 2. Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network\\_security\\_config.xml). |\n| 310002 - appId invalid | Check the Taku dashboard Kuaishou Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes. |\n| 310004 - packageName does not match the registered packageName | **The package name configured in the code** does not match the one in the Kuaishou dashboard. |\n| 330002 - posId invalid | Check the Taku dashboard Kuaishou Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes. |\n| 330004 - posId and registered appId info inconsistent | Check the Taku dashboard Kuaishou Ad Source configuration, and whether a different appId was used to Initialize Kuaishou. |\n| Native ad display abnormal | Set fixed width and height values for ATNativeAdView. |\n\n\n\nFor more Kuaishou error information, see: (Login required) [Kuaishou Error Codes](https:\/\/ssp.e.kuaishou.com\/#\/access\/sdk)\n\n### \u25cf Sigmob\n\n| Common Error | Solution |\n|---|---|\n| 200000 - No ad fill | Use Taku's [Debug Mode (DebuggerConfig)](https:\/\/help.takuad.com\/en\/docs\/How-to-test-ads) for testing. |\n| Sigmob Splash Ad consistently fails to retrieve ads | Devices on Android 6.0 and above need to dynamically request the **READ\\_PHONE\\_STATE** permission. |\n| 500701 - No ad channels have been enabled for the app | Check the app status in the Sigmob dashboard. |\n| 500420 - The requested app has closed ad services | Check the app status in the Sigmob dashboard. |\n| 500473 - The requested app does not exist | Check the Taku dashboard Sigmob Ad Source configuration. |\n| 500424\/500422\/500482 | 1. Devices on Android 6.0 and above need to dynamically request the **READ\\_PHONE\\_STATE** permission. 2. For Android 10, please refer to Sigmob's [FAQ](https:\/\/doc.sigmob.com\/Sigmob%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97\/SDK%E9%9B%86%E6%88%90%E8%AF%B4%E6%98%8E\/Android\/%E5%B8%B8%E8%A7%81%E9%97%AE%E9%A2%98\/) regarding **How to fill ads domestically on Android 10**. |\n| Ads cannot be retrieved on Android 10 | Refer to Sigmob's [FAQ](https:\/\/doc.sigmob.com\/Sigmob%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97\/SDK%E9%9B%86%E6%88%90%E8%AF%B4%E6%98%8E\/Android\/%E5%B8%B8%E8%A7%81%E9%97%AE%E9%A2%98\/) regarding **How to fill ads domestically on Android 10**. |\n| After ad loads successfully, there is no playback or subsequent callbacks | Sigmob's callbacks depend on the LocalBroadcastManager library. Check whether the com.android.support:appcompat-v7 dependency is imported (for Androidx, the corresponding one is androidx.localbroadcastmanager:localbroadcastmanager). |\n\n\n\nFor more Sigmob error information, see: [Sigmob Error Codes](https:\/\/doc.sigmob.com\/#\/Sigmob%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97\/SDK%E9%9B%86%E6%88%90%E8%AF%B4%E6%98%8E\/Android\/%E9%94%99%E8%AF%AF%E7%A0%81\/)\n\n### \u25cf TapTap\n\n| Common Error | Solution |\n|---|---|\n| 3002 - Network error | Check whether the phone's network environment is normal. |\n| 3003 - Interstitial Ad orientation parameter does not match the supported direction of the Ad Placement | Modify the landscape and portrait configuration of the TapTap dashboard Ad Placement. |\n| 9999 - Failed to retrieve ad creative: Unknown error | Regular no-fill error. Use Taku's [Debug Mode (DebuggerConfig)](https:\/\/help.takuad.com\/en\/docs\/How-to-test-ads) for testing. |\n\n\n\nFor more error information, see: [TapTap Error Codes](https:\/\/developer.taptap.cn\/docs\/sdk\/tap-adn\/tds-tapad\/#sdk-%E5%B8%B8%E8%A7%81%E9%94%99%E8%AF%AF%E7%A0%81%E6%B1%87%E6%80%BB)\n\n### \u25cf Jingdong Ads\n\n| Common Error | Solution |\n|---|---|\n| 2001 - Network error | Check whether the phone's network environment is normal. |\n| 2002 - No ad matched | It is recommended to switch to a device registered with a JD account, then initiate the ad request again. |\n| 3000 - The tagid and app id fields in the request are inconsistent with the platform configuration | Check whether the placement ID parameters are set correctly. |\n| 4041 - Occasional occurrence, retry the request | Occasional occurrence, retry the request. If it occurs frequently, contact JD R&D. |\n| 4042, 4043 - Request too frequent, retry the request | No ad matched. It is recommended to re-initiate the ad request. |\n\n\n\nFor more error information, see: [Jingdong Ads Error Codes](https:\/\/help-sdk-doc.jd.com\/ansdkDoc\/access_docs\/Android\/%E9%94%99%E8%AF%AF%E7%A0%81\/%E9%94%99%E8%AF%AF%E7%A0%81.html)\n\n### \u25cf Mintegral\n\n| Common Error | Solution |\n|---|---|\n| EXCEPTION\\_RETURN\\_EMPTY | China version: 1. Ensure that the option **Accept APK ad delivery** is enabled in the Mintegral dashboard - App Settings. Non-China version: 1. Check whether the VPN is enabled and proxied to the US region. If the issue persists after the above checks, use Taku's [Debug Mode](https:\/\/help.takuad.com\/en\/docs\/How-to-test-ads) for testing. |\n| errorCode: 3507 errorMessage: data load failed, errorMsg is Network error,I\/O exception | Check whether a proxy is connected and SSL Proxying is enabled. Remove it and try again. |\n| Network error,I\/O exception | Check whether a proxy is connected and SSL Proxying is enabled. Remove it and try again. |\n| EXCEPTION\\_UNIT\\_NOT\\_FOUND | Check the Taku dashboard Mintegral Ad Source configuration (ad unit ID). |\n| EXCEPTION\\_UNIT\\_NOT\\_FOUND\\_IN\\_APP | Check the Taku dashboard Mintegral Ad Source configuration (ad unit ID). |\n| EXCEPTION\\_SIGN\\_ERROR | Check the Taku dashboard Mintegral Ad Source configuration (AppKey). |\n| EXCEPTION\\_UNIT\\_ADTYPE\\_ERROR | Check the Taku dashboard Mintegral Ad Source configuration (ad format mismatch). |\n| resource load timeout | Check whether the network is normal and then retry. |\n\n\n\nFor more Mintegral error information, see: [Mintegral Error Codes](http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown_v2\/index.html?file=sdk-m_sdk-android&lang=en)\n\n### \u25cf Huawei\n\nNote: When testing Huawei ads, **a Huawei phone or a phone with HMS Core Huawei services must be used**.\n\n**To test overseas Huawei: A VPN must be enabled.**\n\n| Common Error | Solution |\n|---|---|\n| 3 - NO\\_AD | Use Taku's [Debug Mode](https:\/\/help.takuad.com\/en\/docs\/How-to-test-ads) for testing. |\n| 2 - NETWORK\\_ERROR | Check whether the network has a VPN enabled. |\n| 1 - INVALID\\_REQUEST | Check the Taku dashboard Huawei Ad Source configuration. |\n\n\n\nFor more Huawei error information, see: [Huawei Error Codes](https:\/\/developer.huawei.com\/consumer\/cn\/doc\/development\/HMSCore-Guides-V5\/error-code-0000001051073340-V5)","pure_content":"Tips:\n\nTo quickly locate the cause of the issue, it is recommended to get the full error information through AdError#getFullErrorInfo()\n\"code[ \" + code + \" ],desc[ \" + desc + \" ],\nplatformCode[ \" + platformCode + \" ],\nplatformMSG[ \" + platformMSG + \" ]\"\n\ncode: Taku SDK's error code\ndesc: Taku SDK's error message\nplatformCode: The third-party ad platform's error code (the error code to check when no ad fill occurs)\nplatformMsg: The third-party ad platform's error message (the error message to check when no ad fill occurs)\n\n\n\n\n1. Taku Error Code Information\n\n\n\n Error Code\n Description\n\n\n\n\n 10001\n Incorrect App ID or App Key. Please check the App ID and App Key passed when Initializing the Taku SDK.\n\n\n 10003\n 1. Incorrect App ID. Please check the App ID passed when Initializing the Taku SDK. 2. The Taku Ad Placement ID does not match the App ID. Please check the Placement ID passed when calling the load method in the code.\n\n\n 10004\n Incorrect Taku Ad Placement ID. Please check the Placement ID passed when calling the load method.\n\n\n 9999\n 1. Generally a network request error. Check whether the network status is normal. 2. platformMSG:[ chain validation failed ], check whether the system time has been adjusted.\n\n\n 9990\n HTTP interface request returned a status error. Contact Taku colleagues to check the error message.\n\n\n 9991\n Interface request returned a business code error. Contact Taku colleagues to check the error message.\n\n\n 9992\n The GDPR level is set too low. Check whether the FORBIDDEN level has been manually set.\n\n\n 2001\n Ad loading timeout. Check whether the current tested Ad Source is an overseas platform and whether the phone's network has a VPN enabled.\n\n\n 2002\n The Taku SDK package is not fully imported. The third-party ad vendor's Adapter package is missing (anythink_network_*.aar). Confirm whether all required third-party SDK packages for the Mediation have been imported as instructed.\n\n\n 2003\n The display count for the current Ad Placement has reached the limit. Check whether the Taku dashboard configuration has restricted the display count for this Ad Placement.\n\n\n 2004\n The current Ad Placement is in a non-display time period. Check whether the Taku dashboard configuration has restricted the display interval for the Ad Placement.\n\n\n 2005\n The Ad Placement is in the loading phase. After initiating a request for the same Ad Placement, before receiving the load success or failure callback, this Ad Placement cannot initiate the next load. Wait for the load success or failure callback.\n\n\n 2006\n Check whether the imported third-party ad platform SDK packages are complete. If complete, check whether the imported version matches the version specified on GitHub. If not, the third-party SDK packages need to be supplemented.\n\n\n 2007\n Usually occurs when ad loading is immediately initiated in the load failure callback. Prohibited: Do not immediately initiate ad loading in the load failure callback. A certain time interval must pass since the last Ad Placement load failure before initiating ad loading again. Delay the ad loading call.\n\n\n 2008\n After a load failure for the same Ad Placement, do not call the load method immediately in the load failure callback for retry. Wait for more than 10 seconds before retrying.\n\n\n 2009\n The number of ad placement loads within a certain time interval has reached the limit.\n\n\n 3001\n Strategy acquisition error. 1. Check whether the network is normal. 2. Check whether the AppId, AppKey, and PlacementId used match. 3. Check whether the AppId, AppKey, and PlacementId in the code are correct and match (must not contain spaces). Call ATSDK.setNetworkLogDebug(true); and filter anythink in Logcat to view the parameters currently passed to the SDK. Please check these parameters.\n\n\n 3002\n One of the passed AppId, AppKey, or PlacementId is an empty string. Call ATSDK.setNetworkLogDebug(true); and filter anythink in Logcat to view the parameters currently passed to the SDK. Please check these parameters.\n\n\n 3003\n The Ad Placement does not match the called API. For example: a Banner Ad Placement was called using the Rewarded Video API to load an ad.\n\n\n 4001\n Usually occurs when a third-party ad platform returns an error resulting in no ad fill. You can get the full error information via AdError.getFullErrorInfo(). Use platformCode and platformMsg to view the ad platform's error code and error message. Please check the third-party ad platform error codes for troubleshooting.\n\n\n 4002\n The Context has been destroyed. You need to recreate the corresponding ad type object and then re-initiate ad loading.\n\n\n 4003\n The status of this Ad Placement has been closed. Check whether the status switch for this Ad Placement in the Taku dashboard is enabled.\n\n\n 4004\n This Ad Placement has no Ad Source configured in the Taku dashboard. You need to go to Taku Dashboard - Mediation Management to add a third-party ad platform's Ad Source for the Ad Placement.\n\n\n 4005\n All Ad Sources under the Ad Placement have been filtered. Possible reasons are as follows: 1. Check whether Display Limit or Display Interval has been set for the Ad Source in the Taku dashboard. 2. If only Header Bidding Ad Sources are configured, when the bidding fails, the Header Bidding Ad Sources will be filtered.\n\n\n 4006\n Video playback failed. Refer to Error Code 4001 for troubleshooting.\n\n\n 4007\n Ad Source bidding failed. Refer to Error Code 4001 for troubleshooting.\n\n\n 4008\n The Ad Source has been filtered due to custom filtering logic in the developer's code. If the filtering does not meet expectations, troubleshoot the custom filtering logic.\n\n\n 4009\n In debug mode, the Ad Placement has no Ad Source configured.\n\n\n\n2. Third-Party Ad Platform Error Codes\n\u25cf Tencent Ads\n\n\n\n Common Error\n Solution\n\n\n\n\n 6000 - 102006\n No suitable ad matched. Retries are prohibited, otherwise it may trigger system policies leading to decreased traffic revenue. For testing integration, you can use Taku's debug mode (DebuggerConfig) for testing.\n\n\n 5002 - Video creative download error\n Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n Ad images not displaying\n Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n Native ad video black screen or transparent\n Enable hardware acceleration in AndroidManifest.xml.\n\n\n 5004 - No suitable ad matched\n In this situation, retrying ad requests multiple times is prohibited, otherwise it may affect the system's evaluation of your traffic and thus affect monetization. For testing integration, you can use Taku's debug mode (DebuggerConfig) for testing.\n\n\n 5004 - No ads\n 1. Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml). 2. Check the Tencent Ads Ad Source configuration in the Taku dashboard (whether it is template rendering 2.0).\n\n\n 5006 - Package name verification error. The current app's package name does not match the package name filled in during media registration on the GDT official website, resulting in no ad return.\n The package name configured in the code must match the one in the GDT dashboard.\n\n\n 5010 - Ad format verification failed. Check whether the Ad Placement and API usage are consistent.\n Check the Tencent Ads Ad Source configuration in the Taku dashboard (whether it is template rendering, whether it is full-screen video, etc.).\n\n\n 2001 - Initialization error\n Developer self-checks parameter issues. 1. Do not split the Tencent Ads SDK package. 2. Check the Tencent Ads Ad Source configuration in the Taku dashboard. 3. If parameters are correct, confirm whether a real device is being used. Do not use a simulator for testing.\n\n\n 4004 - Splash Ad container not visible\n 1. Troubleshoot whether the container is hidden or obscured. 2. If show is executed directly in the Activity's onCreate, a delay may be needed. It is recommended to use the main thread's Handler to postDelay by 10ms before calling the showAd method and try again. 3. Add container.removeAllViews(); call before displaying.\n\n\n 102006 - No ad found matching the price requirement or experience requirement\n It is recommended to appropriately adjust the floor price\/target price settings, or go to the platform's ad center to check the blocking rules.\n\n\n\nFor more Tencent Ads error information, see: Tencent Ads Error Codes\n\u25cf Pangle (China)\n\n\n\n Common Error\n Solution\n\n\n\n\n 4201 - No initializer\n 1. Check whether the ABI architecture has been restricted according to the integration documentation. 2. Check whether the com.android.support:appcompat-v7 dependency or androidx.appcompat:appcompat dependency has been added according to the integration documentation.\n\n\n -7 - Splash Ad image load failed\n Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n No result callback after loading\n Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n Ad images not displaying\n Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n Video playback shows black screen\n Check whether the WAKE_LOCK permission is configured in the Manifest.\n\n\n 20001\n Request has no fill due to no suitable ad returned. Occasional occurrences are normal. Try switching devices for verification. Do not use a simulator for testing, or try again later. If the issue cannot be resolved, check the Pangle (China) SDK error codes for troubleshooting or submit a ticket to the Pangle platform for inquiry. For testing integration, you can use the test mode in the Taku dashboard's Ad Placement - Advanced Settings.\n\n\n 40029\n Check the rendering type of the Pangle (China) placement ID. The Taku dashboard's Pangle (China) Ad Source configuration must be consistent with the Pangle (China) dashboard's configuration.\n\n\n 40025\n 1. Check whether the system time of the test device is the current correct time. 2. Check whether the ABI architecture has been restricted according to the integration documentation. 3. If obfuscation is enabled, check the obfuscation rules provided in the downloaded SDK package. 4. Download the SDK from the Pangle (China) dashboard and replace the Pangle (China) SDK provided by Taku (open_ad_sdk_*.aar).\n\n\n 40021 - APK signature SHA1 value does not match the media platform entry\n The app's signature must be consistent with the signature configured in the Pangle (China) dashboard. If it was just configured, clear the cache and try again after 5 minutes.\n\n\n 40019 - Media configuration adtype does not match the request\n Check the Taku dashboard Pangle (China) Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes.\n\n\n 40018 - Media package name does not match the registered one\n The package name configured in the code must match the one in the Pangle (China) dashboard. If it was just configured, clear the cache and try again after 5 minutes.\n\n\n 40016 - slot_id and app_id correspondence is invalid\n Check the Taku dashboard Pangle (China) Ad Source configuration for spaces or special characters.\n\n\n 40006 - Ad Placement ID invalid\n Check the Taku dashboard Pangle (China) Ad Source configuration for spaces or special characters.\n\n\n 0 - null\n This error is reported on weak networks. Check the network status or switch networks and try again.\n\n\n Banner display size issue\n Before calling load, specify the LayoutParams width and height values for ATBannerView.\n\n\n Null pointer error when playing Pangle (China) Rewarded Video ad\n If multiple dex files are generated during packaging, ensure that Pangle (China) related classes are included in classes.dex.\n\n\n\nFor more error information, see: (Login required) Pangle (China) Error Codes\n\u25cf Baidu\n\n\n\n Common Error\n Solution\n\n\n\n\n Ad cannot be obtained\n 1. Rewarded Video takes effect two hours after configuration. 2. Use the test mode in the Taku dashboard's Ad Placement - Advanced Settings for testing.\n\n\n No callback when loading Banner Ad\n ATBannerView needs to be first added to the window before initiating a load request.\n\n\n\nFor more Baidu error information, see: Baidu Error Codes\n\u25cf Kuaishou\n\n\n\n Common Error\n Solution\n\n\n\n\n 40003 - Ad data is empty\n If it occurs consistently, contact Kuaishou personnel.\n\n\n 40004 - Video resource cache failed\n Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n Native ad video black screen or transparent\n Enable hardware acceleration in AndroidManifest.xml.\n\n\n 0 - Network error\n 1. Check whether the network is normal. 2. Check whether the Android 9 and above system has been correctly adapted according to the integration documentation (network_security_config.xml).\n\n\n 310002 - appId invalid\n Check the Taku dashboard Kuaishou Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes.\n\n\n 310004 - packageName does not match the registered packageName\n The package name configured in the code does not match the one in the Kuaishou dashboard.\n\n\n 330002 - posId invalid\n Check the Taku dashboard Kuaishou Ad Source configuration. If it was just configured, clear the cache and try again after 5 minutes.\n\n\n 330004 - posId and registered appId info inconsistent\n Check the Taku dashboard Kuaishou Ad Source configuration, and whether a different appId was used to Initialize Kuaishou.\n\n\n Native ad display abnormal\n Set fixed width and height values for ATNativeAdView.\n\n\n\nFor more Kuaishou error information, see: (Login required) Kuaishou Error Codes\n\u25cf Sigmob\n\n\n\n Common Error\n Solution\n\n\n\n\n 200000 - No ad fill\n Use Taku's Debug Mode (DebuggerConfig) for testing.\n\n\n Sigmob Splash Ad consistently fails to retrieve ads\n Devices on Android 6.0 and above need to dynamically request the READ_PHONE_STATE permission.\n\n\n 500701 - No ad channels have been enabled for the app\n Check the app status in the Sigmob dashboard.\n\n\n 500420 - The requested app has closed ad services\n Check the app status in the Sigmob dashboard.\n\n\n 500473 - The requested app does not exist\n Check the Taku dashboard Sigmob Ad Source configuration.\n\n\n 500424\/500422\/500482\n 1. Devices on Android 6.0 and above need to dynamically request the READ_PHONE_STATE permission. 2. For Android 10, please refer to Sigmob's FAQ regarding How to fill ads domestically on Android 10.\n\n\n Ads cannot be retrieved on Android 10\n Refer to Sigmob's FAQ regarding How to fill ads domestically on Android 10.\n\n\n After ad loads successfully, there is no playback or subsequent callbacks\n Sigmob's callbacks depend on the LocalBroadcastManager library. Check whether the com.android.support:appcompat-v7 dependency is imported (for Androidx, the corresponding one is androidx.localbroadcastmanager:localbroadcastmanager).\n\n\n\nFor more Sigmob error information, see: Sigmob Error Codes\n\u25cf TapTap\n\n\n\n Common Error\n Solution\n\n\n\n\n 3002 - Network error\n Check whether the phone's network environment is normal.\n\n\n 3003 - Interstitial Ad orientation parameter does not match the supported direction of the Ad Placement\n Modify the landscape and portrait configuration of the TapTap dashboard Ad Placement.\n\n\n 9999 - Failed to retrieve ad creative: Unknown error\n Regular no-fill error. Use Taku's Debug Mode (DebuggerConfig) for testing.\n\n\n\nFor more error information, see: TapTap Error Codes\n\u25cf Jingdong Ads\n\n\n\n Common Error\n Solution\n\n\n\n\n 2001 - Network error\n Check whether the phone's network environment is normal.\n\n\n 2002 - No ad matched\n It is recommended to switch to a device registered with a JD account, then initiate the ad request again.\n\n\n 3000 - The tagid and app id fields in the request are inconsistent with the platform configuration\n Check whether the placement ID parameters are set correctly.\n\n\n 4041 - Occasional occurrence, retry the request\n Occasional occurrence, retry the request. If it occurs frequently, contact JD R&D.\n\n\n 4042, 4043 - Request too frequent, retry the request\n No ad matched. It is recommended to re-initiate the ad request.\n\n\n\nFor more error information, see: Jingdong Ads Error Codes\n\u25cf Mintegral\n\n\n\n Common Error\n Solution\n\n\n\n\n EXCEPTION_RETURN_EMPTY\n China version: 1. Ensure that the option Accept APK ad delivery is enabled in the Mintegral dashboard - App Settings. Non-China version: 1. Check whether the VPN is enabled and proxied to the US region. If the issue persists after the above checks, use Taku's Debug Mode for testing.\n\n\n errorCode: 3507 errorMessage: data load failed, errorMsg is Network error,I\/O exception\n Check whether a proxy is connected and SSL Proxying is enabled. Remove it and try again.\n\n\n Network error,I\/O exception\n Check whether a proxy is connected and SSL Proxying is enabled. Remove it and try again.\n\n\n EXCEPTION_UNIT_NOT_FOUND\n Check the Taku dashboard Mintegral Ad Source configuration (ad unit ID).\n\n\n EXCEPTION_UNIT_NOT_FOUND_IN_APP\n Check the Taku dashboard Mintegral Ad Source configuration (ad unit ID).\n\n\n EXCEPTION_SIGN_ERROR\n Check the Taku dashboard Mintegral Ad Source configuration (AppKey).\n\n\n EXCEPTION_UNIT_ADTYPE_ERROR\n Check the Taku dashboard Mintegral Ad Source configuration (ad format mismatch).\n\n\n resource load timeout\n Check whether the network is normal and then retry.\n\n\n\nFor more Mintegral error information, see: Mintegral Error Codes\n\u25cf Huawei\nNote: When testing Huawei ads, a Huawei phone or a phone with HMS Core Huawei services must be used.\nTo test overseas Huawei: A VPN must be enabled.\n\n\n\n Common Error\n Solution\n\n\n\n\n 3 - NO_AD\n Use Taku's Debug Mode for testing.\n\n\n 2 - NETWORK_ERROR\n Check whether the network has a VPN enabled.\n\n\n 1 - INVALID_REQUEST\n Check the Taku dashboard Huawei Ad Source configuration.\n\n\n\nFor more Huawei error information, see: Huawei Error Codes","is_draft":"0","editor_type":"2","file_path":"","add_time":"1709721488","update_time":"1782974885"},"pure_content":"Tips:\n\nTo quickly locate the cause of the issue, it is recommended to get the full error information through AdError#getFullErrorInfo()\n\"code[ \" + code + \" ],desc[ \" + desc + \" ],\nplatformCode[ \" + p"},{"id":"76254","string_id":"qHUTBS","status":"1","parent_id":"76251","slug":"Test-Tool-Beta","order":"0","name":"Test Tool","type":"2","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1709722540","add_time":"1709721489","update_time":"1758105056","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"76254","content":"

Notes:<\/strong><\/p>

Support developers to detect and use after accessing TopOn SDK<\/li>
Developers are testing After completion, the relevant code that calls the test tool will be deleted before going online<\/li>

Version requirements: v6.2.70 and above<\/li><\/ul>
1. Product Introduction<\/h1>
Improve the efficiency of developer access testing by using testing tools:<\/p>
Basic information: detect information about applications, devices, and sdk<\/li>
TopOn SDK setting information: detect privacy settings , whether the permissions are successfully configured<\/li>
Integration detection: detect the integration of the third-party platform SDK and adapter and test suggestions, and test the ad loading of the third-party advertising platform<\/li><\/ul>
Release Notes<\/strong><\/p>
TopOn SDK Version<\/th> Test Tool version<\/th> Description<\/th><\/tr>
v6.2.70 and above(recommand)<\/td> v1.1.2<\/td> 1. Supports the latest version of the TaKu SDK
2. Fixed known issues<\/td><\/tr>
v6.2.70 and above<\/td> v1.0.8<\/td> 1. Support Kwai platform debugging
2. Support sub-style debugging of native ads, banner ads, and interstitial ads on the Adx platform<\/td><\/tr>
v6.2.70-v6.3.68<\/td> v1.0.5<\/td> Support online advertising ID testing (for SDK 6.3.68 and above)<\/td><\/tr>
v6.2.70-v6.3.65<\/td> v1.0.3<\/td> Adapt to Vungle Version 7.0.0<\/td><\/tr>
v6.2.70-v6.3.65<\/td> v1.0.1<\/td> Compatible with org.jetbrains.kotlin:kotlin-stdlib:1.4.0 and Above version<\/td><\/tr>
v6.2.70-v6.3.65<\/td> v1.0.0<\/td> Adaptive aggregation version< li style=\"text-align: left;\">The testing tool is only used to detect SDK integration and cannot replace the APP's own advertising logic testing<\/td><\/tr><\/tbody><\/table>
2. Access process<\/h1>
Refer to the TopOn SDK access document and integrate the SDK first.<\/li>
Introduce testing tools and add references to Build.gradle:<\/li><\/ul>
repositories {\n maven {\n url \"https:\/\/jfrog.anythinktech.com\/artifactory\/debugger\"\n }\n}\ndependencies {\n \/\/ Debugger UI Tools\n implementation 'com.anythink.sdk:debugger-ui:1.1.2'\n}\nCopy<\/code><\/pre>Calling up the test tool<\/li><\/ul>Note: <\/strong><\/span>must be in After initializing the TopOn SDK, call the following method to call up the test tool.<\/p> ATDebuggerUITest.showDebuggerUI(context); \n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test \n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\");<\/code><\/pre>3. Use of test tools<\/h1> 1. Basic information<\/h2>Function: Support long press to copy information and Current page data sharing.<\/p> GAID<\/strong> is Google Advertising ID, if GAID shows empty, please check the following factors:<\/span><\/li><\/ul>Whether the phone has Google services.<\/span><\/li> Before entering this page, whether to call The following method restrictions<\/span>GAID<\/strong><\/span> .<\/span><\/li><\/ol>ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.GAID)\n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test\n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\"); <\/code><\/pre>Android ID<\/strong> is the unique identifier of the device. If AndroidId is displayed as empty , please check whether the following method is called to limit the acquisition of AndroidId:<\/li><\/ul>ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.ANDROID_ID)<\/code><\/pre><\/p> 2.TopOn SDK settings<\/h2>TopOn SDK settings It includes two parts: privacy settings and permission settings.<\/p> Privacy settings<\/strong><\/li><\/ul>Limit reported data<\/strong><\/span>(<\/span>Only for Domestic<\/span>): There is a personalized recommendation advertising switch, Set the privacy information control switch. For details, please see<\/span> Domestic privacy configuration.<\/span><\/a><\/p> GDPR<\/strong><\/span>(<\/span>Only for Overseas<\/span>):<\/span><\/a> For details, please see Overseas Privacy Configuration<\/a>.<\/p> Permission settings:<\/strong> List of permissions applied for by the application.<\/li><\/ul><\/p> 3. Integration detection<\/h2>1. View the integration status of the advertising platform list: Integration exception, integration completed, Not integrated<\/strong>.<\/p> <\/p> 2. Check the switch to turn on debugging mode. If Gaid is empty, the debug mode function cannot be used.<\/p> <\/p> 3. Select the advertising platform to enter Debug Mode<\/strong>, and click on the upper right corner to share the advertising platform information of the current page.<\/p> 4. Select the advertising style of the advertising platform for test operation.<\/p> <\/p> 4.Online ID Test<\/h2>Online ID testing supports <\/span>using online configured ad slots to test ads, and supports filtering ad sources under ad slots for testing.<\/span><\/p> Note:<\/span> After running the online ID test, you need to restart the app to switch back to the developer app for testing to avoid caching problems caused by the in-app test ad slots and the test tool ad slots being consistent.<\/span><\/blockquote>Prerequeisties<\/h3>SDK version: v6.3.68 and above<\/span><\/li> Test tool version: v1.0.5 and above<\/span><\/li> Set<\/span> SDK Debug Key: The steps to obtain it are Log in to background<\/code><\/span>-> Account Manager<\/code><\/span> -> Key<\/code><\/span><\/li> Debug mode is off<\/li><\/ul>Start<\/h3>When initializing the SDK, pass in the application ID. When entering the online ID, the ad space configured in the application will be pulled.<\/li> Enter the test tool by setting the Debug Key<\/li><\/ol>The sample code is as follows:<\/span><\/p> \/\/1. \u521d\u59cb\u5316SDK\nATSDK.init(context, \"Your App Id\", \"Your App Key\");\n\/\/2.\u8bbe\u7f6eDebug Key\u8fdb\u5165\u6d4b\u8bd5\u5de5\u5177\nATDebuggerUITest.showDebuggerUI(context, \"Your Debug Key\");<\/code><\/pre>Online ID List<\/h4>Support viewing application information: application name, App ID, application package name, SDK version<\/li> Support viewing the list of ad slots configured in the application<\/li> Support viewing ad slot information: name, ID<\/li> Supports clicking on an ad slot to jump to the ad slot test page for testing (video stream ads do not support testing for the time being)<\/li><\/ul><\/p> Ad Placement Test<\/h4>Support switching traffic groups<\/li> Supports bidding and waterfall advertising sources<\/li> Supports filtering advertising sources: unchecked advertising sources will be filtered when initiating lo<\/li><\/ul><\/p> <\/p> <\/p>","pure_content":"Notes:Support developers to detect and use after accessing TopOn SDKDevelopers are testing After completion, the relevant code that calls the test tool will be deleted before going onlineVersion requirements: v6.2.70 and above1. Product IntroductionImprove the efficiency of developer access testing by using testing tools:Basic information: detect information about applications, devices, and sdkTopOn SDK setting information: detect privacy settings , whether the permissions are successfully configuredIntegration detection: detect the integration of the third-party platform SDK and adapter and test suggestions, and test the ad loading of the third-party advertising platformRelease Notes TopOn SDK Version Test Tool version Description v6.2.70 and above(recommand) v1.1.2 1. Supports the latest version of the TaKu SDK2. Fixed known issues v6.2.70 and above v1.0.8 1. Support Kwai platform debugging 2. Support sub-style debugging of native ads, banner ads, and interstitial ads on the Adx platform v6.2.70-v6.3.68 v1.0.5 Support online advertising ID testing (for SDK 6.3.68 and above) v6.2.70-v6.3.65 v1.0.3 Adapt to Vungle Version 7.0.0 v6.2.70-v6.3.65 v1.0.1 Compatible with org.jetbrains.kotlin:kotlin-stdlib:1.4.0 and Above version v6.2.70-v6.3.65 v1.0.0 Adaptive aggregation version< li style=\"text-align: left;\">The testing tool is only used to detect SDK integration and cannot replace the APP's own advertising logic testing2. Access processRefer to the TopOn SDK access document and integrate the SDK first.Introduce testing tools and add references to Build.gradle:repositories {\n maven {\n url \"https:\/\/jfrog.anythinktech.com\/artifactory\/debugger\"\n }\n}\ndependencies {\n \/\/ Debugger UI Tools\n implementation 'com.anythink.sdk:debugger-ui:1.1.2'\n}\nCopyCalling up the test toolNote: must be in After initializing the TopOn SDK, call the following method to call up the test tool.ATDebuggerUITest.showDebuggerUI(context); \n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test \n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\");3. Use of test tools1. Basic informationFunction: Support long press to copy information and Current page data sharing.GAID is Google Advertising ID, if GAID shows empty, please check the following factors:Whether the phone has Google services.Before entering this page, whether to call The following method restrictionsGAID .ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.GAID)\n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test\n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\"); Android ID is the unique identifier of the device. If AndroidId is displayed as empty , please check whether the following method is called to limit the acquisition of AndroidId:ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.ANDROID_ID)2.TopOn SDK settingsTopOn SDK settings It includes two parts: privacy settings and permission settings.Privacy settingsLimit reported data(Only for Domestic): There is a personalized recommendation advertising switch, Set the privacy information control switch. For details, please see Domestic privacy configuration.GDPR(Only for Overseas): For details, please see Overseas Privacy Configuration.Permission settings: List of permissions applied for by the application.3. Integration detection1. View the integration status of the advertising platform list: Integration exception, integration completed, Not integrated.2. Check the switch to turn on debugging mode. If Gaid is empty, the debug mode function cannot be used.3. Select the advertising platform to enter Debug Mode, and click on the upper right corner to share the advertising platform information of the current page.4. Select the advertising style of the advertising platform for test operation.4.Online ID TestOnline ID testing supports using online configured ad slots to test ads, and supports filtering ad sources under ad slots for testing.Note: After running the online ID test, you need to restart the app to switch back to the developer app for testing to avoid caching problems caused by the in-app test ad slots and the test tool ad slots being consistent.PrerequeistiesSDK version: v6.3.68 and aboveTest tool version: v1.0.5 and aboveSet SDK Debug Key: The steps to obtain it are Log in to background-> Account Manager -> KeyDebug mode is offStartWhen initializing the SDK, pass in the application ID. When entering the online ID, the ad space configured in the application will be pulled.Enter the test tool by setting the Debug KeyThe sample code is as follows:\/\/1. \u521d\u59cb\u5316SDK\nATSDK.init(context, \"Your App Id\", \"Your App Key\");\n\/\/2.\u8bbe\u7f6eDebug Key\u8fdb\u5165\u6d4b\u8bd5\u5de5\u5177\nATDebuggerUITest.showDebuggerUI(context, \"Your Debug Key\");Online ID ListSupport viewing application information: application name, App ID, application package name, SDK versionSupport viewing the list of ad slots configured in the applicationSupport viewing ad slot information: name, IDSupports clicking on an ad slot to jump to the ad slot test page for testing (video stream ads do not support testing for the time being)Ad Placement TestSupport switching traffic groupsSupports bidding and waterfall advertising sourcesSupports filtering advertising sources: unchecked advertising sources will be filtered when initiating lo","is_draft":"0","editor_type":"1","file_path":"","add_time":"1709721493","update_time":"1758105056"},"pure_content":"Notes:Support developers to detect and use after accessing TopOn SDKDevelopers are testing After completion, the relevant code that calls the test tool will be deleted before going onlineVersion requi"}],"content":{"icon":"","desc":"","content_id":"76251","add_time":"1709721485","update_time":"1709722539","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}

TopOn SDK Version<\/th>	Test Tool version<\/th>	Description<\/th><\/tr>
v6.2.70 and above(recommand)<\/td>	v1.1.2<\/td>	1. Supports the latest version of the TaKu SDK 2. Fixed known issues<\/td><\/tr>
v6.2.70 and above<\/td>	v1.0.8<\/td>	1. Support Kwai platform debugging 2. Support sub-style debugging of native ads, banner ads, and interstitial ads on the Adx platform<\/td><\/tr>
v6.2.70-v6.3.68<\/td>	v1.0.5<\/td>	Support online advertising ID testing (for SDK 6.3.68 and above)<\/td><\/tr>
v6.2.70-v6.3.65<\/td>	v1.0.3<\/td>	Adapt to Vungle Version 7.0.0<\/td><\/tr>
v6.2.70-v6.3.65<\/td>	v1.0.1<\/td>	Compatible with org.jetbrains.kotlin:kotlin-stdlib:1.4.0 and Above version<\/td><\/tr>
v6.2.70-v6.3.65<\/td>	v1.0.0<\/td>	Adaptive aggregation version< li style=\"text-align: left;\">The testing tool is only used to detect SDK integration and cannot replace the APP's own advertising logic testing<\/td><\/tr><\/tbody><\/table> 2. Access process<\/h1> Refer to the TopOn SDK access document and integrate the SDK first.<\/li> Introduce testing tools and add references to Build.gradle:<\/li><\/ul> repositories {\n maven {\n url \"https:\/\/jfrog.anythinktech.com\/artifactory\/debugger\"\n }\n}\ndependencies {\n \/\/ Debugger UI Tools\n implementation 'com.anythink.sdk:debugger-ui:1.1.2'\n}\nCopy<\/code><\/pre>Calling up the test tool<\/li><\/ul>Note: <\/strong><\/span>must be in After initializing the TopOn SDK, call the following method to call up the test tool.<\/p> ATDebuggerUITest.showDebuggerUI(context); \n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test \n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\");<\/code><\/pre>3. Use of test tools<\/h1> 1. Basic information<\/h2>Function: Support long press to copy information and Current page data sharing.<\/p> GAID<\/strong> is Google Advertising ID, if GAID shows empty, please check the following factors:<\/span><\/li><\/ul>Whether the phone has Google services.<\/span><\/li> Before entering this page, whether to call The following method restrictions<\/span>GAID<\/strong><\/span> .<\/span><\/li><\/ol>ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.GAID)\n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test\n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\"); <\/code><\/pre>Android ID<\/strong> is the unique identifier of the device. If AndroidId is displayed as empty , please check whether the following method is called to limit the acquisition of AndroidId:<\/li><\/ul>ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.ANDROID_ID)<\/code><\/pre><\/p> 2.TopOn SDK settings<\/h2>TopOn SDK settings It includes two parts: privacy settings and permission settings.<\/p> Privacy settings<\/strong><\/li><\/ul>Limit reported data<\/strong><\/span>(<\/span>Only for Domestic<\/span>): There is a personalized recommendation advertising switch, Set the privacy information control switch. For details, please see<\/span> Domestic privacy configuration.<\/span><\/a><\/p> GDPR<\/strong><\/span>(<\/span>Only for Overseas<\/span>):<\/span><\/a> For details, please see Overseas Privacy Configuration<\/a>.<\/p> Permission settings:<\/strong> List of permissions applied for by the application.<\/li><\/ul><\/p> 3. Integration detection<\/h2>1. View the integration status of the advertising platform list: Integration exception, integration completed, Not integrated<\/strong>.<\/p> <\/p> 2. Check the switch to turn on debugging mode. If Gaid is empty, the debug mode function cannot be used.<\/p> <\/p> 3. Select the advertising platform to enter Debug Mode<\/strong>, and click on the upper right corner to share the advertising platform information of the current page.<\/p> 4. Select the advertising style of the advertising platform for test operation.<\/p> <\/p> 4.Online ID Test<\/h2>Online ID testing supports <\/span>using online configured ad slots to test ads, and supports filtering ad sources under ad slots for testing.<\/span><\/p> Note:<\/span> After running the online ID test, you need to restart the app to switch back to the developer app for testing to avoid caching problems caused by the in-app test ad slots and the test tool ad slots being consistent.<\/span><\/blockquote>Prerequeisties<\/h3>SDK version: v6.3.68 and above<\/span><\/li> Test tool version: v1.0.5 and above<\/span><\/li> Set<\/span> SDK Debug Key: The steps to obtain it are Log in to background<\/code><\/span>-> Account Manager<\/code><\/span> -> Key<\/code><\/span><\/li> Debug mode is off<\/li><\/ul>Start<\/h3>When initializing the SDK, pass in the application ID. When entering the online ID, the ad space configured in the application will be pulled.<\/li> Enter the test tool by setting the Debug Key<\/li><\/ol>The sample code is as follows:<\/span><\/p> \/\/1. \u521d\u59cb\u5316SDK\nATSDK.init(context, \"Your App Id\", \"Your App Key\");\n\/\/2.\u8bbe\u7f6eDebug Key\u8fdb\u5165\u6d4b\u8bd5\u5de5\u5177\nATDebuggerUITest.showDebuggerUI(context, \"Your Debug Key\");<\/code><\/pre>Online ID List<\/h4>Support viewing application information: application name, App ID, application package name, SDK version<\/li> Support viewing the list of ad slots configured in the application<\/li> Support viewing ad slot information: name, ID<\/li> Supports clicking on an ad slot to jump to the ad slot test page for testing (video stream ads do not support testing for the time being)<\/li><\/ul><\/p> Ad Placement Test<\/h4>Support switching traffic groups<\/li> Supports bidding and waterfall advertising sources<\/li> Supports filtering advertising sources: unchecked advertising sources will be filtered when initiating lo<\/li><\/ul><\/p> <\/p> <\/p>","pure_content":"Notes:Support developers to detect and use after accessing TopOn SDKDevelopers are testing After completion, the relevant code that calls the test tool will be deleted before going onlineVersion requirements: v6.2.70 and above1. Product IntroductionImprove the efficiency of developer access testing by using testing tools:Basic information: detect information about applications, devices, and sdkTopOn SDK setting information: detect privacy settings , whether the permissions are successfully configuredIntegration detection: detect the integration of the third-party platform SDK and adapter and test suggestions, and test the ad loading of the third-party advertising platformRelease Notes TopOn SDK Version Test Tool version Description v6.2.70 and above(recommand) v1.1.2 1. Supports the latest version of the TaKu SDK2. Fixed known issues v6.2.70 and above v1.0.8 1. Support Kwai platform debugging 2. Support sub-style debugging of native ads, banner ads, and interstitial ads on the Adx platform v6.2.70-v6.3.68 v1.0.5 Support online advertising ID testing (for SDK 6.3.68 and above) v6.2.70-v6.3.65 v1.0.3 Adapt to Vungle Version 7.0.0 v6.2.70-v6.3.65 v1.0.1 Compatible with org.jetbrains.kotlin:kotlin-stdlib:1.4.0 and Above version v6.2.70-v6.3.65 v1.0.0 Adaptive aggregation version< li style=\"text-align: left;\">The testing tool is only used to detect SDK integration and cannot replace the APP's own advertising logic testing2. Access processRefer to the TopOn SDK access document and integrate the SDK first.Introduce testing tools and add references to Build.gradle:repositories {\n maven {\n url \"https:\/\/jfrog.anythinktech.com\/artifactory\/debugger\"\n }\n}\ndependencies {\n \/\/ Debugger UI Tools\n implementation 'com.anythink.sdk:debugger-ui:1.1.2'\n}\nCopyCalling up the test toolNote: must be in After initializing the TopOn SDK, call the following method to call up the test tool.ATDebuggerUITest.showDebuggerUI(context); \n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test \n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\");3. Use of test tools1. Basic informationFunction: Support long press to copy information and Current page data sharing.GAID is Google Advertising ID, if GAID shows empty, please check the following factors:Whether the phone has Google services.Before entering this page, whether to call The following method restrictionsGAID .ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.GAID)\n\/\/If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test\n\/\/ATDebuggerUITest.showDebuggerUI(context, \"Your Debug_Key\"); Android ID is the unique identifier of the device. If AndroidId is displayed as empty , please check whether the following method is called to limit the acquisition of AndroidId:ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.ANDROID_ID)2.TopOn SDK settingsTopOn SDK settings It includes two parts: privacy settings and permission settings.Privacy settingsLimit reported data(Only for Domestic): There is a personalized recommendation advertising switch, Set the privacy information control switch. For details, please see Domestic privacy configuration.GDPR(Only for Overseas): For details, please see Overseas Privacy Configuration.Permission settings: List of permissions applied for by the application.3. Integration detection1. View the integration status of the advertising platform list: Integration exception, integration completed, Not integrated.2. Check the switch to turn on debugging mode. If Gaid is empty, the debug mode function cannot be used.3. Select the advertising platform to enter Debug Mode, and click on the upper right corner to share the advertising platform information of the current page.4. Select the advertising style of the advertising platform for test operation.4.Online ID TestOnline ID testing supports using online configured ad slots to test ads, and supports filtering ad sources under ad slots for testing.Note: After running the online ID test, you need to restart the app to switch back to the developer app for testing to avoid caching problems caused by the in-app test ad slots and the test tool ad slots being consistent.PrerequeistiesSDK version: v6.3.68 and aboveTest tool version: v1.0.5 and aboveSet SDK Debug Key: The steps to obtain it are Log in to background-> Account Manager -> KeyDebug mode is offStartWhen initializing the SDK, pass in the application ID. When entering the online ID, the ad space configured in the application will be pulled.Enter the test tool by setting the Debug KeyThe sample code is as follows:\/\/1. \u521d\u59cb\u5316SDK\nATSDK.init(context, \"Your App Id\", \"Your App Key\");\n\/\/2.\u8bbe\u7f6eDebug Key\u8fdb\u5165\u6d4b\u8bd5\u5de5\u5177\nATDebuggerUITest.showDebuggerUI(context, \"Your Debug Key\");Online ID ListSupport viewing application information: application name, App ID, application package name, SDK versionSupport viewing the list of ad slots configured in the applicationSupport viewing ad slot information: name, IDSupports clicking on an ad slot to jump to the ad slot test page for testing (video stream ads do not support testing for the time being)Ad Placement TestSupport switching traffic groupsSupports bidding and waterfall advertising sourcesSupports filtering advertising sources: unchecked advertising sources will be filtered when initiating lo","is_draft":"0","editor_type":"1","file_path":"","add_time":"1709721493","update_time":"1758105056"},"pure_content":"Notes:Support developers to detect and use after accessing TopOn SDKDevelopers are testing After completion, the relevant code that calls the test tool will be deleted before going onlineVersion requi"}],"content":{"icon":"","desc":"","content_id":"76251","add_time":"1709721485","update_time":"1709722539","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}