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

Rob, i have done what you suggested. I enabled iads, I signed the contract, I checked I am using IDFA, I included iads in buid.setting. I initialize the ads (one note: is not app id is bundle id, I tested both)…I show a banner in about screen… (it doesnt show and my app get locked) but anyway I uploaded it…

I still get the same error: " it’s not respecting the Limit Ad Tracking settings on iOS"

Running into this issue as well when trying to patch one line of code … today same build 2231 gets rejected.  I did not check the IDFA box when setting up the new Version.  I do include the Facebook plugin.

So couple of questions:

  1. how do you change that setting in itunesconnect ?

  2. any update on the suggested course of action to get around this issue? 

well 3 questions then:

  1. Will we have the same problem if we do not use the facebook plugin and just use the social plugin?

Answer to this one is: No the social plugin does not seem to get flagged by itunes.  So in my case i was able to set facebook plugin to just be included for android builds and make sure that my include for facebook was wrapped by an os check so it is not pulled when running on ios.

I’m running the same problem as @whammy and @noeger.

To confirm:

  • Using public build 2189
  • using Facebook plugin for publishInstall
  • on iTunes Connect, when creating new version checked “Using IDFA”
  • “Attribute app installation to a previously served advertisement”
  • Checked “Limit Ad Tracking setting in iOS”
  • Sent new version with Application Loader
  • Application Loader didn’t let me upload the new version with an error saying that the app is not respecting the Limit Ad Tracking Setting in iOS

You can remove all plugins & build the app. Submit this new build (without plugins) and after the upload is successful (status in waiting for review), reject the binary.

And rebuild the app with appropriate plugins and upload, you are able to change the settings. 

This is how I did it.

But I am still very confused about these IDFA options. 

Corona should explain this in details. Which plugin makes this IDFA a must? And what options should I check inside the IDFA option? Any other impact or side effect?

Now after I checked IDFA & checked the advertisement option, the uploading is successful. 

@joe528, but now if you selected advertisement option than you have to display at least one ad or a review team (possibly) rejects your app 

@Rob, any Corona official statement on respecting Limit Ad Tracking in future Corona builds?

Hello all,

I have the same trouble being rejected while uploading because of the IDFA stuff – though my app does *not use any ads or social / facebook plugins. 

Being rejected is really bad for me because I am close to the deadline for shipping.

I am using public build 2013.2100 because newer builds do not display the lines in tableViews properly – in my case.

So I have to stay at build 2013.2100. 

Is there already a solution for build 2013.2100 ?

Any other ideas what I could do?

Thanks in advance!

 @whammy

I really don’t know if I should or should NOT select advertisement option. Since my app does use admob to show some ad, so I checked the option. It’s just a “guess”.

And that’s why in my message I also asked if Corona can officially explain what plugins require IDFA & what options should we check under IDFA? For now I am just guessing because probably if I get lucky I can get my app approved before Corona ever answers my questions.

Hi all…I could upload my version. I check IDFA…but I was still having problems with other error:

" it’s not respecting the Limit Ad Tracking settings on iOS"

I was thinking and In my buid setting I had two plugis,

Facebook and social…
I remove Facebook plugin , and I let social only. Take care, remove the require(facebook) in your code…
And the app was aproved…

Perhaps the limit ad tracking is cause for using both plugins.

 

Just curious - for those of you using FB only for install tracking (besides the Limited Ad Tracking issue), is it OK with Apple? Looking at our app submission portal, it looks like you can go for 1 of 3 reasons for IDFA…

* Serve advertisement within the app

* attribute this app installation to a previously served advertisement

* Attribute an action taken within this app to a previously served advertisement

Engineering is looking into it.  I don’t know much more than the current Facebook SDK still contains it and you will have to tell Apple you are using it and probably demonstrate that you are using it.

Rob

@akao, IMO the second option covers publishInstall - it attributes your app installation to a previously served (clicked) facebook ad.

@Rob, it seems not to be about demonstrating the ad, but this respecting ‘limit ad tracking’. Noeguer wrote that he showed ads but still got rejected in application loader due to this ad tracking. If you can select IDFA purpose, then you don’t have to show the ad if it was just to attribute the app installation, I guess? Let’s see what engineering says.

I finally found a way to upload an app with iAds and Vungle in it.

If your app was previously rejected you need to upload a dummy version with absolutely no plugins to reset the IDFA thing.

Then you reject the dummy binary.

Go to the itunes connect and set app ready to upload, this will give you the fresh IDFA window again.

I checked all the boxes being YES the first one

(NOTE: this happened just this morning and I don’t know if they will approve or not the app, at least they accepted it and it’s currently ‘wating for review’)

I used 2189a for building.

Also check this link for clarification: https://mohound.com/blog/2014/04/29/avoid-appstore-rejection-by-following-this-2-easy-steps/

let’s see what happens…

My app is rejected because of IDFA as well when using build 2100. 

And it works after I upgraded to 2189 without modify the code.

@orangecyan

I think it should be easier to fix the tableview in 2189 instead of keep trying to build with 2100.

My table view’s line is not displayed properly as well, the line between the list is not start from the left side, but start form about 1/3 in the middle. What I did those to fix it:

  • set the table view’s wide about .5 times wider, 

  • add 10 space in front of the text to each row

  • add a mask to cover the left part.

Hope this helps

Hi dan300,

my app has been accepted for upload with 2189 as well.

And yes, it has not been so much work to fix the tableViews :wink:

I did it another way: As the lines in the tableView never showed up properly, I put small rectangles on top of each row: width = row.width, height = 1 or 2. This works fine. They should not have an alpha as this might result in white lines.

I keep getting rejected over and over again. Any word Corona?

Elevate Entertainment…  What version of Corona SDK are you using?  What plugins are you using? Are you using the facebook.* API?  Are you using any Ads?

I tried multiple daily builds (2288, 2189). I’m using Flurry & Facebook. No ads.

Facebook’s SDK users this IDFA.   You must select the right values in iTunes Connect when telling it you’re ready to upload your binary, which is to say that your app uses it.  You may have to include the iAds plugin in case their scanner looks for it.  I don’t know all the magic tricks here.  Now assuming you can get by the auto-check when uploading, you may still get punted by Apple’s reviewers unless you are actively showing advertising.  Several people  have posted recipes for getting this done.

What can Corona Labs do about it?  Well right now, not much. It appears with 2189 or later and not using Facebook and making sure you get the settings right in iTunes Connect apps are getting apps through,  As for apps that need the Facebook API, until Facebook releases an SDK that doesn’t use this, you will have to check the right settings and potentially show an ad.

Rob

We did check the right settings, but still got rejected multiple times. We’re not going to show an ad because its paid. I guess i’ll plead our case to apple.

Did you try initializing iAds at least or including the plugin?