Post marked as solved
4.7k
Views
I'm testing my implementation of the new App Tracking Transparency framework and am running into an issue: requestTrackingAuthorization() never shows the authorization prompt, and ATTrackingManager.trackingAuthorizationStatus always returns .denied.
I've verified that the following settings are enabled: Privacy -> Tracking -> Allow Apps to Request to Track
Privacy -> Apple Advertising -> Personalized Ads (not sure this is even related)
I've deleted and reinstalled the app and restarted my device, but to no avail.
Any ideas as to what's going on here? Notably, I do see the prompt when running on the simulator, just not when running on actual hardware.
Versions of stuff
iOS: 14.3 (18C66)
Xcode: 12.3 (12C33)
Post not yet marked as solved
434
Views
Hi everyone,
My question is about the ATT requirement and if the app itself meets the qualifications to require it.
After reading the guidelines it has left me even more confused, so here is the situation.
Our app sends back user data to our servers, part of this user data is tied to our in-house analytics (not 3rd party) so we do 'track' a user in an analytics sense X user clicked on X part of the app etc.
This data is never sold and is not tied to any advertising etc. We do not use IDFA at all.
With that being said, we got an email saying that based on how we answered the questionnaire we would require this, but I have a feeling it may be because of how the term 'track' is used by Apple.
So basically, we are looking for clarity on this, because adding the tracking prompt is misleading to users as it states we will share data with 3rd party apps etc, again something we do not do so I'm curious if ATT is needed in this case
Any help is greatly appreciated.
Thanks
Post not yet marked as solved
129
Views
TLDR: Adding the Facebook SDK to a fresh, empty Xcode project yields an executable that links to AdSupport. Q: Can I prevent this?
This happens without importing or using the SDK. The mere presence of the dependency (via SPM) in an otherwise empty app triggers the inclusion of AdSupport.framework in the executable, as confirmed by nm and otool.
The phrase "Facebook SDK does not require AdSupport.framework to be included." appears in lots of searches, but is never accompanied with an explanation of how to exclude the framework.
This is also a question for a Facebook forum, but I am posting it here as a question about build tools: Apart from downloading the SDK source and painstakingly commenting out the transitive closure of all references to AdSupport, ASIdentifierManager, and IDFA, are there any compile/link directives that could stop the inclusion of the forbidden fruit?
Post not yet marked as solved
228
Views
Hi,
Currently working on Xamarin forms which supports IOS also, in IOS need to implement Privacy policies (Allow tracking) mainly.
For this we need to add specified string need to add in Info.plist.
Issue: once permission Allow tracking is allowed from . Later user denied it from go to phone setting -> apps -> myapp -> permissions-> Allow tracking to **deny **.
Now with out opening / interacting myapp how to know the permission is modified(Allow to Deny).
Thanks in advance.
Siva Y
Post not yet marked as solved
331
Views
We just got a reject because the they think we do not use App Tracking Transparency to request the user's permission ,
Instead, displays a custom prompt that requests the user to allow tracking.
But based on Unity official doc, we can show customised prompt and then after click Next then show ATT popup.
Does the apple change the policy to refuse the customised prompt?
Post not yet marked as solved
1.1k
Views
Hi everyone,
we are developing an app using cordova and an admob plugin (https://github.com/tomitank/cordova-plugin-admob-tomitank) and implementing the iOS 14 ATT functionality.
We were testing it on iOS 14, and noticed that when "allow apps to request to track" is disabled, the adMob SDK can not load any interstitial ad (NO\_FILL error).
We then tried to write a very simple test app using native code only and implementing the adMob SDK, to check if the behaviour was tied to cordova or not.
The behaviour happens on the native app too.
Basically, when "allow apps to request to track" is enabled, everything works fine and the interstitial ad is loaded correctly.
When "allow apps to request to track" is disabled, the adMob SDK can not load any interstitial ad, always returning error 1 (NO\_FILL).
A screen record of the full behaviour can be found on the original issue on this answer - https://github.com/tomitank/cordova-plugin-admob-tomitank/issues/3#issuecomment-706974309 in the github page of the cordova plugin.
We searched everywere, posted on the admob help community forum, but could find nothing.
We believe that this functionality is one of the most used, so it seems strange that no one pointed it out before if it was a bug.
Are we maybe missing something in our implementation? Any suggestion on what can we check?
Thank you very much.
Post not yet marked as solved
95
Views
Testing tracking on iPhone.
We are currently implementing ATT support for iOS14 and later, using the following SDK.
[https://github.com/adjust/unity_sdk)
The test itself went well, and I was able to display a dialog asking for permission, and get a status of "Allowed" or "Denied". However, I don't know how to test the restricted status (ATTrackingManagerAuthorizationStatusRestricted in the following URL).
What steps should I take on a real machine?
[https://developer.apple.com/documentation/apptrackingtransparency/attrackingmanagerauthorizationstatus/attrackingmanagerauthorizationstatusrestricted)
Development environment
Unity2019.4.3f1
iPhone11
iOS Version 14.4.2
Post not yet marked as solved
86
Views
Testing tracking on iPhone.
We are currently implementing ATT support for iOS14 and later, using the following SDK.
[https://github.com/adjust/unity_sdk)
The test itself went well, and I was able to display a dialog asking for permission, and get a status of "Allowed" or "Denied". However, I don't know how to test the restricted status (ATTrackingManagerAuthorizationStatusRestricted in the following URL).
What steps should I take on a real machine?
[https://developer.apple.com/documentation/apptrackingtransparency/attrackingmanagerauthorizationstatus/attrackingmanagerauthorizationstatusrestricted)
Development environment
Unity2019.4.3f1
iPhone11
iOS Version 14.4.2
Post not yet marked as solved
70
Views
Testing tracking on iPhone.
We are currently implementing ATT support for iOS14 and later, using the following SDK.
[https://github.com/adjust/unity_sdk)
The test itself went well, and I was able to display a dialog asking for permission, and get a status of "Allowed" or "Denied". However, I don't know how to test the restricted status (ATTrackingManagerAuthorizationStatusRestricted in the following URL).
What steps should I take on a real machine?
[https://developer.apple.com/documentation/apptrackingtransparency/attrackingmanagerauthorizationstatus/attrackingmanagerauthorizationstatusrestricted)
Development environment
Unity2019.4.3f1
iPhone11
iOS Version 14.4.2
Post not yet marked as solved
71
Views
Testing tracking on iPhone.
We are currently implementing ATT support for iOS14 and later, using the following SDK
[https://github.com/adjust/unity_sdk)
The test itself went well, and I was able to display a dialog asking for permission, and get a status of "Allowed" or "Denied".
However, I don't know how to test the restricted status (ATTrackingManagerAuthorizationStatusRestricted in the following URL).
[https://developer.apple.com/documentation/apptrackingtransparency/attrackingmanagerauthorizationstatus/attrackingmanagerauthorizationstatusrestricted)
What steps should I take on a real machine?
//Development environment
Unity2019.4.3f1
// iPhone11
// iOS Version 14.4.2
Post not yet marked as solved
2.0k
Views
Can not update app privacy information about tracking user after remove the tracking functionality and "NSUserTrackingUsageDescription" from info.plist. Always reminds us App contains "NSUserTrackingUsageDescription"
Post not yet marked as solved
211
Views
I have enabled SKAdNetwork and implemented requestIDFA() method as suggested by Google AdMob. Now my app is pushed to the app store without any problem. But my app is not receiving ads when the user disagrees to allow tracking.. Anyway I'm loading ad in both scenarios. Is anything I'm missing here
Post not yet marked as solved
138
Views
Hi guys
i'm experiencing problems with NSUserTrackingUsageDescription, even after I implemented NSUserTrackingUsageDescription in my info.plist file and implemented the idfa pluggin (I'm using IONIC with cordova) apple continues to disapprove my application, you know how to inform me if there is any other solution to that problem?
Post not yet marked as solved
317
Views
Dear All
Though my app doesn't implement ATT and has declared Data Not Collected in the privacy section, Apple has rejected its update for many times, saying
The app privacy information you provided in App Store Connect indicates you collect data in order to track the user,
Apple also says:
If your app does not collect user or device data for tracking purposes, please update the information you provided about your app’s privacy practices in App Store Connect.
The point is that the app does not include ATT framework nor the AdSupport framework. It is a paid app and does not include ads sdks either.
I have repeatedly requested Apple to tell me where my app had declared that it would collect user or device data, Apple never answered directly, and finally suggested:Review developer documentation for the AppTrackingTransparency framework.
See Frequently Asked Questions about App Tracking Transparency.
Ask fellow developers and Apple engineers a question in the Apple Developer Forums.
Since the app does not implement ATT at all, I come here to ask for your help.
Thank you in advance.
Post marked as solved
305
Views
We are implementing a new view-through attribution in our SDK.
But we have a weird issue with startImpression:completionHandler: static method of SKAdNetwork class. It seems like it just blocks current thread execution without calling completionHandler. It doesn't matter if this method was called on main thread or on background thread.
Also when we were missing some required fields in SKAdImpression object, completionHandler was called with corresponding error message and thread execution wasn't blocked.
Does anyone else has the same issue?
We are using latest XCode 12.5 and iPhone X with iOS 14.5. Both are final, not betas.