Apple Rejecting Apps For Not Showing Ads
blog.tapstream.com
Apple Rejecting Apps For Not Showing Ads
1–10 of 25 posts
Re: Apple Rejecting Apps For Not Showing Ads
#2I’m not sure my understanding of this is correct. It seems to be crying about the problems this will cause. Ostensibly, it’s saying that there’s a problem with the identifier for ads being requested in apps that don’t have ads (i.e. being used as a surrogate identifier).
But, more nefariously (again, if my understanding is correct) it’s saying that many ad networks rely on this info being passed to advertisers (despite the policy being that it shouldn’t), and how problematic it’s going to be if Apple enforces this policy.
If this is the case, my sympathy is close to zero. Not because “advertising = bad”, but because this was a known no-no. Don’t cry foul when you can’t do what you were told you couldn’t.
Re: Apple Rejecting Apps For Not Showing Ads
#3Hang on, you think Apple are worried about the privacy of end users? I call shenanigans! There are likely many reasons they're doing this, that is firmly at the bottom of the list three rooms over entitled "things Apple don't care about".
Re: Apple Rejecting Apps For Not Showing Ads
#4No, Apple is rejecting apps for pulling the advertising unique identifier and not using it for ads, but instead to spy.
Stop it.
Re: Apple Rejecting Apps For Not Showing Ads
#5No, Apple is rejecting apps for pulling the advertising unique identifier and not using it for ads, but instead to spy. Stop it.
Allowing the use of the IDFA by publishers and not by advertisers renders it useless, since it can no longer be used for attribution. I don't think conversion tracking - measuring the performance of ads you bought to promote your app - counts as spying.
Re: Apple Rejecting Apps For Not Showing Ads
#6Hang on, you think Apple are worried about the privacy of end users? I call shenanigans! There are likely many reasons they're doing this, that is firmly at the bottom of the list three rooms over entitled "things Apple don't care about".
Well, if you see what happened with UDID and how much kerfuffle there was to get from there to IDFA it's pretty obvious Apple wants to protect the user.
For a contrast to Android you just need to read this article: http://www.linkedin.com/today/post/article/20140130170002-11...
Re: Apple Rejecting Apps For Not Showing Ads
#7This might be a shot at Stripe/Braintree/Paypal. All those companies want to use the IDFA as a part of their scheme to uniquely identify devices/users for their one touch payment solution, and Apple has been rumored to be getting into the mobile payments arena.
Re: Apple Rejecting Apps For Not Showing Ads
#8Even if Apple has some nefarious motive for doing this, if it really does have a beneficial effect on privacy, I find it hard to fault them for it. Can we save the pitchforks and torches for when they do something actually bad? (that is a serious question, there are arguments both ways)
Re: Apple Rejecting Apps For Not Showing Ads
#9Original text from Apple with tips to fix using strings and otool at: https://github.com/mixpanel/mixpanel-iphone/issues/109
Note that this affects quite a few major platforms:
* parse.com seems to have added it when they added social.framework for Facebook features
* TestFlight uses it for obvious reasons: https://testflightapp.com/sdk/ios/doc/2.0.0/ -- they add it even if you forget to.
* Mixpanel affected (with workaround above)
Not affected:
* AFAIK, Google doesn't use it unless you added it as a custom metric with your own custom code (or a third-party integration library)
* Flurry split off their advertising library from their analytics one, in part likely because of this requirement from Apple. If you implement just the analytics, it does not require AdSupport.framework.
Re: Apple Rejecting Apps For Not Showing Ads
#10I’m not sure my understanding of this is correct. It seems to be crying about the problems this will cause. Ostensibly, it’s saying that there’s a problem with the identifier for ads being requested in apps that don’t have ads (i.e. being used as a surrogate identifier). But, more nefariously (again, if my understanding is correct) it’s saying that many ad networks rely on this info being passed to advertisers (despi…
I think what they're saying is that for something as simple as analytics (just an example), apps need some sort of unique identifier for the user, but that the only unique identifier iOS provides is the advertising ID of the user. Of course the correct answer is to stop doing any sort of analytics, or anything else that requires a unique identifier. But the point I think the author is making is that that is a bad solution.
Of course this all ignores the possibility of creating user accounts or generating a unique identifier whenever the use installs the app, so maybe there is something more to it that I'm not understanding. Because I tend to agree with you, that developers shouldn't be doing something with user data that is prohibited.