Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing NSPrivacyTracking in PrivacyInfo.xcprivacy #189

Closed
Mihai-Moniflo opened this issue May 2, 2024 · 4 comments
Closed

Missing NSPrivacyTracking in PrivacyInfo.xcprivacy #189

Mihai-Moniflo opened this issue May 2, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Mihai-Moniflo
Copy link

Expected Behavior

The app doesn't get any warnings from Apple.

Current Behavior

The app receives the following warning when sending for review to Apple:

ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: “Frameworks/AmplitudeSwift.framework/PrivacyInfo.xcprivacy”. NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn’t empty. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, keys and values in your app’s privacy manifest must be valid. For more details about privacy manifest files, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files.

We can't complete our weekly release schedule due to this issue.

Possible Solution

Add the following snippet to PrivacyInfo.xcprivacy:

<key>NSPrivacyTracking</key>
<true/>

Steps to Reproduce

  1. Add the amplitude_flutter: ^4.0.0-beta.3 plugin to your app.
  2. Upload the app to App Store Connect and send for review.
  3. You'll receive an email with the warning listed above.

Environment

  • SDK Version: 4.0.0-beta.3
  • Flutter Version: 3.19.3
  • Device: not relevant
  • Device OS and Version: not relevant
@Mihai-Moniflo Mihai-Moniflo added the bug Something isn't working label May 2, 2024
@nikolaydymura
Copy link

Experiencing the same problem as well

@crleona
Copy link

crleona commented May 8, 2024

Hi @Mihai-Moniflo, if you're using 4.0.0-beta.3, you should just be able to run pod update to pull in the latest updates to the Amplitude-Swift SDK which have already fixed this issue. (You can check your Podfile.lock for Amplitude-Swift 1.4.5).

@Mihai-Moniflo
Copy link
Author

Thanks for the answer! I just saw the PR that removed the NSPrivacyTrackingDomains. My bad :(. However, from what I see, the following file
https://github.com/amplitude/Amplitude-Flutter/blob/beta/ios/amplitude_flutter.podspec points to Amplitude-Swift 1.4.4. Shouldn't it be pointing to 1.4.5 in this case? pod update doesn't update Amplitude-Swift to 1.4.5 due to this reason.

@Mercy811
Copy link
Contributor

Mercy811 commented May 9, 2024

Hi @Mihai-Moniflo, I confirm that pod update should update to use Amplitude-Swift 1.4.5.
image

@Mercy811 Mercy811 closed this as completed May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants