Skip to content

[BUG] Incorrect value inside the Privacy manifest file #538

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

Closed
1 task done
Faber92 opened this issue Jan 11, 2024 · 2 comments
Closed
1 task done

[BUG] Incorrect value inside the Privacy manifest file #538

Faber92 opened this issue Jan 11, 2024 · 2 comments
Assignees
Labels
acknowledged bug Something isn't working

Comments

@Faber92
Copy link

Faber92 commented Jan 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

SDK Version

3.10.4

iOS Version

Any

Current Behavior

The used value To store configuration and event data temporarily for NSPrivacyAccessedAPITypeReasons is not compliant with the requirements by Apple

<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>To store configuration and event data temporarily</string>
</array>

Expected Behavior

I expect to see one of the following values as listed here:

  • CA92.1
  • 1C8F.1
  • C56D.1
  • AC6B.1

Steps To Reproduce

None

Link

No response

Logs / Stacktraces

No response

Severity

Minor issue

Workaround/Solution

No response

Recent Change

No response

Conflicts

No response

@Faber92 Faber92 added the bug Something isn't working label Jan 11, 2024
@Faber92 Faber92 changed the title [BUG] <title> [BUG] Incorrect value inside the Privacy manifest file Jan 11, 2024
@muzahidul-opti
Copy link
Contributor

Hi @Faber92 thanks for reporting the issue. Will get back to you.

@muzahidul-opti
Copy link
Contributor

@Faber92 Issue is fixed in our latest release, thank you for your contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledged bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants