Coder Social home page Coder Social logo

Comments (3)

robertherber avatar robertherber commented on May 28, 2024

I'm fairly certain what you're describing is working as intended (by Apple that is). A few things that might help:

  • Apple only lets apps present the dialog once per type of data. So it's probably a good idea to prepare the user before presenting the dialog.
  • There is no way to tell if a user denied the app access to reading data - you will simply receive no data.
  • isHealthDataAvailable is for indicating whether the device supports health data, as per Apples docs. I guess it makes most sense to call this before anything else.

from react-native-healthkit.

pratikdhody avatar pratikdhody commented on May 28, 2024

I'm fairly certain what you're describing is working as intended (by Apple that is). A few things that might help:

  • Apple only lets apps present the dialog once per type of data. So it's probably a good idea to prepare the user before presenting the dialog.
  • There is no way to tell if a user denied the app access to reading data - you will simply receive no data.
  • isHealthDataAvailable is for indicating whether the device supports health data, as per Apples docs

Thanks @robertherber. Regardless of the scenario I mentioned above, I'm also finding also that if the user granted access in current version of out app and then if we then released a newer version of the app then HealthKit.authorizationStatusFor(HKCategoryTypeIdentifier.sleepAnalysis) is false and so when we try and present the modal again, the modal doesn't show.

The only workaround that works is that we need to ask users to uninstall the app and then re-open and then the modal appears.

from react-native-healthkit.

robertherber avatar robertherber commented on May 28, 2024

@pratikdhody Yes, this is the same behaviour for any iOS app regarding showing the permission UI. You can only show it once per type of health data, that's it.

As for the authorizationStatusFor there is some discussion going on in #61 on whether it's reporting the correct value currently. I haven't had time to dig into it yet.

I'd recommend using getRequestStatusForAuthorization instead since it directly indicates whether you can/should ask the user for permissions (shouldRequest) or if you should just go ahead (i.e. you have already presented the UI). This is all that is exposed by Apple, there is no way to know what the user responded.

from react-native-healthkit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.