problem with IOS Facebook federated identify when user cancel instead of confirm the signout

[ericowhadi]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have tried disabling all browser extensions or using a different browser
• I have tried deleting the node_modules folder and reinstalling my dependencies
• I have read the guide for submitting bug reports.

On which framework/platform are you having an issue?

React Native

Which UI component?

Authenticator

How is your app built?

react-native start

What browsers are you seeing the problem on?

iOS (React Native)

Which region are you seeing the problem in?

No response

Please describe your bug.

when login using facebook federated identity to login, then click on signout button, on IOS, get prompted with something like:
"myapp" wants to use "amazoncognito" to sign in (note the confusing message because I am signin out, not signin in).
Now if I hit cancel instead of Continue, the Authenticator is in bogus state:
The ui will display the login page, but if you click on Sign In With Facebook, you will get a "Possible unhandled promise rejection. UserAlreadyAuthenticatedException: There is already a signed in user.
The only way I found to get out of that state is to restart the IOS simulator, then signoff and now correctly hit continue instead of cancel when prompted with the message.

What's the expected behaviour?

ideally, the code should detect this situation and force logout

Help us reproduce the bug!

when login using facebook federated identity to login, then click on signout button, on IOS, get prompted with something like:
"myapp" wants to use "amazoncognito" to sign in (note the confusing message because I am signin out, not signin in).
Now if I hit cancel instead of Continue, the Authenticator is in bogus state:
The ui will display the login page, but if you click on Sign In With Facebook, you will get a "Possible unhandled promise rejection. UserAlreadyAuthenticatedException: There is already a signed in user.
The only way I found to get out of that state is to restart the IOS simulator, then signoff and now correctly hit continue instead of cancel when prompted with the message.

Code Snippet

// Put your code below this line.

Console log output

No response

Additional information and screenshots

No response

[calebpollman]

@ericowhadi Was able to reproduce the sign out behavior on our end when using the signOut function returned from useAuthenticator. Until a fix is available, a workaround is available by importing signOut directly from aws-amplify/auth:

import { signOut } from 'aws-amplify/auth';'