NextJS Deployment Failure Reason: Failed to deploy the Azure Functions.

[Banshee099]

DeploymentId: 238fc694-ea8e-4376-ad81-250bad73358e
Try to validate location at: '/github/workspace'.
App Directory Location: '/' was found.
Try to validate location at: '/github/workspace/swa-db-connections'.
Looking for event info
Starting to build app with Oryx
Azure Static Web Apps utilizes Oryx to build both static applications and Azure Functions. You can find more details on Oryx here: https://github.com/microsoft/Oryx
---Oryx build logs---

Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20250107.1+ef3fb2f9c490a4fbb1f76b5746cd4ba2ff0409f4, Commit: ef3fb2f9c490a4fbb1f76b5746cd4ba2ff0409f4, ReleaseTagName: 20250107.1

Build Operation ID: 0fa963ad6c384afd
OS Type : bullseye
Image Type : githubactions

Detecting platforms...
Detected following platforms:
nodejs: 18.20.8
php: 8.0.30
Version '18.20.8' of platform 'nodejs' is not installed. Generating script to install it...
Version '8.0.30' of platform 'php' is not installed. Generating script to install it...
Detected the following frameworks: Typescript,Next.js,Three.js

Source directory : /github/workspace
Destination directory: /bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app

Downloading and extracting 'nodejs' version '18.20.8' to '/tmp/oryx/platforms/nodejs/18.20.8'...
Detected image debian flavor: bullseye.
Downloaded in 1 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: nodejs...
Done in 2 sec(s).

Downloading and extracting 'php' version '8.0.30' to '/tmp/oryx/platforms/php/8.0.30'...
Detected image debian flavor: bullseye.
Downloaded in 0 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: php...
Done in 1 sec(s).

Downloading and extracting 'php-composer' version '2.6.2' to '/tmp/oryx/platforms/php-composer/2.6.2'...
Detected image debian flavor: bullseye.
Downloaded in 0 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: php-composer...
Done in 0 sec(s).

Removing existing manifest file
Creating directory for command manifest file if it does not exist
Creating a manifest file...
Node Build Command Manifest file created.

Using Node version:
v18.20.8

Using Npm version:
10.8.2

Running 'npm install'...

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: 'locomotive-scroll@5.0.0-beta.21',
npm warn EBADENGINE required: { node: '>=20' },
npm warn EBADENGINE current: { node: 'v18.20.8', npm: '10.8.2' }
npm warn EBADENGINE }

prudentbit-website-2.0@0.1.0 prepare
husky install

install command is DEPRECATED

up to date, audited 606 packages in 10s

187 packages are looking for funding
run npm fund for details

9 vulnerabilities (1 low, 3 moderate, 4 high, 1 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.

Running 'npm run build'...

prudentbit-website-2.0@0.1.0 build
next build

⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

▲ Next.js 15.0.2

• Environments: .env

Creating an optimized production build ...

warn - The class duration-[260ms] is ambiguous and matches multiple utilities.
warn - If this is content and not a class, replace it with duration-[260ms] to silence this warning.
✓ Compiled successfully
Skipping linting
Checking validity of types ...
Collecting page data ...
Generating static pages (0/34) ...
Generating static pages (8/34)
Generating static pages (16/34)
Generating static pages (25/34)
✓ Generating static pages (34/34)
Finalizing page optimization ...
Collecting build traces ...

Route (app) Size First Load JS
┌ ○ / 9.38 kB 167 kB
├ ○ /_not-found 897 B 101 kB
├ ○ /about 7.25 kB 157 kB
├ ƒ /api/contact 140 B 99.9 kB
├ ○ /career 863 B 151 kB
├ ○ /contact 4.88 kB 162 kB
├ ○ /products 3.07 kB 153 kB
├ ○ /services 15.3 kB 165 kB
├ ● /services/[service] 37.4 kB 187 kB
├ ├ /services/soc-as-a-service-mssp
├ ├ /services/infrastructure-security-audit
├ ├ /services/security-product-procurement-implementation
├ └ [+17 more paths]
├ ○ /training 6.23 kB 156 kB
├ ○ /training/intermediate-to-advanced 137 B 154 kB
└ ○ /training/zero-to-hero 138 B 154 kB

• First Load JS shared by all 99.8 kB
  ├ chunks/215-b9314ef4375e6610.js 45.2 kB
  ├ chunks/4bd1b696-16488e83fa535b13.js 52.6 kB
  └ other shared chunks (total) 1.96 kB

○ (Static) prerendered as static content
● (SSG) prerendered as static HTML (uses generateStaticParams)
ƒ (Dynamic) server-rendered on demand

Preparing output...

Copying files to destination directory '/bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app'...
Done in 10 sec(s).

Removing existing manifest file
Creating a manifest file...
Manifest file created.
Copying .ostype to manifest output directory.

Done in 69 sec(s).

---End of Oryx build logs---
Try to validate location at: '/bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app/.next'.
Oryx has determined that the app build artifacts are in the '.next' directory. If this is incorrect please specify the app artifact location.
Finished building app with Oryx
Repackaged Next.js app to deploy on the backend.
Starting to build function app with Oryx
---Oryx build logs---

Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20250107.1+ef3fb2f9c490a4fbb1f76b5746cd4ba2ff0409f4, Commit: ef3fb2f9c490a4fbb1f76b5746cd4ba2ff0409f4, ReleaseTagName: 20250107.1

Build Operation ID: 6fae6fcae305656e
OS Type : bullseye
Image Type : githubactions

Detecting platforms...
Detected following platforms:
nodejs: 18.20.8
Detected the following frameworks: Next.js,Three.js

Source directory : /bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app
Destination directory: /bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/api

Removing existing manifest file
Creating directory for command manifest file if it does not exist
Creating a manifest file...
Node Build Command Manifest file created.

Using Node version:
v18.20.8

Using Npm version:
10.8.2

Installing production dependencies in '/bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app/.oryx_prod_node_modules'...

Running 'npm install --production'...

npm warn config production Use --omit=dev instead.
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: 'locomotive-scroll@5.0.0-beta.21',
npm warn EBADENGINE required: { node: '>=20' },
npm warn EBADENGINE current: { node: 'v18.20.8', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn deprecated three-mesh-bvh@0.7.8: Deprecated due to three.js version incompatibility. Please use v0.8.0, instead.

added 317 packages, and audited 318 packages in 19s

48 packages are looking for funding
run npm fund for details

6 vulnerabilities (1 low, 2 moderate, 2 high, 1 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues, run:
npm audit fix --force

Run npm audit for details.

Copying production dependencies from '/bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app/.oryx_prod_node_modules' to '/bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/app/node_modules'...
Done in 8 sec(s).

Running 'npm install'...

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: 'locomotive-scroll@5.0.0-beta.21',
npm warn EBADENGINE required: { node: '>=20' },
npm warn EBADENGINE current: { node: 'v18.20.8', npm: '10.8.2' }
npm warn EBADENGINE }

up to date, audited 318 packages in 2s

48 packages are looking for funding
run npm fund for details

6 vulnerabilities (1 low, 2 moderate, 2 high, 1 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues, run:
npm audit fix --force

Run npm audit for details.

Running 'npm run build'...

function-handler-build@0.1.0 build
echo 'restoring the framework'

restoring the framework
Preparing output...

Copying files to destination directory '/bin/staticsites/238fc694-ea8e-4376-ad81-250bad73358e-swa-oryx/api'...
Done in 10 sec(s).

Removing existing manifest file
Creating a manifest file...
Manifest file created.
Copying .ostype to manifest output directory.

Done in 40 sec(s).

---End of Oryx build logs---
Web App Runtime Information. OS: linux, node version: 18
Finished building function app with Oryx
Zipping Api Artifacts
Done Zipping Api Artifacts
Zipping App Artifacts
Done Zipping App Artifacts
Uploading build artifacts.
Finished Upload. Polling on deployment.
Status: InProgress. Time: 0.3179388(s)
Status: Failed. Time: 15.6385261(s)
Deployment Failed :(
Deployment Failure Reason: Failed to deploy the Azure Functions.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
Exiting

these are the logs for my NextJs app deployement

i have already tried
output_location: "build", ".next", ".next/". "./next", "/.next"

this is only a static website no backend api in this

[strikertushar19]

I am getting similar error , did you find the solution ?

[Banshee099]

not right now

[princekumar-UH]

This issue is really frustrating. Did anyone find the exact root cause or any proper solution?

[clementdemily]

Same issue here. I believe the root cause is an underlying dependency upgrade related to Next.js.

I reverted to a commit from three weeks ago that was working fine.

• If I deploy the app from that commit without any changes, the deployment succeeds.
• If I delete node_modules and package-lock.json, run npm install, and commit the newly generated package-lock.json, the deployment fails.

There are no logs or error messages available to help with debugging. It’s been like this for two days now. Unfortunately, I have a deadline by the end of the week, and at this point, switching to a different provider might be my best option.

Good luck to those who aren’t able to migrate.