Please refer to below list of known issues and bugs for Alexa Presentation Language.
- The functions String.toUpperCase, String.toLowerCase, and String.slice each require that any string argument be enclosed in single quotes, not double quotes.
- 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 rendered on an Alexa device, a TouchWrapper within a Pager does not send a UserEvent to the skill. This issue was first reported here.
- 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.
- Setting the "align" property on Video seems to work on Echo Show even though no such property is supported by the Video component (see https://developer.amazon.com/docs/alexa-presentation-language/apl-video.html). However, the authoring tool and test simulator perform correctly. When this issue is fixed, Echo Show will ignore the align property on video components.
- maxLines doesn't always render correctly on devices.
- PlayMedia commands finish immediately even if the audioTrack is set to foreground. When this issue is fixed, a foreground PlayMedia command won't finish (and subsequent commands won't execute) until the video is finished.
- The AlexaTransportControls can only be used in APL documents that have a single Video component.
- 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.
- Skill session sometimes fails to timeout after video playback ends if the PlayMedia command is used to play video.
- Passing a parameter as arguments array to TouchWrapper/SendEvent does not work.
- Event information is missing from the Video.onTrackUpdate event.
- On Echo Show, Echo Spot, Fire TV and Fire tablets, sending multiple ControlMedia next commands in the same ExecuteCommands directive does not work. When responding with an ExecuteCommands directive, ensure that it has no more than 1 ControlMedia next command.
- For ControlMedia command, the seek property does not respect relative offsets at this time. When a seek value is supplied, the video always seeks to the absolute position of the value in the video. When this issue is fixed, the ControlMedia's seek command will respect the current offset of the video and add the seek value to it.
- When using an utterance like "Alexa, select number one" the AMAZON.SelectIntent request will incorrectly tag the Anaphor slot instead of the ListPosition slot. When this issue is fixed, the built-in intent will correctly tag the ListPosition slot.
- On devices, setting top/left values for a Container child effects layout even if the child does not have position set to absolute. When this issue is fixed, only children with position set to absolute will respond to top/left values.
Built-in scroll intents, page intents and MoreIntent only work if the scrollable component (ScrollView, Sequence) has an id assigned. To enable scrolling on an APL ScrollView or Sequence component, assign a value to it's id property.
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.0",
"mainTemplate": {
"items": [
{
"type": "Container",
"width": "100%",
"height": "100%",
"alignItems": "center",
"justifyContent": "center",
"items": [
{
"type": "Text",
"fontSize": "@fontSizeRegular",
"text": "${environment.agentName}"
},
{
"type": "Text",
"fontSize": "@fontSizeRegular",
"text": "${environment.agentVersion}"
}
]
}
]
}
}
