-
Notifications
You must be signed in to change notification settings - Fork 0
Error
Sorry for the inconvenience.
If you're seeing this page, you might have run into an error with the app.
Here is a list of the possible error codes you might see with links to more details about how to resolve them.
This error indicates that the base browser object, chrome
, is undefined, which is a severe/catastrophic error.
If chrome is undefined, you may have tried installing it in a private or incognito window and it doesn't yet have permission to run in that context. To make it work in Private or Incognito Windows, you'll want to go to your Browser's Extension Options. The steps differ depending on the browser you are using:
Chrome
- Navigate your browser to
chrome://extensions
- Find (App Name) in the Extension List and click the Details Button
- Toggle on
Allow in Incognito
Edge
- Navigate your browser to
edge://extensions
- Find (App Name) in the Extension List and click the Details Button
- Check
Allow in InPrivate
Firefox
- Navigate your browser to
about:addons
- Click (App Name) and then click the Details Tab
- Check
Run in Private Windows
If this doesn't work, please feel free to report an issue.
This error unfortunately indicates that your storage data/settings somehow got cleared or corrupted and needs to be reset. This issue is most likely to occur on Firefox, especially if you keep it disabled and try re-enabling it after a long period of time, although this is mostly based on anecdotal and emperical evidence.
To fix this issue, you can try reseting your data back to the default values using the below methods.
ElemPick Only: Because ElemPick doesn't have an Options Screen, if you're using ElemPick, please uninstall and reinstall it.
To reset your data normally:
- Go to the Options Screen
- An Error Dialog should open up
- Click the Reset Data Button in the Error Dialog to reset your data
If the Options Screen or Error Dialog is blank or non-functional, try the alternative way:
- Go to the Options Screen and Right Click > Inspect anywhere to open up your browser's DevTools
- Click on the Console tab
- In the Console, type and enter the following command:
Options.resetData();
After reseting your data:
- If successful, the data should be reset and you can try refreshing the page to see if the Options screen is functional again
- Infy Scroll Only: If you are relying on optional data like Databases, go to the DATABASES section and re-download them
If this doesn't work, please feel free to report an issue.
This error is unlikely to occur. The app needs to query the browser for the current tab you are on in order to see the current URL. If this fails, this error will be displayed. There is no solution for fixing this so please report an issue if you see this error.
This error indicates the content script could not be injected on the page.
This can be caused by a variety of issues:
- This usually means you just need to wait a few more seconds for this page to finish loading, as the content script isn't injected until the page is idle.
- In very rare situations, the browser may not have injected the content script correctly and you may just need to refresh this page again.
- The extension no longer has its "Site Access" set to "On all sites"; please check your Browser's Extension Settings Page (in Chrome:
chrome://extensions
) by clicking the Manage Button. - You might have another extension that is interfering with it; please try disabling all your other extensions to see if the issue persists.
- It might not have permission to work on this page (for example, protected browser pages).
- The data may be corrupted and you may just need to reset the app's data (OPTIONS > DATA).
If none of these solutions work, please report an issue.
This error is the most common error you'll see. It occurs whenever you try invoking the app on protected browser pages, extension pages, error pages, the new tab page, or any URL in which it doesn't have permission to work on. This also includes missing file pages, which are considered to be protected error pages by your browser. Usually, there isn't much that can be done in this situation because the browser itself is preventing the app from working on the page. However, if you feel like it should be working on the page, please feel free to report an issue.
This error indicates that the app ran into an exception at runtime. You should be able to see the reason for the exception displayed. One possible reason might be that you tried invoking the app on a protected page, like your browser's web store (e.g. the Chrome Web Store or AMO). Sometimes, it may also be due to a bug in the app. Exceptions can be caused by a wide variety of issues so the best way to resolve this is to report an issue.
As a last resort, you can try the following:
- Disable and re-enable it.
- Uninstall and reinstall it again, although this will clear and reset your entire data.
- And lastly, as always, please feel free to report an issue.