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

Question

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

Reasons Pro

Answer 1

For me, Flurry Analytics and TestFlight were both the problem.

For TestFlight, it's as easy as updating it. The 2.2.1 version won't cause any problem (I checked using strings, as Apple suggest)

For Flurry, there is currently no fix apart from removing Flurry, and contrary to Lou Weed suggestion, even if AdSupport.framework is not linked, your app will be rejected.

Here is Flurry support answer :

"Thank you for reaching out to Flurry. We have recently learned that Apple has rejected some apps it believes are using the Identifier for Advertising (IDFA) without including ad functionality. Please note that Flurry does not collect the IDFA unless an app includes the AdSupport.framework for ad functionality. We are seeking clarification with Apple and we will update our affected customers as we learn more over the next several days."

Flurry just released the version 4.3.2 of their SDK, which specifically address that problem.

Answer 2

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

Answer 3

In Terminal:

1. Go to the root folder of your project
2. Type: grep -r advertisingIdentifier . (the dot at the end is critical)

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

(in my case, it was Flurry)