Acquired the identical notification from Apple:
ITMS-91053: Lacking API declaration – Your app’s code within the “ ” file references a number of APIs that require causes, together with the next API classes: NSPrivacyAccessedAPICategorySystemBootTime. Whereas no motion is required right now…
ITMS-91053: Lacking API declaration – Your app’s code within the “ ” file references a number of APIs that require causes, together with the next API classes: NSPrivacyAccessedAPICategoryUserDefaults. Whereas no motion is required right now…
Added PrivacyInfo.xcprivacy file as in video https://developer.apple.com/movies/play/wwdc2023/10060 with following content material:
<?xml model="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist model="1.0">
<dict>
<key>NSPrivacyAccessedAPITypes</key>
<array>
<dict>
<key>NSPrivacyAccessedAPIType</key>
<string>NSPrivacyAccessedAPICategoryUserDefaults</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>CA92.1</string>
</array>
</dict>
<dict>
<key>NSPrivacyAccessedAPIType</key>
<string>NSPrivacyAccessedAPICategorySystemBootTime</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>35F9.1</string>
</array>
</dict>
</array>
</dict>
</plist>
And do not forget to set Goal Membership for this file to your major bundle. In any other case you’re going to get the identical consequence.
After this I did not get warning from Apple.
P.S. Yet one more essential word. If extensions are used within the challenge, the e-mail from Apple will in all probability embrace these extensions as properly. On this case, the separate PrivacyInfo.xcprivacy recordsdata with the mandatory causes have to be added to the desired extensions as properly. Accordingly, you will need to set the Goal Membership for PrivacyInfo.xcprivacy relying on the extension required.
