Smokeball Web App troubleshooting guide

Available on Smokeball Bill, Boost and the Grow and Prosper+ Cloud Companion App

Use this troubleshooting guide to resolve issues with the Smokeball Web App, which powers Smokeball Bill, Smokeball Boost and the Grow/Prosper+ web app products.

Use Google Chrome

The Smokeball Web App runs best on Google Chrome. Using other browsers may cause performance and display issues.

Replicate the issue in an incognito window

Issues with data syncing or discrepancies in your billing may be caused by the cookies saved to your Google Chrome browser. Check if the issue fixes itself when logging in to the web app via an incognito window:

  1. In Google Chrome, select the three dots on the top-right corner of the browser, then click on New Incognito Window. Alternatively, press Ctrl+Shift+N on your keyboard.
  2. Open in the incognito window and log in with your details.
  3. Check if the data sync or discrepancies in billing figures have resolved themselves in the incognito window.

Delete Smokeball Web App cookies

If the Smokeball Web App displays data correctly in the incognito window, then you will need to delete the Smokeball web cookies from your browser:

  1. In a regular Google Chrome browser, select the three dots on the top-right corner, then click on Settings.
  2. Select Privacy and security from the left panel, then select Third-party cookies.
  3. Click on See all site data and permissions.
  4. Search for "" in the search bar. Then, click on the entry and delete the entry for
  5. Close and reopen Google Chrome. Log back into and check if the issue has been resolved.

Further troubleshooting

If the issue persists after deleting Smokeball Web App cookies, try the following steps:

  • Perform a hard refresh of Google Chrome by holding Ctrl+F5 with the web app open.
  • Disable any third-party extensions such as ad-blockers. Do not disable any Smokeball Chrome extensions.
  • Log out and log back into the web app.

As a last resort, contact Smokeball Support to conduct further troubleshooting, such as gathering console logs and hardware information.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section