Missing option to configure backend for branch autodetection?

[lorengordon]

** Please describe which feature you have a question about? **

Pattern-based feature branch deployments

** Provide additional details**

I created an amplify app and enabled branch autodetection, but the option to configure the backend is not available. This means whenever a new branch is created, the build fails because it is not linked to a backend. How can I turn this feature on for this app?

[Athena96]

Hi @lorengordon do you have an existing backend setup for your app?

[lorengordon]

Yes, there is a backend. I'm not sure what "existing" refers to... I used amplify to create the backend.

Here is a new branch I just pushed to the repo:

And here you can see I can assign a backend manually:

[Athena96]

Did you have a backend environment setup before you tried to enable the pattern-based feature?
Because in the first screenshot you shared, there is no option for "Branch autodetection - backend environment" like in the docs
https://docs.aws.amazon.com/amplify/latest/userguide/pattern-based-feature-branch-deployments.html

[lorengordon]

Because in the first screenshot you shared, there is no option for "Branch autodetection - backend environment" like in the docs

Yes, exactly, that's exactly what I'm saying. There is no option for it in our project. That's why I shared the screenshot, so you could see what I'm seeing.

Did you have a backend environment setup before you tried to enable the pattern-based feature?

Fairly sure, yes, but it's been a long week so who knows. I definitely have disabled and re-enabled branch autodetection to try pick it up. I have also reconnected the repo. The option just is not there.

[lorengordon]

@Athena96 I went back through our slack workspace and remembered that no, we did not have the backend configured when we first setup the pattern-based feature. I added the backend later. But since adding the backend, I have disabled the branch builds and re-enabled them, and reconnected the repo, several times, to no avail.

[lorengordon]

@Athena96 sorry, hate to bother you, but just wanted to follow up if this is some bug in the UI, when the project is created without a backend first? It's not critical to me, I have a workflow for the project. So if this is not something you want to investigate further then we can close this. I just hate to open issues and leave them unworked/untriaged.

[mansiva]

We're having the same issue, project was created, multiple backend environments were setup as per the amplify docs (dev, test, prod), then when enabling branch auto-detection no option to specify which backend to connect to.

Now any new branches created in git are failing to build since no backend is being defined, and strangely enough yesterday a bunch of new backend environments started to appear with strange names: arabelle, belicia, blakeley, bobbye, britt... Nobody in the team claims to have created them, so it's pretty weird.

[vic-blt]

Same issue here.
The project was initially created with a backend.

[vic-blt]

See my comment #448 (comment)
It appears that if your app's framework is set to "React" you won't have options to set a default backend either for "branch autodetection" or "previews".
You have to set your app's framework to "React - Amplify".
The only way I found to do this is by deploying a fullstack amplify app from samples :
Host web app > From fullstack samples > Authentication Starter

[vic-blt]

I found the solution, see my new comment #448 (comment)

[ganipcanot]

Resolving due to age - please re-open if you are still experiencing issues.

[github-actions]

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.