as

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

Fix Vega SDK Issues

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


Installation script fails to download

Cause: Network restrictions, corporate firewall blocking downloads, or DNS resolution issues preventing access to sdk-installer.vega.labcollab.net.

Solution:

  1. Verify network connectivity:

    curl -I https://sdk-installer.vega.labcollab.net/get_vvm.sh
    
  2. If blocked by corporate firewall, contact your IT department to allowlist the domain.

  3. Check if you're using the Snap version of curl on Ubuntu (which has sandbox limitations):

    which curl
    

    If it shows a snap path, install native curl:

    sudo apt remove curl
    sudo apt install curl
    
  4. Retry the installation command from Install Vega SDK.

SDK installation fails during bootstrap

Cause: Network connectivity issues, firewall restrictions, or insufficient permissions during the automated SDK download that occurs after Vega CLI installation.

Solution:

  1. Verify network connectivity:

    curl -I https://sdk-installer.vega.labcollab.net/get_vvm.sh
    
  2. If blocked by corporate firewall, contact your IT department to allowlist the domain.

  3. Check if you're using the Snap version of curl on Ubuntu (which has sandbox limitations):

    which curl
    

    If it shows a snap path, install native curl:

    sudo apt remove curl
    sudo apt install curl
    
  4. Retry the installation command from Install Vega SDK.

Unable to download Vega CLI

Cause: Network restrictions, corporate firewall blocking downloads, or installation script access issues preventing CLI binary installation.

Solution: Use the legacy bootstrapper setup: Install Vega SDK

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 administrator privileges, or Homebrew isn't installed in the correct directory for your system architecture.

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

  1. Disable Rosetta.

  2. Install brew following the instructions on the Homebrew page.

  3. Verify brew is 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. Set the HOMEBREW variables correctly in 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. Update your brew packages.

    Copied to clipboard.

    brew upgrade
    

SDK download error

Failed to load the SDK installation interface

Cause: The download URL might not have generated correctly.

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. Verify whether your terminal is running under Rosetta:

    uname -m
    
    • If it returns x86_64 on an M-series Mac, your terminal is using Rosetta.
    • If it returns arm64 on an M-series Mac, you're running natively.
  2. Disable Rosetta for your terminal if it's enabled:

    a. Quit Terminal/iTerm completely

    b. Right-click Terminal.app (or iTerm.app) in Applications

    c. Select Get Info

    d. Uncheck Open using Rosetta if it's enabled

    e. Reopen Terminal and verify with uname -m (should show arm64)

  3. Rerun the installation command:

    curl https://sdk-installer.vega.labcollab.net/get_vvm.sh | bash && source ~/vega/env
    
  4. Confirm the installation script detects your native architecture.

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>/vega/sdk/<version>. Remove? [y/N]:

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

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

Solution:

Option 1: Overwrite existing installation:

  1. Enter y when prompted 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.

Too many open files error

You might receive the following error while building your apps:

node:events:495
throw er; // Unhandled 'error' event
^
Error: EMFILE: too many open files, watch
at FSWatcher._handle.onchange (node:internal/fs/watchers:207:21)
Emitted 'error' event on NodeWatcher instance at:
at FSWatcher._checkedEmitError (/Users/username/sampleapp/node_modules/metro-file-map/src/watchers/NodeWatcher.js:134:12)
at FSWatcher.emit (node:events:517:28)
at FSWatcher._handle.onchange (node:internal/fs/watchers:213:12) {
errno: -24,
syscall: 'watch',
code: 'EMFILE',
filename: null
}

Cause: A known issue with Watchman impacts Mac M1 users. Watchman is a file watching system that the Metro bundler uses.

Solution: Reinstall Watchman:

Copied to clipboard.

brew reinstall watchman
watchman shutdown-server; watchman watch-del-all; watchman

node_api.h file not found

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

Solution:

  1. Verify 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. Remove the dist folder in the turbo module project.

    b. Run a clean build of the turbo module project.

    c. Run a clean build of the app project.

  2. Verify autolinking:

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

    b. Verify autolinking settings are correct.


Last updated: Apr 01, 2026