Base44 App Preview Blank or White? Diagnose It Safely

The blank page is emotionally loud but diagnostically quiet

When a screen becomes completely white, it feels as if the whole app disappeared. Often the underlying failure is narrower: one component threw before rendering, a route redirected repeatedly, a required request failed, a stored value no longer matches its schema, or the browser blocked part of the editor. The absence of visible content gives you less evidence, so the temptation is to make large speculative changes. Resist that temptation.

Open a note and describe what actually happens: 'The dashboard appears for one second, then the screen becomes white after choosing a customer; it happens for an admin in Chrome and Edge; the console shows the first error at the same time.' That statement is far more useful than 'the app is broken.' If the failure comes from a backend function, use the ISOLATE_INTERNAL_FAILURE guide. If it happens only on your custom hostname, use the Base44 domain and SSL checklist.

When the published app fails after a schema change

Base44's troubleshooting documentation calls out blank screens after publishing when field definitions and saved values do not agree. A flexible object still needs a shape the renderer and form can understand. If a field was changed from text to object, or an object accepts values whose properties were never defined, older records may no longer satisfy the page's expectations.

Do not repair this by deleting production records. Copy or export a representative record, compare it with the current field definition, and decide whether the schema should accept the historical value or the data should be migrated. Test the change with non-production data and more than one user role. A white page that disappears after deleting evidence has not been diagnosed.

For a broader recovery method when fixes keep causing regressions, use the vibe-coding-stuck playbook. It explains how to protect working progress, isolate one layer, and define an acceptance test before asking an AI builder to edit anything.

How to read console and network evidence without drowning in it

Open developer tools before reproducing the failure, clear old entries, then perform the smallest action that triggers the blank state. In the console, find the earliest red error at the trigger time. Later errors may only report that components or requests failed after the first exception. In the network panel, sort by time and inspect the first failed request, its status, response, initiator, and whether it was redirected.

A 401 points toward missing or expired identity. A 403 points toward authorization. A 404 can mean a wrong route or deployment. A 500 indicates a server-side failure but does not prove your code or the platform is solely responsible. A successful response with an unexpected shape can still crash rendering. Record what the evidence says and what it does not say. Do not paste an entire noisy console into chat and ask the AI to choose randomly.

If no console or request failure appears, inspect navigation loops, a component that returns nothing for one state, and styling that makes content invisible. Use the accessibility tree or temporarily inspect computed styles before deleting CSS. The goal is the first divergence from the working path.

When preview works but the published app is blank

Compare environments instead of rewriting the feature. Confirm the published version is the one you tested. Open the built-in Base44 URL to separate app deployment from custom DNS. Compare user identity, available data, integration connections, secrets, and backend deployment between preview and production. A production record with an older shape can expose an assumption that test data never triggered.

Run the same journey with a controlled account and capture the production evidence. If only the custom domain fails, move to DNS and SSL. If both production URLs fail while preview works, inspect deployment logs and configuration. Do not copy production secrets into preview to make the environments look equal. List the required configuration keys and verify their presence without revealing values.