Chrome 155 and 156 shipped to stable in October 2026 with Web Install manifest diagnostics in the Issues panel — no more guessing why navigator.install() silently refuses to fire.
Chrome 155 and Chrome 156 shipped to stable in October 2026, and tucked inside the release notes is a fix for one of the more frustrating failure modes in web app installability: navigator.install() and the <install> element would simply do nothing, with zero indication of why. As of this release, DevTools' Application and Issues panels add dedicated Web Install manifest diagnostics — fetch failures, syntax errors, invalid start_url values, missing names or IDs, and missing manifests are now surfaced with a direct link to the offending file. For teams running mobile app development alongside a web-based install flow — using the Web Install API as a lighter-weight alternative to a native app store listing — this is the debugging tool that was conspicuously missing until now.
The Chrome for Developers release notes describe the fix precisely: the Issues panel can now inspect navigator.install and <install> manifest errors, covering fetch failures, syntax errors, invalid start_url values, missing names or IDs, and missing manifests entirely — each flagged with a direct link to the file DevTools is complaining about. It ships alongside ad-provenance diagnostics in the same Application-panel update, part of the broader Chrome 155/156 stable rollout this month.
Before this, a broken manifest just meant the install prompt never appeared. There was no error in the console, no network tab clue beyond a 404 if you went looking for one, and no panel that connected "the button does nothing" to "your manifest's start_url doesn't match your scope." Developers debugged this by diffing their JSON against a working example from memory. That workflow is now obsolete.
The Web Install API — navigator.install() plus the declarative <install> element — only recently exited its origin trial. It was designed to fix a real, long-standing problem: every browser historically had its own fragmented set of install entry points (address-bar icons, menu items, the old beforeinstallprompt event), and developers had almost no control over when or how an install flow appeared. The new API gives you that control back, but a manifest-driven install flow is also a manifest-driven failure mode — one malformed field and the whole thing goes quiet. DevTools tooling simply hadn't caught up to the new surface area the API introduced.
navigator.install() or rendering an <install> element — if it fails, the specific field and file are named for you instead of a silent no-op.id, a start_url outside your declared scope, or a manifest the browser can't fetch are the exact failure classes this release targets — all previously invisible, all now one panel away from diagnosis.This is not a future proposal — it's already in stable Chrome as of the Chrome 155/156 release this month, dated 20 October 2026 in the official notes. There's no origin-trial flag to enable and no opt-in required: open DevTools on any page that calls the Web Install API and the diagnostics are active. Firefox and Safari don't implement the Web Install API itself yet, so this tooling is Chromium-specific for now — the same caveat that applies to the API it's diagnosing.
If you shipped a Web Install manifest during the origin trial and never circled back to validate it, this is the week to check. The failure you've been shrugging off as "the prompt doesn't fire on some devices" may just be a typo DevTools can now point at directly.