2 people reported
All time, since Aug 26.
Sensitive env vars empty in Preview
“The Preview runtime treated CONTACT_BLOB_READ_WRITE_TOKEN as unavailable/falsy even though the variable is correctly configured in the Vercel dashboard.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/vercel/issues/10249/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Sensitive environment variables arrive empty in Preview deployments. Variables correctly scoped to Production and Preview are treated as "unavailable/falsy" or the deployed Preview received empty values.
Is this your bug?
File my report- Where
- Preview deployments
- Error text
ENOENT: no such file or directory, mkdir '/var/task/data/contact'- Versions
- 59.26.0
- How bad
- Breaks a normal workflow.
Original reports4, newest first
- Vercel Preview build does not receive Sensitive environment variables, but Config variables work#49661
- “Sensitive Preview environment variable unavailable at runtime.#48518
- “Sensitive Preview environment variable unavailable at runtime.#48502
- Sensitive Preview environment variable unavailable at runtime#48484