Player.DISCONTINUITY_REASON_AUTO_TRANSITION is being triggered when controller.stop() is called.

[debz-eight]

Scenario: I have my player UI that has a close button in its minimized state.

UI:

When I click on the close(cross) button, I am calling controller.stop(). Now this is trigerring Player.DISCONTINUITY_REASON_AUTO_TRANSITION. Is this expected behaviour?

My understanding is that AUTO_TRANSITION is being called when one mediaItem ends and next mediaItem starts playing automatically.

The issue I am facing due to this is: I have a specific set of logic that I want to only call when one mediaItem ends automatically and starts playing the next mediaItem. But when pressing the close button which calls controller.stop(), the logic is being called in this scenario too which I do not want it to be.

[tonihei]

I can't see this event happening in my setup. Could you provide more detailed reproduction steps for the media session demo app or share a minimal example that lets us reproduce the issue? If needed, you can send information to android-media-github@google.com with "Issue #1669" in the subject and report back here once you've done that.

[google-oss-bot]

Hey @debz-eight. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@debz-eight if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.