网络跟踪
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
借助网络跟踪功能,您可以查看与 Google 移动广告 SDK 相关的网络活动。该功能非常适合调试 Google 移动广告的实现。
使用网络跟踪功能而非 Charles Proxy 等工具的主要原因是:网络跟踪功能适用于所有 iOS 版本和设备,无需信任任何第三方安全证书配置文件。自 iOS 10.3 以来,由于相关的证书配置文件要求,代理工具并不具备如此广泛的适用性。
本指南介绍了如何出于调试目的而启用网络跟踪功能。
启用跟踪功能
如需启用网络跟踪功能,请在 plist 文件中将 GADEnableNetworkTracing
键设置为 YES
。
启用网络跟踪功能后,Google 移动广告 SDK 会将网络事件记录到控制台。然后,您可以将日志副本提供给我们的工程师,以便他们将其作为开发者论坛上的私人回复进行分析。
日志记录
适用于标准平台的控制台日志用于输出网络日志。
控制台日志消息始终以字符串 GMA Debug BEGIN
、GMA Debug CONTENT
或 GMA Debug FINISH
开头,因此您可以对其进行搜索或滤除。对于每个网络日志,第一条日志消息为 GMA Debug BEGIN
,最后一条日志消息为 GMA Debug FINISH
,并且网络日志内容以 GMA Debug CONTENT
开头。如果网络日志内容过长,无法完全显示在一行中,则会将其拆分为多行,且每一行都以 GMA Debug CONTENT
开头。
示例输出
<Your App Name>[2710:30568] <Google> GMA Debug BEGIN
2017-12-06 09:47:09.268020-0800 <Your App Name>[2710:30568] <Google> GMA Debug CONTENT: {
"components" : [
"network_request_31107D12-E54E-45D6-AEA9-4A303C659EDF"
],
"timestamp" : 1512582429267.2629,
"event" : "onNetworkRequest",
"params" : {
"firstline" : {
"uri" : "<encoded text>",
"verb" : "<encoded text>"
},
"headers" : [
{
"name" : "<encoded text>",
"value" : "<encoded text>"
}
]
}
}
2017-12-06 09:47:09.275742-0800 <Your App Name>[2710:30568] <Google> GMA Debug FINISH
然后,您可以将日志副本提供给我们的工程师进行分析。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-27。
[null,null,["最后更新时间 (UTC):2025-08-27。"],[[["\u003cp\u003eNetwork tracing provides insights into Google Mobile Ads SDK network activities, aiding in debugging your ad implementation.\u003c/p\u003e\n"],["\u003cp\u003eIt offers a debugging advantage over proxy tools by functioning on all iOS versions and devices without requiring third-party security certificate profiles.\u003c/p\u003e\n"],["\u003cp\u003eTo enable tracing, simply set the \u003ccode\u003eGADEnableNetworkTracing\u003c/code\u003e key to \u003ccode\u003eYES\u003c/code\u003e within your plist file.\u003c/p\u003e\n"],["\u003cp\u003eWhen enabled, the SDK logs network events to the console, which can be shared with Google engineers for analysis.\u003c/p\u003e\n"],["\u003cp\u003eConsole logs are easily identifiable, starting with \u003ccode\u003eGMA Debug BEGIN\u003c/code\u003e, \u003ccode\u003eGMA Debug CONTENT\u003c/code\u003e, or \u003ccode\u003eGMA Debug FINISH\u003c/code\u003e, allowing for efficient searching and filtering.\u003c/p\u003e\n"]]],[],null,["Select platform: [Android](/ad-manager/mobile-ads-sdk/android/network-tracing \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/network-tracing \"View this page for the iOS platform docs.\")\n\n\u003cbr /\u003e\n\nNetwork tracing lets you see network activities relating to the\nGoogle Mobile Ads SDK. This can be useful in debugging your Google Mobile Ads\nimplementation.\n\nA key reason to use network tracing instead of tools such as [Charles\nProxy](//www.charlesproxy.com) is that it will work on **all** iOS versions and\ndevices without trusting any third party security certificate profiles. This is\nnot the case with proxying tools due [certificate profile\nrequirements](https://support.apple.com/en-nz/HT204477) in place since iOS 10.3.\n\nThis guide explains how to enable network tracing for debugging purposes.\n\nEnable tracing\n\nTo enable network tracing, set the `GADEnableNetworkTracing` key to `YES` in\nyour plist file.\n\nWhen network tracing is enabled, the Google Mobile Ads SDK logs network events\nto the console. You can then provide copies of the logs to our engineers for\nanalysis as a private reply on the [developer\nforum](//groups.google.com/forum/#!forum/google-admob-ads-sdk).\n\nLogging\n\nStandard platform-appropriate console logs are used to output the network logs.\n\nConsole log messages always begin with the string `GMA Debug BEGIN`,\n`GMA Debug CONTENT`, or `GMA Debug FINISH` so that it can be searched for or\nfiltered out. For each network log, the first log message is `GMA Debug BEGIN`,\nthe last log message is `GMA Debug FINISH`, and the network log content begins\nwith `GMA Debug CONTENT`. If a network log content is too long to fit on a line,\nit is split among multiple lines, each line beginning with `GMA Debug CONTENT`.\n\nSample output \n\n \u003cYour App Name\u003e[2710:30568] \u003cGoogle\u003e GMA Debug BEGIN\n 2017-12-06 09:47:09.268020-0800 \u003cYour App Name\u003e[2710:30568] \u003cGoogle\u003e GMA Debug CONTENT: {\n \"components\" : [\n \"network_request_31107D12-E54E-45D6-AEA9-4A303C659EDF\"\n ],\n \"timestamp\" : 1512582429267.2629,\n \"event\" : \"onNetworkRequest\",\n \"params\" : {\n \"firstline\" : {\n \"uri\" : \"\u003cencoded text\u003e\",\n \"verb\" : \"\u003cencoded text\u003e\"\n },\n \"headers\" : [\n {\n \"name\" : \"\u003cencoded text\u003e\",\n \"value\" : \"\u003cencoded text\u003e\"\n }\n ]\n }\n }\n 2017-12-06 09:47:09.275742-0800 \u003cYour App Name\u003e[2710:30568] \u003cGoogle\u003e GMA Debug FINISH\n\nYou can then [provide copies of the logs to our\nengineers](//groups.google.com/forum/#!forum/google-admob-ads-sdk) for analysis."]]