You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On May 1st, Apple will require privacy manifests in all new app store submissions (source).
Feature Description
It appears Cordova has not yet officially added a way for plugins to handle this (source), but the latest cordova-ios release does provide support for an app-level privacy manifest (source).
For the time being, it would be helpful if this plugin could provide a privacy manifest file that consumers could manually cobble together for now, adding full support in the future when Cordova provides a way to do so.
For this plugin, we need two things in the privacy manifest:
API usage
NSPrivacyCollectedDataTypeDeviceID in the NSPrivacyCollectedDataTypes array (source).
Alternatives or Workarounds
I can reasonably determine what needs to be included in the privacy manifest so that others can follow suit and manually add these entries to their manifest.
Which is found in the uniqueAppInstanceIdentifier method which is called in deviceProperties which is used in getDeviceInfo.
The usage would seem to possibly fall under two categories:
CA92.1
Declare this reason to access user defaults to read and write information that is only accessible to the app itself.
This reason does not permit reading information that was written by other apps or the system, or writing information that can be accessed by other apps.
For NSPrivacyCollectedDataTypeDeviceID consumers of this plugin are probably going to need to provide this themselves. To that end, it may be useful to add an argument to getDeviceInfo so that uuid can be excluded. That way plugin consumers who do not wish to include NSPrivacyCollectedDataTypeDeviceID in their privacy manifest do not need to.
The text was updated successfully, but these errors were encountered:
Feature Request
Motivation Behind Feature
On May 1st, Apple will require privacy manifests in all new app store submissions (source).
Feature Description
It appears Cordova has not yet officially added a way for plugins to handle this (source), but the latest cordova-ios release does provide support for an app-level privacy manifest (source).
For the time being, it would be helpful if this plugin could provide a privacy manifest file that consumers could manually cobble together for now, adding full support in the future when Cordova provides a way to do so.
For this plugin, we need two things in the privacy manifest:
NSPrivacyCollectedDataTypeDeviceID
in theNSPrivacyCollectedDataTypes
array (source).Alternatives or Workarounds
I can reasonably determine what needs to be included in the privacy manifest so that others can follow suit and manually add these entries to their manifest.
Grepping the plugin's iOS source files
grep -r -E 'NSURLVolumeAvailableCapacityKey|NSURLVolumeAvailableCapacityForImportantUsageKey|NSURLVolumeAvailableCapacityForOpportunisticUsageKey|NSURLVolumeTotalCapacityKey|NSFileSystemFreeSize|NSFileSystemSize|statfs|statvfs|fstatfs|fstatvfs|getattrlist|fgetattrlist|getattrlistat|activeInputModes|NSUserDefaults'
Yields:
Which is found in the
uniqueAppInstanceIdentifier
method which is called indeviceProperties
which is used ingetDeviceInfo
.The usage would seem to possibly fall under two categories:
NSPrivacyCollectedDataTypeDeviceID
consumers of this plugin are probably going to need to provide this themselves. To that end, it may be useful to add an argument togetDeviceInfo
so thatuuid
can be excluded. That way plugin consumers who do not wish to includeNSPrivacyCollectedDataTypeDeviceID
in their privacy manifest do not need to.The text was updated successfully, but these errors were encountered: