-
Notifications
You must be signed in to change notification settings 8000 - Fork 28.5k
[google_sign_in] Update GoogleSignIn dependency to 6.2 #86436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Wow you beat me by a minute. More details in #86435 |
Bumping to a P3 to prevent users from having to do the same workaround from flutter/plugins#4128. |
GoogleSignIn 6.0 doesn't allow scopes to be requested at the same time as sign in. That means we need to sign in, then request the scopes previously specified during initialization. So sign in happens, then immediately there's a separate permissions flow: Then it asks for permission AGAIN: I'm not sure this is an acceptable user experience. What do you think, @stuartmorgan? |
It doesn't seem great. Maybe we should give that issue a little while to see how things proceed; if it's going to be changed we can wait, and if not maybe we take a look at whether we need a significant breaking change to our API to itself be based on incremental auth? |
\cc @petea |
I'm not sure on the timeline of this happening but this issue was quite a headache for me to track down. It'd be nice if there were a note in the |
@Nolence #85713 is where we're tracking that the |
Ah, that makes sense. Thanks for the clarification |
Just as FYI, even though #85713 fixed the build problems (thank you @jmagman !) this is still tripping up people who in a foolhardy fit of optimism stopped running the Simulator under Rosetta, then later started using Firebase Auth (which makes an app have a transitive dependency on Would there be any thoughts on when at least ver 5 could be adopted by the plugin to get support for arm64 simulators? |
Almost 1 year since this issue was open, what's the hold up? |
See the discussion above, as well as this comment about the upstream issue. |
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 |
We're currently using 5.0; 6.0 was just released. This isn't pressing, but it would be good to handle the API updates relatively soon so that we're not stuck dealing with that suddenly if there's a bug fix we need.
(6.0 also adds SPM support, which would be relevant for those investigations.)
/cc @jmagman
The text was updated successfully, but these errors were encountered: