initialize HealthKit. this will show the HealthKit permissions prompt for any read/write permissions set in the required `options` object.
initialize HealthKit. this will show the HealthKit permissions prompt for any read/write permissions set in the required `options` object.
due to Apple's privacy model if an app user has previously denied a specific permission then they can not be prompted again for that same permission. the app user would have to go into the Apple Health app and grant the permission to your react-native under *sources* tab.
due to Apple's privacy model if an app user has previously denied a specific permission then they can not be prompted again for that same permission. the app user would have to go into the Apple Health app and grant the permission to your react-native app under *sources* tab.
for any data that is read from HealthKit the status/error is the same for both. this privacy restriction results in having no knowledge of whether the permission was denied (make sure it's added to the permissions options object), or the data for the specific request was nil (ex. no steps recorded today)
for any data that is read from HealthKit the status/error is the same for both. this privacy restriction results in having no knowledge of whether the permission was denied (make sure it's added to the permissions options object), or the data for the specific request was nil (ex. no steps recorded today)
...
@@ -175,7 +173,7 @@ if new read/write permissions are added to the options object then the app user
...
@@ -175,7 +173,7 @@ if new read/write permissions are added to the options object then the app user
`initHealthKit` requires an options object with HealthKit permission settings
`initHealthKit` requires an options object with HealthKit permission settings