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

[Bug]: Privacy Manifest Issue #125

Closed
bejewel-daye opened this issue Apr 26, 2024 · 7 comments
Closed

[Bug]: Privacy Manifest Issue #125

bejewel-daye opened this issue Apr 26, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@bejewel-daye
Copy link

Platform

iOS

Platform Version

All

Braze SDK Version

9.0.0

Xcode Version

Xcode 15.2

Computer Processor

Apple (M1)

Repro Rate

100%

Steps To Reproduce

Expected Behavior

Actual Incorrect Behavior

Verbose Logs

No response

Additional Information

I updated the Braze to 9.0.0 but still have an issue.
I got an email from Apple when we submit our app:

ITMS-91053: Missing API declaration - Your app’s code in the “PlugIns/NotificationContentExtension.appex/NotificationContentExtension” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

Apple Developer Relations

@bejewel-daye bejewel-daye added the bug Something isn't working label Apr 26, 2024
@lowip
Copy link
Collaborator

lowip commented Apr 26, 2024

Hi @bejewel-daye,

Thank you for reporting this issue. Could you provide more information regarding how you are currently integrating the SDK, specifically:

@bejewel-daye
Copy link
Author

Hi @lowip,
These are the details:

@lowip
Copy link
Collaborator

lowip commented Apr 26, 2024

Thank you for these information.

We're still investigating for a possible solution on our side. In the meantime, you should be able to resolve the issue on your own by following the workaround in this comment.

We will make sure to update this thread with any new findings.

Best,

@bejewel-daye
Copy link
Author

Hi @lowip,
Is there any update about this issue?
As May 1st is approaching, I'd like to know if there's an update schedule or any information for this issue.

Thanks,

@hokstuff
Copy link
Collaborator

hokstuff commented Apr 30, 2024

Hi @bejewel-daye,

We are attempting to reproduce the issue and have a few follow up questions for you:

  1. When you receive this error, which of the Braze packages did you import in your app (e.g. BrazeKit, BrazeUI, BrazePushStory, BrazeNotificationService, etc)?
  2. In the warning message, does it say if the issue is with your main app target or if it affects one of your app's extension targets?
  3. Have you been able to attempt the workaround described here, and does it remove those warnings during upload?

Thanks!

@bejewel-daye
Copy link
Author

Hi @hokstuff,

  1. We've been using BrazeKit, BrazeUI, BrazePushStory, BrazeNotificationService. I couldn't tell you specific package.
  2. I attached the warning message on the section of 'Additional Information'. I think It looks being with my app target.
  3. Before updating the Braze SDK to version 9.0.0, I encountered the same warning message. This is the only remaining warning message.

Thanks.

@bejewel-daye
Copy link
Author

Hi @hokstuff ,

We submitted app with Braze SDK version 7.7.0, it was passed.
Since it is not an issue at the moment for us, I think it's might be ok to close this issue.

Thank you for your supporting.

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

3 participants