aws-amplify/amplify-swift

Missing an expected key: 'NSPrivacyCollectedDataTypes' in Amplify_InternalAmplifyCredentials.bundle/PrivacyInfo.xcprivacy

kernelcraft opened this issue · 7 comments

kernelcraft commented

Describe the bug

I'm using Amplify in my new app and getting an invalid binary error when I upload it to the App Store for review.
Privacy report has the following error: "Missing an expected key: 'NSPrivacyCollectedDataTypes' in Amplify_InternalAmplifyCredentials.bundle/PrivacyInfo.xcprivacy"
It seems similar to this issue: #3552. However, 3552 is marked as fixed already.

Any thoughts?

Steps To Reproduce

Steps to reproduce the behavior:
1. Add Amplify to your project
2. Archive the bundle for distribution.
3. Generate Privacy Report for the Archive.
4. See the report

Expected behavior

Clean privacy report

Amplify Framework Version

2.35.5

Amplify Categories

Auth

Dependency manager

Swift PM

Swift version

5.10

CLI version

n/a

Xcode version

Xcode 15.4 (15F31d)

Relevant log output

<details>
<summary>Log Messages</summary>


INSERT LOG MESSAGES HERE
```

Is this a regression?

Yes

Regression additional context

There is a similar bug that marked as fixed: #3552

Platforms

iOS

OS Version

iOS 17.5 / MacOS 14.5

Device

iPhone 15 pro

Specific to simulators

No response

Additional context

No response

harsh62 commented

@kernelcraft Thanks for raising this issue. Would you be able to validate if this issue goes away when using fix/3776 WIP branch?

kernelcraft commented

@harsh62, could you tell me how to do it?

harsh62 commented
  1. Go to project
  2. Click on "Package Dependencies" Tab
  3. Double click on the package you want to change the branch of. In this case Amplify
  4. Specify the branch/commit. In this case fix/3776
kernelcraft commented

@harsh62, yes, it fixes the problem with the Privacy Report.
I'm still getting the invalid binary from the App Store, though. But it's probably something else.

Thanks for the lightning-speed resolution :)

harsh62 commented

Thanks for confirming. I will work with my team to get this released early next week.

harsh62 commented

The fix has been released. Please use the latest version of Amplify.

github-actions commented

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.