as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
AWS
Documentation
Support
Contact Us
My Cases
Get Started
Design and Develop
Publish
Reference
Support

Vega SDK Installation Issues

This page helps you resolve common issues when installing the SDK. If you don't find a solution to your specific problem here, post an issue in Developer Forum for additional support.


Homebrew installation

While attempting to install Homebrew, you might see this message:

Homebrew: error while attempting to install Homebrew:...
==> Running in non-interactive mode because `$NONINTERACTIVE` is set.==> Checking or `sudo` access (which may request your password)...
Need sudo access on macOS (for example, the user USERNAME needs to be an Administrator)!

Cause: You might not have an administrator privileges or Homebrew isn't properly installed in the correct directory based on your system architecture.

Solution: Make sure you have an Administrator privileges, then complete the following steps:

  1. Disable Rosetta.

  2. Install brew.

    Follow the instructions in Homebrew page.

  3. Find brew on your PATH.

    Copied to clipboard.

    which brew
    

    The PATH should be:

    arm64: Install Homebrew under /opt/homebrew/bin/brew.

    x86_64: Install Homebrew under /usr/local/bin/brew.

  4. Make sure the HOMEBREW variables are set correctly by checking your .profile/.rc file.

    arm64:

    Copied to clipboard.

    eval $(/opt/homebrew/bin/brew shellenv)
    

    x86_64:

    Copied to clipboard.

     eval $(/usr/local/bin/brew shellenv)
    
  5. Check if your brew packages are up-to-date.

    Copied to clipboard.

    brew upgrade
    

SDK download error

Failed to load the SDK installation interface

Cause: There could be an issue with generating the download URL.

Solution: Reload the page. If the issue persists after reloading the page, post an issue in Vega community space.

Platform mismatch error during SDK installation

Download succeeded [OK]
Installing Vega SDK <version>. This takes 5 minutes.
Installation failed [X]
[X] Vega SDK for darwin-x86_64 is incompatible with current darwin-aarch64

Cause: The Vega SDK installer doesn't match your system architecture.

For example: You're using an M-series Mac (arm64) but downloaded the Intel Mac (x86_64) version.

Solution:

  1. Return to the Install Vega SDK page.
  2. Select the correct platform for your machine.
  3. Get the new install command.
  4. Rerun the installer.

Download failed during installation

If the installation process stops or fails during download, you might see:

  • Installation hanging without progress.
  • Network-related error messages.
  • Incomplete download notifications.

Cause: Network issues during download.

Solution:

  1. Press Command+C (Mac) or Ctrl+C (Linux) to stop the installation.
  2. Connect to a reliable network.
  3. Return to the Install Vega SDK page.
  4. Rerun the installer.

Installation failed due to low disk space

Vega Error:  Installation failed: [Errno 28] No space left on device

Cause: Your device doesn't have enough available storage.

Solution:

  1. Free up disk space.
  2. After clearing disk space, verify you have at least 20 GB free.
  3. Rerun the installer.

SDK already installed

Directory found at /Users/<user>/kepler/sdk/<version>. Remove? [y/N]:

Cause: The installer has detected an SDK directory at the specified install path. This can happen when:

  • A previous installation exists.
  • A previous installation failed but left files behind.
  • You attempted multiple installations.

Solution:

Option 1: Overwrite existing installation:

  1. Enter y when prompted, allowing installer to replace all existing files.

Option 2: Clean installation:

  1. Back up the existing folder to another location.
  2. Remove old installation using rm -rf <install-path>.
  3. Rerun the installer.

node_api.h file not found

Cause: You might have removed find_package and target_link_libraries calls for turbomoduleAPI package.

Solution:

  1. Make sure your CMakeLists.txt file has the following lines:

    • find_package (turbomoduleAPI REQUIRED)
    • target_link_libraries (…turbomoduleAPI::turbomoduleAPI…)
  2. Rebuild your project.

App crashes due to missing Turbo Module registration

"TurboModuleRegistry.getEnforcing(...): '[module]' could not be found" error.

Cause: The Turbo Module isn't properly registered so the app can't find it at runtime.

Solution:

  1. Clean and rebuild:

    a. Clean dist folder in turbo module project.

    b. Perform clean build of turbo module project.

    c. Perform clean build of app project.

  2. Verify autolinking:

    a. Check react-native.config.js exists.

    b. Make sure autolinking settings are correct.


Last updated: Sep 30, 2025