Trying to enable developer mode gives 'Error: Session expired. Please run 'vega dev login' again'

Vega Open Beta Q&A
1

vega devmode enable-device --code <6 digit code>

Above is the command that I am running.I am already logged into the CLI.Everytime I am running this command, getting the same error.

My SDK Version: Active SDK Version: 0.24.9785

Vega CLI Version: 1.2.22.

please help

3

Hi @Rishabh_Ritweek,

Could you please share the exact error message you’re getting when running vega devmode enable-device --code <code>?

Also, to help troubleshoot:

  1. What device are you trying to enable developer mode on? (Fire TV Stick 4K Select?)
  2. Are you generating a fresh 6-digit code from the device each time? (Settings → Device → Developer Mode → the code shown on screen)
  3. Is your device registered to the same Amazon account you used to log into the Vega CLI?

The code expires after a short time, so if you’re reusing an old code, it will fail. Generate a new code and run the command immediately.

Common causes:

  • Expired code - generate fresh and use within 60 seconds
  • Account mismatch - CLI login account must match the device’s registered Amazon account
  • Network issue - device and Mac must both have internet access
  • Not logged in - run vega devmode login first and complete the browser auth flow before running enable-device

For the full setup walkthrough: Enable Developer Mode | Vega Get Started

Please share the error output and we’ll get you sorted.

Warm regards,
Ivy

4

Hi @Rishabh_Ritweek,

To resolve this, please run the following commands:

:warning: Log out first (do NOT skip this step):

vega devmode logout

Update:

vega update

Verify:

vega -v

Expected output:

Active SDK Version: 0.24.9785
Vega CLI Version: 1.3.2

Log in and enable your device:

vega devmode login
vega devmode enable-device --code <6-digit-code>

Note: The enable-device command requires Vega CLI version 1.3.2 or above, as stated in the Developer Mode prerequisites.

Let us know if you need further help!

5

Thank you. CLI version was the root cause it seems. issue is resolved.