Exiting because of an error: could not get latest connector version

🚀 Support (Q&A)
1

After a couple of months of not useing the app I tried to run an app again. I first upgraded the viktor-cli. After the I got the following message when installing an app;

C:\Users\bart\viktor-apps>viktor-cli.exe install --app-dir first-app-tutorial
could not determine the latest version of viktor-cli
Exiting because of an error: could not get latest connector version

Any ideas?

Thanks!

Bart

2

Hi Bart,
Often this message is shown when the cli does not have the right access. Can you try viktor-cli.exe check-system and share the result?

3

Hi Matthijs,

Lijkt geen problemen te geven;

C:\Users\bart\viktor-apps>viktor-cli.exe check-system
Starting VIKTOR system check
V Operating system internet access
V Docker runs
V Docker using correct container
V Docker access to user directory
V Docker internet access
V Docker access to PyPI
V Docker access to VIKTOR domains
V Operating system access to PyPi
V Operating system access to VIKTOR domains

The system check has been completed with the following conclusions:
V Your system is ready to use VIKTOR with isolation mode ‘docker’
V Your system is ready to use VIKTOR with isolation mode ‘venv’

4

Oh ja en dit is de versie:

C:\Users\bart\viktor-apps>viktor-cli version
viktor-cli v0.13.1
could not determine the latest version of viktor-cli

5

will DM you to have a more detailed look at this

6

found the issue: invalid credentials (leading space in mail address) stored in credentials file. originated from config command not succeeding.

suggestions for improving this flow:

  • explicit message that credentials are incorrect (instead of implicit “cannot find latest version”)
  • do not write credentials file (or even .viktor folder) if credentials are not successful (allows for .env fallback)
  • allow for sourcing config from existing .env file (no copy-paste errors possible)