Fix Vega SDK Issues - Amazon Vega Docs

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 the Developer Forum for additional support.

Installation issues
Build and run issues

Homebrew installation

When 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 you haven’t installed Homebrew in the correct directory based on your system architecture.Solution: Make sure you have administrator privileges, then complete the following steps:

Disable Rosetta.
Install brew following the instructions on the Homebrew page.
Find brew on your PATH.
which brew
The PATH should be: arm64: Install Homebrew under /opt/homebrew/bin/brew. x86_64: Install Homebrew under /usr/local/bin/brew.

Set the HOMEBREW variables correctly in your .profile/.rc file. arm64:

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

x86_64:

eval $(/usr/local/bin/brew shellenv)

Check if your brew packages are up-to-date.
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 the 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:

Return to the Install Vega SDK page.
Select the correct platform for your machine.
Get the new install command.
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:

Press Command+C (Mac) or Ctrl+C (Linux) to stop the installation.
Connect to a reliable network.
Return to the Install Vega SDK page.
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:

Free up disk space.
After clearing disk space, verify you have at least 20 GB free.
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 error 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:

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

Option 2: Clean installation:

Back up the existing folder to another location.
Remove old installation using .
Rerun the installer.

Too many open files error

You might receive an error when building your apps stating that there are too many open files:

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/keplersampleapp/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: The error is due to a known issue with Watchman, which impacts Mac M1 users. Watchman is a file watching system used by the Metro bundler.Solution: To resolve the issue, reinstall Watchman:

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 turbomoduleAPI package.Solution:

Make sure your CMakeLists.txt file has the following lines:
- find_package (turbomoduleAPI REQUIRED)
- target_link_libraries (…turbomoduleAPI::turbomoduleAPI…)
Rebuild your project.

App crashes due to missing Turbo Module registration

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

Cause: The Turbo Module didn’t register properly, so the app can’t find it at runtime.Solution:

Clean and rebuild:
1. Clean the dist folder in the Turbo Module project.
2. Perform a clean build of the Turbo Module project.
3. Perform a clean build of the app project.
Verify autolinking:
1. Check that react-native.config.js exists.
2. Make sure the autolinking settings are correct.

Install the Vega SDK

​Homebrew installation

​SDK download error

​Platform mismatch error during SDK installation

​Download failed during installation

​Installation failed due to low disk space

​SDK already installed

​Too many open files error

​node_api.h file not found

​App crashes due to missing Turbo Module registration

​Related topics