You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Load the extension in Chrome and check the browser’s console for any error messages.
Observe the network request failure due to the non-existent URL, and the error on the Service worker debugger, causing the script to fail.
Expected behavior
When following the tutorial, the fetch request to https://extension-tips.glitch.me/tips.json should successfully retrieve the tips.json file without causing any errors. The extension should function properly, displaying or processing the fetched data as described in the tutorial. No network or console errors should occur during the request.
Thanks a lot for the detailed bug report. I just tried the sample and it still works. However, the glitch service might've been suspended (or unavailable), which could've caused this issue.
However, we should replace all links to glitch etc with chrome.dev. //cc @oliverdunk
The step 6 of the tutorial "Handling events with service workers" in Chrome extensions, suggests requesting data from https://extension-tips.glitch.me/tips.json, but the URL is broken, causing the script to fail.
A fix could be updating the URL or providing an alternative endpoint. Here’s the relevant tutorial link: Step 6: Set up a recurring event - Service Worker Events Tutorial.
To Reproduce
Steps to reproduce the behavior, or file the issue is found in:
Expected behavior
When following the tutorial, the fetch request to https://extension-tips.glitch.me/tips.json should successfully retrieve the tips.json file without causing any errors. The extension should function properly, displaying or processing the fetched data as described in the tutorial. No network or console errors should occur during the request.
Screenshots
Notes
Opened a ticket also on Google Issue Tracker https://issuetracker.google.com/issues/370174363
The text was updated successfully, but these errors were encountered: