SDK logs are not generating on the device
Device is not supported Make sure you are using a supported device. Check with your Amazon contact for a list of device types currently supported. Device software is outdated If you are using a supported device, make sure that you have installed the latest software. Navigate to Settings > My Fire TV > About and then click Check for Updates. Artifact not included in app correctly If you are using a supported device and have the latest software, double check that you have the artifact included in your app correctly. For additional details, see Include the SDK in your app.App is calling the SDK and generating SDK logs but no content appears in the Continue Watching Row
Checkpoint #1 - Confirm feature is enabled Validate that your CustomerID is enabled for the Content Personalization feature by navigating to Settings > Preferences > Privacy Settings > Manage Sharing from Apps. If the Manage Sharing from Apps option is missing, contact your Amazon contact and provide your CustomerID and DSN.
Expected menu items under Settings > Preferences > Privacy Settings
- Make sure your app is installed on the device. This list only shows installed apps.
- Select Sync Amazon Content and wait up to 15 minutes before checking the list again.
- If the app is still missing from the list, reach out to your Amazon contact and provide your CustomerID, DSN, and the package name you are using for development.

Your app should appear in this list under Settings > Preferences > Privacy Settings > Manage Sharing from Apps > Manage By App

Share App Viewing and Content Info should be set to ON
- are using a supported device with the latest updates
- have completed up to Get Started with the Fire TV Integration SDK - Step 4
- have confirmed feature enablement and app allowlisting in Checkpoint #3
- have confirmed that you are using an Amazon content ID that appears in your catalog file
The SDK feature check is returning true but the device is not showing the Continue Watching Row
Some devices might be capable of loading the SDK library but are not fully supported yet for the Continue Watching experience. The feature check only shows if the library is available and does not guarantee feature availability. We recommend you still include calls to the SDK on device as these devices might be supported in the future. Your Amazon contact can share the list of current devices supporting the Continue Watching Feature.The Continue Watching Row is not working as expected
See Troubleshooting.Handling scenarios where background processes end
When foreground processes need memory, Android OS stops other processes to free up memory. However, the activity history stays in the activity stack. The next time the activity is started, it is launched using the original launch intent before the process is stopped. The second, most up-to-date intent, occurs next using theonNewIntent() callback.
Background information
Android’s process flow
Knowing the process flow will help you understand how processes and intents are used by the OS.- 3P app (Activity A) is started with a deeplink intent (Intent A).
-
ActivityA.onCreate()is called, andgetIntent()yields Intent A. - Activity A is moved to the background, and the customer might use other apps and features.
- The Android low memory killer daemon (lmkd) stops Activity A to free up memory.
-
ActivityA.onDestroy()is called and then the Activity A process is stopped. - Activity A starts later with a different use case, and a different intent (Intent B).
-
ActivityA.onCreate()is called, butgetIntent()still yields Intent A.- If using a non-standard launch mode, such as
singleTop,singleTask, orsingleInstance, Android OS checks if an activity already exists for a task, and tries to route the intent with theonNewIntent()callback. - For standard launch mode, the you must create a new instance of the target task, and deliver the intent to that new instance.
- If using a non-standard launch mode, such as
-
ActivityA.onNewIntent()is called next, with Intent B as the intent in the callback.
Saving states across instances
When a process ends in the background by Android OS, the system first callsonSaveInstanceState(Bundle) so the activity can save state information to an instance state bundle. In onCreate() during the next activity startup, a saved instance bundle can be used to show that the process is restarted after Android OS ends it, or if it is a newly started activity.
The activity won’t end to free up memory, but the process the activity runs in will be stopped. When recreating an activity, the saved instance can be recovered from the bundle.
For more information, see the following:
Using a previous intent, such as for a deeplink, does not work
If a deeplink does not seem to work, it might be because a previous intent, rather than the latest intent, has been chosen. There are two ways to fix this issue.Option 1
The first option is to use the most up-to-date intent that’s received from your app. If deeplinks don’t show the correct information, it might be because you aren’t using the most recent intent. All intents other than the most recent are dropped or ignored by the system. For more information, seeonNewIntent().
Option 2
Instead of option 1, you can use a dedicated activity to receive and forward the deeplink. The advantage of this is that after processing the deeplink, the activity can callfinish(), removing it from the activity history. The next time it’s started, it contains the most up-to-date intent when using getIntent() from lifecycle callbacks like onCreate(). Then the system won’t need to wait for an onNewIntent() callback.
