Brett Sutton

Good question and I don't know the answer. I should say that we are removing ioscategory from the API as we are looking for the API to be completely platform...

The wasUser flag is meant to indicate that a user caused the stop to occur. If wasUser is false then the system naturally ended. There is a bug in ShadePlayer...

There are separate events for onPause, onResume etc. wasUser on the onStop was intended to differentiate between the playback ending naturally vs the user stopping the playback through something like...

No the events are the same no matter whether you use the shade or not. I don't understand the source of your question as it doesn't seem to lead in...

we should suppress onStopped events being generated form indirect actions like skip that causes a stop as a side effect. onStop should only be called if it is the 'end...

At the very least the finally block is a problem as it will execute even if the exception is thrown

Can you provide a more complete example. On Wed, 2 Sep 2020, 11:41 pm mtkgeek, wrote: > Removing the finally block doesn't solve the issue. The problem ultimately > for...

I have a theory the problem is in QuickPlay._play try changing it to the following (note the extra awaits) ``` dart Future _play(double volume) async { await _player.setVolume(volume); await _player.audioFocus(AudioFocus.hushOthersWithResume);...

I've pushed the above code to git. If you could give it a test that would be helpful.

I've pushed a possible fix to github. On Wed, 16 Sep 2020 at 18:30, IWANTANELEPHANT wrote: > Hi, > I have the same problem. I record an acc file, save...