Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PROTOCOL_TIMEOUT (Method: Page.getAppManifest)

See original GitHub issue

Provide the steps to reproduce

Run LH on https://seo4.net or https://krakowskakancelaria.pl/

What is the current behavior?

Error: Lighthouse returned error: PROTOCOL_TIMEOUT. Waiting for DevTools protocol response has exceeded the allotted time. (Method: Page.getAppManifest) (PROTOCOL_TIMEOUT)

What is the expected behavior?

No errors.

Environment Information

Affected Channels: Pagespeed API returns 500, web.dev and pagespeedinsights return issue.
Lighthouse version: ?
Node.js version: ?
Operating System: ?

Extra info

Issues started to occur since thursday, no action were performed on website, we tried modifying appmanifest but it doesn’t seem to be the issue as it is valid and working. ~100 other websites we are tracking regularly do have manifest and they work fine.

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:17 (4 by maintainers)

Top GitHub Comments

2reactions

connorjclarkcommented, Feb 6, 2019

Dug in a bit more. A page can actually use WebSockets (although a connection will always fail). The issue looks to be the long polling. I made a minimal repro here: http://uninterested-badge.surge.sh/index4.html

Without the manifest file, PSI runs fine (no protocol timeout). With the manifest file, it times out.

internal bug: b/124008171

0reactions

lrusikcommented, Feb 5, 2020

The same here http://77.68.7.68/

Top Results From Across the Web

Page domain - Chrome DevTools Protocol

Enables page domain notifications. Page.getAppManifest #. Return Object. url: string. Manifest location.

Lighthouse returned error: PROTOCOL_TIMEOUT. Waiting for ...

Waiting for DevTools protocol response has exceeded the allotted time. (Method: Page.getAppManifest) (PROTOCOL_TIMEOUT" while testing the site https://www.muvi.

Page.setFontFamilies - Vanilla Protocol Viewer

Intercept file chooser requests and transfer control to protocol clients. ... Instead, a protocol event `Page. ... Referenced By. MethodPage.getAppManifest ...

Understanding Selenium Timeouts with Examples

pageLoadTimeout (); Thread.sleep(). Let's discuss each method in detail. 1. implicitlyWait(). This timeout is used to specify the amount of time ...

Getting Started with Headless Chrome - Chrome Developers

If you're using Headless programmatically, this page is also a powerful debugging tool for seeing all the raw DevTools protocol commands ...