Amplify-console: Issue in connecting feature branch to Amplify

[SFaraji]

I'm trying to add a new feature branch to our amplify project, but when I'm trying to "Add repository branch" it failed and return a Failed to load resource: the server responded with a status of 404 () and doesn't allow us to add any branches, but our limit for adding branches is the default 50.

Please advise what to do.

[Athena96]

Hi @SFaraji can you please share your appId and also if possible the number of branches in your repo. Thanks!

[SFaraji]

Hi Athena96, here is the Amplify App ID: d4i8d52zi6kcj and we got 3 branches for this repo.

[SFaraji]

@Athena96 and @abhi7cr, any solution?

[SFaraji]

This bug is very annoying and causes integration manually.

[Athena96]

Hi, @SFaraji are you still facing this issue? If so can you provide any additional repro steps, I have not been able to repro on my end. Thanks!

[SFaraji]

Hi @Athena96, yes I'm still facing this issue.

Here the repro steps:

1. Click connect branch
2. Select the Repository service provider, in my case is "Gitlab" and click Next button
3. The screen will be locked and if you open from inspect element you can see Failed to load resource: the server responded with a status of 404 ()

Please advise what to do, because this bug is very annoying and require manually integrate the branch.

[SFaraji]

What is going on? Why no one responsible to solve this issue. This is causing a huge issue for us for not allowing us to create any branch from the console.
cc: @abhi7cr @Athena96 @ericclemmons @hyandell

[arturocanalda]

Same issue here. Actually in my case I could manage to connect branches from the console until I had to migrate my repo and update the link of my Amplify App (which btw, can only be done from the command line). It seems from the Console Amplify tries to read Github's branches by using the old OAuth token.

Amplify has great things but also horrible ones that make you easily feel like loosing control of your project.

[SFaraji]

Exactly right @arturocanalda, Amplify is so great for managing web apps but this bug regarding managing multiple branches for prod, sandbox, and pre-release make it annoying to use the command line in order to connect a new branch.

I'm looking forward they will fix this issue ASAP 🤞

[SFaraji]

Please look over the issue with the wrong GitLab id which is used in amplify and that stops us from connecting our branches. So annoying.

[UniLu419]

Same issue here. As I found by adding fetch breakpoint(url contains gitlab), the url sent to gitlab is using number 1 as projectid in the url and that's the reason why it is returning 404

[SFaraji]

@abhi7cr @Athena96 @arturocanalda @abhi7cr @UniLu419, I have contacted AWS tech support and they finally found the issue which is causing if there is a number at the start of the group/username URL (e.g. 1abc should be abc) otherwise Amplify will take the number as the projectId.

[abhi7cr]

Yup @SFaraji that’s correct. We had an issue with the way we parsed the repository namespace(_username/reponame_ _groupname/reponame_) when it starts with a number. We have a fix ready, and will update this thread once it’s deployed 🙂