-
Notifications
You must be signed in to change notification settings - Fork 26
How To Make An Issue
Go to the issues page and click "New Issue" in the top right. Depending on your issue, you may be asked to collect different things to debug it. But, in general, it's a good idea to at least include your browser information and extension version along with a brief description of the problem.
Blue Blocker is available on both Chrome and Firefox, though it can be used by any chromium based browser. If you're not using Chrome or Firefox, you may need to google how to retrieve your browser version
- In the top right corner of the browser window click the 3 vertical dots next to your profile icon and click
Settings
- On the left side of this page, click
About Chrome
at the bottom of the list - Below the Chrome logo it should say "Version xxx.x.xxxx.xxx (Official Build) (something)"
- In the top right corner of the browser window click the 3 horizontal next to your profile icon and click
Settings
- search "version" in the search bar
- version information should be highlighted that says "Version xxx.x.x (64-bit)"
Include both this version info along with your OS!
ex: Chrome Version 114.0.5735.198 (Official Build) (arm64) on MacOs
or: Firefox 114.0.2 64 bit on Windows 11
In order to know what version of the extension this error is in, or even if it's already been fixed in a newer version, we need to know what extension version you're using.
- Find the extension logo in your browser toolbar. On most browsers, they will be in the top right of the window, next to the browser's URL bar
- note: Your extension might be in a list with other extensions. These are usually found by clicking a puzzle piece found at
1.
- note: Your extension might be in a list with other extensions. These are usually found by clicking a puzzle piece found at
- Just click the extension logo, this will open up a menu that shows the extension version in the top right in the form
vX.X.X

Depending on the issue you're experiencing, you may need to include more or fewer logs listed here. In general, at least include twitter logs, depending on your issue someone may ask you to include more info and will link you to the appropriate steps to take to get it!
These are not logs made by twitter, rather extension logs made while on twitter.com or tweetdeck, as opposed to other pages.
- Go to twitter.com or tweetdeck (where ever the error is occuring for you
- Open your browser's Developer Tools by pressing F12 (fn+F12 on mac) or Ctrl+Shift+J (Cmd+Option+J on mac)
- If not already open, find the tab labelled
Console
at the top of the Developer Tools panel - Find recent logs and errors labelled
[Blue Blocker]
and add them to your issue- older versions of Blue Blocker sometimes output sensitive information in the developer console. be sure to check anything you put in an issue and remove anything with the terms
auth
orauthorization
- older versions of Blue Blocker sometimes output sensitive information in the developer console. be sure to check anything you put in an issue and remove anything with the terms
[Chrome]
- Click the puzzle piece in your browser toolbar, to the left of your profile icon and click "Manage Extensions" at the bottom
- In the top right of the page, make sure "Developer mode" is enabled
- Find Blue Blocker in the list and click "service worker" next to "Inspect views"
- this might also say "service worker (Inactive)" and that's totally normal
- If there is a button labelled "Errors" also take note of everything in there
[Firefox]
- Go to
about:debugging#/runtime/this-firefox
in your browser's url bar - Find Blue Blocker in this list and click the "Inspect" button in the top right of the item