[BUG] iOS jwplayer example - ListExample seekTo not working

[leinnus]

Describe the bug
iOS ListExample seekTo() not working

Example/app/jsx/screens/ListExample.js

  const onBeforePlay = tag => {
    tags.map(player => {
      if (player !== tag) {
        playerRef.current[player]?.pause();
      }
    });

    playerRef.current['JWPlayer-1']?.seekTo('11');
  };

package.json

  "dependencies": {
    "@jwplayer/jwplayer-react-native": "https://github.com/jwplayer/jwplayer-react-native.git",
    "@react-navigation/native": "^7.0.13",
    "@react-navigation/native-stack": "^7.1.14",
    "react": "18.3.1",
    "react-native": "0.76.4",
    "react-native-bootsplash": "^6.3.2",
    "react-native-device-info": "^14.0.1",
    "react-native-fs": "^2.20.0",
    "react-native-gesture-handler": "^2.21.2",
    "react-native-orientation-locker": "^1.7.0",
    "react-native-safe-area-context": "^5.0.0",
    "react-native-screens": "^4.3.0",
    "react-native-vector-icons": "^10.2.0",
    "rn-iphone-helper": "^2.0.4"
  },

To Reproduce
Nothing note worthy here to reproduce

Steps to reproduce the behavior:

1. touch play icon
2. skip to 11 sec

Expected behavior
seek to 11 sec

Screenshots / Visual evidence

Device(s) affected

• Device: iPhone14
• OS: iOS 18.1

[Jmilham21]

Hey @leinnus, the seek function expects a number, and it looks like you're providing a string:

Do:
playerRef.current['JWPlayer-1']?.seekTo(11);
Instead of:
playerRef.current['JWPlayer-1']?.seekTo('11');

When passing a Number, I was able to have the player seek the expected timestamp like in your provided snippet (thank you). You should have seen a react-native debug warning if the app/device surfaces them when attempting to pass the String. If this isn't the issue, please let me know!

[leinnus]

Not working.

playerRef.current['JWPlayer-1']?.seekTo(11);

also not working.

playerRef.current['JWPlayer-1']?.play();

Could it be the difference in react-native versions?
my react-native version is 0.76.4
example version is 0.70.14

[Jmilham21]

@leinnus, you're correct; the issue is most likely related to your react-native version. Our library must still be prepared for production in the new architecture (bridgeless) model. I'd suggest that for now, if possible, to opt out.

I'll review what it will take for us to become usable in the new framework.

Created this Issue to look into this