Amplify-console: Errors in amplify.yaml are incorrectly reported as a connection error to your app

Created on 1 Jun 2020  路  16Comments  路  Source: aws-amplify/amplify-console

If there is a YAML syntax error in amplify.yaml, you get the following:

There was an issue connecting to your repo provider, click "Re-authenticate app" in General Settings, and then try your build again.

This is misleading, and let me down 30 minutes of debugging my connection to github before I realized this error had nothing to do with what the actual problem was.

bug pending-prioritization

All 16 comments

@cjsedwards thanks for reporting. Can you share your appid and region so we can take a closer look?

FYI - I've resolved my underlying issue, but the incorrect error message is still a bug IMO

Hi @cjsedwards, where did you get this message? in build stage?

Yes
image

Would you mind tell me which syntax error do you have? I tried to add something on my amplify.yaml, but I didn't get the same error message

Here is the syntax I had in my file:

      commands:
        - 'VUE_APP_WEB_PUSH_PUBLIC_KEY=$WEB_PUSH_PUBLIC_KEY' >> .env
        - yarn run build            - yarn run build
2020-06-01T15:35:33.969Z [ERROR]: !!! YAMLException: bad indentation of a sequence entry at line 15, column 62:
                                  ... UBLIC_KEY=$WEB_PUSH_PUBLIC_KEY' >> .env

I reproduced the issue. Added it to team backlog. Thank you for reporting the issue!

Hello all, thank you for your patience. We have deployed a fix for this, so it should no longer be an issue. Feel free to re-open this ticket if you continue to face this or related issues. Thank you!

Hi,

I have also the issue

There was an issue connecting to your repo provider, click "Re-authenticate app" in General Settings, and then try your build again.

in Amplify. I used CodeCommit as git provider.
The APP ARN is arn:aws:amplify:eu-central-1:356761004113:apps/d34faikz7imb88

same here, after try the "Re-authenticate app" button, the issue still here.

same issue here

Same issue is still there!

Same issue! About to give up on Amplify and go back to Netlify. Never had an issue like this.

Was this page helpful?
0 / 5 - 0 ratings