You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[google_sign_in] Implement canAccessScopes on mobile #124206
flutter/packages#3461 is adding a new API, which for now is only being implemented on web. We should add mobile implementations to avoid people hitting unimplemented errors if they try to use it on mobile. See flutter/packages#3461 (comment) for initial discussion.
@ditman Sounds like the docs should be adjusted here somewhat (since we've shipped the method name we'll need to keep that).
@stuartmorgan What adjustments do we want to make here? I can tweak the docs in any way without having to necessarily wait for the mobile implementations!
I think we probably just want to change it to say something like "has been granted access to all the given [scopes]", or "has been authorized to access all the given [scopes]"; something to make it clearer that what's being checked is whether the authorization is already done.
Im confused with the implemnentation of this method for mobile. In the changelogs, it says this is only implemented on web and not needed for mobile. Indeed, if this is called for Mobile I get an Unimplemented exception. So how does one check if these scopes have been granted on mobile? The documentation on the method mentions no such restrictions regarding implementation for mobile.
Would it be possible to get a clarification on the above question? Thanks
Reacted by Samuel Mallet , Joshua Lin, Michał Dobrzanski, Paolo Lammens, Tomer Rosenfeld and Raul Mabe
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
jmagman commentedon Apr 5, 2023
https://github.com/flutter/packages/pull/3461/files#diff-ee105b5f152d7dbf49ec11ee1e0d3628b53dd7e2d6494df8e1def0596f99f103R449-R454
Implemented in web as have all the scopes already been granted ("can access" is kind of vague imo).
stuartmorgan-g commentedon Apr 7, 2023
@ditman Sounds like the docs should be adjusted here somewhat (since we've shipped the method name we'll need to keep that).
jmagman commentedon Apr 7, 2023
@stuartmorgan should this be
dependency: androidorplatform-androidlabel? I don't think we actually need anything from the Android OS folks?stuartmorgan-g commentedon Apr 7, 2023
Thanks. I hate that label being first 😒
ditman commentedon May 26, 2023
@stuartmorgan What adjustments do we want to make here? I can tweak the docs in any way without having to necessarily wait for the mobile implementations!
stuartmorgan-g commentedon May 26, 2023
I think we probably just want to change it to say something like "has been granted access to all the given [scopes]", or "has been authorized to access all the given [scopes]"; something to make it clearer that what's being checked is whether the authorization is already done.
ditman commentedon May 26, 2023
(I've created a quick PR to update the dartdoc in a couple of places: flutter/packages#4092)
2 remaining items
muzzah commentedon Feb 13, 2024
Im confused with the implemnentation of this method for mobile. In the changelogs, it says this is only implemented on web and not needed for mobile. Indeed, if this is called for Mobile I get an Unimplemented exception. So how does one check if these scopes have been granted on mobile? The documentation on the method mentions no such restrictions regarding implementation for mobile.
Would it be possible to get a clarification on the above question? Thanks
leman7193 commentedon May 29, 2024
The current solution is to call GET API to get list scopes from the access_token and check it again. Hope the Flutter team can finish
https://www.googleapis.com/oauth2/v3/tokeninfo?access_token=....
PresKhaled commentedon Apr 9, 2025
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
github-actions commentedon Jul 8, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)