Hello all,
in a previous post (https://www.b4x.com/android/forum/threads/firebase-facebook-authentication.130898/#post-828869) I noticed that the error messages using Firebase Authentication for Facebook aren't triggering an event in B4i, which was fixed by @Erel with a Facebook Authentication Library Update/Patch.
Using Firebase Apple Authentication (described here: https://www.b4x.com/android/forum/threads/sign-in-with-apple-and-firebase.116280/) , I noticed that there is almost the same situation here: if an authentication process is cancelled using Apple + Firebase Authentication (described here: https://www.b4x.com/android/forum/threads/sign-in-with-apple-and-firebase.116280/), when the process is cancelled or there is an error in the flow (ex: Error Domain=com.apple.AuthenticationServices.AuthorizationError Code=1001 "(null)" ), B4i doesn't receive any event.
If the app is waiting for an answer there is no way to notify the user or to continue the app flow reacting to the problem (showing an alert box for example).
It looks that it's a similar situation which needs an update in the class AppleAuthButton.bas correct?
Thanks!
in a previous post (https://www.b4x.com/android/forum/threads/firebase-facebook-authentication.130898/#post-828869) I noticed that the error messages using Firebase Authentication for Facebook aren't triggering an event in B4i, which was fixed by @Erel with a Facebook Authentication Library Update/Patch.
Using Firebase Apple Authentication (described here: https://www.b4x.com/android/forum/threads/sign-in-with-apple-and-firebase.116280/) , I noticed that there is almost the same situation here: if an authentication process is cancelled using Apple + Firebase Authentication (described here: https://www.b4x.com/android/forum/threads/sign-in-with-apple-and-firebase.116280/), when the process is cancelled or there is an error in the flow (ex: Error Domain=com.apple.AuthenticationServices.AuthorizationError Code=1001 "(null)" ), B4i doesn't receive any event.
If the app is waiting for an answer there is no way to notify the user or to continue the app flow reacting to the problem (showing an alert box for example).
It looks that it's a similar situation which needs an update in the class AppleAuthButton.bas correct?
Thanks!