Title: ServiceWorker: Uncaught exception DomException in Chrome · Issue #49021 · angular/angular · GitHub
Open Graph Title: ServiceWorker: Uncaught exception DomException in Chrome · Issue #49021 · angular/angular
X Title: ServiceWorker: Uncaught exception DomException in Chrome · Issue #49021 · angular/angular
Description: 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...
Open Graph Description: 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...
X Description: 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...
Opengraph URL: https://github.com/angular/angular/issues/49021
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ServiceWorker: Uncaught exception DomException in Chrome","articleBody":"### Which @angular/* package(s) are the source of the bug?\n\nservice-worker\n\n### Is this a regression?\n\nNo\n\n### Description\n\nThis bug https://github.com/GoogleChrome/workbox/issues/792 still reproduces in some cases in spite of fix https://github.com/angular/angular/pull/26042\r\n\r\nIt reproduces in Chrome 77, 78, 79, 80 and an error appeared:\r\nUncaught (in promise) DOMException: Entry was not found.\r\n\r\nIt reproduces in Angular 11, 12, 14.\r\nIt reproduces in MacOs and Windows.\r\n\r\nSteps for reproduce:\r\n\r\n- create new Angular app (v14, for example)\r\n- add ServiceWorker to the project\r\n- build and run project\r\n- install Chromium v80 https://chromium.cypress.io/mac/stable/80.0.3987.163 and open\r\n- in 1st tab open the running project\r\n- in 2nd tab open the running project\r\n- in 2nd tab go to DevTools > Application > Storage and click the button \"Clear site data\"\r\n- go to 1st tab and refresh the page (F5)\r\n- refresh the page again (F5)\r\n- after that the page will crash and the error appear: `Uncaught (in promise) DOMException: Entry was not found.`\r\n\n\n### Please provide a link to a minimal reproduction of the bug\n\n_No response_\n\n### Please provide the exception or error you saw\n\n```true\nUncaught (in promise) DOMException: Entry was not found.\n```\n\n\n### Please provide the environment you discovered this bug in (run `ng version`)\n\n```true\nBrowser: Chrome 77, 78, 79, 80\r\nAngular: 11, 12, 14.\r\nOS: MacOS and Windows\n```\n\n\n### Anything else?\n\n_No response_","author":{"url":"https://github.com/anton-marchenko","@type":"Person","name":"anton-marchenko"},"datePublished":"2023-02-10T10:07:36Z","url":"https://github.com/angular/angular/issues/49021"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:5e8260da-5b5c-bc01-195d-834e171a71f2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B20C:1D8AA1:10C3FD9:161BBDC:6B010857 |
| html-safe-nonce | 0e41d72355b893b682dde99d7f14eac40db10828cdf0f419679d0a40e1bad780 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMjBDOjFEOEFBMToxMEMzRkQ5OjE2MUJCREM6NkIwMTA4NTciLCJ2aXNpdG9yX2lkIjoiMTAzNTcwNjA1MDY4ODM4NzE1OSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 24758a6ac715651596dc3dcccfa5f61661f00d70570d02ecc1fad5fcef2aa822 |
| hovercard-subject-tag | issue:1579394840 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/49021/issue_layout |
| twitter:image | https://opengraph.githubassets.com/f2e569657861871f7941b1c0c2cde79195b102ad2227cf60e288d632c449ca7d/angular/angular/issues/49021 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/f2e569657861871f7941b1c0c2cde79195b102ad2227cf60e288d632c449ca7d/angular/angular/issues/49021 |
| og:image:alt | 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... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | anton-marchenko |
| hostname | github.com |
| expected-hostname | github.com |
| None | cb7fa109eca7d4156c889f474306b0e91336055e9adf8fd4684b61e49094d124 |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular git https://github.com/angular/angular.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 24195339 |
| octolytics-dimension-repository_nwo | angular/angular |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24195339 |
| octolytics-dimension-repository_network_root_nwo | angular/angular |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 2b59d31a4e44f08b7af67a4b67f8fd0af3befe2a |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width