PlaybackProgressUpdated event dispatches different "buffer" property on Android and on IOS

[czekFREE]

Describe the Bug PlaybackProgressUpdated event dispatches different "buffer" property on Android and on IOS. On IOS event.buffered is being dispatched, on Android event.buffer is being dispatched. According to documentation only event.buffer should be dispatched - see https://rntp.dev/docs/next/api/events#playbackprogressupdated, but according to typings event.buffered should be dispatched (see https://github.com/doublesymmetry/react-native-track-player/blob/main/src/interfaces/events/PlaybackProgressUpdatedEvent.ts and https://github.com/doublesymmetry/react-native-track-player/blob/main/src/interfaces/Progress.ts)

Steps To Reproduce

Code To Reproduce

Replicable on Example App?

Environment Info: System: OS: macOS 13.5.2 CPU: (10) arm64 Apple M1 Pro Memory: 105.73 MB / 16.00 GB Shell: version: 3.2.57 path: /bin/bash Binaries: Node: version: 16.19.0 path: ~/.nvm/versions/node/v16.19.0/bin/node Yarn: Not Found npm: version: 8.19.3 path: ~/.nvm/versions/node/v16.19.0/bin/npm Watchman: version: 2023.05.01.00 path: /opt/homebrew/bin/watchman Managers: CocoaPods: version: 1.11.3 path: /Users/jibeleck/.rbenv/shims/pod SDKs: iOS SDK: Platforms:

• DriverKit 22.4
• iOS 16.4
• macOS 13.3
• tvOS 16.4
• watchOS 9.4 Android SDK: Not Found IDEs: Android Studio: 2022.2 AI-222.4459.24.2221.9862592 Xcode: version: 14.3.1/14E300c path: /usr/bin/xcodebuild Languages: Java: version: 11.0.15 path: /Users/jibeleck/.jenv/shims/javac Ruby: version: 2.7.4 path: /Users/jibeleck/.rbenv/shims/ruby npmPackages: "@react-native-community/cli": Not Found react: installed: 18.2.0 wanted: 18.2.0 react-native: installed: 0.72.1 wanted: 0.72.1 react-native-macos: Not Found npmGlobalPackages: "react-native": Not Found Android: hermesEnabled: true newArchEnabled: false iOS: hermesEnabled: true newArchEnabled: false

Paste the exact react-native-track-player version you are using "react-native-track-player": "4.0.0-rc08",

Real device? Or simulator? IOS tested on simulator, android on device

How I can Help If you want, I could help with that, but I would have to know what it the way how this should be fixed - I would guess to rename ios/android property to be consistent, I do not know which one + this might be considered dangerous / breaking change, so I do not know if you want that...

[dcvz]

Thanks for reporting @czekFREE! This has been fixed and will go out in the next RC