Amplify-console: Build fails while cloning: "Unable to clone repository"

[butaca]

Log output:

2019-09-25T21:54:53.807Z [INFO]: Git SSH Key acquired
2019-09-25T21:54:53.910Z [INFO]: # Cloning repository: [email protected]:******
2019-09-25T21:54:54.063Z [INFO]: Agent pid 72
2019-09-25T21:54:54.067Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2019-09-25T21:54:54.119Z [INFO]: Cloning into '******'...
2019-09-25T21:54:54.240Z [INFO]: Warning: Permanently added the RSA host key for IP address '18.205.93.1' to the list of known hosts.
2019-09-25T21:54:54.368Z [INFO]: [email protected]: Permission denied (publickey).
2019-09-25T21:54:54.369Z [INFO]: fatal: Could not read from remote repository.
                                 Please make sure you have the correct access rights
                                 and the repository exists.
2019-09-25T21:54:54.370Z [ERROR]: !!! Unable to clone repository.
2019-09-25T21:54:54.370Z [INFO]: # Starting environment caching...
2019-09-25T21:54:54.370Z [INFO]: # Environment caching completed
Terminating logging...

App ARN
arn:aws:amplify:us-east-2:970150125456:apps/d1sstkga163z5f

_Edit to add some extra info:_

• Last successful build was on 2019-09-25T20:20:40 (timezone as shown in the logs).
• I didn't change anything in AWS Console or Bitbucket since then.
• The repo is private.

[Mangosteen-Yang]

Log output:

2019-09-25T21:54:53.807Z [INFO]: Git SSH Key acquired
2019-09-25T21:54:53.910Z [INFO]: # Cloning repository: [email protected]:******
2019-09-25T21:54:54.063Z [INFO]: Agent pid 72
2019-09-25T21:54:54.067Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2019-09-25T21:54:54.119Z [INFO]: Cloning into '******'...
2019-09-25T21:54:54.240Z [INFO]: Warning: Permanently added the RSA host key for IP address '18.205.93.1' to the list of known hosts.
2019-09-25T21:54:54.368Z [INFO]: [email protected]: Permission denied (publickey).
2019-09-25T21:54:54.369Z [INFO]: fatal: Could not read from remote repository.
                                 Please make sure you have the correct access rights
                                 and the repository exists.
2019-09-25T21:54:54.370Z [ERROR]: !!! Unable to clone repository.
2019-09-25T21:54:54.370Z [INFO]: # Starting environment caching...
2019-09-25T21:54:54.370Z [INFO]: # Environment caching completed
Terminating logging...

App ARN
arn:aws:amplify:us-east-2:970150125456:apps/d1sstkga163z5f

Same error here in Sydney region with bitbucket

[madrussa]

Same again, eu-west-2. I've also tried removing and reconnecting the branch to no avail. I also tried removing the oauth connection in Bitbucket and recreating it... still same issue. All builds failing for us now.

[sarahsweat]

Having the same issue. All builds failing.

[RumieTech]

Having the same issue as-well.

[garyleefight]

Thanks for reporting. We are working on it right now

[garyleefight]

@sarahsweat @TariqRumie Can you let me know which region your app lives? Please provides the appId as well. Thanks

[randallPerez]

@garyleefight i'm having the same issue, my region is us-east-1

[sarahsweat]

@garyleefight
App ARN
arn:aws:amplify:us-east-1:190931189545:apps/dizosossq3y7o

[victorhsb]

same thing here, region is us-east-1
app id is:
arn:aws:amplify:us-east-1:830062373251:apps/d2936znhm1bogq

[swaminator]

@victorhsb @sarahsweat @randallPerez @TariqRumie @madrussa @Mangosteen-Yang @butaca We are currently experiencing issues building and deploying apps that are connected to BitBucket repositories. We are actively working on a fix to give users the ability to reauthenticate with Bitbucket. We apologize for any inconvenience caused and will update this issue with an ETA shortly.

[butaca]

@swaminator thanks. good to know you are working on this. Is there a way to deploy my app using a build done locally in my computer? I’m thinking this as a workaround, in order to be able to update my site.

[swaminator]

We are testing a fix currently and should roll something out shortly.

[swaminator]

@butaca yes you can use manual deploys: https://docs.aws.amazon.com/amplify/latest/userguide/manual-deploys.html

[Mangosteen-Yang]

@swaminator Can we manual deploy on current butbucket project because we need to keep using the domain URL.

I only find upload entry for new application.

[swaminator]

@victorhsb @sarahsweat @randallPerez @TariqRumie @madrussa @Mangosteen-Yang @butaca The fix has been rolled out. Can you please go to General > App settings and choose Re-authenticate. After this is done trigger a new build which should fix the issue. Please let us know if this works.

[Mangosteen-Yang]

@swaminator After clicked the button, I got the same error during deployment.

[swaminator]

@Mangosteen-Yang can you refresh the browser and try to reauthenticate again. After that, trigger a new build. It's possible that your oauth token was in a stale state.

[Mangosteen-Yang]

@Mangosteen-Yang can you refresh the browser and try to reauthenticate again. After that, trigger a new build. It's possible that your oauth token was in a stale state.

It success now, thanks. I will try other applications.

[anthonyjc]

@swaminator Working for me now - thanks very much for the fix

[butaca]

@swaminatoe it’s working now. Thank you 🙏

[devengarg]

@victorhsb @sarahsweat @randallPerez @TariqRumie @madrussa @Mangosteen-Yang @butaca The fix has been rolled out. Can you please go to General > App settings and choose Re-authenticate. After this is done trigger a new build which should fix the issue. Please let us know if this works.

Thanks a ton! Its working now

[sarahsweat]

SUCCESS! Thank you thank you thank youuu! <3

[randallPerez]

@swaminator it's working, thank you

[salzbrenner]

@swaminator I am still getting this error. I'm dealing with two different AWS accounts, both with projects connected to Bitbucket. On one account, the re-auth fix worked. On the other account, re-authorizing does nothing. Still get the same auth build error

[butaca]

@salzbrenner I had to re authorize two times to make it work. Maybe this works for you.

[salzbrenner]

thanks @butaca , i've re authorized multiple times to no avail

[salzbrenner]

@butaca @swaminator nevermind, my fault. I wasn't admin of repo