Playing Amazon Music failed to display matadata on the timestamp on v2.1

[yuan0258]

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.

Briefly summarize your issue:

The timestamp can be display correctly on SSSDK v2.4 but not on v2.1.
We cloudn't upgrade version from v2.1 to v2.4 for MP purpose.
How could we get the patch for this issue only?

What is the expected behavior?

UI show timestamp information corretly
v2.4

v2.1

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Play amazon music on device

Tell us about your environment:

What version of the AVS Device SDK are you using?

  AVS Device SDK: <1.19.1>
  APL core library: <1.3.3>
  Alexa smart screen SDK: <2.1.0>

Tell us what hardware you're using:

• [] Desktop / Laptop
• [*] Raspberry Pi
• [] Other - tell us more:

Tell us about your OS (Type & version):

• [*] Linux
• MacOS
• Raspbian Stretch
• Raspbian Jessy
• Other - tell us more:

Have you tried the same use case with AVS Device SDK SampleApp?

• The issue is not applicable to the AVS Device SDK SampleApp.
• [*] The issue is not reproducible on the AVS Device SDK SampleApp.

[zsubas]

Hello,

Thank you for reaching out!

Time/Length support for player info card introduced at version 2.3: https://github.com/alexa/alexa-smart-screen-sdk/releases/tag/v2.3.0

Unfortunately, we don't have a specific patch for supporting this on 2.1, in order to get this future you need to use 2.3 or above.

[yuan0258]

@zsubas,

Thanks for your reply.
One more question abouot it.
Which module(apl-core-library or ss-sdk) will impact this issue?

[zsubas]

Hey yuan0258,

In this scenario both affects. apl-core provides the APL (which contains the length information). Smart screen sdk parses this information and displays it on the screen.

[yuan0258]

Hi zsubas,
OK. We are trying to find Amazon QA team to negotiated this issue.
Thanks for your reply

[vkarpuram]

Closing out this issue as there is no further action required from our end. Please let us know if you need additional assistance

[yuan0258]

@vkarpuram,

We need to re-open this issue because Amazon QA team couldn't waiver this issue.