Dillon Nys

Hi @hackrx - sorry you are facing this issue. It appears to be a bug in the Android library which is currently under investigation: https://github.com/aws-amplify/amplify-android/issues/1287. We will be following the...

Hi guys, unfortunately, we do not have any updates on this issue. We will be closely following the Android issue linked above, though, and will prioritize an update as soon...

Have you ever tried to use the Amplify or AWS CLI without a config file? If you do, you're gonna have a bad time lol. You're either copy/pasting creds into...

Well, so the signer is the only escape hatch we offer developers right now. In lieu of a full AWS SDK, it's the least we can do to provide proper...

@guplem - The user ID will always be the Cognito identifier. It seems there is a discrepancy around username in some cases, but the user ID will not be affected...

Also, should the banner be a different color/symbol for errors? Right now, it's the same for all messages.

Thank you @Lorenzohidalgo for all the incredible resources and insights. @zamarwells @spbarber - do you feel like you have enough info to mitigate the issue your seeing with the list...

Hi @flodaniel - sorry you are experiencing this issue. Changing the following: ```js await adminLinkUserAccounts({ username: cognitoUsername, userPoolId, providerName, providerUserId, }); ``` to this: ```js await adminLinkUserAccounts({ username: cognitoUsername, userPoolId,...

Ah, sorry about that. I missed that difference between the two IDs. I will keep digging!

I found a couple mentions of the same issue: - https://github.com/aws-amplify/amplify-js/issues/5104 - https://github.com/aws-amplify/amplify-js/issues/9976 It looks like many people have implemented a front-end check to catch the error thrown and retry...