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 Properties] Privacy Manifest, unable to generate privacy report #1655

Closed
RoblesJ opened this issue Feb 5, 2024 · 1 comment · Fixed by #1656
Closed

[Missing Properties] Privacy Manifest, unable to generate privacy report #1655

RoblesJ opened this issue Feb 5, 2024 · 1 comment · Fixed by #1656
Assignees
Labels
bug Something isn't working

Comments

@RoblesJ
Copy link

RoblesJ commented Feb 5, 2024

Privacy Report missing properties

We are working on setting up our modules privacy manifests (reference on issue: #1406), when we attempted to use your privacy manifest introduced on v 2.7.0 we found it is missing the type of data it should declare for the usage of UserDefaults

Screenshot 2024-02-05 at 15 52 10

I'll provide an example of a working manifest for reference.
image

My conclusion would be that while you are manifesting you use user defaults you are not defining the reason of doing so.
Here is an example with a working manifest i attempted on a fork
Screenshot 2024-02-05 at 15 57 18

@maciejburda maciejburda added the bug Something isn't working label Feb 6, 2024
@maxep
Copy link
Member

maxep commented Feb 6, 2024

Hey @RoblesJ 👋 Thank you for the report.

Indeed, our privacy manifest do not declare NSPrivacyCollectedDataTypes because those strongly depend on your configuration and usage. It appears that missing this key will prevent for generating the Privacy Report from the app archive.
Adding an empty array seems to fix the issue:

<key>NSPrivacyCollectedDataTypes</key>
<array></array>

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

Successfully merging a pull request may close this issue.

3 participants