-
Notifications
You must be signed in to change notification settings - Fork 4
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
Package.swift copy Privacy Manifest Resource file #53
Comments
Hello, Even I am able to reproduce this issue, without Note: Tried by editing Package.swift file locally as below by including
Can you please look into this and help here Thank you |
@frankus Could we get an update on this when you're free. Thanks! |
@FONickReichard I'll get this prioritized. We seem to have a bit of a gap in our issue ingestion system where this has gotten lost in the shuffle. |
Thank you for the update @frankus |
Hey @frankus , Friendly check in. Is there an eta for a new version? Thanks. |
Just released as part of the v6.6.0. (We're aware of an issue with displaying surveys in this release (only) due to an API rollout taking longer than the SDK release. On the off chance you run into it should be fixed within 24 hours). |
I believe the same would apply to the podspec... thank you. |
Still broken... The current Package.swift file has |
That's correct, it's also missing from the podspec, it must be specified as a resource. Specifically it's missing from this line:
which should be
|
Environment Details:
Version: 6.5.0
Dependency Management: SPM
Relates To: Privacy Manifest (#529) commit: 3daaa10
Hello,
Based on the following path structure: Sources/ApptentiveKit/Resources/PrivacyInfo.xcprivacy
I am wondering if the PrivacyInfo.xcprivacy file needs to be copied in the Package.swift file.
Ex:
Correct me if I'm wrong, I believe the PrivacyInfo.xcprivacy file should be included in the clients apps' bundle so that the privacy report can be generated after archiving a build.
Any feedback would be great.
Thank you
The text was updated successfully, but these errors were encountered: