Vercel deployment blank page with Uncaught ReferenceError: job is not defined

v0
, , ,
1

Hi, I am having issue with an app that has been deployed many times and was successful 90% of the times. Yesterday I made some update to 4 files in my app, after I deployed I got a blank screen.

Console Error

Uncaught ReferenceError: job is not defined

at index-vlGY8UlG.js:246:15602
(anonymous) @ index-vlGY8UlG.js:246

Network Logs

jobflow.kush-edu.com

304 document Other 88 B 72 ms
index-vlGY8UlG.js 304 script (index):31 52 B 184 ms
clerk-C1G_1Ltu.js 304 script (index):32 52 B 139 ms
vendor-CACp-KUT.js 304 script (index):33 52 B 150 ms
genai-CrTxBhCN.js 304 script (index):34 52 B 139 ms
index-C8bvwtiK.css 304 stylesheet (index):35 52 B 104 ms
css2?family=Inter:wght@300;400;500;600;700&display=swap 200 stylesheet (index):7 0 B 21 ms (disk cache)
[Upload failed]favicon.ico 304 vnd.microsoft.icon Other 76 B 401 ms

Troubleshooting Steps Taken

  • Same deployment worked 2-3 days ago, now shows blank screen
  • Error: Uncaught ReferenceError: job is not defined
  • Cleared all external data sources (Clerk, Neon, browser cache) still blank screen and same console and network output
  • Even old working deployments now fail with blank screen
  • I restored code from backup, but same issue
3

Hey omarkarim9-cell! Great to see you here. It sounds like you’re having a bit of a hiccup with your Vercel deployment. Could you share more details about the issue? Specifically, any error messages you’re seeing, what kind of project you’re working on, and if you’ve checked your build logs? :blush: Thanks!

7

Hello Maya, and thanks for the quick response.
There are no errors in the diployment logs, and the only output I am seeing I already pasted. The project is a vite/react project. uses clerk for authentication, vercel for diployment, and neon for DB. both clerk and vercel are in production mode. all API keys are valid and uptodate. My build logs are clean, and as I have mentioned in my message, previous diployment that were working are not now

8

Hey @omarkarim9-cell , thanks for the info!

Let’s start with your recent changes - if you have a look at the 4 files you updated, did any of them reference a variable called job? This type of error can happen if a variable hasn’t been imported/defined properly.

10

Thanks alot Maya for your reply and attention.
I found out the issue was a console.log statement in another file code. I removed the line and the app worked back. Thanks again dear

1 Like
11

Hey @omarkarim9-cell, thanks for circling back - glad it got sorted! Have a great week.

12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.