Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazonアプリストア
Ring
AWS
ドキュメント
Support
Contact Us
My Cases
開発
設計と開発
公開
リファレンス
サポート
メインコンテンツへスキップ

Verify using Universal Search launcher UX

You can verify the Account Login thorough universal search from the Fire TV home screen.

Verify Content Launcher integration using the remote

  1. Install and log in to your app.
  2. From the Fire TV Home screen, search for your app’s content
  3. On the content detail page, select “Watch Now.”
Expected result: Your app should launch automatically, once the Content Launcher handler is invoked, and playback of the selected contents should begin.

Verify Content Launcher integration using voice

Install and log into your app. While the app is running in the foreground, use a voice command (“Alexa…”) to play content available in your app. The Content Launcher handler is invoked, and your app properly handles the request and begins playback of the requested content. Example utterances:
  • “watch <movie name>”
  • “Watch <TV Show name> with season <number> and episode <number>”
  • “Watch comedy movies”

Verify Account Login integration using KCP CLI

You can also verify your Account Login integration from the command line. Use this to debug and confirm that your app reports its login status correctly.

Prerequisites

  • You’ve enabled Developer Mode on your Vega device. For instructions, see Enable Developer Mode.
  • Your app is installed by sideloading, launched at least once, and is running in either the foreground or background. The app component shell won’t work on apps installed through Live App Testing or through the Appstore.

Enter the component shell

Once developer mode is enabled, enter your component shell and check the CLI.
The CLI is pre-installed at /usr/bin/kcp-cli-v2 and may be accessed through the component shell.

Read Account Login status

To check your app’s login status from the component shell, run the following command.
Example:
Expected output:
If the value is true, the app is SIGNED_IN. If it’s false, the app is SIGNED_OUT.

Subscribe to Account Login status changes

To monitor login status changes in real time, use the watch-status command.
Example:
Expected output:
The output stream updates when the status changes. Log in and out of your app while this command runs to verify status transitions. For detailed usage, run:

Test CLI scenarios for Account Login

  1. Verify SIGNED_IN: Log in to your app, then run account-login read-status. The status should return true.
  2. Verify SIGNED_OUT: Log out of your app, then run account-login read-status. The status should return false.
  3. Verify transitions: Run account-login watch-status, then log in and out of your app. Confirm the status updates each time.

Verify Content Launcher integration using KCP CLI

You can use the KCP CLI tool to invoke Content Launcher requests on your app. This allows you to test launch requests without the use of Universal Search, the remote, or voice commands.

Prerequisites

  • You’ve enabled Developer Mode on your Vega device. For instructions, see Enable Developer Mode.
  • You’ve installed and registered your app with KCP, and you’ve launched it at least once.

Add content search JSON

The --content-search parameter accepts a JSON object with the following structure:

Add external_id_list fields

Launch a movie by title

Simulating: “Alexa, Watch <Movie Name>”
Expected result: Your app should launch and begin playback of the requested movie.

Launch a specific season and episode

Simulating: “Alexa, Watch Season 1, Episode 3 in <Show Name>”
Parameter breakdown:

Launch a specific episode (no season)

Simulating: “Alexa, Watch Episode 3 in <Show Name>”
Expected result: Your app should launch and begin playback of Episode 3 of the requested show.

Launch a specific season

Simulating: “Alexa, Watch Season 1 in <Show Name>”
Expected result: Your app should launch and begin playback of Season 1 (typically starting with Episode 1).

Search cases (currently supported only for specific apps)

Search for a movie (no auto-play)

Simulating: “Alexa, Search <Movie Name>”
Expected result: Your app should display search results for the requested content.

Search by actor

Simulating: “Alexa, Find <Actor Name>”
Expected result: Your app should display content associated with the specified actor.

Search by genre

Simulating: “Alexa, Find Comedy Movies”
Expected result: Your app should display comedy content, or begin playback if --auto-play is specified.

Content search parameter types

Use the param_type field in your content search JSON to specify the type of search:

CLI test scenarios for Content Launcher

  • Basic movie launch: Send a launch request with --auto-play for a known movie title with valid external_id_list values. Verify your app launches and begins playback.
  • Season and episode launch: Send a launch request with season and episode parameters. Verify your app navigates to the correct episode.
  • Episode-only launch: Send a launch request with only an episode number. Verify your app navigates to the correct content.
  • Search results display: Send a launch request without --auto-play. Verify your app displays relevant search results.
  • Actor search: Send a launch request with param_type: 0 and an actor’s name. Verify your app displays content from that actor.
  • Genre search: Send a launch request with param_type: 6 and a genre. Verify your app displays or plays content from that genre.
  • Playback preferences: Send a launch request with --optional-fields specifying a playback position. Verify your app resumes at the correct timestamp.
  • Unknown content handling: Send a launch request for content that doesn’t exist in your catalog. Verify your app handles the request gracefully.
For detailed usage, run:

Troubleshooting

最終更新日 2026年10月30日