Hello,

I'm only a little familiar with Power Apps. Is your app a mobile app or a web app?

This link lists out the alternatives.

The primary recommended alternative for the Google Fit REST API is Health Connect.

If your app does not work on Android mobile devices, you can also consider the Fitbit Web API.

Thanks for confirming this, really helpful.

You raise good questions here, and I think at the moment it may be a challenge at the least to identify that third time. Equally, we need to explore guidance should it be necessary for the user to be directed to the HC app.

We're actively exploring this topic, and I hope you'll understand if it takes us a little while to iterate on this behaviour. Will update this bug at that time.

Many thanks for the activity on this, glad to help! We're looking forward for updates.

Usually with permissions we can find out if the user denied us the permission too many times and thus can show some kind of dialog and/or jump into the settings of the app in question. I would do the same here (and jump to the health connect app) but I can't find out in advance whether a call to requestPermissions.launch(PERMISSIONS) will result in the permission dialog being opened or not (and my callback being triggered right away).

The tipp from here:

For now, if you want to determine whether you're app has requested a particular permission before, you'll need to keep track of that within your app.

is not viable because one would need to keep track of that between installations of the app, because if an app is deinstalled and then reinstalled the call to requestPermissions.launch(PERMISSIONS) still does not open up the HC app once the permission sheet was cancelled twice or more.

I know it was marked as Obsolete, but I see that my question is relative to the discussion from this thread and I don't want to spam with duplicates.

You previously mentioned the general logic of internal permissions handling:

As background to help as to why, here's how requesting permissions currently works: When the Permissions UI is launched from your app, if you click cancel, then a counter is incremented for each of the permissions that you requested. If that counter reaches a limit (currently 2), then subsequent requests to launch the Permissions UI for that permission will not work, and you'll just get the empty permissions result.

Do you know whether this approach was changed during Android 14 upgrade?

For Android 13 and lower - clicking Cancel button twice results in avoiding all the subsequent runs (until the permissions are being reset manually). But it does not increment the counter when I give just a few permissions (like, 3 out of 10). I can call this request as much as I want granting at least 1 permission and clicking Allow, not Cancel.

For Android 14 - I see the same behavior for Cancel treatment. But now it seems that clicking Allow with just a portion of permissions also increments the counter. I can only perform 2 requests with 1 permission in each, with all the following requests being skipped.

Tested on Pixel 6.