Please refer to below list of known issues and bugs for Alexa Presentation Language.
- Using more than 100 images in an APL document prevent the document from rendering on devices. When this issue is fixed, developers will see validation errors for documents that use more images than are supported by a device.
- APL 1.1 Context elements transform, uid, media.entity, media.url, and scrollable.allowBackward are not implemented.
- APL templates fail to render in the APL authoring tool when using a device with custom settings.
- Skills that aren't optimized for Echo Show 5 are rendered as if they are being scaled down from their TV versions. To workaround this issue, optimize your skill for Echo Show 5, check the box under the APL interface to declare that you have optimized for Echo Show 5, and re-submit your skill. When this issue is addressed, unoptimized skills will be scaled down from their Echo Show version when they are invoked on an Echo Show 5.
- The Hub Round Small viewport profile in the simulator looks cropped from the top/bottom. This issue does not affect actual display on Echo Spot devices.
- The imageAspectRatio property on responsive components does not support the value round at this time. Setting this value still results in rectangular images. When this issue is fixed, the round value will work as expected.
- Devices cannot handle Frame’s border radius over image.
- The AlexaButton component does not show a pressed state on TV devices.
- APL Commands start immediately without waiting Alexa to finish saying outputSpeech on Fire TV.
- When rendered in the simulator, a TouchWrapper within a Pager sends incorrect UserEvent information to a skill. In some cases, the UserEvent information corresponds to Pager items not currently visible in the simulator.
- When components that have container child properties such as alignSelf or position (see https://developer.amazon.com/docs/alexa-presentation-language/apl-container.html#container-children for complete list) are dragged out of a container in the authoring tool, the authoring tool warns about these properties. However, the authoring tool does not provide a way to remove these properties. Developers must switch over to the raw JSON view to remove these properties and get rid of the authoring tool warnings.
- AMAZON.SelectIntent is not fired for utterances like "select number 3". When this issue is fixed, the built-in intent will also handle these utterances.
- When testing voice-based selection in the simulator, please use voice input. Using the text box will work, however the results will not be the same as you would get when using voice input. When this issue is addressed, you will be able to use the text box to test voice-based selection scenarios.
- The AlexaTransportControls can only be used in APL documents that have a single Video component.
- When a single video is played using the Video component the previous/next buttons of an associated AlexaTransportControl just pause the video. When this issue is fixed, the buttons will skip to the first/last frame of the video respectively.
- When used with a video that has autoplay set to false, the AlexaTransportControls will start out by showing a Pause button in the simulator. This is a known issue. However, on Alexa devices the button will correctly render as a Play button.
- The ControlMedia seek command does not work in the Alexa Skills Kit test simulator.
- onPlay and onPause events are not firing correctly in the simulator - onPlay is not sent when a video begins to play, and onPause is only sent when the video has stopped playing similar to the onEnd event.
- The Video component's onPause and onPlay event handlers can not be used to invoke a SendEvent command on devices.
If you have any questions, please post on this forum space with this link and provide below information!
- Device(s) Affected: <Alexa device(s) affected>
- Device Serial Number (DSN):
- Skill Request received by the skill: <This can be captured by logging the skill request you get when the skill is invoked>
- Skill response containing the APL and any applicable datasources: <This can be captured in the Test tab of the skill developer console>
- Screenshot of the authoring tool: <Link to a screenshot of the authoring tool if relevant>
- Picture(s) of device(s) affected: <Link to pictures of device issues. Videos if the issue is related to animation/interactions>
- SW Build number on the respective device(s): <Accessible by pulling down the notification tray, click on Settings>Device Options->Check for software updates>
- Environment agentName and agentVersion: <You can capture this information by running below document>
{
"type": "APL",
"version": "1.1",
"mainTemplate": {
"items": [
{
"type": "Container",
"width": "100%",
"height": "100%",
"alignItems": "center",
"justifyContent": "center",
"items": [
{
"type": "Text",
"text": "${environment.agentName}"
},
{
"type": "Text",
"text": "${environment.agentVersion}"
}
]
}
]
}
}
