`/api/auth/login` failing with "secret" is required on AWS Amplify

Description

I am deploying next.js application with auth0 authentication onto AWS Amplify. This is working on localhost as expected. I created “Environment variables” with AUTH0_SECRET and others in the amplify App Settings, and I am able to authenticate and it is working fine. Suddenly after one of the deployment, I keep getting this error

Browser Error

503 ERROR
The request could not be satisfied.

Logs:

ERROR	Invoke Error 	
{
    "errorType": "TypeError",
    "errorMessage": "\"secret\" is required",
    "stack": [
        "TypeError: \"secret\" is required",
        "    at Object.get (/var/task/node_modules/@auth0/nextjs-auth0/dist/auth0-session/get-config.js:147:15)",
        "    at Object.getConfig (/var/task/node_modules/@auth0/nextjs-auth0/dist/config.js:66:38)",
        "    at Object.initAuth0 (/var/task/node_modules/@auth0/nextjs-auth0/dist/index.js:22:23)",
        "    at getInstance (/var/task/node_modules/@auth0/nextjs-auth0/dist/index.js:18:24)",
        "    at handleAuth (/var/task/node_modules/@auth0/nextjs-auth0/dist/index.js:124:18)",
        "    at Object.5862 (/var/task/pages/api/auth/[...auth0].js:214:129)",
        "    at __webpack_require__ (/var/task/webpack-api-runtime.js:25:42)",
        "    at Object.7416 (/var/task/pages/api/auth/[...auth0].js:189:23)",
        "    at __webpack_require__ (/var/task/webpack-api-runtime.js:25:42)",
        "    at __webpack_exec__ (/var/task/pages/api/auth/[...auth0].js:325:39)"
    ]
}

for debugging, I printed the secret using console.log and I am able to see it.

Reproduction

my […auth0].js

import { handleAuth } from '@auth0/nextjs-auth0';
console.log('the AUTH0_SECRET env var is set: ', !!process.env.AUTH0_SECRET);
export default handleAuth();

Environment

Please provide the following:

• Version of this library used:

"@auth0/auth0-react": "^1.9.0",
    "@auth0/nextjs-auth0": "^1.7.0",
    "axios": "^0.26.1",
    "jsonwebtoken": "^8.5.1",
    "next": "latest",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-is": "^18.0.0",
    "swr": "^1.3.0",

[alexboulay]

@ilarumk I am having the same issue. It feels weird having to write a script that will create a .env file when the vars can be logged and are visible…makes no sense.

do you think it’s a problem with Amplify?

[noanflaherty]

@axelmukwena after much trial and error, I stumbled upon these AWS help docs which helped a lot.

Specifically, going to the “Build settings” page of my app and updating the build section to:

        build:
          commands:
            - env | grep -e AUTH0_ >> .env.production
            - npm run build