Base44 prompts

“an authenticated non-admin user can call User.update(self, {role: "admin"}) and entity RLS then treats them as admin”

Quite possibly. A Base44 entity with no access rule returns every record to anyone — no login needed. Two builders reported tenant-isolation failures in the Base44 Discord in one week. Here is the sixty-second check.

“Google AdSense say website doesn't exist”

Yes, it works — but four Base44 defaults break it. "Site doesn't exist" almost always means you gave AdSense the *.base44.app URL instead of your own domain, or the crawler hit a login wall and gave up.

“My website is not showing up on Google when I search it up — it says it's live on Base44”

Two different problems wear that sentence. Either the site is live but not indexed yet — normal, and fixed in Search Console — or the domain has stopped resolving, which is not an SEO problem at all. Work out which one you have first.

“Base44 Dashboard shows the domain as Active, but browsers say the server cannot be found”

If it worked for roughly two weeks and then died, and you never clicked a verification email, this is almost certainly ICANN registrant verification. Your registrar suspended the domain. Base44 showing "Active" will not fix it — only the registrar can lift it.

“429 Too Many Requests / Rate Limit Exceeded”

Usually your app polling or re-fetching harder than you think, not your plan. Three entity write limits are fixed on every plan — including Enterprise — so upgrading will not clear them. Find the loop first.

“It works when I use it. I don't know what I've missed before I let other people in.”

Six things break Base44 apps on the day real users arrive: open data, auth walls, request volume, publish state, domain and SSL, and thin content. This runs all six as one read-only audit and tells you which to fix first.

“I paid $50 to get 250 credits, and 50% of those credits were wasted just fixing errors”

Because a broken app plus a vague prompt is a loop, and you pay for every lap. Credits are non-refundable for AI mistakes, so the fix is upstream: standing instructions, smaller asks, and reverting instead of re-prompting.

“i cannot publish my edit, the button is on grey — and when it does publish, the live site doesn't change”

The editor preview and the published site are different runtimes and can disagree. Usually it is cache, a stale build, or auth state — but a successful publish can also fail to push assets to the CDN, which looks identical from inside.

“user.data.practice_id is client-editable, so it cannot safely establish tenant membership”

Not with `user.role` and not with anything in `user.data` — a signed-in user can edit both. Tenancy has to live in a membership record the client cannot write, enforced by rules and backend functions rather than by your UI.

“The official Base44 integration doesn't seem to be available yet, and Stripe can't be used for digital purchases on iOS”

Yes, as a wrapped web app — but if you sell digital goods, Stripe inside the app means rejection. Base44's own docs say so. The workable route is selling on the web and keeping the app free of purchase flows.