You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Deploy on Vercel flow fails due to an incorrect environment variable. Vercel has BIGCOMMERCE_CUSTOMER_IMPERSONATION_TOKEN but the client is expecting BIGCOMMERCE_STOREFRONT_TOKEN. Once updated, the build will deploy successfully. However, I'm still experiencing a 503 SERVICE UNAVAILABLE with the deployed site.
To Reproduce
Steps to reproduce the behavior:
Click on "Deploy" to Vercel in the README.
Follow the instructions to connect to your Vercel account
Go to project settings and environment variables
See incorrect variable keys.
Expected behavior
Correct environment variables
Additional context
Should we hold off on using Catalyst with Vercel until the launch of 1.0?
The text was updated successfully, but these errors were encountered:
Thanks for the report @michaelmerrill. I was able to reproduce the issue on my end (see screenshot). After generating a storefront token and updating the environment variables, though, everything deployed for me without issue. Perhaps there's a configuration missing for your storefront that's resulting in the 503? Have you deployed Catalyst before? Do you mind sharing logs?
migueloller
changed the title
Deploy on Vercel is not working
Vercel integration does not set BIGCOMMERCE_STOREFRONT_TOKENFeb 5, 2025
Describe the bug
The Deploy on Vercel flow fails due to an incorrect environment variable. Vercel has
BIGCOMMERCE_CUSTOMER_IMPERSONATION_TOKEN
but the client is expectingBIGCOMMERCE_STOREFRONT_TOKEN
. Once updated, the build will deploy successfully. However, I'm still experiencing a 503 SERVICE UNAVAILABLE with the deployed site.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Correct environment variables
Additional context
Should we hold off on using Catalyst with Vercel until the launch of 1.0?
The text was updated successfully, but these errors were encountered: