@adam, it probably won’t pass the human review since you don’t display the ads while you just declared you did. You have to either build with no ads using 2169 Corona build (or later), or update using 1262 build but display some ads in your app.
Hi
I’m getting the same message using 2332
I’m using Admob plugin v2
If I use 2189, I get:
Error: Get plugin failed.
Publisher: com.coronalabs
Plugin: plugin.google.play.services
So, I’m trapped… PLEASE HELP!!!
@egruttner, if you’re using Admob on iOS, then you’re using advertising and it should pass Apple’s rules. You just have to make sure you’re using the right combination of check marks when telling iTunes Connect that you’re ready to submit your binary.
You cannot use AdMob v2 with 2189. It requires Android 2.3 as a minimum which was a change we made after 2189.
Rob
Thanks Rob!
I’ve finally passed the Apple’s first approval (the problem was iOS only)
Some tips:
-
Admob v2 plugin
-
Corona Daily Build 2332
-
Itunes Connect preparation, I’ve said yes to IDFA, checked the first statement and the mandatory one
That’s it…thanks again!
Hey Rob - any chance you can take a look at the ticket I spawned from here a while back regarding issues with compatibilty mode? http://forums.coronalabs.com/topic/47664-issues-with-graphicscompatibility-1/
I just read all this post…
I have the same problem with IDFA
– I’m using version 2100
–I have no ads at all
–no facebook
I call apple and they say is the third party problem
now Rob…Do I have to upgrade to 2189?
do you think it will solve the problem?
and earl3 – is it really difficult to change all the code for 2189?
Yes, you will need to upgrade to 2189. 2100 has the facebook library built in and it trips up the IDFA tester. There shouldn’t be much in the way of changes between 2100 and 2189, though some bugs have been fixed that you may be depending on or have worked around. You should thoroughly test your app after switching to 2189a. Make sure to get the “a” version. Apple will reject 2189 for a different reason.
Rob
I’m getting
"Your app is using Advertising Identifier (IDFA). You must either provide details about IDFA usage or remove it from the app and submit your binary again"
while I submit my app for review.
Plugins enabled: flurry (with dependency of plugin.google.play.services)
I’m using flurry Using 2014.2511 (latest public relase)
Flurry console reports that app uses Flurry SDK 4.3.2 (which should resolve IDFA issues from few months ago)
Removal of flurry (and play services) solves the problem.
Does anyone else experience this?
Well Google Play Services is the AdMob plugin. I would expect it to use the IDFA. There should be an option when you go to tell iTunes Connect that you’re preparing to upload the binary where it asks you if this has encryption, is being uploaded for legal reasons, etc. There will be questions about the IDFA there and one of the options is its being used for install tracking or analytics. I don’t have the questions in front of me, but one of the answers should be checked.
Rob
I’m getting
"Your app is using Advertising Identifier (IDFA). You must either provide details about IDFA usage or remove it from the app and submit your binary again"
while I submit my app for review.
Plugins enabled: flurry (with dependency of plugin.google.play.services)
I’m using flurry Using 2014.2511 (latest public relase)
Flurry console reports that app uses Flurry SDK 4.3.2 (which should resolve IDFA issues from few months ago)
Removal of flurry (and play services) solves the problem.
Does anyone else experience this?
Well Google Play Services is the AdMob plugin. I would expect it to use the IDFA. There should be an option when you go to tell iTunes Connect that you’re preparing to upload the binary where it asks you if this has encryption, is being uploaded for legal reasons, etc. There will be questions about the IDFA there and one of the options is its being used for install tracking or analytics. I don’t have the questions in front of me, but one of the answers should be checked.
Rob