Alexa Presentation Language Known Issues

Refer to the following list of known issues, bugs, and breaking changes for Alexa Presentation Language (APL).

Known issues

  • [Echo Show 10] Skills that set a "Wake Word Response" using their skill manifest or the developer console Interfaces tab might crash when launched on Echo Show 10 devices. An urgent patch to fix this should roll out in the coming days. In the meantime, see Workaround for Echo Show 10 issue.

  • VectorGraphic linear gradient looks different between the Authoring tool and Physical devices

  • [Tablets] AlexaImageList: Disabled List Item behavior is broken on Portrait 10 inches devices

  • On physical devices, when a Frame contains an Image component, the borderRadius property for the Frame doesn't properly adjust the Frame corners

  • [Fire TV Editions TVs] Recipe video doesn't revert to the original volume after dismissing the volume panel

  • Word break opportunity before <nobr> tag not breaking correctly

  • Text with <nobr> incorrectly wrapping at the end of a container

  • [APL Simulator] [Large Hub/Extra Large TV Hub] Videos are not playing for both autoplay false and true scenarios

  • APL documents that use the Video component to play audio by settings its width/height to 0 will stop working. To work around this issue set the width/height to 1

Workaround for Echo Show 10 issue

Skills that set a "Wake Word Response" using their skill manifest or the developer console Interfaces tab might crash when launched on Echo Show 10 devices. An urgent patch to fix this should roll out in the coming days. In the meantime, use the following steps to mitigate the issue.

To mitigate the issue

  1. Make sure that you have installed and configured the ASK CLI. For details, see Quick Start: Alexa Skills Kit Command Line Interface (ASK CLI).

  2. Retrieve the manifest for your skill by running the following command:

    ask smapi get-skill-manifest -s [Your Skill Identifier] -g development > manifest.json

    Replace [Your Skill Identifier] with the ID for your skill.

  3. Open the manifest.json file produced by the CLI. In the manifest.apis.custom.interfaces array, find the interface with the type ALEXA_EXTENSION.

  4. In the ALEXA_EXTENSION object, remove the array called autoInitializedExtensions and save the manifest.json.

  5. Update the manifest for your skill by running the following command:

    ask smapi update-skill-manifest -s [Your Skill Identifier] -g development --manifest "file:manifest.json"

    This command is an async operation. To confirm that the command worked, open the ASK developer console and open the Interfaces tab. Confirm that the Wake Word Response box is empty and no Alexa Extensions are selected.

  6. Retest the development version of your skill with an Echo Show 10 and confirm that skill no longer crashes.

    If you were setting the Wake Word Response to Follow On Wake Word, you shouldn't lose any functionality because Follow On Wake Word is the default behavior for Echo Show 10 devices out of the box.

  7. If the issue is resolved for your skill, open the Interfaces page of the developer console and click Update live skill.

    This action updates the manifest of your live skill to fix the issue in your live skill.

    If Update live skill is disabled, resubmit your skill for certification. In the testing instructions, make a note that you're removing the default wake word response from the skill manifest and this update is to respond to a known issue with Alexa APIs. Include a link this known issue page for reference: https://developer.amazon.com/en-US/docs/alexa/alexa-presentation-language/apl-known-issues.html#workaround-echo-show-10.

Breaking Changes

  • [APL 1.6] Echo Show 8 is now a Hub Landscape Medium device. Customer feedback on the Echo Show 8 indicated that the font size was too small on many Alexa experiences. To address this, we've updated how the device reports it's screen size, which results in the device being classified as a Hub Landscape Medium device instead of a Hub Landscape Large. To account for this change, we recommend you review the Interfaces page in the Alexa developer console and ensure you have Hub Landscape Medium checked, as well as all the boxes for any other viewports that you support. Existing skills will not be impacted. They will continue to see Echo Show 8 as a Hub Landscape Large device until they check the box to opt in to Hub Landscape Medium as a supported viewport profile.

  • [APL 1.6] On FireTV directional keys no longer cause Pagers to animate in APL documents with version <1.6. To mitigate, change the APL document version to 1.6.

  • [APL 1.6] On an Alexa-enabled device with a screen, the viewport is the area of the screen that the user can see. A viewport has a shape, orientation, size, and density. In that, size and density are defined as ranges so that the profile can represent multiple physical devices. When you manually provide fixed/legacy viewport dimension values instead of the currently supported viewport ranges in the skill manifest for Hub Round Small, Hub Landscape Small, Hub Landscape Medium, and Hub Landscape Large devices, the corresponding viewport profile checkboxes aren't checked in the developer console. The current best practice is to verify whether your APL content renders correctly on the required viewport profiles, and then select the corresponding viewport profiles in the console or provide the corresponding supported viewport ranges manually in the skill manifest.

  • [APL 1.7] AVG radial gradients no longer render with incorrect radius, positioning, or scaling on Android devices


For support and help, visit the Alexa developer forum. Go to Contact Us to report an issue.

Last updated on 2021-09-29