HOWTO: Debugging

There are two primary methods of figuring out what is going wrong with SaltyBoy. First is Verbose Debugging which allows users to see what the extension is doing, how it's betting and any other factors that might be in play. As well if you feel like the extension pop-up window is not reflective of what the app is doing you can also Dump Settings which allows users to verify what SaltyBoy has stored in the extension storage.

Verbose Debugging

1. Open the SaltyBoy pop-up and ensure debugging is enabled under "Debug Information":

2. Navigate to chrome://extensions.

3. Ensure "Developer mode" is enabled.

4. Locate "Salty Boy" extension in the cards and click on the "service worker" link. This should pop-open a Chrome inspector window, leave this window open.

5. Navigate to SaltyBet and the inspector window should now include verbose debug information about what it is doing.

6. Send screen grabs or copy paste logs for further investigation in a GitHub issue.

Dump Settings

1. Navigate to "Debug Information" and click on "Alert & Log Local Storage".

2. This should pop open an alert window with all the information stored locally.

Note: This may not show all available information and some of it may be cut-off with a .... When you hit this button if you follow Verbose Debugging this should also console log the information.