Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vercel integration does not set BIGCOMMERCE_STOREFRONT_TOKEN #1948

Open
michaelmerrill opened this issue Feb 1, 2025 · 1 comment
Open

Comments

@michaelmerrill
Copy link

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:

  1. Click on "Deploy" to Vercel in the README.
  2. Follow the instructions to connect to your Vercel account
  3. Go to project settings and environment variables
  4. 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?

@migueloller
Copy link
Collaborator

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?

Image

@migueloller migueloller changed the title Deploy on Vercel is not working Vercel integration does not set BIGCOMMERCE_STOREFRONT_TOKEN Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants