Improper use of IDFA, your application does not comply with the ios end ad tracking option

Question

I checked iTC settings

I downloaded the same application 2 days ago and it works fine, but when today I downloaded the same application with a little bug fix, it now shows this error.

I use Admob, Revmob and Applovin. But I know that the culprit is the culprit.

Answer 1

The only solution for me was to destroy the Admob-SDK and integrate the Startapp-SDK , it complies with the new IDFA rules for Apple, you can read them here .

I will let you know if the Admob guys fix this problem.

---

From Applovin Users

I wanted to update you on the IDFA change Apple made on Saturday. Apple systems automatically reject applications that download if the application has SDKs that access IDFA and still support pre-iOS 6 (where the IDFA was not present). Our new SDK 2.3.6 (and Unity, 3.0.9) will now go through the Apple screen, since we have outdated support for iOS 4 and 5 (only 1.5% of the traffic); and note that many of the popular SDKs on the market do the same, so you may need to work with your other vendors when updating their software for compatibility.

---

Edit

I downloaded the update today (May 5, 2014) with admob 6.8.0 and it was downloaded successfully

Answer 2

This was confirmed for me. Initially, I thought the problem was in the question, and maybe it was, but after removing TapJoy and all the links approved by the application.

Answer 3

I had to remove both InMobi and Conversant (aka ValueClick / Greystripe). He then ceased to be "Invalid Binary" and switched to "Waiting for Review". I can confirm that AdColony, Chartboost and TapJoy all definitely pass Apple's test with the latest versions of the SDK. InMobi has released an SDK update on 29/4 (v4.3.0), but this test fails.

Answer 4

I used Google AdMob and Flurry. With the AdSupport card removed, it shows that AdMob is the culprit.

I can’t find any recently released SDK for AdMob and Flurry, so I just changed the status to readiness for binary download again, select the answer as shown above on the screen dump, and it works for me, on some dump screen on my blog below. Hope this helps. Thanks!

http://new2objectivec.blogspot.com.au/2014/05/app-store-invalid-binary-error-due-to.html

Answer 5

Today I presented an application with AdMob with the same settings. Now he is on standby.

I used Xcode Organizer to submit the application. Apple may have changed the validation.

Answer 6

It looks like your problem really comes from Applovin, not AdMob. Others seem to have succeeded in AdMob somehow, so that makes sense. These guys concluded that this is Applowin → Source

I finally got my confirmation! If you remove AdSupport.framework, any culprits who caused this failed check will NOT cause a linker error. Thus, the SDK, which shows errors, correctly uses the structure, removes any others, and retries. In my case, the Millennium was a problem.

Answer 7

I downloaded the application with admob sdk 6.8.0 successfully today (after uninstalling mmedia sdk 5.2.0). I think you need to check out another sdk ad network.

Answer 8

I had an application that was able to "wait for download" until April 12th. After that, the itunes guidelines were updated to contain the IDFA usage section when the state of the application is “Preparing to Download”. Therefore, because of this situation, every time I included in the binary, I would get the error "IDFA misuse".

For me, the solution was

1.upload binary without IDFA SDK.

2. Cancel it "the developer rejected."

3. Set the IDFA settings after selecting the "ready to upload binary" option from itunes connect.

4. Run the new binary using the IDFA SDK.