Damian Phillips-King
Results
2
comments of
Damian Phillips-King
Also ran into this issue using 1.6.0 and I can confirm that downgrading until the issue has been resolved is an acceptable workaround.
For anyone else running into this issue, all I had to do is add the following Environment Variables in AWS Amplify console. AMPLIFY_USERPOOL_ID AMPLIFY_WEBCLIENT_ID AMPLIFY_NATIVECLIENT_ID I was receiving the same...