"Advertising Identifier" Rejections from Apple

Update 5/6/2014: The following integrations have been reintroduced to iOS apps built by the Mag+ Publish portal:

  • Ad Marvel (v3.1.1)
  • AdMob (v6.8.0)

Update 3/6/2014: The following integrations have been reintroduced to iOS apps built by the Mag+ Publish portal:

  • Localytics (v2.23.0)
  • Fiksu (v4.1.0)

The following integrations are still unavailable due to their inclusion of an Advertising Identifier which Apple deems unacceptable:

  • Tapjoy

We are in contact with the companies above to get their code in line with Apple guidelines so that they can be reintroduced.

---

Update 2/25/14: As of 10am EST, the Ad Marvel, AdMob, and Tapjoy integrations have been removed (in addition to the Localytics and Fiksu removals on Feb 14th) from all iOS builds, in order to comply with new Apple restrictions on use of an "Advertising Identifier." We will update this article once they have been added back in.

For those users that have had their post-2/14 5.0 app rejected by Apple, we recommend generating a new build as of today and resubmitting using the instructions below.

For those users that have had trouble getting Apple to accept their 4.4 resubmission, you might consider moving on to a 5.0 submission, as the 5.0 update will only affect brand new customers that are not able to update their device to iOS7, which, according to Apple's latest statistics, 78% of users have already done. For more information on our 5.0 release and iOS compatibility, read the article "5.0 Release and iOS Compatibility".

---

Update 2/14/14:  As of 4am EST, we have temporarily removed Localytics and Fiksu from all app builds, in order to comply with new Apple restrictions on use of an "Advertising Identifier." We will restore both services soon, but in the meantime if you have Localytics as your analytics choice, DO NOT build and submit an app update or you will lose all analytics.

---

It has come to our attention that some of our customers have recently experienced iOS app rejections in iTunes Connect due to the inclusion of the "iOS Advertising Identifier" in their app code (when that functionality is not actually being used).

Apple rejection wording:

"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."

The Mag+ development team has identified that while our own app code does not use the Advertising Identifier, some of our third party integrations do.  To date, we have removed two instances of the offending code by incorporating new versions of third party service SDKs.  We are, however, continuing our investigation as to whether it could possibly exist elsewhere.  

*We can confirm that multiple builds using the current Mag+ build version have been approved after initial rejection, however we will update this page with more information after our additional testing is complete.

For those that would like to attempt resubmitting a new build now, you can follow the recommendations below:

Resubmitting a 5.0 Build

1. Generate a new version of your app build on your Mag+ Publish site in the "Apps" tab, download the resulting TGZ file, and unzip the file.

2. Log in to iTunes Connect and enter the "Resolution Center" for your app.

2. Log in to iTunes Connect and enter the "Resolution Center" for your app.

3. In the "Reply" field, enter the text below and then click "Send".

"We've identified that the Advertising Identifier was present in a piece third party code that is integrated with our app.  We will we submitting new binary to the Application Loader momentarily that includes the updated SDK they recently released, which opts out of using the Advertising Identifier.  Thank you."

*2-3. If the Resolution Center is not available in iTunes Connect for your rejected app, or it is not currently accepting comments, please do the following:

*2-3. If the Resolution Center is not available in iTunes Connect for your rejected app, or it is not currently accepting comments, please do the following:

Click "View Details" under the new version of your app in iTunes Connect, then scroll down to "Contact Information" and click "Edit" to the right.  Enter the text mentioned in step 3 into the "Review Notes" field and save.

4. In "View Details" under the new version of your app in iTunes Connect, click "Ready to Upload Binary" in the upper right.

4. In "View Details" under the new version of your app in iTunes Connect, click "Ready to Upload Binary" in the upper right.

5. Open the Application Loader and submit the newly generated "AppStore" zip file from within your unzipped TGZ.

Resubmitting a 4.4 Build (Resolution Center Not Open for Comments)

If the Resolution Center is not open within your app in iTunes Connect, you will first need to request that it be opened.

1. Click on the "Contact Us" link in the bottom right corner in iTunes Connect.

1. Click on the "Contact Us" link in the bottom right corner in iTunes Connect.

2. From the options, select "App Review", then "Continuing Communications".

2. From the options, select "App Review", then "Continuing Communications".

3. Enter your "App Name" and "Apple ID".  Then enter the text below in the explanation field and click "Submit".

3. Enter your "App Name" and "Apple ID".  Then enter the text below in the explanation field and click "Submit".

"The Application Loader will not accept our corrected binary due to the fact that it "must be built with Xcode 5.0 and iOS 7 SDK", per the February 1st cutoff.

We originally submitted this version of our app before the cutoff with the intention of putting an updated release in place before our eventual update to the iOS 7 SDK (so existing users on devices that cannot update to iOS 7 - iPad 1 - can access an updated version of our app).

Another app in the same situation, using the same digital publishing software, was allowed to submit a new binary by uploading their file directly into the Resolution Center and it was subsequently approved..

Could you please open the Resolution Center for our app (allowing for comments and file submission from our end) so we can do the same?"

Resubmitting a 4.4 Build (Resolution Center Open for Comments)

Once the Resolution Center has been opened for your app (or if it has been available all along), please do the following:

1. Generate a new version of your app build on your Mag+ Publish site under "Apps/iOS App 4.4", download the resulting TGZ file, and unzip the file.

*If there is not an "iOS App 4.4" tab under "Apps" on your Publish site, please contact support to enable it for you.

2. Log in to iTunes Connect and enter the "Resolution Center" for your app.

2. Log in to iTunes Connect and enter the "Resolution Center" for your app.

3. In the "Reply" field, enter the text below:

"We have identified that the Advertising Identifier was present in a piece third party code that is integrated with our app.  Our most recent binary, attached here, includes the new SDK they released, which opts out of using the advertising identifier.

The Application Loader will not accept our adjusted binary due to the fact that it "must be built with Xcode 5.0 and iOS 7 SDK", per the Feb 1 cutoff.  We originally submitted this version of our app before the cutoff with the intention of putting an updated release in place before our eventual update to the iOS 7 SDK (so existing users on devices that cannot update to iOS 7 - iPad 1 - can access an updated version of our app).

Another app in the same situation, using the same digital publishing software, was allowed to resubmit a fixed version of their binary by uploading their file directly into the Resolution Center and was it subsequently approved."

4. Submit the newly generated "AppStore" zip file from within your unzipped TGZ by clicking "Attach File" and navigating to the file.  Then click "Send".

4. Submit the newly generated "AppStore" zip file from within your unzipped TGZ by clicking "Attach File" and navigating to the file.  Then click "Send".

*If these suggestions do not result in Apple approving your application, please respond to us in your existing support ticket or open a new ticket if one does not already exist.

*If these suggestions do not result in Apple approving your application, please respond to us in your existing support ticket or open a new ticket if one does not already exist.
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk