Improper Advertising Identifier [IDFA] Usage. Your app contains the Advertising Identifier [IDFA] API but you have not indicated its usage on the Prep

Solar2D General Questions/Discussion
#1

My app doesnt have any ad, and has no any code to show ads but I am recieving that error when i try to upload a new version.

And the problem is now I am stuck, I can’t upload any new version!, because I can’t delete de new version which is waiting for upload. I check no IDFA and now I can’t change it!

I am only using the social plugins, and this is new, same code, a few hourse it worked without any problem.

EDIT************

I GOT UNLOCK, UPLOADING THE PHOTOPICKER SAMPLE CODE WITH MY APP PROVISIONING FILE AND THEN DELETING THE BINARY, but same error every time I upload…I am not using ads why this appear?

It says: Is not respecting the limit ad tracking setting in iOs…
I am not using any ads!

#2

I am getting the same error when I tried to upload an update to my app. I have no problem with this just a few days back.

#3

Yep me too.   I am assuming is a case of when submitted for build that there is code appended e.g. in binary can see reference to Facebook etc.

So even though my code has no ads nor references to 3rd party API’s, it is the build process that is causing this.  Probably no problem in the past, but now that Apple is cracking down harder on IDFA this is the outcome.  

If my assumption is correct then would subsequently assume that will need Corona to sort out.

#4

For me the same message. I have an app and I want to upload a new version and the xcode application loader show to me the same message. I’m using corona Version 2013.2076. Is the first time it appears to me. I have changed only some images. My app have not any ads plugin

the message in appllication loader is 

Improper advertising identifier idfa usage. Your app contains the advertising identifier idfa api but you have not indicated its usage on the prepare for upload page in itunes connect

 

#5

What version(s) of Corona SDK are you building with?  We removed this Identifier in 2169.  You need to run a version newer than this, like the last public build 2187. 

Please note, that the Facebook SDK was also pulled out and put into a Plugin with that version because the Facebook SDK includes this identifier. 

Rob

#6

Tried build 2282.

#7

2189, we know about plugin. My app was being uploaded without problems until yesterday. I have uploaded version even with 2282.but yesterday problems

#8

I’ve built a new version app in corona version 2013.2076 and i receive the same message.

After I try to upload the same app that I uploaded 3 weeks ago and the xcode application loader say to me the same message.

One app that was aproved 3 weeks ago now say this message.

The app has not any ads. Only show photos, videos and pdf’s.

#9

For those being rejected are you using any 3rd party services, like Facebook, Analytics, any plugins?  There are multiple reports.  Can you be very clear:  Corona Version Number rejected, Corona Version number working.

Thanks

Rob

#10

In my case I built with corona 2013.2076 an app made with kwiksher.

This is an app that show images, txt, photos, videos and pdf’s ( native.newWebView ) 

Also the user can click to send a email.

  system.openURL( “mailto:logistica@ponsquimicas.es” ) 

The app has not any 3rd party services like facebook, analytics or any plugins.

The new version is like the version that is actually in appstore (only I have change some images)

And in both with corona 2013.2076. 

If i try to upload the version that appstore approved 3 weeks ago, now it say to me the same message:

Improper advertising identifier idfa usage. Your app contains the advertising identifier idfa api but you have not indicated its usage on the prepare for upload page in itunes connect.

#11

Tested and rejected 2014.2282 and public 2014,2189

Using social plugin(facebook)

#12

Yes. I have dowload the corona version 2014.2189a and now it’s ok

Approved in application loader.

Not show the error.

#13

Version 2013.2100 (2013.12.7)

Worked one week ago, does not work today. NO code changes, NO plugins, NO ads, no 3rd party anything.

I really didn’t want to be forced to update Corona until I have time to test my app on a new Corona build. I’m trying to submit an app update with bug fixes.

Something has happened on your build. Hope you can fix this ASAP… I can’t get bug fixes out!

#14

I’m having the exact same problem - can’t upload my app using application loader due to this Improper Advertising Identifier. Tried 2189a and 2282 corona builds - it’s the same. I’m using a social plugin and pushwoosh for push notifications, and I also call facebook publishInstall but I have NO ADS inside my app.

What’s going on? :confused:

#15

Uh oh. I am using PushWoosh too.

But they aren’t a plugin. Just network requests and onNotification listeners.

I cannot afford to remove PushWoosh, it’s integral to my app. But I’m not using anything else, no third party plugins, no FaceBook, nothing.

What’s really strange is that this just started for me on an older Corona build, 2100. So to me that makes it seem like it’s something they just started to do on their server for ALL builds. I hope they are taking this into consideration.

And this is preventing me from updating a critical bug fix, so I hope Corona is on it.

#16

Good news! 2189 worked for me. And yes I did have to change my code to use 2189, didn’t really wanna do that.

So either Apple just happened to fix it after I tried my 2189 build, or 2189 fixes the problem. If you’re still having the issue with a 2189 build then it has to be one of the other plugins. It’s not PushWoosh, which as I said, isn’t really a plugin anyhow. I am having other PushWoosh issues, though that’s another topic.

#17

OK, so IDFA is in a facebook plugin.

I did some testing - firstly I removed a social plugin from build settings and built my app without it - still application loader rejected it. Then I reverted the social plugin back, and removed the facebook plugin (I only use these two plugins in my app) and built the app without it - application loader accepted my built with no warnings!

Ouch, now I read Rob’s answer saying that’s facebook was pulled out into a plugin because it has this identifier.

OK… so what should I do now? How can I get this IDFA from facebook to provide it to apple? Also - is it possible to change settings of the app in itunes connect once I chose that my app doesn’t have IDFA? I can’t find any option for that. Do I really have to make a new App ID with bundle and all this stuff to include IDFA?

Now I found Rob’s answer in another topic: “According to the Tech Crunch article, Apple is going to reject apps that use the ASidentiferManager library that doesn’t show ads.”

So even if I declare that I have this IDFA, but I just call facebook.publishInstall to market my app in facebook feed, I’m going to be rejected because my app doesn’t show ads itself? 

#18

Well that is not a solution, I am using facebook sharing. So i could not update my apps.

Must be something that Apple changed one day ago but it needs a solution. Even when I check I am using IDFA and I use facebook, it gives me other error.

#19

Everyone please read this in detail.

Apple has started rejecting any app that calls this identifier that doesn’t have ads in the app.  They appear to be scanning the code looking for the SDK.  Prior to build 2169 (as I mentioned above), we provided this identifier through an API call for apps that need it.  When Apple started rejecting it, we pulled the identifier out of the core.  We also pulled the Facebook API out (iOS only) and made it a plugin so that people not using Facebook would be okay.  The Facebook SDK includes this identifer and it’s not something we control.  Since the facebook.* API is now a plugin, iOS people have to include it on purpose.

So if you do not use the facebook.* API calls (social plugin should be fine) you must build with a build after 2169.  That means using 2189 for those who have to use public builds.  We cannot go back and patch old daily builds.  New builds and daily builds are the patched updates.  You should not get rejected using 2189 or later if you are not using the facebook.plugin.

For those who need facebook.* calls, if Apple is now rejecting the app because you’re using facebook, then you may have to add at least one ad in your app.  I don’t know if the answer is just to initialize iAds, sign the contract on iTunes Connect and enable it for your app.  If it’s being rejected by software, then that might be enough.  If these rejects are coming from the review team, you might be able to bury the ad on an “about us” page or something. 

Is any one seeing this with 2189 or later and not using Facebook?

Rob

#20

@noeguer, you’re right I tried to resubmit my app with IDFA selected on but application loader still doesn’t allow me to upload the build :confused:

Now it says, that I have declared the IDFA but " it’s not respecting the Limit Ad Tracking settings on iOS"

@Rob, I think you may be wrong - there was an option to declare what IDFA was used for. In my case it was just to say the app was installed when clicked the facebook ad (publishInstall call). Apparently apple knows that this case is quite common if they make this choice available for selection. So I guess you don’t have to place an actual ad in your app to use IDFA. The problem is that in Corona API it doesn’t respect the Limit Ad Tracking settings. Is it something you can patch?

When submitting the binary details there’s a declaration that has to be checked once declaring IDFA:

 “I confirm that this app, and any third party that interfaces with this app, uses the Advertising Identifier checks and honors a user’s Limit Ad Tracking setting in iOS and, when it is enabled by a user, this app does not use Advertising Identifier, and any information obtained through the use of the Advertising Identifier, in any way other than for “Limited Advertising Purposes” as defined in the iOS Developer Program License Agreement.”

So I guess apple takes it seriously.