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

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, [AsIdentifierManager class], 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 NSClassFromString(@"AsIdentfierManager") 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. https://github.com/distefam/AdSupportDemo