Unable to clone repository due to user error code: 128 after a force push to a previous commit (rollback):

[dickreuter]

Environment information

react JS with vite

Describe the bug

2025-06-09T22:11:47.631Z [INFO]: # Switching to commit: 594ee38d67aa373560e38e1ea5aafbf0213f76ca

2025-06-09T22:11:47.642Z [INFO]: fatal: unable to read tree (594ee38d67aa373560e38e1ea5aafbf0213f76ca)

2025-06-09T22:11:47.695Z [INFO]: Successfully cleaned up Git credentials

2025-06-09T22:11:47.696Z [ERROR]: !!! CustomerError: Unable to clone repository due to user error code: 128

2025-06-09T22:11:47.696Z [INFO]: # Starting environment caching...

2025-06-09T22:11:47.696Z [INFO]: # Environment caching completed

Reproduction steps

Push a repo to amplify. The website is deployed. Do a hard reset to a previous commit and do a force push.

[terrymun]

This happens intermittently with our Amplify app as well, where the deployment will randomly fail. Rerunning the same deployment fixes the issue, albeit being quite annoying.

[pandemicyash]

Has started happening with my amplify app as well - despite having all the necessary permissions

[BS14]

Facing similar issue in my deployment as well. Random couple of tries, and i am able to deploy application. Double checked necessary permission every thing seems to be in place.

[wanseob]

i also have a same problem now, previously i had to 'reconnect repository' and it worked around but now it just fails. seems like there's an issue between amplify hosting and github integration

---

this bug is pretty random, after multiple retries it started to work again

[OwenAvery]

this has been happening to me intermittently for the past month. The rate of error seems to have increased in the last ~week

[lmscloud-io]

I was able to fix this by moving to the Amazon Linux 2023 build image (from Amazon Linux 2) in the Build Settings page.

[akshbhu]

Hi, from Amplify Hosting.

We added git clone retries to account for the replication delay as suggested by GitHub support. The fix is deployed in all regions.

#4080 (comment)