Pandora music goes to Idle state unexpectedly

[zeusshuang]

Hi AVS team,

SDK 1.7.1

After about one hour, Pandora music goes to Idle state automatically.
From the log, I saw the last display card message at line#62589.

Actually, this issue also can be found on Prime Music or TuneIn radio test.
Here I attached Pandora log.

19416.txt

[visayamv]

@zeusshuang , I'm reviewing the log you submitted

[visayamv]

@zeusshuang , The log shows "Connecting" at the end which means that your device was disconnected from the network. During this time, the device failed to fetch the next audio stream to be played.

[zeusshuang]

Hi @visayamv ,

Do you mean that the player go to idle state automatically while connected fail at that time ?

[visayamv]

The player will stop if it can play the music or was not able to receive the appropriate directive. Please reference this doc: https://developer.amazon.com/docs/alexa-voice-service/audioplayer.html

[zeusshuang]

Hi @visayamv

We have got the case again at customer's home. see my attached log. You can search keyword "pandora".
The customer said it's suddenly stop music, and Alexa will not respond any command until now.
It seems it's go into some kind of loop (seems related to case#473 , due to I add log followed by case#473 suggestion, and I can see it in my log).

In the log, I still can see HTTP ping okay to server, but seems some E message dump.
You will see two different time stamp in the log, the time stamp in [xxx] is our internal log, it's local time, AVS is UTC time.
It's SDK 1.7.1

fail.log

[zeusshuang]

Hi,

I forgot to mention different symptom while running this case.
The worst case is as my log, it will go into some kind of loop, and no response anymore, restart AVS is the only way to rescue AVS.
Sometimes, it will just stop playing, but it's interesting, the APP will still show it's under playing.
I can ask Alexa to resume it and let it continue to play.

[BennyAvramson]

Hi,

(Looking on the 2nd logs)
The issue starts with getting exceptions from the cloud:

2018-06-27 22:24:49.069 [ 4c] E MessageRequest:onExceptionReceived:exception={"header"\:{"namespace"\:"System"\,"name"\:"Exception"\,"messageId"\:"8cd30a1c-079d-4e98-9de7-df58c7b6b1dc"}\,"payload"\:{"code"\:"INTERNAL_SERVICE_EXCEPTION"\,"description"\:"Request could not be executed due to an internal service error."}}

In order to investigate the reason for the exception, could you reproduce the issue?

Then the SDK is getting into abnormal state:

2018-06-28 10:55:11.985 [  a] E ContextManager:updateStatesLoopFailed case#473:waiting on=PlaybackState,nameSpace=AudioPlayer
2018-06-28 10:55:11.985 [  a] E ContextManager:updateStatesLoopFailed:reason=stateProviderTimedOut
2018-06-28 10:55:11.986 [  a] E SpotifyESDKAdapter:contextRetrievalFailed:reason=contextRequestErrorOccurred,error=STATE_PROVIDER_TIMEDOUT

which is a bug (See: #727) we'll fix in the next release.

Thanks,
Benny

[zeusshuang]

Hi @BennyAvramson ,

In our site, I still cannot find a way to reproduce this case by steps.
By users reports, it looks like happens during playing music and seems not only happen on Pandora, also a user reported on iHeartRadio and TuneIn.
And by users' feedback, the symptom ever happen in 15 minutes, but could not reproduce again after a restart.

Thanks,

[celinval]

As Benny pointed out, this is likely to have the same root cause as #727.

I'm going to close this issue now, but please feel free to reopen it if you find any new information related to this problem.

Thanks

[zeusshuang]

Hi @celinval ,

Just got the same case from user site, and it's the same symptom, but this user playing TuneIn radio for two hours.