Skip to main content
Known Participant
February 4, 2014
Question

New Appstore rejection fun - adIdentifier issues..

  • February 4, 2014
  • 1 reply
  • 6198 views

Hello - I've just had an app kicked back for something I've not seen before that *may* be to do with the new guideline - although I'm using the latest version of air (4.0) which should get around the xcode5 issue that's going to bother a lot of people.

it's this basically... (more below)

I'm only including storeKit and Flurry extensions and I can't find anything of the advertisingIdentifier in them. Has anyone else had this yet. I'm happy to dump Flurry for the time being, but I have a 'bad feeling' it's not going to be that.

Any help would be massively appreciated !

-Cheers,

Jerry

This topic has been closed for replies.

1 reply

Colin Holgate
Inspiring
February 4, 2014

Flurry did an update a while ago, to stop using the UUID. Might be worth a try with their latest build.

Known Participant
February 4, 2014

yup - this is the update i used - it seems whatever the workaround then was (using adIdentifier or something related to it) has now become taboo also.

If that is the case, I'll probably dump flurry in this one, resubmit, and cross my fingers. Will miss parsing all that mad Flurry stat stuff though : (

thanks for the reply btw Colin !

-J

Colin Holgate
Inspiring
February 4, 2014

Incidentally, I recently dropped Flurry too, because our tracking wasn’t showing up. We switched to Google Analytics, and that seems to be working ok.