Harsh

@kparichan Would you be able to open another issue with the relevant details and verbose logs. With the brief description you've give us, your issue seems to be something else,...

@LarissaKim Thanks for creating the issue. Our team will look into your questions and provide and update as soon as we can. Appreciate your patience.

@LarissaKim Answers to your original questions first > The Amplify.Categories.Auth.AuthCategory+ClientBehavior interface seems to indicate that signInWithWebUI is supported on visionOS. However, the [docs](https://docs.amplify.aws/swift/build-a-backend/auth/sign-in-with-web-ui/) state that "Social sign-in (OAuth) functionality is...

From what you have described, I don't see anything that poses red flags. You can read more about our federation to Identity Pool API's [here](https://docs.amplify.aws/swift/build-a-backend/auth/advanced-workflows/#identity-pool-federation).

Quick update: The fix has been merged in `amplify-swift` and is awaiting `amplify-cli` teams review.

The issue has been released. Please update amplify cli using `amplify upgrade`.

@Krishna-Dockare Would you be able to share your amplify configuration which has the credentials provider info. Your config should have something like: ``` "CredentialsProvider": { "CognitoIdentity": { "Default": { "PoolId":...

If the configuration doesn't have the credentials provider, unfortunately getting identity id and AWSCredentials won't work.

Would you be able to share the following in details? 1. Dev environment amplify configuration json file redacted all the sensitive info. 2. Share verbose logs from sign in to...

@Krishna-Dockare I see that both dev and prod returns the same result for Authorization. i.e. ` "AuthorizationState.sessionEstablished" = userPoolOnly;`. So if you try to do a `fetchAuthSession` on either dev...