Failed to register a ServiceWorker for scope (myurl) with script (myurl/sw.js) A bad HTTP response code (404) was received when fetching the script. #377

belkocik · 2022-07-31T20:19:29Z

belkocik
Jul 31, 2022

Hello, in production when I go to dev tools in chrome and then to console I got an error
Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://plumber-app-chakraui.vercel.app/') with script ('https://plumber-app-chakraui.vercel.app/sw.js'): A bad HTTP response code (404) was received when fetching the script.
What is the problem? I even declared in next.config. js sw: "sw.js", but it is default value and it hasn't helped.
my next.config.js

/** @type {import('next').NextConfig} */
const withPWA = require("next-pwa");

const nextConfig = withPWA({
  reactStrictMode: true,
  // swcMinify: true,
  concurrentFeatures: true,
  images: {
    domains: ["media.graphcms.com", "media.graphassets.com"],
  },
  i18n: {
    locales: ["pl"],
    defaultLocale: "pl",
  },
  pwa: {
    dest: "public",
    scope: "/",
// sw:"/sw.js",
    register: true,
    skipWaiting: true,
    disable: process.env.NODE_ENV === "development",
    fallbacks: {
      document: "/pwaOffline",
    },
  },
});

module.exports = nextConfig;

but in development (npm run dev) I got the icon to download as an app:

edit1: on mobile phone in production it works, but in browsers in production it doesn't (i tried chrome and firefox)

belkocik · 2022-08-02T10:01:59Z

belkocik
Aug 2, 2022
Author

I found out that a component DefaultSeo from next-seo library doesn't read

 additionalLinkTags={[
             {
               rel: "icon",
               href: "/favicon.ico",
             },
             {
               rel: "apple-touch-icon",
               href: "/icon.png",
               sizes: "76x76",
             },
             {
               rel: "manifest",
               href: "/manifest.json",
             },
           ]}

in app.js and I got to define it in Head component from Next.js in _document.js file in /pages

    <Head>
          <meta
            name="application-name"
            content="Instalacje Hydrauliczne Krzysztof Niedbalec"
          />
          <meta name="apple-mobile-web-app-capable" content="yes" />
          <meta
            name="apple-mobile-web-app-status-bar-style"
            content="default"
          />
          <meta
            name="apple-mobile-web-app-title"
            content="Instalacje Hydrauliczne Krzysztof Niedbalec"
          />
          <meta
            name="description"
            content="Instalacje gazowe, centralne ogrzewanie, ogrzewanie podłogowe, instalacje hydrauliczne - Hydraulik - Dębica i okolice (Podkarpacie)"
          />
          <meta name="format-detection" content="telephone=no" />
          <meta name="mobile-web-app-capable" content="yes" />

          <link rel="manifest" href="/manifest.json" />
          <link rel="apple-touch-icon" href="/icon.png" />
          <link rel="shortcut-icon" href="/favicon.ico" />
        </Head>

and it now works!

Nevertheless I still got a problem with: offline-fallback-v2 don't routing to _offline.js page when offline

same here: got ann error Application error: a client-side exception has occurred (see the browser console for more information). and it doesn't route to _offline.js (if I slide from up to down - refresh a page) then it shows _offline.js page :/ what is it?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Failed to register a ServiceWorker for scope (myurl) with script (myurl/sw.js) A bad HTTP response code (404) was received when fetching the script. #377

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Uh oh!

Failed to register a ServiceWorker for scope (myurl) with script (myurl/sw.js) A bad HTTP response code (404) was received when fetching the script. #377

Uh oh!

Uh oh!

belkocik Jul 31, 2022

Replies: 1 comment

Uh oh!

Uh oh!

belkocik Aug 2, 2022 Author

belkocik
Jul 31, 2022

belkocik
Aug 2, 2022
Author