If you don't verify your scopes, google fit's OAuth page is stuck in loading. you may not notice when your app is in testing but if you are in production, that's the case pretty much.
I spent 2 months verifying fitness.activity.read scope and that's the only thing I need for my app. Currently, this library also adds fitness.body.read request on the getFitnessOptions method. I removed that line on my fork and solved the problem.
feature-request is this:
customize permissions based on what we need, so we don't ask google for extra permissions and stuck in loading. currently, pub.dev/health package allows you to do that.
brief info about the issue I've faced:
If you don't verify your scopes, google fit's OAuth page is stuck in loading. you may not notice when your app is in testing but if you are in production, that's the case pretty much. I spent 2 months verifying fitness.activity.read scope and that's the only thing I need for my app. Currently, this library also adds fitness.body.read request on the getFitnessOptions method. I removed that line on my fork and solved the problem.
feature-request is this:
customize permissions based on what we need, so we don't ask google for extra permissions and stuck in loading. currently, pub.dev/health package allows you to do that.