Harsh

The fix has been released.

@dcristolovean Thanks for opening the issue, I will work on reproducing this in my local environment and get back to you.

@dcristolovean What was the version you upgraded from?

Yeah.. That could definitely be possible, I don't see anything that changed from 2.45.0 to 2.45.4 that should affect encoding. Are you able to test this in the following 3...

@dcristolovean Thanks for getting back and providing these details.. I'll keep this issue open as a bug, as Amplify Swift seems to be not doing encoding correctly whereas Android does....

@BigVeila Is this an issue with only `About case Sign In Already`? Does Android also throw an invalid state and the underlying exception is `SignInException`?

It would be nice if we can write some tests around the parsing logic, just to make sure everything works as intended.