Skip to content

Deploy to Test Environment

Deploy changes to a test environment. Publishing changes to a test environment loading screen.

Known IssueTroubleshootingStatus
Network calls are appending the static web URL in front of the app service web URL.Make sure the https:// is on the VITE_APIURL.Fixed in 2.0.7.
Trying to hit https://localhost:7288/Api/invoke when listening on http://localhost:5123.Change .env to correct port to 5123 and remove “s” in https. Retest in 2.0.7.Fixed in 2.0.7.
Frontend process is not ending and skipping to a new port.netstat -ano | findstr :<portnumber>

It will list the PID, then you enter that below.

taskkill /PID <PIDnumber> /F
Fixed in 2.0.7
Throwing a 404 error when deploying on Azure because we aren’t serving route.in react-app/public/routes.json: {"routes": [{"route": "/*", "serve": "/index.html", "statusCode": 200}]}Fixed in 2.0.7.
Make changes ready to push to Test. Exit Project Details page. When I open a project, it doesn’t recognize I have changes that need to be pushed.I have to make another change and push the change.Need to retest.
Errors when pushing to Test:
“Merge and deployment failed. Reason: Failed to trigger deployment workflow.”

“Merge and deployment failed. Reason: Cannot transition session in MergedToDevelop state. Must be InProgress.”

When I returned to the project, it didn’t recognize any changes.
I have to make another change and push the change.
Access to fetch at ” from origin ” has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.CORS settings on the develop slot App Service are not getting set to the correct value. It is missing the develop and some other values.

CORS settings on the develop and production are missing https:// prefix.
Fixed in 2.0.19