SDK Manager Issues - Amazon Vega Docs

This page covers common problems you may encounter when using the SDK manager and provides step-by-step solutions to resolve them quickly. If you don’t find a solution to your specific problem here, post an issue in the Developer Forum for additional support.

Common issues

Command fails with SDK version not found

Cause: Required SDK version isn’t installed locally Solution:

# Check available versions
vega sdk list-remote

# Check what's installed
vega sdk list-installed

# Install the missing version
vega sdk install <version>

New SDK version isn’t active after you install it

Cause: Installing a new SDK version, with vega sdk install or the installer, doesn’t always make it the active version. If another SDK version was active before you installed, Vega can keep using that version. Solution:

# Check which SDK version is active
vega sdk ls

# If the new version isn't marked as active, switch to it
vega sdk use <SDK_VERSION>

# Confirm the new version is now marked as active
vega sdk ls

The active version is marked with an arrow and Active SDK Version:

Channel: main
  0.24.12112
→ 2.0.13377 - Active SDK Version

If vega --version shows (not installed) next to the active version, the vega-sdk-requirements.json file in your project requests a version that isn’t installed. Install that version with vega sdk install <version>, or update the vegaSdkVersion field in the file to an installed version. For details, see How requirements files work.

Builds use a different SDK version after you run `vega sdk use`

Cause: A vega-sdk-requirements.json file in your project directory or one of its parent directories pins a different SDK version. The version in a requirements file overrides the global default that you set with . vega sdk ls shows the active version, but not that a requirements file set it. Solution:

From your project directory, look for requirements files in the current directory and its parent directories:

dir="$PWD"; while [ "$dir" != "/" ]; do ls "$dir/vega-sdk-requirements.json" 2>/dev/null; dir=$(dirname "$dir"); done

For each file the command lists, do one of the following:
- To use the version in the file, install it with .
- To use a different version for the project, update the vegaSdkVersion field in the file.
- To use the global default instead, delete the file.
Confirm that the version you expect is marked as active:
vega sdk ls

The KEPLER_SDK_PATH environment variable doesn’t affect which SDK version is active. For the full order that Vega uses to choose a version, see How Vega chooses the active SDK version.

SDK commands fail unexpectedly or produce errors

Cause: Installation files are damaged or incomplete Solution:

# Diagnose issues
vega sdk config doctor

# Fix by reinstalling
vega sdk uninstall <version>
vega sdk install <version>

Pipeline execution stops and waits indefinitely

Cause: Interactive prompts are blocking automated execution Solution:

Set the NONINTERACTIVE=true environment variable.
Use the --non-interactive flag on commands.
Check for interactive prompts in scripts.

Manage Your SDK Versions

​Common issues

​Command fails with SDK version not found

​New SDK version isn’t active after you install it

​Builds use a different SDK version after you run vega sdk use

​SDK commands fail unexpectedly or produce errors

​Pipeline execution stops and waits indefinitely

​Related topics