Test your Fire OS and Vega Apps Concurrently with Live App Testing

Vega Open Beta Knowledge Base
1

Live App Testing (LAT) supports multiple binary types (i.e. APK, VPKG) within a single test run. No more waiting for your current Fire OS LAT to end before starting your Vega app. With the updated multi-binary LAT, you can now upload both binary types together before starting your LAT. Forgot to add both builds at the same time? No problem. The updated LAT flow also allows you to edit your in-flight LAT to add a second binary type for a test.

Sounds interesting? Here’s how to get started.

How to create a LAT with different binary types:

  1. From the Developer Console, go to your App List page (Apps & Services → My Apps)
  2. Select the app you want to run your LAT on, and go to Live App Testing
  3. From here you can create your LAT test
  4. To create the LAT with multiple binary types (e.g. APK, VPKG), simply add both binaries to the LAT test. The Console will automatically add compatible devices to your binary. You can always edit the device list to remove devices.
  5. Complete the required fields and submit your LAT as you typically would.

With multi-binary LAT, tester assignments are done at the binary level vs LAT. Go to Manage Testers under Live App testing to assign testers to each binary. We recommend keeping your tester email addresses unique for each binary.

MultiLAT
MultiLAT1565×544 44.3 KB

How to add another binary type to an existing LAT:

  1. To add another binary to an existing single binary LAT, go to the Live App Testing page
  2. Edit your current LAT and add the second binary type
  3. Complete all required fields
  4. Submit.

A separate notification will be sent once your second binary is available for LAT.

EditLAT
EditLAT1137×447 25.3 KB

Things to note:

  1. Multi-binary LAT supports accelerated subscriptions similar to single binary LAT.
  2. We recommend keeping tester email addresses mutually exclusive between both binaries. This is important as access to your app and its subscriptions (if applicable) are tied to the email address. If a tester uses the same email address for both binaries, a subscription purchase or expiration done via one binary will reflect on other.
  3. Devices targeted for each binary are mutually exclusive. You can not target the same device to both binaries within a LAT.
  4. Promote to Upcoming feature is not available if you combine both binary types in your LAT.

Want to learn more about LAT for Vega? Review our more in-depth documentation.

Last updated: Mar 10, 2026