Skip to content

Fix: Resolve Blank Screen Issue on Vercel Deployment#8

Draft
google-labs-jules[bot] wants to merge 1 commit intomainfrom
fix/vercel-white-screen-8553076711892104706
Draft

Fix: Resolve Blank Screen Issue on Vercel Deployment#8
google-labs-jules[bot] wants to merge 1 commit intomainfrom
fix/vercel-white-screen-8553076711892104706

Conversation

@google-labs-jules
Copy link
Copy Markdown

This commit fixes a critical bug that caused a white screen to appear when the application was deployed to Vercel.

The root cause was the incorrect method of accessing environment variables in a Vite project. The code was using process.env.API_KEY to access the Gemini API key, which is not available in the client-side bundle created by Vite.

The fix involves:

  • Modifying services/geminiService.ts to use import.meta.env.VITE_GEMINI_API_KEY, which is the correct way to access environment variables in Vite.
  • Creating a .env.local file with a dummy key to facilitate local development.
  • Ensuring .env.local is included in .gitignore to prevent leaking secrets.

This change allows the application to initialize correctly by providing the necessary API key, thus resolving the blank screen issue. For the fix to work in production, the VITE_GEMINI_API_KEY environment variable must be set in the Vercel project settings.


PR created automatically by Jules for task 8553076711892104706 started by @orbiscode-ops

The application was failing to render on Vercel (white screen) because it was attempting to access the Gemini API key via `process.env.API_KEY`. This is not supported in Vite for client-side code.

This commit corrects the implementation to use `import.meta.env.VITE_GEMINI_API_KEY`, which is the standard way to expose environment variables to the client in a Vite application.

Additionally, a `.env.local` file has been created to support local development, and `*.local` has been confirmed to be in `.gitignore`.
@vercel
Copy link
Copy Markdown

vercel bot commented Jan 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
deals Ready Ready Preview, Comment Jan 25, 2026 0:50am

@google-labs-jules
Copy link
Copy Markdown
Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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

Successfully merging this pull request may close these issues.

0 participants