Even after reconnecting the repo, The Amplify build fails

[Bala2Excel]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d32zgy8ma9vi6p

AWS Region

ap-south-1

Amplify Hosting feature

Git providers

Frontend framework

Next.js

Next.js version

next

Next.js router

Pages Router

Describe the bug

Even after connecting the repository, I still get
There was an issue connecting to your repo provider, click "Reconnect repository" in General Settings, and then try your build again.

Expected behavior

Would like to host the open source application. https://github.com/lowdefy/lowdefy-example-aws-amplify

Reproduction steps

Fork https://github.com/lowdefy/lowdefy-example-aws-amplify
Create Amplify Hosting App.
Connect the GithubOrg and provide necessary app.
App should be hosted

Build Settings

N/A

Log output

# Put your logs below this line

2023-12-13T12:45:42.624Z [INFO]: # Checking for Git submodules at: /codebuild/output/src2711933704/src/lowdefy-example-aws-amplify/.gitmodules
2023-12-13T12:45:42.629Z [INFO]: # Retrieving environment cache...
2023-12-13T12:45:42.678Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}

Additional information

N/A

[mauerbac]

Hello -- can you disconnect GitHub and re-establish the connection to Hosting? You can go to GitHub settings and disable Hosting access

[Bala2Excel]

I completely disconnected Github & tried again. Same problem.
AppId: d1jk6re3o7sy75

[mauerbac]

We had someone on our team take a look and found a potential issue with your build script. Are you in Discord? Could you ping me? or DM me on Twitter? @mauerbac

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue has been automatically locked.