Tariq Mahamid

Hey @josefaidt! `usernameAttributes` was previously also set to `email` and `phone_number`

They were previously set as one attribute as well, this remains unchanged: ``` "usernameAttributes": [ "email, phone_number" ], ```

Yes of course, and just to be clear, we are talking about the **.../amplify/backend/auth/_resourceName_/parameters.json** before and **.../amplify/backend/auth/_resourceName_/build/parameters.json** after correct?

Here are the files (Took out the name attributes): `parameters.json` before: ``` { ..., "allowUnauthenticatedIdentities": false, "autoVerifiedAttributes": ["email"], "mfaConfiguration": "OFF", "mfaTypes": ["SMS Text Message"], "smsAuthenticationMessage": "Your authentication code is {####}",...

Hey @akshbhu, thank you so much for the suggestion! After removing the `usernameCaseSensitive` flag from the cli-inputs.json, I used amplify push successfully! However, why was I getting this error in...

Hey @akshbhu Are you referring to this checkbox in the attributes section of general settings, this checkbox was unchecked before and after the push? 

Hello @josefaidt, after checking Cloud Watch, I found this Log Group that did not see before I added Sign in With Apple: Upon checking the stream, I found this: I...

Hello @ykethan, thanks for following up! I inputted the credentials again and I am still facing the same issue. I just find it very strange that there is no error...

Hello @ykethan, sorry for the delay. I removed all of the existing auth providers that I had and ensured with a file checker that the providers were being added correctly....

Hello @josefaidt, are you talking about username attributes? If so then I set up the auth resource with email and phone number (user can choose one) from what I can...