Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create new Amplify application: Error connecting repository "There was an issue setting up your repository." #3434

Closed
5 tasks done
JackLot opened this issue Apr 19, 2023 · 8 comments
Labels
archived This issue has been locked. git-providers investigating question Further information is requested

Comments

@JackLot
Copy link

JackLot commented Apr 19, 2023

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

NEW_APP

AWS Region

us-east-1

Amplify Hosting feature

Not Applicable

Describe the bug

The Amplify web UI fails to create a new hosting application. After clicking "Save and deploy" I get the following 400 error:

There was an issue setting up your repository. Please try again later.
({"message":"Not Found","documentation_url":"https://docs.github.com/rest/webhooks/repos#create-a-repository-webhook"})

Screenshot 2023-04-19 at 12 31 58 AM

I followed the steps in the user guide. GitHub authorization is successful and I am able to select a repository and branch. Build settings are left as the defaults; however, when I click "Save and deploy" I am immediately shown the error message above.

Logging in and logging out (as suggested by other issues) did not work. Revoking permissions on GitHub then reauthorizing Amplify did not work. Permissions on the Github side seem to be fine.

Expected behavior

I click "Save and deploy" after authorizing my GitHub repository, and I am able to proceed with the Amplify hosting workflow. I have not used Amplify before so I'm not sure what is supposed to happen next - I assume a new Amplify app will be created.

Reproduction steps

  1. Follow the steps in the Amplify user-guide for connecting a Github repository: https://docs.aws.amazon.com/amplify/latest/userguide/setting-up-GitHub-access.html#setting-up-github-app
  2. Receive "There was an issue setting up your repository." after clicking "Save & Deploy" on step 14

Build Settings

No response

Log output

# Put your logs below this line


Additional information

No response

@JackLot JackLot added bug Something isn't working pending-triage labels Apr 19, 2023
@ghost ghost added investigating and removed pending-triage labels Apr 19, 2023
@ghost ghost self-assigned this Apr 19, 2023
@ghost ghost added the git-providers label Apr 19, 2023
@ghost
Copy link

ghost commented Apr 19, 2023

Hi @JackLot 👋🏽 thanks for raising this issue. There should be a webhook that gets created for your repository when you try to deploy the application. Can you confirm if that webhook was created when you tried to deploy?

To find the webhook:

  1. Navigate to your repository in GitHub
  2. Click Settings
  3. Select Webhooks

@ghost ghost added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Apr 19, 2023
@JackLot
Copy link
Author

JackLot commented Apr 19, 2023

Thank you so much for the quick reply. When I navigate to the repo's settings, I see no webhooks:

Screenshot 2023-04-19 at 2 45 10 PM

@ghost
Copy link

ghost commented Apr 19, 2023

@JackLot okay thanks for the verification. I have a few more follow up questions.

  1. Can you provide a screenshot of the build settings that are generated?
  2. What framework is your application using?

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Apr 19, 2023
@ghost ghost added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Apr 19, 2023
@JackLot
Copy link
Author

JackLot commented Apr 19, 2023

Sure.

  1. Screenshot of the build settings (I left everything default)

Screenshot 2023-04-19 at 3 58 46 PM

Advanced settings
Screenshot 2023-04-19 at 3 59 06 PM

Final review page before clicking "Save and deploy"
Screenshot 2023-04-19 at 4 00 00 PM

  1. The framework is Gatsby

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Apr 19, 2023
@ghost ghost removed the bug Something isn't working label Apr 19, 2023
@ghost
Copy link

ghost commented Apr 19, 2023

@ThePatrickDavis In order to further troubleshoot your issue, please reach out to the AWS Support team: https://aws.amazon.com/support for additional assistance. They will be able to assist you in getting your first Amplify app deployed.

Thank you!

@ghost ghost added the question Further information is requested label Apr 19, 2023
@ghost ghost closed this as completed Apr 19, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@JackLot
Copy link
Author

JackLot commented Apr 19, 2023

@hloriii I believe this issue was closed by accident. In your previous comment the person you @ mentioned is not me.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot added the archived This issue has been locked. label Apr 20, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Apr 20, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked. git-providers investigating question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant