You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand this is kind of a tricky thing but I just experienced some glitches where the API was unreachable (could be something on my end) and during that time frame the tool just shut down when I tried to set up a new connection. This kind of scared me as this means the tool is completely useless if something happens to your server and/or routing issues. Luckily the API was back in a few minutes and it started working again. Please implement some kind of local fallback check so I can continue using the tool if something is flaky when doing this license check.
edit: Turns out it was my flaky Nordlayer VPN connection with the slowest DNS resolver in the world but still a valid point I think?
The text was updated successfully, but these errors were encountered:
Hi, thanks for opening the issue. That is a valid point, I wonder how other tools manage this. For a desktop application it's less of a problem because the application is used for a long time, so the license check can always be async/delayed 🤔
We are also brainstorming on a future major version for 7777, I'm keeping this in mind.
I understand this is kind of a tricky thing but I just experienced some glitches where the API was unreachable (could be something on my end) and during that time frame the tool just shut down when I tried to set up a new connection. This kind of scared me as this means the tool is completely useless if something happens to your server and/or routing issues. Luckily the API was back in a few minutes and it started working again. Please implement some kind of local fallback check so I can continue using the tool if something is flaky when doing this license check.
edit: Turns out it was my flaky Nordlayer VPN connection with the slowest DNS resolver in the world but still a valid point I think?
The text was updated successfully, but these errors were encountered: