Repository navigation
FetchEvent.respondWith received an error: TypeError: Internal error (WebKitServiceWorker: 0) #26500
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
Current behavior
On Safari, if you have service worker registered, when you "Empty Cache" and refresh page, you get an error:
Expected behavior
There should be polyfill that fixes this error.
Minimal reproduction of the problem with instructions
- Register service worker on project
- Open in safari
- Empty cache
- Refresh page
What is the motivation / use case for changing the behavior?
To make service worker workable in Safari
Environment
Angular version: 6.1.9
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [x] Safari (desktop) version 12.0
- [x] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: 10.10.0
- Platform: Mac
Others:
Activity
gkalpak commentedon Oct 17, 2018
I am not sure what the exact problem is, but it has hopefully been fixed by #26042.
It is included in 7.0.0-beta.7+, but not in 6.x yet (not sure if there is going to be another 6.x release).
Closing this as "fixed", but feel free to open a new issue if you try with the latest version and it is still a problem.
NourasHamwi commentedon Oct 30, 2018
I am having the same error.
NourasHamwi commentedon Oct 30, 2018
I am having the same problem, I am not able to access angular.io from Safari 12.0, but when entering responsive mode, the website works.
feat(service-worker): exports RegistrationOptions
angular-automatic-lock-bot commentedon Sep 14, 2019
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.