This is a similar problem to the issue "Authorization with Migration to Google Accounts" and has come up since Google accounts are (seemingly) now the only way of creating new Fitbit user accounts.
My research is currently using a managed set of GSuite accounts for Fitbit. When using one of these accounts to attempt to login to Fitbit, I get the error "Can’t use Fitbit with this Google Account. This could be because you’re using a Workspace account or because your account is supervised." We already have hundreds of participants with associated Fitbit accounts and plans for hundreds and eventually thousands more. Managing these is challenging and the GSuite solution at least puts all of the Google accounts in one place. Is there a plan to support managed accounts, or a suggested workaround that suits our workflow?
Additionally, Google sign-in was previously explicitly advised against when establishing OAuth keys for third party applications. Can you confirm that this is no longer the case?
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Best Answer