Tyler Roach

The Authenticator component does not need to take up the full screen. You can additionally add a button on the screen to sign in with Google (onClick to call `signInWithSocialWebUI`....

@sayasheng If you have any specific test devices where you can replicate this issue, I would be curious if you are able to use EncryptedSharedPreferences at all on these devices:...

@sayasheng Since you mentioned custom hardware, I'm a bit concerned the devices have a non-standard implementation of the Android KeyStore. Amplify v2 uses the latest official release of EncryptedSharedPrefrences provided...

@Uma1r We will determine our best past forward away from EncryptedSharedPreferences and internally handle the data migration when it is time to change. While no new updates are being made...

Thank you for the report. I can see how it is confusing to introduce backend capabilities under a front-end product that does not support the given feature. I will bring...

Moving Discussion question to issues.

Currently, there is no way to auto sign in a user on sign up confirmation. You must call the `signIn` api to sign a user in.

We will have to further investigate the approach. I'm not sure this custom header will be allowed by the Custom Tab as it is not on the approved list of...

I'm going to relabel this as a feature request, but after looking at this a bit more, this is working as intended. v2 requires the redirect to complete before continuing...

In attempting to figure out a workaround to allow sign out in no network conditions(such as manually clearing shared preferences file), I discovered the original report does contain a valid...