Authenticate Developer Mode on Vega Fire TV displays an error message

Vega Open Beta Bug Reports
1

:backhand_index_pointing_right: Bug Description

1. Summary

I am trying to enable developer mode on the device, but when I attempt to authenticate, the following error appears:
Waiting for authentication to complete...
Error: Failed to verify vendor registration: http 401: {"error":"invalid_token","error_description":"Authentication failed"}
and it won’t let me install new builds,

App Name:
Authenticate Developer Mode on Fire TV

Bug Severity
Select one that applies

  • Impacts operation of app
  • Blocks current development
  • Improvement suggestion
  • Issue with documentation (If selected, please share the doc link and describe the issue)
  • Other

2. Steps to Reproduce

  1. To authenticate with your Amazon Developer Account, run the login command in the Terminal:vega devmode loginFollow the instructions from the CLI to complete authentication. The CLI automatically opens your default web browser to the Amazon authentication page. If the browser doesn’t open automatically, navigate to the URL provided in the terminal.
  2. Authorize Vega CLI access in your browser.The Amazon OAuth consent screen displays “Vega Authentication Test would like access to:” along with your basic profile information and name.a. Review the requested permissions.b. Select Allow to authorize Vega Authentication.
  3. Take a look at the terminal, Displays a message error.

3. Observed Behavior

I am trying to enable developer mode on the device, but when I attempt to authenticate, the following error appears:Waiting for authentication to complete...Error: Failed to verify vendor registration: http 401: {"error":"invalid_token","error_description":"Authentication failed"}

4. Expected Behavior

After selecting Allow, a confirmation page appears with a checkmark icon and the message “Device connected to your account.”

4.a Possible Root Cause & Temporary Workaround

There may be an issue with the permissions assigned to the new development accounts. An older account does allow authentication.

5. Logs or crash report

Waiting for authentication to complete...
Error: Failed to verify vendor registration: http 401: {"error":"invalid_token","error_description":"Authentication failed"}

6. Environment

Activating the Development Account

7. Example Code Snippet / Screenshots / Screengrabs

image
image587×392 24.8 KB

image
image865×725 87.7 KB

image
image589×388 44.4 KB

3

Hi @Fredy_Alexander_Pena_Forero

Welcome to the community, and thanks for the detailed report and screenshots.

The error you’re seeing happens after you successfully authorize in the browser, at the step where the Vega CLI verifies the vendor linked to your Amazon Developer account.

You mentioned login works on your older account but fails on the new one. This usually means the new account isn’t yet fully set up as a registered developer/vendor account, so the vendor-verification step returns 401 even though the browser “Allow” step succeeds.

Looks like you are trying to use [keplerultimate@gmail.com(mailto:keplerultimate@gmail.com) for dev mode registration as per the screenshot, however, we are not able to identify/locate a registered developer account with this email. If you have not yet created a developer account or completed the account registration with this email on https://developer.amazon.com/, please follow the below steps.

  1. Complete developer registration: Sign in to https://developer.amazon.com/ with the exact account you’re using for vega devmode login, and make sure you’ve finished the full developer registration (accepted the developer agreement and completed any required profile/company details). A newly created account that hasn’t finished registration won’t have a vendor provisioned yet.
  2. Confirm it’s the same account: In your screenshot, the browser consent screen shows keplerultimate@gmail.com (Name: “Vega”). Please confirm this is the same account that’s registered as a developer - a mismatch between the browser account and your registered developer account is a common cause of this error.
  3. Latest tooling: Confirm you’re on the latest CLI/SDK - run vega --version, then vega update.

After completing registration if you still face issues, please share the following so we can investigate the account’s vendor/registration status on our side:

  • the email/account used for the failing vega devmode login, and
  • the approximate date/time of your most recent attempt.

Warm Regards,
Ivy

5

Thank you so much for your help!!! The solution worked!!!

image
image1146×358 97.6 KB