Help Request – Issues with My Grabbit App Deployment on Vercel

Open Source
1

I’m currently building a voice-activated shopping reminder app called Grabbit, and I’m running into several deployment and reliability issues on Vercel that are making it difficult to move forward.

I need help understanding and resolving the following:

:gear: Technical Issues

  1. Deployment Conflicts & Overwrites
  • When attempting to test minor changes (e.g. adjusting geofencing alerts), the Vercel deployment sometimes overwrites or resets significant parts of my app.
  • A recent incident caused me to lose nearly two weeks of code because the bot/AI assistant tried to “fix” a bug and redesigned the app instead.
  1. App Behavior Not Matching Deployed Site
  • The version that’s currently deployed and working does not match the versions I see during preview or edit mode.
  • I have trouble accessing the exact code running in production through the Vercel dashboard.
  1. Alert System Not Triggering on Device
  • While debug tools confirm that location and store detection work correctly, alerts (buzz/sound notifications) don’t actually trigger on my phone.
  • Adding buzz or sound effects to fix this broke functionality completely at one point.
  1. Confusing File Structure in Vercel
  • Inside the /app folder are several subfolders. When I open them in Vercel, the code does not update visually, making it hard to back up or understand what’s deployed.
  • I’m not confident I know how to safely copy/export the entire current state.

What I’ve Tried

  • I’ve asked the bot to “restore” the working version, but each time it seems to result in a different version being deployed or rebuilt.
  • I exported the live Vercel site’s HTML to try and rebuild manually—but the behavior doesn’t match even with the same files.

:hammer_and_wrench: What I Need Help With

  1. How to safely back up the currently deployed version of the PWA (all folders/files).
  2. Best practice for editing/test deploying without overwriting the working version.
  3. How to fix geofence-triggered alerts so that they consistently buzz/sound on mobile.
  4. Clarification on file structure in Vercel – which folder is actually live and how to read/update it confidently.

:folded_hands: Final Notes

I’m relatively new to Vercel and PWA deployment. I’m working really hard on this app and just need some guidance to regain control over my project. Any support—step-by-step, tutorials, advice, or mentorship—would mean a lot. I do not code and completely Illiiterate in that regard. (maybe an issue, not going to lie)

I just want to get back to here and fix the alert bug in my v0. https://v0-new-project-u21l1u1b27g.vercel.app/

Thanks in advance for your time and help.

—Rob
Creator of Grabbit

1 Like
4

Hey @rob-1985!

In the top right corner of v0, have you seen the selector where you can jump back into prior versions? It’s a small box that says “v30” (or whichever version you’re on) and clicking it will allow you to quickly resurface prior versions…

1 Like
6

I just reviewed all the versions, and what I’m seeing are the ones created "after’’ my last deployment. These weren’t deployed by me, looks like the bot made changes trying to fix the alert notifications, and that’s when everything broke. None of those changes are reflected in my current live version on the PWA.. ugh! Almost Excited!!

1 Like
7

@rob-1985 if it was your very last deployment, there’s something hobby accounts can use called “Instant Rollback” - otherwise, as you build in v0, are you forking versions every so often so that you retain prior versions? Performing an Instant Rollback on a Deployment

So sorry for the trouble here - if we’re not able to access this prior deployment, happy to help troubleshoot as you build here…

8

I forked my project as soon as I noticed the code starting to go off the rails. My last deployment was made from the previous fork, how can I access that fork and view the last version that was deployed from it?