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.
- 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.
- 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.
- 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.
- The Video component's onPause and onPlay event handlers can not be used to invoke a SendEvent command on the simulator.
- The onCursorEnter/onCursorExit events don't work for all components. To work around the issue, set the inheritParentState property to true on the component that is being targeted by onCursorEnter/onCursorExit. When this issue is fixed, you will no longer need to set inheritParentState.
- Incorrect data binding expressions such as "height": "${payload.templateData.properties.text.height + 10}" when payload.templateData.properties.text.height isn't in the data source will lead to unpredictable APL rendering behavior.
- APL animation (AnimateItem command) gets jittery if too many elements are simultaneously animated on-screen.
- When automatic scaling is being applied to an APL document, Image components with scale set to 'none' don't scale correctly with the rest of the experience. To work around this issue, opt out of automatic scaling by selecting the checkbox for the relevant viewport profile in the ASK Console.
- In some scenarios, touching the screen on an Echo device does not stop APL command execution. When this issue is addressed, touching the screen will stop any ongoing APL command sequence in line with the command sequencing rules defined here https://developer.amazon.com/docs/alexa-presentation-language/apl-commands.html.
- Certain Fire tablets stop showing APL as a supported interface after being idle for some time. We believe the root cause may be APL's interaction with the tablet screen saver. When this issue is addressed, Fire tablets will consistently support APL even if the screen saver is active.
- Array of commands do not work as a part of onCursorEnter/onCursorExit event handlers. onCursorEnter/onCursorExit event handler only runs the first command in an array of commands.
- APL Runtime version is incorrectly reported as 1.1 instead of 1.2 on Simulator.
- Skill session continues after getting out of skill by pressing remote Back button on FireTV.
- ExecuteCommands directive can not be used to invoke user-defined commands
- Key event handlers (handleKeyDown/handleKeyUp) attached directly to APL documents are not executed unless the document contains an actionable component such as a TouchWrapper that has focus.
- When a customer uses an utterance (such as "select the third one") and the list on-screen does not have visible ordinals, the entity resolution logic does not match the selected item's id.
- Ordinal-based selection does not function reliably. The Resolutions Object is not populated accurately.
- When implementing Lazy Loading, visible blank space would be observed when "items" property is missing in the document sent as a part of SendIndexList or RenderDocument directive. This can be avoided by assigning an empty array to the "items" property.
- APL Sequence component: Images are swapped when scrolling fast.
- APL Data-Binding Evaluation within AVG does not work correctly
- SetPage with relative positioning does not work correctly in authoring tool
- APL sequence component: Images are swapped when scrolling fast
- [APLT] A pager that makes multiple references to a data source only displays the first page, ignoring the other pages in the pager
- [APLT] The screen is locked on the first page of a pager when the "duration" property of the AutoPage command is omitted.
- [APLT] The starting index is not reset when using the SetValue command for a text component with marquee overflow.
- [APLT] Rendering of APL-T RenderDocument and ExecuteCommands directives do not persist through the skill session unless idleTimeout property is defined as a part of the directive.
- [APLT] Delay property for an AutoPage command on Echo Dot (3rd Gen) does not work and is throwing an error.
- [APLT] On any device supporting APLT (currently only Echo Dot (3rd Gen)), a document that uses "resources" will not render properly unless "datasources" field is present in directive payload. The workaround is to include an empty "datasources" field.
- Known Issue: The commands for SetWakeWordResponse has regressed on device, and does not appear to be setting properly on this latest SM client release.
- Known Issue: The commands for PlayNamedChoreo are not yet supported/functioning on device.
- Known Issue: Event context ${event} in SmartMotion:OnDeviceStateChanged is not supported.
- Known Issue: SmartMotion extensions Environment value defaultWakeWordResponse, wakeWordResponseSupported and availableChoreos are not supported in SM Simulator.
- Known Issue: Wake word response set via skill manifest continues to persist outside of Skill Session on Device.
- Known Issue: Skill developers may occasionally not see SmartMotion and EntitySensing extensions in their skill request on motion/sensing capable devices or motion extensions may not work even after they request the extensions in their skill manifest. To workaround the issue, toggle the "Intelligent Motion" setting off/on on the device and invoke your skill again. When this issue is addressed the SmartMotion and EntitySensing extensions will show up in the skill request for all motion/sensing capable devices irrespective of the current state of the intelligent motion setting. To detect whether a device that supports motion has motion enabled inspect the DeviceState live data object provided by the Smart Motion extension.
- Known Issue: Utterance in Simulator will not trigger the wake word for Smart Motion Simulator. The only way to trigger the wake word for Smart Motion Simulator is to click the User object in the UI.
- Known Issue: Web simulator does not support PlayNamedChoreo command in SmartMotion extension yet.
- Skills with SmartMotion and EntitySensing extensions in their manifest may experience increased latency of up to 90 seconds and even time out when they are invoked for the first time during a skill session. To work around this issue, invoke the skill again.
- Video components do not play reliably on the Simulator.
- On devices using APLViewHostAndroid, the container component is not hiding/clipping the child component if child component overflows (larger) than the parent container component.
- Text taller than 95% of viewport height can not be shown.
- Shadows for zero opacity Frame components are visible and don't animate in/out with the Frame.
- Applying a transform on a Text component inside a ScrollView has no effect on devices but works in the authoring tool.
- Skills with SmartMotion and EntitySensing extensions in their manifest will see the extensions array in their skill request, when invoked from the simulator, despite the motion-simulator toggle not turned on.
- Known Issue: When using the ASK developer console's Test motion simulator to test APL documents PrimaryUser data (https://developer.amazon.com/en-US/docs/alexa/alexa-presentation-language/apl-ext-entity-sensing.html#primaryuser) may not update. To workaround this issue developers should set up both primaryUserName and entitySensingStateName in the entity sensing extension settings. When this issue is addressed developers will only need to set up the primaryUserName setting is all they need is PrimaryUser data.
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.2",
"mainTemplate": {
"items": [
{
"type": "Container",
"width": "100%",
"height": "100%",
"alignItems": "center",
"justifyContent": "center",
"items": [
{
"type": "Text",
"text": "${environment.agentName}"
},
{
"type": "Text",
"text": "${environment.agentVersion}"
}
]
}
]
}
}
