You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@core-dev-out, in our repro, we're opening VS Code at the repo root in a repo that has multiple projects with host.json files. if you try to create a SWA for a downlevel project (not the first host.jon project), we think you'll get the results that we got, which is that the API path for the downlevel project SWA is the first project in the repo with a host.json file.
Maybe this is clearer: Repo has projects A and B, both with Azure functions and host.json files. Try to create a SWA for project B using the custom option in the wizard. In the YML worfklow file that gets generated, the API path is for project A.
A couple of issues are mine: location of api needed a / - this was a UI issue as the prompts cycled quickly - maybe due to codespaces. The other issue is that the build container needs to be node 18. I'll investigate how to set that.
How can I figure out why it thinks it failed? It looks like it worked to me?
The text was updated successfully, but these errors were encountered: