What should I do if Lime Go stops responding?
Of course, if you are experiencing problems with Lime Go, you should contact our support. But there are some things you could do yourself that would make our developers really happy.
You could begin with not reloading your browser or the tab in your browser that Lime Go are running in. There is a lot of valuable information in the browser if Lime Go is in some kind of state where it’s not responding.
The thing you could do to help us is taking a screenshot of something that is called “the console”. In every browser there is something called “developer tools”. No matter what browser you are using, they all have a console, and it contains all the valuable information.
You can give us this information by doing the following:
If you are using Google Chrome, Microsoft Edge, Opera or Firefox:
- Right click wherever you want in Lime Go.
- Press the “inspect element” alternative.
- The developer tools will now appear in the web browser window. Press the tab(in the dev tools) that is called “console”
- Now take a “screenshot” on the consoles content.
If you are using Safari:
- If you don’t have the “Show developer tools” options active you will have to put it on(If you already have it activated skip the 3 following steps. You probably don’t have it activated). Press “Safari” in the Mac OS menu bar (the upper left corner of your screen).
- Then click at the “preferences” alternative.
- Then click at the “advanced” tab (to the right).
- In the bottom of the settings form you click at the checkbox that says “Show Develop menu in menu bar” (the checkbox should be checked).
- Right click wherever you want in Lime Go.
- Press the “inspect element” alternative.
- The developer tools will now appear in the web browser window. Press the tab (in the dev tools) that is called “console”
- Now take a screenshoot on the “console” content.
Give this/these screenshots to our support (they will give you options on how to send it to us) together with a description of what you are experiencing is wrong with the app.
0 Comments