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
I am currently unable to deploy my SWA to a production environment, as it fails with the following error:
---End of Oryx build logs---
Web App Runtime Information. OS: linux, node version: 20
...
The content server has rejected the request with: BadRequest
Reason: The Static Web App does not support managed functions since there are user provided functions registered with the static web app. Please either detach the user provided functions from the static web app or remove or rename the functions folder to stop uploading to the managed functions.
I have verified that the SWA does not include any code in the /api path that might get picked up as a managed backend.
This error does not appear when deploying to a preview environment via pull request.
To Reproduce
Steps to reproduce the behavior:
Commit a change to the SWA GitHub repo
GitHub action is triggered
Deployment fails with the above error during the Build and Deploy step
Workflow .yml and staticwebapp.config.json attached.
Expected behavior
SWA deploys successfully and uses the linked backend. In the event of a deployment failure, useful error messages that reference the issue should be provided.
Describe the bug
I am currently unable to deploy my SWA to a production environment, as it fails with the following error:
I have verified that the SWA does not include any code in the
/api
path that might get picked up as a managed backend.This error does not appear when deploying to a preview environment via pull request.
To Reproduce
Steps to reproduce the behavior:
Workflow .yml and staticwebapp.config.json attached.
Expected behavior
SWA deploys successfully and uses the linked backend. In the event of a deployment failure, useful error messages that reference the issue should be provided.
azure-staticwebapp-prod.yml.txt
staticwebapp.config.json
The text was updated successfully, but these errors were encountered: