Capacitor release build white screen after splash: WebView failed to loa

Not specified by the original author.

TL;DR

Attach the device console to the release build, read the first error at the splash hang, and fix the usual release-only causes: a web asset path or base URL the release configuration builds differently, a plugin missing from the release target, or a JavaScript error that debug builds surface but release builds swallow. Reproduce with the release scheme on a device, watch the console through launch, and compare against the debug build on the same device.

Capacitor iOS release crash on splash screen: console error debug release build

Use this when

• A Capacitor app hangs or crashes on the splash screen only in release or TestFlight builds.
• The debug build from Xcode runs fine on the same device.
• A plugin or the web build pipeline changed since the last release.

Not for this skill when

• The native app crashes before the web view loads with a native stack trace. That is a native crash, not a web layer hang.
• The app hangs identically in debug. Then it is a general startup bug, easier to debug in the browser tools.

Steps

1. Install the release build on a device, open the device console in Xcode or Console.app, and launch the app while watching output. Verify: console output from process start to the hang is captured
2. Read the first error: missing file, plugin not implemented, or an uncaught JavaScript exception are the common shapes. Verify: the first real error is identified, ignoring later noise
3. Verify the built web assets exist inside the app bundle at the path the native config expects, comparing debug and release bundle contents. Verify: asset presence and paths are confirmed or the gap is found
4. Check every plugin used at startup is registered for the release configuration and its iOS deployment requirements are met. Verify: startup plugins are present in the release target
5. Run the release scheme with the JavaScript console visible through Safari web inspector on the device build. Verify: the web view connects and shows any runtime error live
6. Fix the cause, rebuild the release, and cold-launch it on the device three times. Verify: the app passes the splash screen to first content on every launch
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Capacitor release builds diverge from debug in minified web assets, different logging behaviour and stricter native configurations. A JavaScript exception that shows a friendly overlay in development can freeze the splash screen in production, and a mis-synced asset copy leaves the web view with nothing to load. The device console is the only place these failures speak.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

Capacitor splash screen stuck release iOS fix

Symptom phrasing; console first, then asset and plugin checks. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Capacitor white screen TestFlight build

White screen phrasing for the same release-only startup failure. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: remote server URL configuration

Apps configured to load a remote URL in some environments hang when that URL is unreachable in release conditions. Confirm the release config loads local assets if intended. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_rZKShTqJW0HVhO7Q2WaM-A

Resolved from the public thread: https://vectle.com/posts/pst_rZKShTqJW0HVhO7Q2WaM-A

Thread query: Capacitor iOS release crash on splash screen: console error debug release build

TL;DR: Attach the device console to the release build, read the first error at the splash hang, and fix the usual release-only causes: a web asset path or base URL the release configuration builds differently, a plugin missing from the release target, or a JavaScript error that debug builds surface but release builds swallow. Reproduce with the release scheme on a device, watch the console through launch, and compare against the debug build on the same device.

Not specified by the original author.

TL;DR

We changed nothing in our code. What changed and how do we fix it?

Steps

1. Our Typeform embed recently stopped loading inside our Capacitor and Cordova mobile apps. The console shows: Refused to load .. the frame-ancestors directive of the Content Security Policy. We changed nothing in our code. On iOS some of our typeforms still work and some do not. What changed and how do we fix it?
2. Typeform had tightened their CSP frame-ancestors headers, which broke loading inside Capacitor/Cordova webviews (they run on capacitor:// and ionic:// origins that CSP did not allow). The two different behaviors you see are because Typeform was sending different CSP headers per form: the ones sending content-security-policy with restrictive frame-ancestors broke, while the ones with content-security-policy-report-only kept working. Typeform fixed it server-side in December 2021 by updating the headers to frame-ancestors YOUR_HOST capacitor: ionic: https:;. Users confirmed embeds work in Capacitor PWAs after that. If you hit this today on a new typeform, reinstall the app to clear any cached page, and if it persists contact Typeform support - but the underlying fix is already deployed.

When to use

You are seeing this: Our Typeform embed recently stopped loading inside our Capacitor and Cordova mobile apps. Use this skill when you run into "Typeform embed blocked in Capacitor/Cordova: CSP frame-ancestors violation".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Asked in the thread (https://vectle.com/threads/thr4nuDABl2V68ChDza3uVSPQ): Our Typeform embed recently stopped loading inside our Capacitor and Cordova mobile apps. The console shows: Refused to load .. the frame-ancestors directive of the Content Security Policy. We changed nothing in our code. On iOS some of our typeforms still work and some do not. What changed and how do we fix it? The verified answer: Typeform had tightened their CSP frame-ancestors headers, which broke loading inside Capacitor/Cordova webviews (they run on capacitor:// and ionic:// origins that CSP did not allow). The two different behaviors you see are because Typeform was sending different CSP headers per form: the ones sending content-security-policy with restrictive frame-ancestors broke, while the ones with content-security-policy-report-only kept working. Typeform fixed it server-side in December 2021 by updating the headers to `frame-ancestors YOURHOST capacitor: ionic: https:;`. Users confirmed embeds work in Capacitor PWAs after that. If you hit this today on a new typeform, reinstall the app to clear any cached page, and if it persists contact Typeform support - but the underlying fix is already deployed.

Source: https://github.com/Typeform/embed/issues/311 Thread: https://vectle.com/threads/thr_4nuDABl2V68ChDza3uVSPQ

Not specified by the original author.

TL;DR

Reproduce on the release build itself, read the symbolicated release crash or log for the named component, and fix the release configuration or dependency version that debug builds do not exercise. Start in the store portal, the CI job log, and the release build output, work on one affected item, and prove the fix there before running the full set. The named signal in this one is net::ERRCLEARTEXTNOTPERMITTED, WebView failed to load resource net::ERRCLEARTEXTNOTPERMITTED. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Capacitor release build white screen after splash: "WebView failed to load resource net::ERR_CLEARTEXT_NOT_PERMITTED" Android

Use this when

• You see this exact message or symptom in generic mobile release: Capacitor release build white screen after splash: WebView failed to load resource net::ERRCLEARTEXTNOT_PERMITTED Android
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• generic mobile release fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the store portal, the CI job log, and the release build output and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the build signing, the store metadata and declarations, the version and build number, and the track or rollout the release targets, and check the symbolicated release stack trace, the release configuration for the named component, and a release build retest on a physical device class. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: reproduce on the release build itself, read the symbolicated release crash or log for the named component, and fix the release configuration or dependency version that debug builds do not exercise. Verify: the corrected value or setting is visible in generic mobile release itself, not only in a local config file
4. Re-run the original operation on the single affected item first: fix the named item, produce a new build with a raised build number, and send it to an internal or test track first. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the test track build processing cleanly and the store page showing the corrected version ready to promote. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Capacitor release build white screen after splash: WebView failed to load resource net::ERRCLEARTEXTNOT_PERMITTED Android

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

generic mobile release net::ERRCLEARTEXTNOT_PERMITTED during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does capacitor release build white screen after splash: WebView failed to load resource net::ERRCLEARTEXTNOT_PERMITTED Android keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Xcode 15 or 16 or Android Studio current releases, fastlane or store direct upload, App Store Connect and Play Console. The steps assume you can read the job or build log and change the named object in generic mobile release.

Why it happens

In generic mobile release, this failure usually means the release build behaves differently from the debug build because release only configuration, shrinking, or network rules change what ships. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ZX7YccgjXee4gv0QlTzSFg

Resolved from the public thread: https://vectle.com/posts/pst_ZX7YccgjXee4gv0QlTzSFg

Thread query: Capacitor release build white screen after splash: "WebView failed to load resource net::ERRCLEARTEXTNOT_PERMITTED" Android

TL;DR: Reproduce on the release build itself, read the symbolicated release crash or log for the named component, and fix the release configuration or dependency version that debug builds do not exercise. Start in the store portal, the CI job log, and the release build output, work on one affected item, and prove the fix there before running the full set. The named signal in this one is net::ERRCLEARTEXTNOTPERMITTED, WebView failed to load resource net::ERRCLEARTEXTNOTPERMITTED. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.