Troubleshooting Guide for ACK-based Device Apps

Having trouble with your Alexa Connect Kit (ACK) device app? If your app encounters errors, review the information in this guide for possible resolutions to common issues.

Enable logs

Logs are usually hidden by default. To turn on system logs after a factory reset or flash erase, enter the following command on the device.

mack log system enable

To dump logs, establish a serial connection to your device, and then enter the following command on the device.

mack log dump system/partner

Crash dumps

How does this happen automatically? Logs are stored in the persistent memory of the device when a crash occurs. Any crash logs residing in the crash log partition are uploaded to the crash log S3 bucket after the device has rebooted and regained wi-fi connection. The logs are wiped from the device after a successful upload. The crash dump backtrace is uploaded as base-64-encoded text.

Issue: <follow with a description of the problem or error.(no limit, REQUIRED)>

Symptoms <one, REQUIRED>

<Describe the symptoms in a paragraph, list, or table. For details, see the "Troubleshooting Section" in the Documentation Model.>

Try this <no limit, REQUIRED>

<Paragraph of text (one, optional)> **To **

  1. <Steps (Up to 10 steps per procedure.) State the location before the action. Style UI elements bold.>
  2. 1. 2.

<Troubleshooting section title, don't use the section title "Troubleshooting." Instead, use words that summarize the problems or procedures that caused the problems.>

<Troubleshooting section 2 (three or more, REQUIRED)> <Paragraph of text (one, optional). Summarize the collection of troubleshooting issues in the section.>

Issue: <follow with a description of the problem or error.(no limit, REQUIRED)>

Symptoms <one, REQUIRED>

<Describe the symptoms in a paragraph, list, or table. For details, see the "Troubleshooting Section" in the Documentation Model.>

Try this <no limit, REQUIRED>

<Paragraph of text (one, optional)> **To **

  1. <Steps (Up to 10 steps per procedure. State the location before the action. Style UI elements bold.>
  2. 1. 2.

<Troubleshooting section title, don't use the section title "Troubleshooting." Instead, use words that summarize the problems or procedures that caused the problems.>

<Troubleshooting section 3 (three or more, REQUIRED)> <Paragraph of text (one, optional). Summarize the collection of troubleshooting issues in the section.>

Issue: <follow with a description of the problem or error.(no limit, REQUIRED)>

Symptoms <one, REQUIRED>

<Describe the symptoms in a paragraph, list, or table. For details, see the "Troubleshooting Section" in the Documentation Model.>

Try this <no limit, REQUIRED>

<Paragraph of text (one, optional)> **To **

  1. <Steps (Up to 10 steps per procedure.) State the location before the action. Style UI elements bold.>
  2. 1. 2.

<Screenshots with callouts section title, sentence case>

<Screenshots with callout section (one or more, optional)>

  • [](../)
  • [](../)
Was this page helpful?

Last updated: frontmatter-missing