Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazonアプリストア
Ring
AWS
ドキュメント
Support
Contact Us
My Cases
開発
設計と開発
公開
リファレンス
サポート
メインコンテンツへスキップ
There are Vega-specific changes that are required for your app to load correctly on the device.

3.1 Manifest.toml interactive components

Update the runtime module path and interface for UI components:
Key changes
  1. Component ID: krl.2 → krl.4
  2. Runtime module path: keplerscript.runtime.loader_2 → runtime.react_native_kepler_4
  3. Interface: IKeplerScript_2_0 → IReactNativeKepler_0

3.2 Manifest.toml headless components

If your app uses headless components (services or tasks), update their runtime modules as shown in the examples below.
Key changes
  1. Runtime module path: headless.runtime.loader_2 → runtime.react_native_kepler_headless_4
  2. Interface: IKeplerScript_2_0 → IReactNativeKeplerHeadless_0

3.3 app.json updates

Update the component ID in app.json from krl.2 to krl.4:

3.4 CMakeLists.txt updates

Update version numbers, C++ standard, and library targets in the CMakeLists.txt file. Template pattern (krl.2 → krl.4)
Version suffix pattern (072 → 083)
Native code linking (if using C++ native modules)
Requirements
  • CMake 3.22+
  • C++20-compatible compiler (GCC 10+, Clang 12+, MSVC 2019+)

3.5 Vega bundle configuration

If your app uses JavaScript system bundling, add the bundle configuration package in your package.json file. A standard app doesn’t need this package, and the Vega app template doesn’t include it.
Optionally, configure bundle splitting in package.json. For production apps, it’s recommended to remove disableSplitBundle or set to false to enable code splitting for better performance.
最終更新日 2026年10月30日