search

Balaso-Software / app-tracking-transparency-for-unity

Later this year Apple will require your apps/games to request user's authorization in order to obtain the Identifier for Advertising (IDFA), used to optimize and maximize your Ads revenue
16 stars 1 forks source link

Is there a way to 'Cancel Auth' so we can test flow again? #18

Closed AnthonyDemanueleFSG closed 3 years ago

AnthonyDemanueleFSG commented 3 years ago

Hello! We just purchased your plugin and was wondering how we can repeat a few tests. Is there a way to cancel the 'Auth' so we get to request permission again?

Thank you.

andymads commented 3 years ago

Delete the app and reinstall.

AnthonyDemanueleFSG commented 3 years ago

I tried this but it stays authorized.

andymads commented 3 years ago

Works for me every time.

AnthonyDemanueleFSG commented 3 years ago

I'm testing on iPhone X on V14.4. What are you testing it on?

andymads commented 3 years ago

I've used an iPad with 14.0 beta and 14.2 and 14.5 beta, and an iPhone SE with 14.2.

andymads commented 3 years ago

Are you sure you haven't disabled tracking in Settings?

AnthonyDemanueleFSG commented 3 years ago

Where could that be in settings? But I don't think that's the case because I'm getting 'Authorized' and I can see the IDFA too.

andymads commented 3 years ago

It's under Privacy/Tracking but it's not relevant if you're already getting Authorized.

On 14.4 you will get the IDFA as it's not turned off until 14.5.

AnthonyDemanueleFSG commented 3 years ago

I see my game under that menu. If I delete the game, the entry goes away but when I install it again, I get 'Authorized' right away.

I never get the prompt asking me to allow tracking or not.

andymads commented 3 years ago

Can't say I've witnessed that behaviour - although I haven't tried with iOS 14.4.

AnthonyDemanueleFSG commented 3 years ago

@andymads are you the developer?

andymads commented 3 years ago

Nope. I'm just a user of this package.

manelizzard commented 3 years ago

After some investigation and discussion, the issue was reproducible on XCode 12.3. Updating to XCode 12.4 does fix the issue.

Thanks @AnthonyDemanueleFSG for your feedback