-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify.Auth.signInWithSocialWebUI logs in but MobileClient is not on version 2.14.6 #2713
Comments
Hi @RoustamManookian Amplify Android v2 and the AWS Android SDK are not compatible with each other. While Amplify v1 was build on top the AWS Android SDK, Amplify v2 uses the AWS Kotlin SDK under the hood. Please look into using the Amplify v2 Storage category for s3 operations. If Amplify Storage does not fit all of your use cases, you can use the escape hatch to eject into the Kotlin SDK: https://docs.amplify.aws/android/build-a-backend/storage/sdk/. The IoT library from the AWS Android SDK can still continue to be used by passing a custom credentials provider that uses Amplify v2 to fetch credentials. Please see this example: #2400 (comment) |
Thank you @tylerjroach . I deleted 'com.amazonaws:aws-android-sdk-mobile-client:2.73.0' dependancy from gradle |
Great! Were you able to migrate storage? If not, you can also pass your credentials provider into TransferUtility.
|
This issue is now closed. Comments on closed issues are hard for our team to see. |
Before opening, please confirm:
Language and Async Model
Kotlin
Amplify Categories
Authentication
Gradle script dependencies
Environment information
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
I updated the Amplify framework version to 2
Before everything worked well, now the Amplify.Auth.signInWithSocialWebUI is completing with success but the MobileClient is not connecting and thus I can't use any AWS services like IOT or S3.
Reproduction steps (if applicable)
No response
Code Snippet
Log output
amplifyconfiguration.json
No response
GraphQL Schema
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: