Open liuchong-94 opened 2 years ago
Hi @liuchong-94,
Thanks for reporting this. While I try to replicate this issue, could you confirm if a similar behavior persists using the latest version of the SDK (8.10.1)?
Hi @liuchong-94,
Thanks for reporting this. While I try to replicate this issue, could you confirm if a similar behavior persists using the latest version of the SDK (8.10.1)?
Thank you for your reply. I tested 8.10.1 and the same error occurred
Hi @liuchong-94,
I haven't been able to replicate your issue yet because I'm facing an error when using the code you provided in Step 2. Could you confirm if the exact code returned no error on your end? It would be helpful if you provide a minimal, reproducible example so that it can be used as a baseline for troubleshooting.
Hi, @paulinon , you can download the sample project here. https://drive.google.com/file/d/1girOChQyZrIXuqRR9MEDXcxI0WQuKhTS/view?usp=sharing
There are two ways to use it.
Hi @liuchong-94,
It appears that I don't have access to your sample project. I recommend that you upload this to a GitHub repository then add me as a collaborator.
Hi @paulinon. I upload project to this repository: https://github.com/liuchong-94/firebaseAuthTest
Thanks for this, @liuchong-94. I was able to replicate the behavior, and I can see how this is a bug. If a user accidentally tapped home while they're in the middle of signing up with the Apple window, they'll return to their app with the Apple window gone, and the app still thinks that the authentication process is ongoing even though the user can't proceed on their end.
That being said, I've relayed my findings to the team. You may refer to this thread for updates. I'll be marking this as a bug for now
Thanks for this, @liuchong-94. I was able to replicate the behavior, and I can see how this is a bug. If a user accidentally tapped home while they're in the middle of signing up with the Apple window, they'll return to their app with the Apple window gone, and the app still thinks that the authentication process is ongoing even though the user can't proceed on their end.
That being said, I've relayed my findings to the team. You may refer to this thread for updates. I'll be marking this as a bug for now
I encountered this problem and found the real trigger process, The details are:
When calling the Web login page, FireBase should open an activity, After the FireBase activity is enabled and before the web page is opened, if you go back, This will cause FireBase's activities to fail to listen to the Web's exit monitoring, As a result, FireBase's logic can't handle the listening logic after the Web page exits, and it is always logged in
I guess this problem can be solved as long as the rollback function is prohibited in the middle process, But the process belongs to Firebase, and we can't modify it
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
I use this example to log in apple id on Android.
Firebase.Auth.FederatedOAuthProviderData providerData =new Firebase.Auth.FederatedOAuthProviderData(); providerData.ProviderId = "apple.com"; providerData.Scopes = new List();
providerData.Scopes.Add("email");
providerData.Scopes.Add("name");
Firebase.Auth.FederatedOAuthProvider provider =
new Firebase.Auth.FederatedOAuthProvider();
provider.SetProviderData(providerData);
auth.SignInWithProviderAsync(provider).ContinueOnMainThread(task => {
if (task.IsCanceled) {
Debug.LogError("SignInWithProviderAsync was canceled.");
return;
}
if (task.IsFaulted) {
Debug.LogError("SignInWithProviderAsync encountered an error: " +
task.Exception);
return;
}
});
Everything works fine on Android. But when I pull up the authorization page and click the home button, I go back to my game from the desktop.Then when I call SignInWithProviderAsync again in the same way, I get an error :
SignInWithProviderAsync encountered an error: System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> Firebase.FirebaseException: A headful operation is already in progress. Please wait for that to finish. --- End of inner exception stack trace --- --- End of inner exception stack trace --- ---> (Inner Exception #0) System.AggregateException: One or more errors occurred. ---> Firebase.FirebaseException: A headful operation is already in progress. Please wait for that to finish. --- End of inner exception stack trace --- ---> (Inner Exception #0) Firebase.FirebaseException: A headful operation is already in progress. Please wait for that to finish.<--- <--- UnityEngine.Logger:Log(LogType, Object) MobileLoginService:b__13_0(TaskcAnonStorey9:<>m0()
System.Func
1) System.Action
1:Invoke(T) Firebase.Extensions.1:Invoke() Firebase.<RunAsync>c__AnonStorey1
1:<>m__0() System.Action:Invoke()(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)? Yes. What's the issue repro rate? (eg 100%, 1/5 etc) 100%
What happened? How can we make the problem occur? This could be a description, log/console output, etc.
Download and configure this github project to make it run
Modify the SignInWithProvider function: protected void SignInWithProvider(string providerId) { var providerData = new Firebase.Auth.FederatedOAuthProviderData(); providerData.ProviderId = "apple.com"; providerData.Scopes = new List() { "name", "email" };
}); }
Click SignInWith | Miscrosoft, open the browser and click the home button to return to the Android desktop, click app to return to the application, and click SignInWith | Miscrosoft again.
If you have a downloadable sample project that reproduces the bug you're reporting, you will likely receive a faster response on your issue.
Relevant Code: