August
August
Closing, see #945
We may could think about removing the `onDuration` and `onPosition` event on the native side, and request the according native values on a async runner on the dart side every...
I tested by [replacing](https://github.com/Gustl22/audioplayers/blob/9865ae4e138bd43bc5f4287b1d944f09f9d830b4/packages/audioplayers/example/lib/tabs/sources.dart#L32) `setSource` with `play` in [my example](https://github.com/Gustl22/audioplayers/tree/feat/extended-tests) (where I have added a FilePicker) and didn't experience such behavior. Can you retest with the example. Please use issue...
Still working with API 32. Did you try [my example](https://github.com/Gustl22/audioplayers/tree/feat/extended-tests/packages/audioplayers/example). You can also clone it and replicate your problem there. Plz use proper **issue template** to better determine the source...
Related to #151, but maybe disable this ones permanently (?)
This should be easy to fix by moving the [`onDuration` event](https://github.com/bluefireteam/audioplayers/blob/ff78a42f842e146df7dc98d6d00ae27821355653/packages/audioplayers_android/android/src/main/kotlin/xyz/luan/audioplayers/AudioplayersPlugin.kt#L215) to when `prepared` was called.
Sorry, web, darwin and android are still missing...
On which platforms do you experience this? Can you check, is this still a thing with 1.x.x? Thx :)
Closing as stale.
I don't agree. It's already described one line above. It only wants to clarify what happens, if you resume the stream. See also the `player.stop()` description. It it's confusing, we...