-
Notifications
You must be signed in to change notification settings - Fork 130
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
provider.SignInWithOAuth() throws exception. #3
Comments
Can you try the latest version of the package (v2.0.1)? In case of an error it throws a FirebaseAuthException which should contain all information you should need to debug it (target url, post data and most imporantly responseData, which should contain the reason for the error). |
Thank you for the update. I get "invalid key" as The first option gets the idtoken from Auth0 and creates the fireabse token with firebaseAuthentication
///////////////////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////////////////////
I've also tried generating the access token using I've checked all loose ends. Don't know what is causing this. Maybe I'm not using the tokens or keys correctly. |
I never worked with Auth0 so I'm not sure what kind of tokens it generates. Check out the samples (I just pushed them), they may help. |
I have similar problem.
|
I think the problem is with the Legacy Firebase App, I created another one and it does works for me. |
Can I still create "legacy" app in the current Firebase console? |
Yes I can still create using my current Firebase legacy account, not sure if you can still create new account. It's on https://www.firebase.com/ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing the issue due to inactivity. Feel free to re-open |
Exception: "Response status code does not indicate success: 400" when I call
SignInWithOAuth
var auth = await provider.SignInWithOAuthAsync(FirebaseAuthType.Facebook, facebookAccessToken);
The
facebookAccessToken
is generated properly and I use Firebase Browser APIKey forFirebaseConfig
UWP 10.0
Stack trace:
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at Firebase.Auth.FirebaseAuthProvider.<SignInWithPostContentAsync>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable``1.ConfiguredTaskAwaiter.GetResult() at Firebase.Auth.FirebaseAuthProvider.<SignInWithOAuthAsync>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter``1.GetResult() at simple_social_media.MainPage.<mainlogin_Click>d__1.MoveNext()
Could the problem be at my end?
The text was updated successfully, but these errors were encountered: