Closed TomCorvus closed 2 months ago
Seems that i have to add a PrivacyInfo.xcprivacy file in the extension. Not sure how for now.
But we are all waiting for the new expo.ios.privacyManifests config in SDK 50 đ
@achorein any updates? is there a PR or not really?
the privacy info will be handle in the next expo-config-plugins
version (see CHANGELOG) => wait&see
file PrivacyInfo.xcprivacy
will look like this :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>NSPrivacyAccessedAPITypes</key>
<array>
<dict>
<key>NSPrivacyAccessedAPIType</key>
<string>NSPrivacyAccessedAPICategoryUserDefaults</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>CA92.1</string>
</array>
</dict>
</array>
<key>NSPrivacyCollectedDataTypes</key>
<array/>
<key>NSPrivacyTracking</key>
<false/>
</dict>
</plist>
just received the email today, so has it been handled, I do not any idea on where should I create this privacy file and how to handle the API and information
the PrivacyInfo.xcprivacy
has been added into the ios ShareExtension
in v1.4.1 and v0.6.1.
I have tested that the warning has been removed from the apple email in a production build.
don't hesitate to reopen if needed.
Thanks @achorein, I will try the new version and told you if this message disappears on my side.
đ
Apple seems to need a privacy manifest to provide reasons why APIs are used in app. We got a mail about it before our latest app submission.
I know that there are some discussion about this, especially on Expo repo https://github.com/expo/expo/issues/27796