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

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.