Recover state on resuming application

[Dekkee]

Describe the bug
Recover playerState after minimize/maximize application

To Reproduce
Steps to reproduce the behavior:

1. Start application
2. Start playing
3. Press power button to lock phone
4. Press power button to turn on screen
5. Pause playing from
6. Unlock phone
7. Go to application
8. Application didn't switched state to "paused"

Expected behavior
Application in state "paused"

Runtime Environment (please complete the following information):

• Samsung Galaxy S7

Flutter SDK version

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 3.4)
[√] IntelliJ IDEA Ultimate Edition (version 2019.1)
[√] VS Code, 64-bit edition (version 1.28.0)
[√] Connected device (1 available)

Additional context
As fast fix I can do it in my app by reading state in connect method. But maybe you have some solutions for this?

[ryanheise]

Hi @Dekkee

Does this problem exhibit itself in the example app on your device?

[Dekkee]

Yes. In example from this repo. In both examples. Real and TTS.

[Dekkee]

On your device everything is fine?

[Dekkee]

In my case i solve it with this snippet in connect() method:

  void recoverState() {
    final media = AudioService.currentMediaItem;
    if (media != null) {
      _onMediaChanged(media);
    }
    final state = AudioService.playbackState;
    if (state != null) {
      _onStateChanged(state.basicState);
      _onProgressChanged(state.position);
    }
    debugPrint(
        'recoverState media: ${media?.title} state: ${state?.basicState}');
  }

[ryanheise]

Ah, you're right. In the example, the state changes are sent over the playbackStateStream immediately upon calling connect() but the client is not subscribed to the stream yet. So the solution is to switch the order around so that you subscribe to the stream(s) first and then call connect().

I've updated the example accordingly. Let me know if that also works for you.

[Dekkee]

Ok, I will try. But your idea with rxdart + BehaviorSubject is a good idea. It will resend last message on resubscribing.

[ryanheise]

Yes, I agree the rxdart approach proposed in my first comment (which is now unfortunately deleted) would be more robust. If I were to rewrite the example with a StreamBuilder I have a suspicion that it will subscribe too late and suffer the same consequences, so ultimately BehaviorSubject is probably the way to go. I'll test this tonight.

[Dekkee]

Current example works. Thank you!

[ryanheise]

FYI, I've just changed the streams to use BehaviourSubject so it should be less sensitive to the order in which you connect vs subscribe, and I've changed the example app to use a StreamBuilder.

[Dekkee]

Nice! Thanks!

[Dekkee]

will you bump version?

[ryanheise]

Yep, just published it :-)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs, or use StackOverflow if you need help with audio_service.