I am implementing Transport Control for the first time.
It appears the following issues are occurring:
① handlePrevious is not triggered (even though handleNext is triggered).
→ Saying “Alexa, previous” does not trigger handlePrevious, but saying “Alexa, next” triggers handleNext.
② After implementing Transport Control, simply pressing the “Play/Pause” button on the remote triggers handleTogglePlayPause.
→ handleTogglePlayPause should not be triggered in this case, as no voice command was issued.
③ Is it acceptable for “Alexa, stop” to trigger handlePause?
→ “Alexa, pause” also triggers handlePause.
→ Is it okay for both “Alexa, pause” and “Alexa, stop” to trigger the same handlePause event?
Thank you for your detailed report on the Transport Control implementation issues. We appreciate you providing the SDK version, device OS details, and relevant package information — this is very helpful for our investigation.
Our team will provide an update as soon as we have more information. In the meantime, if you have any additional logs or observations, please feel free to share them here.
Thank you for your patience. To help our team investigate the Transport Control issues, could you please provide the Device logs captured while reproducing each of the three issues (①, ②, and ③)
Please share the logs at your earliest convenience.
Here’s an update on your Transport Control issues:
Issue ② and ③: These are expected behavior by design. Play/Pause remote button routing through KMC and “Stop” mapping to handlePause are intentional.
Issue ① (handlePrevious): We need full end-to-end device logs to continue the investigation. The current logs don’t have enough coverage to confirm whether the directive is being received.
Could you please capture full system logs (not filtered to your app) while reproducing the “Alexa, previous” issue?
Feel free to reach back to me if you have any questions!
