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.

Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

See original GitHub issue

Bildschirmfoto 2019-11-04 um 09 39 44 NWJS Version : 0.42.* Operating System : macOS 10.13.6, Windows 10, Ubuntu 18.4

Expected behavior

Normal app start, should load index.html & local js, css etc. files.

Actual behavior

App does not load local files (js, css etc.) Works fine with Version 0.41.3

Console Error: Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

chrome-extension://elfmfcoigbbelagnlofklbjhcfpcfhgm/css/app.95551f8f.css chrome-extension://elfmfcoigbbelagnlofklbjhcfpcfhgm/js/app.cc02e1af.js chrome-extension://elfmfcoigbbelagnlofklbjhcfpcfhgm/js/chunk-vendors.28b718c5.js chrome-extension://elfmfcoigbbelagnlofklbjhcfpcfhgm/favicon.ico

How to reproduce

Build with: nw-builder-webpack-plugin

<!DOCTYPE html>
<html lang=en>
<head>
    <meta charset=utf-8>
    <meta http-equiv=X-UA-Compatible content="IE=edge">
    <meta name=viewport content="width=device-width,initial-scale=1,shrink-to-fit=no">
    <link rel=icon href=/favicon.ico>
    <title>vue-nw-webpack</title>
    <link href=/css/app.95551f8f.css rel=preload as=style>
    <link href=/js/app.cc02e1af.js rel=preload as=script>
    <link href=/js/chunk-vendors.28b718c5.js rel=preload as=script>
    <link href=/css/app.95551f8f.css rel=stylesheet>
</head>
<body>
<noscript><strong>We're sorry but vue-nw-webpack doesn't work properly without JavaScript enabled. Please enable it to
    continue.</strong></noscript>
<div id=app></div>
<script src=/js/chunk-vendors.28b718c5.js></script>
<script src=/js/app.cc02e1af.js></script>
</body>
</html>

Issue Analytics

State:
Created 4 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

rogerwangcommented, Nov 8, 2019

This is fixed in git and will be available in the next nightly build.

1reaction

rogerwangcommented, Nov 8, 2019

Before it’s fixed, you can workaround it by adding --disable-features=ProcessSharingWithDefaultSiteInstances to the command line arguments or chromium-args field in the manifest.