-
Notifications
You must be signed in to change notification settings - Fork 433
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
SignInAnonymouslyAsync don't work after user been created. #16
Comments
Are you seeing this on iOS or Android? Any chance you could share an example of this, preferably by modifying our auth sample? |
Are you trying to sign in twice with the same app? |
I believed we fixed the issue of user sign-in persistence in our 1.1.0 release. If a user signs in anonymously - and they don't sign out - relaunching the application should result in the user continuing to be signed in. Could you verify? |
We finally got a chance to debug this issue and it turns out that on Android we had a problem where if an async operation completes immediately it would never call the task completion handler. The workaround for the moment - which I'm sure you're already doing - is to check to see whether the user is already signed in and not sign in if they are. We'll have a fix out in our next release. |
This should be resolved in version 1.1.1 |
auth.SignInAnonymouslyAsync().ContinueWith(HandleSigninResult);
after the first anonymous sign in new user is created in Firebase console.
when trying to signin again
HandleSigninResult
is not being called.only after signout `HandleSigninResult is called but creating new user in console.
The text was updated successfully, but these errors were encountered: