blocks|key|161670|text|在终端中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161671|161672|转到项目的根文件夹|ordered-list-item|161673|键入：grep+-r+advertisingIdentifier+.+(末尾的圆点很重要)|offset|length|style|CODE|161674|161675|这将递归地检查每个文件，并给出问题库的名称。|161676|(在我的例子中，它是混乱的)|161677|entityMap^0|0|0|0|3|V|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@$H|W|I|X|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

In Terminal:

<ol>
<li>Go to the root folder of your project</li>
<li>Type: <code>grep -r advertisingIdentifier .</code> (the dot at the end is critical)</li>
</ol>

This will recursively check every file, and give you the name of the offending library.

(in my case, it was Flurry)

blocks|key|2970019|text|我的应用程序也因为同样的错误而被拒绝！我发现在最新的Facebook+SDK+(3.12)中出现了advertisingIdentifier。也许你可以用下面的方法检查你的库中的一个事件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2970020|我在终端中以库的形式打开FacebookSDK.framework，并输入以下命令|2970021|otool+-v+-s+__TEXT+__objc_methname+FacebookSDK+%7C+grep+advertisingIdentifier|2970022|但我不知道该怎么办。我的应用因为这个引用而被拒绝了吗？如果是，如果我想在我的应用程序中使用facebook功能，该怎么办？|2970023|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

My app was also rejected with the same error! I found an occurrence of advertisingIdentifier in the latest Facebook SDK (3.12). Maybe you can check your library's for an occurence with the method below:

I opened the FacebookSDK.framework as a library in the terminal and typed the following command

otool -v -s __TEXT __objc_methname FacebookSDK | grep advertisingIdentifier

But I don't know what to do. Was my app rejected because of this reference? If yes what to do if I want to use facebook functionalities in my app?

blocks|key|2970080|text|事实证明，Testflight+v2.2.0是冲突所在。他们已经根据他们的changelog进行了修复：Consolidate+both+SDK+versions+into+one+which+removes+all+access+to+ASIdentifierManager|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2970081|entityMap^0|1G|2E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Turns out the Testflight v2.2.0 was the conflict. They have since fixed it according to their changelog: <code>Consolidate both SDK versions into one which removes all access to ASIdentifierManager</code>

blocks|key|161708|text|Flurry也使用此API。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161709|终端输出：|161710|Binary+file+./Lib/Flurry/libFlurry_4.3.0.a+matches|code-block|syntax|javascript|161711|Flurry表示，如果AdSupport框架未链接，则不会调用选择器。|161712|因此，我删除了框架，并尝试再次提交。|161713|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Flurry Analytics uses this API as well. 
Terminal output:

<pre><code>Binary file ./Lib/Flurry/libFlurry_4.3.0.a matches
</code></pre>

Flurry says that the selector is not called if AdSupport framework isn't linked. 
So I removed the framework and tried submitting again.

blocks|key|165548|text|Crashlytics是问题所在。因为它，我们有一些应用被拒绝了。但我已经和Crashlytics谈过了，他们今天发布了一个新的更新(2.1.6版)，解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165549|有几个库有AdSupport.framework，但除非特别调用，否则它们不使用它。Crashlytics之所以调用这个框架，是因为它必须检查应用程序是否支持广告。这一变化是在2.1.5版本中实现的|165550|所以如果你在使用crashlytics，这是最有可能的原因。要解决这个问题，只需重新归档您的应用程序，以便crashlytics可以使用此修复的新版本。|165551|来自Crashlytics团队的回应：“我们刚刚推出了一个更新--你能在Mac应用打开的情况下重新构建和运行你的应用，这样它就可以更新你的SDK了吗?你可以继续下去！在你重新提交后，请与我保持联系:)”|165552|PS:这开始发生了，因为苹果似乎已经改变了他们对ADSupport使用的政策。|165553|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Crashlytics was the problem. We had a few apps rejected because of it. But I already talked with Crashlytics and they released a new update today (version 2.1.6) which fix this issue.

Several libraries have the AdSupport.framework but they do not use it unless specifically called. Crashlytics was calling the framework because it had to check if the app had support for ads. And that change was implemented on version 2.1.5

So if you are using crashlytics, that's the most probable reason. To fix that, just re-archive your app so crashlytics can use the new version with this fix.

Response from Crashlytics Team:
"We just pushed out an update for this- can you build and run your app again with the Mac app open so it can update your SDK? You'll be all good to go after that! Keep me posted after you resubmit :)"

PS: This is starting to happen because Apple seem to have changed their policy for ADSupport usage.

blocks|key|161753|text|更新|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|161754|谷歌发布了Google+Analytics+Services+iOS+SDK+v3.03c，它在默认情况下删除了AdSupport.framework依赖。|161755|版本3.03c的完整更改日志条目(2014年2月19日)：https://developers.google.com/analytics/devguides/collection/ios/changelog|161756|旧Awnser|161757|我的问题出在谷歌分析和TestFlight上。|161758|对于TestFlight，我只需将库更新到版本2.2.1+(https://www.testflightapp.com/sdk/ios/release_notes/2.2.1/)。|161759|但是为了更新Google+Analytics，我不得不去掉-ObjC标志。但是，当我使用Cocoapods来管理一些第三个库时，我不能简单地删除它。所以我做了如下操作：|161760|1-开始将libGoogleAnalytics.a更新到版本3.03a+(2014年2月5日)|161761|2-然后还删除了AdSupport.framework|161762|3-在“目标-->构建设置-->其他链接器标志”下添加了“源"${PROJECT_DIR}/Source/Library/GoogleAnalyticsServicesiOS_3.03a"”“(注意，在我的项目中，GoogleAnalytics位于/-force_load\/GoogleAnalytics/文件夹中，您必须配置自己的)|161763|但是由于我不能删除-ObjC标志，我搜索了如何在Cocoapods中使用-force_load标志，然后我找到了两个有用的链接：|161764|1-+https://github.com/CocoaPods/CocoaPods/issues/712|161765|2-+http://www.deanmao.com/2012/12/31/linker-error-using-cocoapods/|161766|总而言之，我还在“目标-->构建设置-->其他链接器标志”下更改了"-force_load+$(TARGET_BUILD_DIR)/libPods.a“的-ObjC标志。|161767|但是，当我试图发布我的应用程序时，我得到一个错误，告诉我编译器没有找到libPods.a，所以我转到“目标-->构建设置-->其他链接器标志-->发布”，并将这个字符串$(TARGET_BUILD_DIR)更改为${BUILT_PRODUCTS_DIR}。|161768|因此，我的其他链接器标志变得像下面的图像。|161769|📷|atomic|161770|​|161771|希望能帮助到一些人。|161772|对不起，我的英语不好。=]|161773|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/analytics/devguides/collection/ios/changelog|1|https://www.testflightapp.com/sdk/ios/release_notes/2.2.1/|2|https://github.com/CocoaPods/CocoaPods/issues/712|3|http://www.deanmao.com/2012/12/31/linker-error-using-cocoapods/|4|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/08f58b4103787e40d2848682818ee540.png|imageAlt^0|0|2|0|0|T|22|0|0|0|7|0|0|U|1M|1|0|0|0|0|0|0|3|1D|2|0|3|1R|3|0|0|0|0|0|1|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|22|8|@$9|23|A|24|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|25|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|26|8|@]|D|@$9|27|A|28|1|29]]|E|$]]|$1|J|3|K|5|6|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|2D|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|2E|8|@]|D|@$9|2F|A|2G|1|2H]]|E|$]]|$1|P|3|Q|5|6|7|2I|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|2J|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|2K|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|2L|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|2M|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2N|8|@]|D|@$9|2O|A|2P|1|2Q]]|E|$]]|$1|11|3|12|5|6|7|2R|8|@]|D|@$9|2S|A|2T|1|2U]]|E|$]]|$1|13|3|14|5|6|7|2V|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|2W|8|@]|D|@]|E|$]]|$1|17|3|18|5|6|7|2X|8|@]|D|@]|E|$]]|$1|19|3|1A|5|1B|7|2Y|8|@]|D|@$9|2Z|A|30|1|31]]|E|$]]|$1|1C|3|1D|5|6|7|32|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|33|8|@]|D|@]|E|$]]|$1|1G|3|1H|5|6|7|34|8|@]|D|@]|E|$]]|$1|1I|3|-4|5|6|7|35|8|@]|D|@]|E|$]]]|1J|$1K|$5|1L|1M|1N|E|$1O|1P]]|1Q|$5|1L|1M|1N|E|$1O|1R]]|1S|$5|1L|1M|1N|E|$1O|1T]]|1U|$5|1L|1M|1N|E|$1O|1V]]|1W|$5|1X|1M|1Y|E|$1Z|20|21|-4]]]]

Update

Google released Google Analytics Services iOS SDK v3.03c which removes the AdSupport.framework dependency by default.

Full changelog entry for Release Version 3.03c (February 19, 2014): <a href="https://developers.google.com/analytics/devguides/collection/ios/changelog" rel="noreferrer">https://developers.google.com/analytics/devguides/collection/ios/changelog</a>

Old Awnser

My problem was with Google Analytics and TestFlight. 

For TestFlight I just update the library to the version 2.2.1 (<a href="https://www.testflightapp.com/sdk/ios/release_notes/2.2.1/" rel="noreferrer">https://www.testflightapp.com/sdk/ios/release_notes/2.2.1/</a>). 

But for updating Google Analytics I had to remove the -ObjC flag. But as I use Cocoapods to manage some of third libraries, I couldn't just remove it. So I did the follow:

1 - started updating the libGoogleAnalytics.a to Version 3.03a (February 5, 2014)

2 - then a removed also the AdSupport.framework

3 - added "-force_load\ "${PROJECT_DIR}/Source/Library/GoogleAnalyticsServicesiOS_3.03a"" under "Target --> Build Settings --> Other Linker Flags"
(Note that in my project the GoogleAnalytics is inside /Source/Library/ folder, and you have to configure your own)

But as I coudn't remove -ObjC flag I searched for how to use -force_load flag with Cocoapods, then I found two useful links:

1 - <a href="https://github.com/CocoaPods/CocoaPods/issues/712" rel="noreferrer">https://github.com/CocoaPods/CocoaPods/issues/712</a>

2 - <a href="http://www.deanmao.com/2012/12/31/linker-error-using-cocoapods/" rel="noreferrer">http://www.deanmao.com/2012/12/31/linker-error-using-cocoapods/</a>

To summarize I changed the -ObjC flag for "-force_load $(TARGET_BUILD_DIR)/libPods.a" also under "Target --> Build Settings --> Other Linker Flags"

But again, when I tried to publish my app I got an error telling me that the compiler didn't find libPods.a, so I went to "Target --> Build Settings --> Other Linker Flags --> Release" and change this string $(TARGET_BUILD_DIR) to ${BUILT_PRODUCTS_DIR}.

So my Other Linker Flags became like the image below.
<img src="https://i.stack.imgur.com/GBWfl.png" alt="Other Linker Flags">

Hope to help somebody.

Sorry for my english.
=]

blocks|key|2757443|text|这比表面上看起来要复杂一点。经过一些实验后，我发现即使只是直接访问在AdSupport框架中引用的类，AdSupport框架也是链接的。具有讽刺意味的是，在许多第三方库中用来检查AdSupport框架是否已链接的[AsIdentifierManager+class]，实际上会导致AdSupport框架被链接。使用NSClassFromString(@"AsIdentfierManager")混淆类不会导致AdSupport框架自动链接。当然，大多数情况下，这些代码将位于第三方库中，因此您无法对其进行太多控制，然而，这就是正在发生的事情。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2757444|我在GitHub上构建了一个示例项目，使用Segment.io的框架演示了这种行为。https://github.com/distefam/AdSupportDemo|2757445|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/distefam/AdSupportDemo^0|2Y|R|4D|14|0|16|15|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

This is a bit more complicated than it seems on the surface. After some experimentation I found that the AdSupport Framework is linked even if only directly accessing classes that are referenced in the AdSupport Framework. Ironically, <code>[AsIdentifierManager class]</code>, which is used in a lot of third-party libraries to check whether or not the AdSupport Framework has been linked, will actually cause the AdSupport Framework to be linked. Obfuscating the class by using <code>NSClassFromString(@"AsIdentfierManager")</code> will not cause the AdSupport framework to be automatically linked. Of course, most of the time this code will be in third-party libraries so you won't have much control over it, however, this is what's going on. 

I built an example project on GitHub that illustrates this behavior using Segment.io's framework. 
<a href="https://github.com/distefam/AdSupportDemo" rel="nofollow">https://github.com/distefam/AdSupportDemo</a>

blocks|key|2757464|text|我之前在注释中写了以下内容，将人们定向到“string”或"otool“终端命令。但是，我真的很喜欢使用grep的建议答案。所以你可以先试一下。我的建议是在该命令前面加上"git“，因为它要快得多：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2757465|git+grep+advertisingIdentifier|code-block|syntax|javascript|2757466|如果这不起作用，那么尝试一下(如前所述)：|2757467|grep+-r+advertisingIdentifier+.+|2757468|下面是我之前在上面的评论中写的内容，作为终端命令的使用方法：|2757469|您可以在Xcode中搜索项目的文件，也可以尝试删除AdSupport框架，以查看在构建/运行时失败的原因。|2757470|要使用终端，请单击Spotlight+(搜索)并键入terminal。等待它作为应用程序出现在搜索结果中。|2757471|在Terminal中，键入"cd“后跟一个空格，然后将Xcode+build文件夹从Finder拖放到Terminal中。这将自动键入该文件夹名称。点击Enter，它会将目录(cd)切换到该文件夹。|2757472|在那里，输入strings，然后输入一个空格，然后输入您的库或otool的文件名，然后输入一个空格和库的文件名。您应该能够按TAB键来自动完成文件名。|offset|length|style|CODE|2757473|entityMap^0|0|0|0|0|0|0|0|0|6|7|V|5|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@$U|19|V|1A|W|X]|$U|1B|V|1C|W|X]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

I'd previously written the following in comments, directing people to the "strings" or "otool" terminal commands. However, I really like the suggested answer of using grep. So you can try it first. My suggestion is to prepend "git" to that command, because it's so much faster:

<pre><code>git grep advertisingIdentifier
</code></pre>

If that doesn't work, then try (as posted earlier):

<pre><code>grep -r advertisingIdentifier . 
</code></pre>

What follows is what I'd previously written in a comment above, as a how-to for terminal commands:

You can search your project's files in Xcode or you can try removing the AdSupport framework to see what fails at build/run time.

To use the terminal, click Spotlight (search) and type Terminal. Wait for it to appear as an Application in the search results. 

Once in Terminal, type "cd" followed by a space, then drag and drop your Xcode build folder from Finder into Terminal. This should automatically type that folder name in. Hit Enter, and it will change directories (cd) you to that folder. 

From there, type <code>strings</code> then a space, then the filename for your library or <code>otool</code>, a space and the filename for library. You should be able to hit TAB to auto-complete filenames.

This was simply an update that didn't change anything to do with the rejection reason. Here is the response from the resolution center:

<blockquote>
 Reasons
 Program License Agreement
 PLA 3.3.12
 
 We found your app uses the iOS Advertising Identifier but does not include ad functionality. This does not comply with the terms of the iOS Developer Program License Agreement, as required by the App Store Review Guidelines.
 
 Specifically, section 3.3.12 of the iOS Developer Program License Agreement states:
 
 "You and Your Applications (and any third party with whom you have contracted to serve advertising) may use the Advertising Identifier, and any information obtained through the use of the Advertising Identifier, only for the purpose of serving advertising. If a user resets the Advertising Identifier, then You agree not to combine, correlate, link or otherwise associate, either directly or indirectly, the prior Advertising Identifier and any derived information with the reset Advertising Identifier."
 
 Please check your code - including any third-party libraries - to remove any instances of:
 
 class: ASIdentifierManager 
 selector: advertisingIdentifier 
 framework: AdSupport.framework
 
 If you are planning to incorporate ads in a future version, please remove the Advertising Identifier from your app until you have included ad functionality.
 
 To help locate the Advertising Identifier, use the “nm” tool. For information on the “nm” tool, open a terminal window and enter, “man nm.” 
 
 If you do not have access to the libraries source, you may be able to search the compiled binary using the "strings" or "otool" command line tools. The "strings" tool lists the methods that the library calls, and "otool -ov" will list the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.
</blockquote>

The third party libraries I'm using is the latest version of <code>parse.com sdk, latest version of flurry analytics, and version 2.2 of test flight</code>. Does anybody know which library is the issue? Thanks

My app was just rejected for using the Ad support framework. Which library is responsible?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

这只是一个简单的更新，没有改变任何与拒绝原因有关的事情。以下是解析中心的响应：原因程序许可协议PLA3.3.12我们发现你的应用程序使用iOS广告标识符，但不包括广告功能。这不符合iOS开发者计划许可协议的条款，如应用商店审查指南所要求的那样。具体而言，iOS开发者计划许可协议的第3.3.12节规定：您和您的应用程序(...

问我的应用因为使用了广告支持框架而被拒绝了。哪个库负责？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我的应用因为使用了广告支持框架而被拒绝了。哪个库负责？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我的应用因为使用了广告支持框架而被拒绝了。哪个库负责？
EN