Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken URL in Service Worker Events Tutorial for Chrome Extensions #1296

Open
ifthenelse opened this issue Sep 28, 2024 · 1 comment
Open

Comments

@ifthenelse
Copy link

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:

  1. Navigate to the Service Worker Events tutorial on the Chrome Developer site.
  2. Follow the instructions to set up the extension, including making a fetch request to https://extension-tips.glitch.me/tips.json.
  3. Load the extension in Chrome and check the browser’s console for any error messages.
  4. 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.

Screenshots
Screenshot 2024-09-28 at 18 24 26

Notes
Opened a ticket also on Google Issue Tracker https://issuetracker.google.com/issues/370174363

@sebastianbenz
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants