Jithin Roy

Thanks for the feedback, your use case makes sense. I have merged in your PR and will be released in the next version.

This is released in the version v1.28.2

This seems to be a bug due to the way AWSMobileClient is designed, the issue happens because we check for an existing custom auth flow confirmation - https://github.com/aws-amplify/aws-sdk-ios/blob/7987c4989e230eeba1cf13aa6a526fd3d233c3bf/AWSAuthSDK/Sources/AWSMobileClient/AWSMobileClientOperations/AWSMobileClient%2BSignIn.swift#L51 This logic...

Auth plugin should automatically refresh the token when it is expired as along as the refresh token is valid. If the refresh token is not valid, auth plugin will return...

Merging of social providers via Amplify iOS library is not supported. You might need to configure pre-signup lambda triggers and invoke AdminLinkProviderForUser.

@daniel-g-pomelo I think you are in the right path, what is the error you are seeing when you invoke `AdminLinkProviderForUser` from the presignup lambda trigger?

We welcome PR if you would like to update the SDK, the team will review it and merge them. But for this particular case it looks like the fix should...

Similar request - https://github.com/aws-amplify/amplify-ios/issues/1543

Released in [v2.0.0](https://github.com/aws-amplify/amplify-swift/releases/tag/v2.0.0)

Amplify Auth has added the feature to clear the cached credentials if the app is a fresh install. This feature was released in v2.0.0. We cannot make the private session...