Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to load resource: the server responded with a status of 404 #174

Open
DidoMarchet opened this issue Nov 5, 2024 · 2 comments
Open

Comments

@DidoMarchet
Copy link

If I return to the website a few days after the latest deployment, I get this error, and the app crashes.

Failed to load resource: the server responded with a status of 404 ()Understand this errorAI
console.js:36 [nuxt] Error fetching app manifest. FetchError: [GET] /_nuxt/builds/meta/0d7d8353-1eb2-475f-a7e1-8b14be13c893.json”: 404
    at async o (ofetch.37386b05.mjs:268:15)
(anonymous) @ console.js:36
Show 1 more frame
Show lessUnderstand this errorAI
console.js:36 [nuxt] error caught during app initialization Xy: [GET] /_nuxt/builds/meta/0d7d8353-1eb2-475f-a7e1-8b14be13c893.json”: 404
    at async o (https://zavaluce.it/_nuxt/NeSLdRRW.js:19:19811)Caused by: FetchError: [GET] “/_nuxt/builds/meta/0d7d8353-1eb2-475f-a7e1-8b14be13c893.json”: 404
    at async o (ofetch.37386b05.mjs:268:15)
(anonymous) @ console.js:36
Show 1 more frame
Show lessUnderstand this errorAI
console.js:36 Xy: [GET] /_nuxt/builds/meta/0d7d8353-1eb2-475f-a7e1-8b14be13c893.json”: 404
    at async o (https://zavaluce.it/_nuxt/NeSLdRRW.js:19:19811)Caused by: FetchError: [GET] “/_nuxt/builds/meta/0d7d8353-1eb2-475f-a7e1-8b14be13c893.json”: 404
    at async o (ofetch.37386b05.mjs:268:15)
(anonymous) @ console.js:36
Show 1 more frame
Show lessUnderstand this errorAI
console.js:36 Hydration completed but contains mismatches.
(anonymous) @ console.js:36
Show 1 more frame
Show lessUnderstand this errorAI

If I clear all site data, it starts working again.

My configuration:

export default {
  pwa: {
    registerWebManifestInRouteRules: true,
    scope: '/',
    base: '/',
    manifest: {
      name: process.env.SITE_NAME_FRONTEND,
      useWebmanifestExtension: false,
    },
    injectRegister: 'auto',
    registerType: 'autoUpdate',
    workbox: {
      globPatterns: ['**/*.{js,css,html,png,svg,ico}'],
      runtimeCaching: [
        {
          urlPattern: '/',
          handler: 'NetworkFirst',
        },
      ],
      navigateFallback: undefined,
    },
  },
}

How can I fix this issue?
Any advice would be appreciated because it's a bit problematic.

Thanks and kind regards;

Davide

@userquin
Copy link
Member

userquin commented Nov 5, 2024

Check cache headers for all your pages

@DidoMarchet
Copy link
Author

Hi @userquin , thanks! Sorry to ask, but I’m not very experienced with PWAs 😅. I didn’t set any cache time myself, I’m just using netlify-edge with their cache settings.
Are there any parameters I can change in my PWA configuration or my settings are ok?
Thanks and kind regards,
Davide

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants