By the PrototypeVerdict Test Team
This is a failure catalog, not a highlight reel. We build the same three small apps in each tool and write down what broke, what it cost, and what we still can’t verify. Every card below comes straight from our Oct 29 lab logs and keeps three things apart: what we saw, what we think it means, and what we never checked.
If you need “what do I do right now?”, start with the how-to: Fix AI app builder errors. This page is the list of what actually happened to us, in a form you can cite.
New here? How we test · Usage Index (CC BY usage data) · Plan-fit calculator.
How to read the cards
| Label | Meaning |
|---|---|
| Observed | Written in our Oct 29 lab log |
| Interpretation | Our plain-English reading, not a quote from the tool |
| Not verified | The exact prompt, a screenshot, or a re-run is not in our log |
We don’t invent tests, prices, or outcomes for this library. Softr’s portal and invoice tracker were not working on Basic at the end of our session, and we never rewrite that as a pass.
The six cards (Oct 29, 2026 lab)
- WAB-01: Login stuck, 500 error from a looping security rule (Bolt Free, client portal)
- WAB-02: Blank
/portalafter the email-confirm link (Lovable Pro) - WAB-03: “Admins only” with no way to become the first admin (Lovable Pro, Bolt Free)
- WAB-04: Invoice data missing from another preview origin (Lovable Pro)
- WAB-05: Out of tokens before the next test (Bolt Free)
- WAB-06: User groups switched off, portal access broken (Softr Basic)
WAB-01: Login stuck, 500 error from a looping security rule (Bolt Free, client portal)
| Tool / plan | Bolt · Free (1M tokens a month, 300K a day) |
| App | Client intake portal (build 1) |
| Symptom | After sign-up, login stuck on the login screen, with a 500 error underneath |
| Cost (observed) | About 84K tokens for the one fix message; about 185K for the whole build including that fix |
| Source | Our Oct 29 Bolt lab log, build 1 |
Observed
- Our log records one fix message: “login stuck on login screen; 500 error from recursive RLS policies on profiles table; Bolt fixed with SECURITY DEFINER is_admin(). The fix alone used ~84K tokens.”
- After the fix, sign-up and login worked, and so did the other portal checks in that log (intake form, file upload, past submissions, admin table, status change after reload). The 3-document limit was not tested.
- Same build: there was no built-in way to make an admin, so we set the role by hand in Bolt’s Database tab (see WAB-03).
Interpretation
Our log attributes the login 500 to recursive security policies on profiles. The exported migration added a SECURITY DEFINER admin-check function and rewrote policies to use it. We did not capture the exact on-screen recursion wording, security-review the generated change, or run Bolt’s second-account check. Restored login was not proof of safe authorization. See the diagnostic explanation and review cautions; we do not reproduce the generated SQL here.
Exact prompt not logged
We saved what the fix message did and what it cost, not its wording, so we don’t quote it. The example message in our fix guide is a suggestion, not the text we sent in this run.
What we did not do
- Did not switch security rules off to get past the error. Keep access restrictions enabled while fixing the cause; disabling RLS can expose data depending on grants and other controls.
- Did not re-run this build on a paid Bolt plan.
- Did not publish the app.
Related
- Fix AI app builder errors: login and security rules
- Add login and a database to an AI-built app
- Token figures: Usage Index
WAB-02: Blank /portal after the email-confirm link (Lovable Pro)
| Tool / plan | Lovable · Pro, 100 credits ($25/mo, the plan we tested) |
| App | Client intake portal (build 1) |
| Symptom | After clicking the email confirmation link, /portal was blank |
| Cost (observed) | No fix message: signing in again at /auth got past it |
| Source | Our Oct 29 Lovable lab log, build 1 |
Observed
- From the log: “blank /portal after email-confirm redirect (fixed by signing in at /auth)”.
- Same build:
/adminwas blank for a few seconds on a hard reload, then loaded on its own. - Email confirmation was required, and example.com addresses were rejected at sign-up.
Interpretation
The confirmation link sent new users to the portal before they had a normal signed-in session, so the page had nothing to show.
Not verified
We haven’t tested a prompt that fixes the redirect for good, or re-run the build to see whether it happens every time.
Credits
Our log shows the balance going from 105 to 104 for this build, while the usage page showed 6 credits for the project and the 5 free daily build credits went to 0. Lovable’s credit accounting can disagree between the balance and the usage page; full write-up in our AI app builder usage study.
Related
WAB-03: "Admins only" with no way to become the first admin (Lovable Pro, Bolt Free)
| Tools | Lovable Pro (fixed by chat) · Bolt Free (fixed by hand in the Database tab) |
| App | Client intake portal (build 1) in both |
| Symptom | The admin page was locked and there was no way in the app to become the first admin |
| Source | Our Oct 29 Lovable and Bolt lab logs, build 1 |
Observed: Lovable
- One fix message, quoted from our log with the test account address removed: “The /admin page says Admins only and I have no way to become an admin. Please make the account [test account email] an admin (add it to the admin role) and add a link to the admin view in the nav for admins, so I can test changing submission statuses.”
- After that message, the admin table worked and status changes stayed saved after a refresh.
Observed: Bolt
- From the log: “no built-in way to make an admin; tester set role=admin by hand in the Database tab.”
- That was a manual step, not a chat message, so it used no tokens.
Interpretation
Both tools built an admin gate with no way to create the first admin. Our guides suggest naming the admin account in your first prompt.
Not verified
We haven’t tested whether naming the admin up front prevents this; that advice is not proven by these runs.
Related
WAB-04: Invoice data missing from another preview origin (Lovable Pro)
| Tool / plan | Lovable · Pro, 100 credits |
| App | Invoice tracker (build 2) |
| Symptom | Data survived a reload in the same preview, but the same app opened from another address showed $0.00 |
| Fix messages | 0 on the first build |
| Source | Our Oct 29 Lovable lab log, build 2 |
Observed
- The checklist passed in that preview: clients, invoices with line items and automatic totals, Paid status, automatic Overdue, dashboard totals, and data still there after a reload.
- From the log: “data appears stored in browser localStorage only (preview iframe on another origin showed $0.00; Lovable suggested ‘Add online invoice storage’)”.
- Same day, for contrast: Base44’s invoice tracker saved to a real database (Client and Invoice tables).
Interpretation
The log’s browser-only explanation was an interpretation, not a database finding. The observation was a reload pass in one preview and $0.00 from another origin. We did not inspect the database, so we cannot rule out other session, environment, save or read problems. For troubleshooting rather than the case record, use the missing-data checklist.
Not verified
We didn’t send the “Add online invoice storage” follow-up on Oct 29, so we can’t tell you what it costs or whether it fully fixes this.
Credits
Build 2 took the balance from 104 to 101 in our log, while the usage page showed 2.70. Lovable’s credit accounting can disagree between the balance and the usage page; full write-up in our AI app builder usage study.
Related
WAB-05: Out of tokens before the next test (Bolt Free)
| Tool / plan | Bolt · Free (1M tokens a month, 300K a day) |
| When | After our three test builds used the full 300K daily allowance |
| Symptom | “You’re out of tokens. Switch to Pro” |
| Blocked work | A CSV export follow-up on the invoice tracker (build 2) |
| Source | Our Oct 29 Bolt lab log, summary and follow-up tests |
Observed
- Usage that day: 300K tokens in total (build 1 about 185K including its fix, build 2 about 100K, build 3 about 15K). The daily cap was hit just as build 3 finished, followed by an “out of tokens” upgrade prompt.
- From the follow-up notes: “CSV export on B2 wasn’t run because free-plan tokens were exhausted (‘You’re out of tokens. Switch to Pro’).”
Interpretation
One expensive fix (WAB-01, about 84K tokens, roughly 28% of the free day) left too little room for a later test on the same day. That sequencing is our reading of the log, not something Bolt told us.
Not verified
We didn’t run the CSV export later, so we have no token cost for it on Bolt.
Related
WAB-06: User groups switched off, portal access broken (Softr Basic)
| Tool / plan | Softr · Basic ($25/mo, the plan we tested) |
| App | Client intake portal (build 1) |
| Symptom | Admin and Client user groups deactivated; clients couldn’t reach the intake form in preview; a client could open the admin submissions |
| Credits (observed) | 0.94 AI credits for the build (0.76 build + 0.18 for one fix) |
| Source | Our Oct 29 Softr lab log, build 1 |
Observed
- The build ended with “Your app is ready”, but our log says: “Not fully working: intake form unreachable in preview and access control broken after 1 fix.”
- Our one fix message: “Sign-in is set to email one-time code, which my plan doesn’t allow, and the Admin and Client user groups are deactivated. Please switch to email and password sign-in, and make the admin view and each client’s own submissions work on my current plan.”
- Result: partly fixed. Sign-in switched to email and password. “Groups still deactivated after reload; AI claimed it reactivated them (false).”
- Softr’s own message on the User Groups screen: “Some user groups are deactivated because you’ve exceeded your plan’s limit. Upgrade to reactivate them!”
- Viewing the preview as a test client, that client could open the Admin tab and the admin URLs and see all 8 sample submissions. That fails the “clients see only their own submissions” check.
- Softr told us added users “can’t access the app until it’s published”, so we checked a second user with Softr’s “Preview as” switcher rather than a real second login.
Interpretation
On Basic, the group-based permissions this portal needs were not usable in our session, and one AI fix didn’t bring them back.
Not verified
We didn’t test Softr’s paid tiers, so we don’t claim a higher plan fixes every gap.
Related
- Plan-fit calculator and Usage Index (both show Softr Basic finishing only the landing page, not the portal or invoice tracker)
- Fix AI app builder errors
Logged, but not a card yet
- Base44 Builder, invoice tracker: the build paused at a “processing checkpoint” and asked to approve deleting its own test record. We replied “continue” (our log marks that message as redundant) and the app was working at about 12.5 minutes. An interruption, not a broken app.
- Softr Basic, invoice tracker (not working at the end): our fourth fix request got this reply: “The request took too long to reason about and I couldn’t retrieve the response. Please try breaking it down into smaller change requests.” At the end of the session the database was in place, but the preview still had no Overdue status and no way to add line items, and the overdue workflow showed an error. We count this build as not working, the same result our Softr review gives. We didn’t save the text of two earlier follow-ups, so it isn’t a full card until we can show the whole chain.
- Bolt Free, landing page: the page showed a literal
\u2019instead of an apostrophe. Cosmetic only, and we didn’t send a fix. - Softr Basic, landing page: the AI made up yearly prices and a “Trusted by 1,000+ small businesses” badge. That’s a content problem rather than a broken app, so it isn’t a card here.
Honesty limits
- One run per app per tool on Oct 29, 2026. Another day could differ.
- Plans tested: Lovable Pro 100, Base44 Builder, Bolt Free, Softr Basic. We say nothing about other plans unless a card says so.
- Fake data and unpublished previews only.
- Lovable’s credit accounting can disagree between the balance and the usage page; full write-up in our AI app builder usage study.
Related
Lab logs from Oct 29, 2026. Not a vendor status page. Published: Nov 6, 2026. Updated: Nov 17, 2026.