Failed to pull the backend CLI 12.12.0 about amplify-cli HOT 5 OPEN

Update. I manage to set cli version to 12.11.1 (there was still a _LIVE_UPDATES entry for my branch which overwrite the global build setting). I think it is very odd that the console creates environments which duplicates the global variables.

Still the same error with 12.11.1 so 12.12.0 is not the culprit.

from amplify-cli.

Another update.

I then deleted the created backend environment and did a redeploy with amplify cli 12.11.0 and it worked :-)

I do not know if the issue was with 12.12.0 or that the first build failed with incorrect node version....

from amplify-cli.

Hey @bergmorten, thank you for reaching out. Glad to hear you were able to mitigate the issue, if the issue reoccurs could you try adding --debug to the command which should provide some verbose logging. But the change in the node version may be the reason for the failed build, but do let us know if the issue reoccurs.

from amplify-cli.

What I think happen was that even when preBuild phase was failing the amplify-cli created an empty backend environment. So when preBuild phase was fixed and it did checkout an empty invalid environment.

It should not have created an empty / invalid environment?

The attempts which failed contained these lines:

2024-05-08T15:06:25.556Z [WARNING]: ✔ Successfully pulled backend environment wcs from the cloud.
2024-05-08T15:06:25.841Z [WARNING]: ✖ There was an error initializing your environment.
2024-05-08T15:06:29.195Z [INFO]: 🛑 Failed to pull the backend.

When I deleted the backend environment it did create a new environment.

2024-05-08T16:15:40.672Z [INFO]: �[0mAdding backend environment wcs to AWS Amplify app: XXXXXXXXX

from amplify-cli.

@bergmorten the branch should pull the backend that the app was connected to. If the backend does not exist it tries to create one for you.

from amplify-cli.