Harsh

Please re-open if this is still an issue. Closing the issue due to inactivity.

This issue has been tackled in Amplify 2.x. Can you please try to update to the latest version of Amplify and validate if its still an issue.

@mbernson The team is actively working on unifying `getCurrentUser` API behaviour on all platforms. We will post an update on the ticket after the change has been implemented. Meanwhile, I...

[Amplify 2.0](https://github.com/aws-amplify/amplify-swift/releases/tag/v2.0.0) has been released which normalizes what values are returned in the `getCurrentUser` API. The API will now use the `accessToken` to determine the `userId` and `username` values. Adding...

@knellr I want to get some information on a few things * Does this only happen to users who have updated to iOS 16 or the new iPhone 14? And...

@mauronate There was a recent fix released around this in 2.27.12. Can you please use the latest version and verify if this still happens.

@klein-thibault The latest SDK release has a potential fix for the issue. Could you please give it a try and let us know if you are still facing the issue?...

Closing the issue. Please reopen if the issue still persists

@rtnlsltn Can you please provide an update?

@hrvoje0099 This feels like that you succeeded to update your email using the API. `codeDeliveryDetailsList` will only have a value if its required to confirm an attribute. In your case...