Can't sign in to the ActiveState Platform in Komodo IDE 12

[jimtut]

Short Summary

I installed the new Komodo IDE 12, and created an AS Platform acct. I can sign into the Platform on the web, but when I try to use the same creds in the IDE, I get an error.

Steps to Reproduce

Launch IDE, log into Platform

Expected results

Platform login, IDE opens

Actual results

Error message "Saving private key failed with: You are not authenticated. Please restart Komodo is this problem persists.". Cancelling the login after this closes the IDE, so I can't even use it! Restarting Komodo always gives the same results.

Platform Information

Komodo Edit or IDE? IDE
Komodo Version? 12
Operating System (and version)? macOS 10.13.6

Additional Information

IDE won't stay running long enough for me to access this menu.

[jimtut]

Some additional info. I repeated the same install on my Windows 10 laptop, and get the exact same error, using the same Platform login.

I actually have an additional Platform login thru my company, and I tried using that login (both as email and as a username), and I still always get the same error.

I don't think Komodo 12 is working at all...

[th3coop]

@jimtut sorry for the frustrating experiencing.
Please grab / check the following:

• After starting Komodo and producing the login fail:
  • grab Komodo logs, per platform config folder locations ref: https://community.activestate.com/faq/komodo-file-locations
  • grab state tool logs:
    • Windows: %AppData%\ActiveState\cli-unstable\log.txt
• confirm the state tool was installed.
  • On Windows: %AppData%\ActiveState\bin\state.exe
  • On OSX: ~/Library/Applicatation Support/KomodoIDE/12.0/XRE/state/state
• See if the state tool is available in a terminal:
• open a terminal and run which state
  • IF it's available, run state --version and send me the info. Also try logging in with it.
  • ELSE try to login to the platform using the relevant install path I listed above.

That should give us some good info to work from.

[jimtut]

I've attached all the logs from the previous failure here.
pystderr.log
pystdout.log
log.txt

State tool is installed: C:\Users\tuttlj\AppData\Roaming\ActiveState\bin\state.EXE

Version:
ActiveState CLI version 0.2.2-3479
Revision ba4b6770ac4143cb0e0cfec39e381881291a2ac3
Branch unstable
Built Sat Jan 4 2020 00:01:02 +0000 GMT

I just tried "state auth" and got:

Keypair generated successfully
You have successfully authenticated, hello jtuttle!

After using state.exe to sign in, I was able to launch Komodo 12, sign in again in the UI, and it worked! I can access the full IDE now. I'll repeat on the Mac later, but this might be a good workaround for now...

[th3coop]

@jimtut, thanks for reporting back so quick. Could you use the state tool to log out in the terminal the Help > Troubleshooting > Restart in Safe-Mode in Komodo? You should get the login dialog again. Please let me know if you get the same error.

Note to self: The terminal session shouldn't effect the Komodo authentication. Looking at the code it looks like we might be throwing away the error coming from the state tool when we try to grab your auth key after the login dialog succeeds. I've pushed a patch to not over write that error output:
https://github.com/Komodo/KomodoIDE/commit/d323b4093b004de1846a3dd5f19d35966975815c

[jimtut]

I launched my original Komodo IDE 12 again, and it did NOT prompt to login, and came right up. I did "state auth logout", and then restarted in Safe Mode. Komodo prompted me to go thru the init screens again (Color Scheme, etc.) and then prompted me to login.

The login failed, but the error was actually different this time!
Saving private key failed with: You need to be authenticated to run this command. Authenticate by running 'state auth'.

[jimtut]

Oh, the linked patch above is not available, at least not to me.

[th3coop]

Oh, the linked patch above is not available, at least not to me.

The IDE repo is private. That comment was a "note to self". The patch won't help any way. I've reverted it since.

I had a look through the code and I unfortunately asked you to grab the wrong log file for the state tool. On Windows it will be in [your Komodo profile folder]\XRE\state\log.txt.

I'm going to get you to test this slightly differently too:

• stop Komodo
• open a cmd terminal
• run the following commands
  • > set VERBOSE=true
  • > set KOMODO_USERDATADIR=C:\path\to\some\temp\dir
• Start Komodo from this terminal, should just be able to type komodo and press enter.
• Reproduce the issue and when the error is in the dialog, grab the log file mentioned above but make sure you look in the %KOMODO_USERDATADIR% you set.

I have to ask one dumb question: When you get that error, have you tried clicking Sign In again?

I've spent a good few hrs trying to reproduce this issue in numerous ways but am having no luck. Thanks fully so far you seem to be special in reproducing this.

[jimtut]

To answer the not-so-dumb question, yes, I had tried to repeatedly login using the dialog (without closing it).

But, something has changed (at least on my PC) since using the state tool and restarting in Safe Mode. Whether using regular mode or Safe Mode, I can now login thru the IDE/UI to the state platform. I will try on my Mac tonight to see if that's working. I'm attaching the new/temp state log, in case that's helpful.

But, unless I can repeat this on my Mac tonight (and I haven't done ANY of the state tool or safe-mode actions there), I doubt the log will show you much.
log.txt

[th3coop]

@jimtut thanks for the heads up and new logs. Nothing helpful in those logs unfortunately. That's a pain but not your problem. At least we've got you up and running. Thanks for your patience!

If anyone else comes across this, please grab the logs mentioned in this comment:
#3817 (comment)

[jimtut]

Some more info from my Mac:

• I still can't login directly on my Mac

• The state tool does not exist, at least for me. The directory ~/Library/Application Support/KomodoIDE/12.0/XRE/state/ exists, but it's empty.

• I renamed the existing 12.0 dir above, relaunched from the Finder icon, and got the same login error (and still nothing in the state/ dir).

• I was going to try the verbose stuff above, but before that, I decided to try launching komodo from the Mac Terminal. When doing so, several "good" things happened:

1. I was able to login!
2. The state/ director finally got populated, with the state tool and a log file (attached)
3. Closing komodo (the one launched from the Terminal) and then relaunching from the Finder icon allows the IDE to open (no more login prompts).
   log.txt

My (amateur) conclusions:

1. The Mac problem was solved by launching from komodo from the Terminal, which finally installed the state tool and allowed me to login.
2. The Windows problem seemed to be solved by running the state cmd, although it's possible that I launched Komodo once from the command-line right before trying "state". So, it's possible that it's the same underlying problem, you need to run komodo from the command-line in order for the state tool to get properly installed.

I only have my Mac right now (back at home), but I can confirm my conclusion #1 above is correct by removing that 12.0 dir in App Support (and thus removing the state dir). When launching Komodo from the Finder, the state tool does NOT exist after going thru the init screens, and I can't login.

But, when launching from the Terminal, the state dir is created during the init process, and then the state executable is copied into that that dir. But, when launching a fresh install from the Finder, only the state dir is created, the state executable is not copied.

I'd bet the same thing happened on Windows too...

[th3coop]

I'd bet the same thing happened on Windows too...

I'll try this right now. Thank you very much for the follow up @jimtut.

[th3coop]

No dice on Windows. And the repro steps don't work on Mac either :(

[th3coop]

I'll have another go at this tomorrow with fresher eyes.

[shawnlaffan]

I get the same issues on Windows.

If I run Komodo 12 from a Cmd prompt, with the variables set as per #3817 (comment) then it starts.

However, there is no state tool under %AppData%\ActiveState\bin\state.exe (the folder is empty).

Requested ...\XRE\state\log.txt attached.

log.txt

[th3coop]

@shawnlaffan what does where state output in CMD?

Nothing helpful in those logs unfortunately. Can you confirm that you were having the exact same issue in that every time you started Komodo using the method other than CMD, the login dialog would error out? Are you able to now start Komodo in the non-CMD flow, with a reset profile, and have the login dialog work?