227072 2021-06-16 08:39:15 -0700 Service worker sometimes inactive after browser start up 2022-03-14 03:38:02 -0700 1 1 1 Unclassified WebKit Service Workers Safari 14 Mac (Intel) macOS 11 RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 marian.schaub webkit-unassigned cdumez webkit-bug-importer youennf oldest_to_newest 1770197 0 marian.schaub 2021-06-16 08:39:15 -0700 We are witnessing a strange behaviour in Safari Desktop regarding service workers when the browser is initially started. Steps to reproduce: 1. Visit https://sw-lifecycle-test.app.baqend.com/swTest/test.html . The Page will display "No SW Response" and install a simple service worker. 2. Close Safari (command+Q). 3. Open Safari and visit https://sw-lifecycle-test.app.baqend.com/swTest/test.html again. While repeating steps 2 + 3 we saw different outcomes. Our expectation would be to always see "SW Response" since the installed service worker simply intercepts the html request and delivers a page with that content. What we found is sometimes the page displayed "SW Response", but often displayed "No SW Response". In these cases we did not see a service worker in Develop -> Service Workers context menu, but navigator.serviceWorker.controller referenced the correct service worker. Reloading (both soft and hard reload) did not reliably lead to the service worker being activated again. We were able to reproduce this on serveral Mac Book Pro machines running Safari 14.1.1 (16611.2.7.1.4). After analyzing our tracking data we estimate about 4% of the Safari page impressions on our customers pages are affected by this. 1770709 1 cdumez 2021-06-17 10:10:07 -0700 I personally haven't been able to reproduce this yet on Safari 15 beta. I see "SW response" every time I relaunch Safari. 1771944 2 webkit-bug-importer 2021-06-23 08:40:31 -0700 <rdar://problem/79667318> 1850044 3 youennf 2022-03-10 05:18:18 -0800 @marian.schaub@baqend.com, can you still reproduce the issue with Safari 15? 1850123 4 marian.schaub 2022-03-10 09:03:47 -0800 Hello Youenn, the issue seems to be resolved, we were not able to reproduce it in Safari 15, thanks.