Amplify-console: Error when deploying through aws amplify console CI

[incr3m]

We're currently getting the error below when deploying changes on amplify console ci:

Current version we use is 3.8.0. We did not change any config on amplify ci console. It was working before,

[im-dnsosso]

same problem after upgrade to 3.9.0

[thedgbrt]

I've had issues with the amplify console since updating too. For me it was because the version of amplify-cli in the console was an old one (by default it was 1.7.0). You can see which version of the cli the console in using in the provision step:

The solution is to override it in Build settings > Build image settings > Live package updates

On the next generation, the right amplify-cli version will be installed at the end of the "cloning repository" step.

[im-dnsosso]

Yes I adjusted those settings but the problem remain the same... The interesting part is I can deploy it from local cli with amplify push but it does not work from the cloud.

[thedgbrt]

@im-dnsosso i've had issues like that too. Right now when that happens I just re-push from local and re-run the cloud deployment right after. It has worked so far but it's not reassuring...

[thedgbrt]

@im-dnsosso did you try this ? https://github.com/aws-amplify/amplify-cli/issues/1415#issuecomment-490297162

[im-dnsosso]

Thank you! Let me try that...

[im-dnsosso]

# Starting phase: build # Executing command: amplifyPush --simple 2019-09-23T10:16:58.646Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache 2019-09-23T10:16:58.652Z [INFO]: # Start initializing Amplify environment: develop 2019-09-23T10:16:58.653Z [INFO]: STACKINFO=context.print.fancy is not a function TypeError: context.print.fancy is not a function at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env/get.js:53:35 at step (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env/get.js:33:23) at Object.next (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env/get.js:14:53) at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env/get.js:8:71 at new Promise (<anonymous>) at __awaiter (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env/get.js:4:12) at Object.run (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env/get.js:41:38) at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env.js:67:56 at step (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env.js:33:23) at Object.next (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/lib/commands/env.js:14:53) # Importing Amplify environment: develop (amplify env import) 2019-09-23T10:16:59.467Z [INFO]: Scanning for plugins... 2019-09-23T10:17:06.445Z [INFO]: Plugin scan successful 2019-09-23T10:17:06.462Z [INFO]: You must pass in the configs of the environment in an object format using the --config flag 2019-09-23T10:17:06.509Z [ERROR]: !!! Build failed 2019-09-23T10:17:06.561Z [ERROR]: !!! Non-Zero Exit Code detected 2019-09-23T10:17:06.561Z [INFO]: # Starting environment caching... 2019-09-23T10:17:06.561Z [INFO]: # Uploading environment cache artifact... 2019-09-23T10:17:06.598Z [INFO]: # Environment caching completed

Same problem... I deleted the cache option from the buildspec but still no luck...

[RossWilliams]

I am also seeing this issue on my latest deploy.

[kaustavghosh06]

This is an issue tied to the Amplify console not able to switch CLI versions - they've been informed and looking into it. Moving it to the console team repo to further investigate and provide a workaround for the same.

[RossWilliams]

Hi, I've made a workaround for myself after guessing at the issue. It looks like the amplifyPush.sh command is failing because envCache has "stackInfo" set to garbage. envCache is normally updated after running amplify commands, but the script fails before it can be updated to a good value, getting "stackInfo" stuck in the bad state, which won't be fixed by updated amplify-cli.

I've gotten around this by modifying my amplify.yml build steps to include

backend:
  phases:
    build:
      commands:
        - envCache --set stackInfo ${STACKINFO}
        - amplifyPush --simple

where STACKINFO is a single-line json object set as an environment variable in the console. There used to be a button to press in the console to download this information, but I couldn't find it and needed to extract it from Cloudformation outputs.

I am still seeing the deploy issue as described in #143

[garyleefight]

@incr3m Can you give me your AppId. So that we can do more research on the bug. Thanks for @RossWilliams 's workaround. The STACK_INFO is messed up due to CLI bug. Anyone who meets this error can reset the stackInfo with the following setting

backend:
  phases:
    build:
      commands:
        - envCache --set stackInfo ""
        - amplifyPush --simple

Make sure after the envCache is reset, you remove the envCache --set stackInfo "" line

[swaminator]

Closing this issue right now. If you're still having issues please reopen.