Deployment of AzureChat via Azure Developer CLI successful, but WebApp shows ":( Application Error"

Hey!

I've deployed AzureChat several times now, without any deployment issues, but in the end the WebApp is throwing an Application Error.

In the Log stream of the webapp i find the following:
2024-03-20T17:13:26.528Z ERROR - Container xxxx-webapp-sd5cwsptk25rq_0_bd9ec074 for site xxxx-webapp-sd5cwsptk25rq has exited, failing site start 2024-03-20T17:13:26.530Z ERROR - Container xxxx-webapp-sd5cwsptk25rq_0_bd9ec074 didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging. 2024-03-20T17:13:26.534Z INFO - Stopping site xxxx-webapp-sd5cwsptk25rq because it failed during startup.

In the container log:

2024-03-20T02:17:26.745016371Z    _____                               
2024-03-20T02:17:26.745044872Z   /  _  \ __________ _________   ____  
2024-03-20T02:17:26.745049472Z  /  /_\  \\___   /  |  \_  __ \_/ __ \ 
2024-03-20T02:17:26.745053172Z /    |    \/    /|  |  /|  | \/\  ___/ 
2024-03-20T02:17:26.745056572Z \____|__  /_____ \____/ |__|    \___  >
2024-03-20T02:17:26.745060272Z         \/      \/                  \/ 
2024-03-20T02:17:26.745063672Z A P P   S E R V I C E   O N   L I N U X
2024-03-20T02:17:26.745066972Z 
2024-03-20T02:17:26.745070073Z Documentation: http://aka.ms/webapp-linux
2024-03-20T02:17:26.745073173Z NodeJS quickstart: https://aka.ms/node-qs
2024-03-20T02:17:26.745076273Z NodeJS Version : v18.19.0
2024-03-20T02:17:26.745079273Z Note: Any data outside '/home' is not persisted
2024-03-20T02:17:26.745082473Z 
2024-03-20T02:17:27.701832454Z Starting OpenBSD Secure Shell server: sshd.
2024-03-20T02:17:27.744094673Z Starting periodic command scheduler: cron.
2024-03-20T02:17:27.751778849Z Could not find build manifest file at '/home/site/wwwroot/oryx-manifest.toml'
2024-03-20T02:17:27.751849852Z Could not find operation ID in manifest. Generating an operation id...
2024-03-20T02:17:27.751858652Z Build Operation ID: b2600354-0d5c-4c21-8a8b-21b6070904e2
2024-03-20T02:17:27.800861213Z Environment Variables for Application Insight's IPA Codeless Configuration exists..
2024-03-20T02:17:27.802549474Z Writing output script to '/opt/startup/startup.sh'
2024-03-20T02:17:27.811806207Z Running #!/bin/sh
2024-03-20T02:17:27.811823407Z 
2024-03-20T02:17:27.811828707Z # Enter the source directory to make sure the script runs where the user expects
2024-03-20T02:17:27.811832708Z cd "/home/site/wwwroot"
2024-03-20T02:17:27.811836708Z 
2024-03-20T02:17:27.811840108Z export NODE_PATH=/usr/local/lib/node_modules:$NODE_PATH
2024-03-20T02:17:27.811897910Z if [ -z "$PORT" ]; then
2024-03-20T02:17:27.811903310Z 		export PORT=8080
2024-03-20T02:17:27.811907510Z fi
2024-03-20T02:17:27.811911010Z 
2024-03-20T02:17:27.821723963Z PATH="$PATH:/home/site/wwwroot" next start
2024-03-20T02:17:27.825401495Z /opt/startup/startup.sh: 11: next: not found

What am I missing? Any idea how I can approach this?
Is there the possibility to trigger only the webapp deployment again via azd?

Start with the Azure Web App log stream and container log shown in the issue, especially the generated startup command and the “next: not found” failure. Trace the Azure Developer CLI deployment configuration to determine why the deployed app cannot start on port 8080; done means the Web App starts successfully and responds to HTTP health pings.