# Vega LAT: Users unable to install or launch app; installed app missing from launcher after restart

**URL:** <https://community.amazondeveloper.com/t/vega-lat-users-unable-to-install-or-launch-app-installed-app-missing-from-launcher-after-restart/29197>\
**Category:** Q&A\
**Tags:** vega-sdk, vega-device, vega-apps, vega-performance\
**Created:** [September 21, 2026, 9:03am UTC](https://community.amazondeveloper.com/t/vega-lat-users-unable-to-install-or-launch-app-installed-app-missing-from-launcher-after-restart/29197 "2026-09-21T09:03:12Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![amen](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@amen](https://community.amazondeveloper.com/u/amen)\
**Post date:** [September 21, 2026, 11:31pm UTC](https://community.amazondeveloper.com/t/vega-lat-users-unable-to-install-or-launch-app-installed-app-missing-from-launcher-after-restart/29197/4 "2026-09-21T23:31:18Z")

</div>

Hi @James_Timms,

Thanks for the detailed report. There are two separate issues here:

1. net::ERR\_FAILED (-2) / bundled web app

Known Vega WebView limitation: a single file:// HTML loads fine, but cross-origin access between local files is CORS-restricted, so a bundled web app referencing separate local JS/CSS/image assets fails. Inlining into one HTML (as you did) is the right first step. Two things to check:

- If the inlined HTML still makes network/API calls, those can throw net::ERR\_FAILED independently - confirm whether the failing load is local or remote.
- More robust option: serve your content via a lightweight local HTTP server ([http://localhost](http://localhost):PORT/) instead of file:// - avoids CORS entirely.

Refs:

- WebView local file + additional files ([Webview, load local file url and additional files](https://community.amazondeveloper.com/t/webview-load-local-file-url-and-additional-files/25094))
- Local file WebView and CORS ([Local file webview and CORS](https://community.amazondeveloper.com/t/local-file-webview-and-cors/27652))

1. Installs via LAT but missing from launcher

Two common manifest causes produce exactly this symptom:

- Icon exactly 512×512 PNG, under 1MB, at assets/image/, referenced as icon = “@image/.png”. (Manifest package ([Manifest [package] Section - Amazon Vega Docs](https://developer.amazon.com/docs/vega/0.24/manifest-package.html)))
- Exactly one interactive component with categories = [“com.amazon.category.main”] - required to launch from Home/Appstore. (Manifest components ([Manifest [components] Section - Amazon Vega Docs](https://developer.amazon.com/docs/vega/0.24/manifest-components.html)))

Key signal: if the sideloaded build (vega device install-app) appears and launches but the LAT build doesn’t, that points to the LAT delivery/launcher-registration path rather than your manifest.

Could you share:

1. Your manifest.toml [package] and [[components.interactive]] sections
2. Icon dimensions and file size
3. Whether the sideloaded build appears/launches vs. the LAT build (incl. the after-restart behavior)
4. Device logs around the install + “Open” hang, plus the device software version

Our team is looking into it and will provide an update as soon as we have more information.

Thanks for helping us improve the Vega platform.

Warm regards,  
Aishwarya

---

_[View the full topic](https://community.amazondeveloper.com/t/vega-lat-users-unable-to-install-or-launch-app-installed-app-missing-from-launcher-after-restart/29197)._