Skip to content

ServiceWorker: Uncaught exception DomException in Chrome #49021

Closed as not planned

Description

@anton-marchenko

Which @angular/* package(s) are the source of the bug?

service-worker

Is this a regression?

No

Description

This bug GoogleChrome/workbox#792 still reproduces in some cases in spite of fix #26042

It reproduces in Chrome 77, 78, 79, 80 and an error appeared:
Uncaught (in promise) DOMException: Entry was not found.

It reproduces in Angular 11, 12, 14.
It reproduces in MacOs and Windows.

Steps for reproduce:

  • create new Angular app (v14, for example)
  • add ServiceWorker to the project
  • build and run project
  • install Chromium v80 https://chromium.cypress.io/mac/stable/80.0.3987.163 and open
  • in 1st tab open the running project
  • in 2nd tab open the running project
  • in 2nd tab go to DevTools > Application > Storage and click the button "Clear site data"
  • go to 1st tab and refresh the page (F5)
  • refresh the page again (F5)
  • after that the page will crash and the error appear: Uncaught (in promise) DOMException: Entry was not found.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Uncaught (in promise) DOMException: Entry was not found.

Please provide the environment you discovered this bug in (run ng version)

Browser: Chrome 77, 78, 79, 80
Angular: 11, 12, 14.
OS: MacOS and Windows

Anything else?

No response

Activity

  1. added this to the needsTriage milestone on Feb 10, 2023
  2. JoostK commented on Feb 10, 2023

    @JoostK
    Member

    Does this reproduce in Chrome 105+? Chrome 80 is quite old and not officially supported.

  3. anton-marchenko commented on Feb 10, 2023

    @anton-marchenko
    Author

    @JoostK This does not reproduces in Chrome 105+

    The problems is that a lot of our users can not update Chrome above v80 yet.
    Are you sure that Chrome 80 is old? It released in april 2020 (3 years ago). It does not seems too old soft in my opinion.

  4. JeanMeche commented on Feb 10, 2023

    @JeanMeche
    Member

    In a world of evergreen browsers, that's definitely old.

  5. anton-marchenko commented on Feb 10, 2023

    @anton-marchenko
    Author

    Looks like workaround will solve my issue:

    // pseudo code:
    if (!isOldChrome()) ServiceWorkerModule.register('ngsw-worker.js');
    
  6. PhuocHoangMinhNguyen commented on Apr 16, 2024

    @PhuocHoangMinhNguyen

    It is happening for me on Chrome Version 123.0.6312.123. Is anyone having issue with the same version?

  7. Waregalias commented on Jun 19, 2024

    @Waregalias

    Same problem with Chrome version 126.0.6478.61

  8. JeanMeche commented on Aug 29, 2025

    @JeanMeche
    Member

    with #63364 we've announced that the service-worker package in now in maintenance mode and will not receive feature PRs and feature requests.

    The message is also visible here: https://angular.dev/ecosystem/service-workers

  9. angular-automatic-lock-bot commented on Sep 29, 2025

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  10. locked and limited conversation to collaborators on Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: service-workerIssues related to the @angular/service-worker package

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions