Repository navigation
[Service Worker] Uncaught TypeError: undefined is not a function #21292
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] 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
Current behavior
When load "@angular/service-worker": "^5.1.0" on old Chrome version (in this case, 40.0.2214.91), happens an error.
Expected behavior
Service Worker should work in this Chrome version.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
I've been need use bowser to check what is Chrome version to prevent it. This a bad practice.
Environment
Angular version: 5.1.0
Browser:
- [x] Chrome (desktop) version 40.0.2214.91
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: 6.10.2
- Platform: Mac, Linux, Windows
Activity
matpag commentedon Jan 4, 2018
Based on this link: https://jakearchibald.github.io/isserviceworkerready/ service worker on Chrome has been introduced in v40 but "fully" completed only in v49. Maybe the actual implementation is using something which was not available in v40 but introduced later (just thinking). Have you tried with v49 to see if the same error is provided?
felipefialho commentedon Jan 4, 2018
The question is not the
service worker, I don't need thatservice workerworks on old Chrome.My problem is because the app broken on this version if I use
@angular/service-workerand some users of my app use the old Chrome.If I remove the
@angular/service-workerand add a manual implementation of service worker, the app works.gkalpak commentedon Mar 20, 2018
@lfeh, can you provide a non-minified stacktrace (and if possible try with the latest
@angular/service-workerversion).gkalpak commentedon Sep 17, 2018
Closing due to lack of response. Possibly duplicate of #20756 (based on #20756 (comment)).
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.