UrgisoftAI-built apps

AI-built apps ยท November 2026

Fix a vibe coded app: a ten-minute check to find what is broken, and the fix for each

Short answer: before you fix a vibe coded app, find out which problem you have. An app built by describing it to Lovable, Bolt, Replit, Base44, Cursor or another AI tool tends to break in the same few places: the step from the builder's preview to the live address, sign-in, who may read which data, payments, and speed on phones. Five checks in your own browser, about ten minutes, tell you which one it is. Then fix that one thing, not the whole app.

The ten-minute check

Do these in order, on a computer, and write down what you see. You do not need to read any code.

  1. Where does it break? Open the app inside the builder's preview, then open its live address. Broken in both: a recent change did it. Fine in the preview and broken live: the live copy is missing something the preview has (a setting, a key, an allowed address, a fresh publish).
  2. Open the live address in a private window (Ctrl+Shift+N in Chrome). A private window has no saved sign-in and no saved files, so you see what a new visitor sees.
  3. Read the red lines. Press F12 and open the Console tab, then reload the page. Red lines are the app saying what failed. Copy the first one word for word; it is worth more than any description of the bug.
  4. Look at the failed requests. In the same panel open the Network tab and reload. A request in red has a number beside it: 401 means "you are not signed in", 403 "you are signed in but not allowed", 404 "that address does not exist", and 500 or higher "the server itself failed". Note the number and the address it belongs to.
  5. Try a second account, and a phone. Sign up as a brand-new user with another email address and repeat the step that fails. Many apps work only for the account that built them. Then open the app on a phone with Wi-Fi turned off.

Match what you saw to the problem

What you sawWhere the fix is
A white or blank page on the live address, fine in the previewA blank page after publishing: six causes
The publish or build stops with an error, or you want the app on your own hostDeploy to Vercel or Netlify: the steps, and six errors that stop it
Sign-up or sign-in fails, people are logged out on refresh, requests answer 401Login and Supabase errors: seven causes
The second account sees nothing, or sees the first account's records; requests answer 403Six security checks you can run yourself
The pay button does nothing, or the customer paid and the app still says "free"Stripe payments not working: seven causes
The first screen takes many seconds on a phoneSlow on phones: our demo shop before and after, and the five mistakes
You work in an editor (Cursor, Claude, ChatGPT) and the code looks finished but failsAI-generated code: seven common problems
The app was built in Base44Base44 bug fixing: seven common problems
The app was built in ReplitReplit app bug fixing: seven common problems

Nothing broken, and you want the app on the iPhone or in the App Store? Convert a Lovable app to iOS: three routes and seven traps.

Before you ask the AI to fix it again

  1. Go back before you go forward. If the app worked yesterday, return to yesterday's version first (the builder's version history, or your last save point in Git), and make the change again in smaller steps.
    Going back takes a minute. Asking the AI to repair its own change can take the afternoon, and each try may touch files that were fine.
  2. One problem per message, with the exact error. Paste the red line from the Console and the failed request's number and address, and name the screen where it happens.
    "Login is broken, please fix" makes the AI guess. "Sign-in answers 401 on the live address and works in the preview" tells it where to look.
  3. Ask for the cause first. "Why does this happen? Do not change anything yet." Read the answer, then ask for the change.
    If the explanation does not match what you saw in the five checks, the fix will not either.
  4. Test the fix the way you found the bug. Private window, second account, live address.
    A fix that only works in the preview, signed in as you, is the same bug again.

When to stop prompting and hand it to a person

Three signs, from our own practice: (1) the same bug has come back after three tries at fixing it; (2) each fix breaks something that worked before; (3) the problem touches money or other people's data (payments, sign-in, who can read what), where "it seems to work now" is not enough. At that point more prompts usually add code without removing the cause, and someone needs to read the code itself.

This is a checklist from engineering practice, not a study: we have not counted how often each problem happens in vibe coded apps, and your app may have one that is not on this page. The meanings of the request numbers (401, 403, 404, 500) are the standard ones for the web. Urgisoft is not affiliated with Lovable, Bolt, Replit, Base44, Cursor, Supabase or Stripe.

Want it fixed for you?

We fix vibe coded apps: Lovable apps, Bolt apps, and apps written with Replit, Base44, Cursor and other AI tools. We find the cause in your own code, get the app working on its live address, and tell you in plain words what was wrong. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from $150. No fix, no charge. We work through GitHub or as a collaborator you invite; we never ask for your password, and we ask you to replace any key we could see once the work is done.

See the gig on Fiverr