LearnNewsExamplesServices
Frontmatter
id6860
titlenew ServiceWorker versions are being stuck inside a waiting state
stateClosed
labels
bugenhancementhelp wantedgood first issue
assignees[]
createdAtJun 24, 2025, 2:16 PM
updatedAtJul 10, 2025, 2:15 PM
githubUrlhttps://github.com/neomjs/neo/issues/6860
authortobiu
commentsCount0
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtJul 10, 2025, 2:15 PM

new ServiceWorker versions are being stuck inside a waiting state

Closed v10.0.0-beta.6 bugenhancementhelp wantedgood first issue
tobiu
tobiu commented on Jun 24, 2025, 2:16 PM
  • not v10 related
  • I noticed a change how chrome handles SWs: before, deploying a new version automatically switched to the new SW, now it still starts, but keeps being locked inside a waiting state.
  • We need to explore the code and ensure that skipWaiting() does get triggered.
Image

Since this is not directly related to the neo core, other interested devs could jump in on this one.

tobiu added the bug label on Jun 24, 2025, 2:16 PM
tobiu added the enhancement label on Jun 24, 2025, 2:16 PM
tobiu added the help wanted label on Jun 24, 2025, 2:16 PM
tobiu added the good first issue label on Jun 24, 2025, 2:16 PM
tobiu referenced in commit 6d626f9 - "new ServiceWorker versions are being stuck inside a waiting state #6860" on Jul 10, 2025, 2:15 PM
tobiu closed this issue on Jul 10, 2025, 2:15 PM