Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

491
Visualizações
Service Worker: The event handler is already finished (even though called synchronously from the event handler)

I have read and think I understand:

  • What does event.waitUntil do in service worker and why is it needed?
  • Service worker error: event already responded to

The just of those answers is that event.waitUntil() must be called synchronously from the event handler. Which is what I am doing below (in fact it is the only line of the event handler):

The Error

Uncaught (in promise) DOMException: Failed to execute 'respondWith' on 'FetchEvent': The event handler is already finished.

Min reproducible example:

self.addEventListener("fetch", (event) => event.waitUntil(handleFetch(event)));

async function handleFetch(event) {
    const response = await runFetch(event);
    event.respondWith(response);  // <---- here the error is raised
}

async function runFetch(event) {
    const response = await fetch(event.request.url);

    if (response.ok) {
        // Don't await cachePut, allow the response to be returned immediately first.
        // Then later it will perform the cachePut promise. Use waitUntil so the Service worker is not killed until the cachePut promise resolves.
        event.waitUntil(cachePut(event.request.url, response.clone()));
    }
    return response
}

async function cachePut(url, response) {
    const cache = await caches.open('my-cache');
    await cache.put(url, response)
}

Note: It seems okay to call waitUntil multiple times (calling waitUntil in a nested sense for cachePut): MDN:

The waitUntil() method must be initially called within the event callback, but after that it can be called multiple times, until all the promises passed to it settle.

about 4 years ago · Juan Pablo Isaza
1 Respostas
Responde à pergunta

0

TLDR: respondWith wait before ending the .event waitUntil wait before killing the service worker.

The differences between respondWith and waitUntil seem obvious at first, but the context is slightly different. If one uses respondWith, then waitUntil is implicit, i.e. can't respond until respondWith completes.

Originally I would bypass the Service worker and not use respondWith in some situations, but I guess then it doesnt know I am still figuring out whether to respond or not, and assumes the event is done. So if I wish to bypass the SW, I just return fetch(event.request), and use respondWith instead.

self.addEventListener("fetch", (event) => { event.respondWith(handleFetch2(event)) });

async function handleFetch2(event) {
    const response = await runFetch2(event);
    return response;
}

async function cachePut2(url, response) {
    const cache = await caches.open('my-cache');
    await cache.put(url, response)
}

async function runFetch2(event) {
    const response = await fetch(event.request.url);

    if (response.ok) {
        event.waitUntil(cachePut2(event.request.url, response.clone()));
    }
    return response
}
about 4 years ago · Juan Pablo Isaza Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda