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

feat: add docs for the new iOS 17+ privacy requirements #215

Merged
merged 1 commit into from Mar 28, 2024

Conversation

hansemannn
Copy link
Contributor

@hansemannn hansemannn commented Mar 17, 2024

Details for the new iOS 17+ privacy requirements. More changes here.

Copy link
Contributor

@m1ga m1ga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hansemannn
Copy link
Contributor Author

@m1ga Have you also been able to submit a build?

@m1ga
Copy link
Contributor

m1ga commented Mar 19, 2024

no, I've only checked the text 😄 didn't do any tests with an app. I can test a Testflight build tomorrow to see if I get the warnings

@m1ga
Copy link
Contributor

m1ga commented Mar 20, 2024

just pushed a 12.3.0 app (without any changes or privacy file) to the testflight and I don't get the warnings 🤷 So I can't test it

@hansemannn
Copy link
Contributor Author

Same here currently with our main app that reproduced it last week. Maybe Apple only sends email for some devs so far to reduce noise. We can keep it open until it get's more concrete, as Titanium devs can already place the file to be sure.

@m1ga
Copy link
Contributor

m1ga commented Mar 28, 2024

as there are more people asking for this now: should we merge the docs so I can link them to the article instead of pointing to this PR all the time?

@hansemannn hansemannn merged commit 7b96977 into main Mar 28, 2024
2 checks passed
@m1ga
Copy link
Contributor

m1ga commented Mar 28, 2024

Thanks 👍

Looks like it doesn't like the link to the file: https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/PrivacyInfo.xcprivacy

Should we add inlince code to display the file as a workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants