Sam
Sam
Running into the same problem, thanks to @benjeater 's work around of doing a pull first, I got this working on automatic branch deployments with the following added step in...
+1. I was experiencing this in the Amplify build console. Locking the version to 7.6.8 has resolved it temporarily.
I got this to work with the following command, and it successfully reconnected (using the aws cli help commands was helpful): `aws amplify update-app --app-id --repository
+1 on this please. I have a bunch of random environment names due to setting up the branch pattern naming with a '/' character and Amplify deciding to generate random...