Closed marked-one closed 1 year ago
What kind of social login are you talking about? Exception handling is different for each social login API. It's not my control.
Any native view (Google, Facebook, Apple) behaves the same way here.
Some update: in case of Google, if I try to login with Google again (after the native dialog disappears), error 12502 is returned instead of the login dialog being opened. And if I try one more time - it successfully opens the dialog again. Update: next day, error 12502 is no more showing up for Google login, so all the logins work as described in initial post.
To me this issue is related to Android killing activities that aren't displayed.
The best choice here would be to restore previously opened activities in native code. Which will include reopening any third-party dialogs, as if they were never closed. From what I understand this is normal Android behaviour.
What did you do?
What did you expect?
either native view doesn't disappear (preferred) or login process returns an error
What happened actually?
native view disappears and login process never returns
Your environment?
Screenshots or Log
not applicable