-
Notifications
You must be signed in to change notification settings - Fork 0
1.2.8 "can't verify license" #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think it's an internet connection issue, especially if it worked before. Hopefully it should work if you try again? This dialog will soon go away and be replaced with a more traditional activation flow, which will also work offline (like IntelliJ does it). |
Just bumping this up. I am on 1.3.0 and getting same error. I think company firewall is blocking the internet connection from Ultorg. |
Thanks for the report! Yes, this happens when the beta version of Ultorg is unable to access the Internet on startup (which is often the case in corporate environments that block all apps other than Chrome from the Internet). I'm working on the billing & license management system for the public release of Ultorg, which will include an offline activation option. |
Ultorg is now out of beta! The new versions have a new activation mechanism which should make the app work completely offline after initial activation. The initial activation can also be done offline via an activation code. I've also changed a few things to try to make the online activation mechanism work better with corporate proxy servers. Initially, Ultorg will be a paid app with a free trial period, available at https://www.ultorg.com/
Oh, and i missed this question before. When Ultorg is open, you can right-click the data source icon in the Folders pane and click "Refresh Table Metadata". |
Just updated to 1.2.8 and it's great but I restarted it so it would detect new tables (how to do it without restart btw?) and stopped working - just displays "Could not verify license" and then exits ((
The text was updated successfully, but these errors were encountered: