Error: Unknown event handler property `onReady`. It will be ignored.

[maks-io]

Hi,

i am using the latest react-player version as of today (3.3.1) and i am receiving a hook.js:608 Unknown event handler property onReady. It will be ignored. error.

Something seems off - the onReady prop did not get deprecated as far as I can see.

Relevant dependencies in my project are as follows:

"dependencies": {
    "env-var-manager": "^3.0.5",
    "next": "15.4.2",
    "react": "^19.1.0",
    "react-dom": "^19.1.0",
    "react-player": "^3.3.1"
  }

Any help is appreciated - thanks!

[leitsyshyn]

Yup, same issue, though it works for me, just shows an error in the browser for some reason

[eshy]

I'm seeing the same warning for onReady and onStart and the event handlers aren't called.

[maks-io]

Exactly, maybe I didn't express myself well enough, but - also for me - the handlers are not being called. If it was "only" about the error in the console I maybe wouldn't even have realized that.

To identify when this regression was introduced, I also tried using the following versions:

• 3.0.0 <- error still there
• 2.16.1. <- error NOT there

So it was introduced with version 3 - i am just surprised that nobody had reported it so far - am I the only one using the event handlers? 😅
Or maybe I am just bad at searching through existing github issues haha.

[maks-io]

I stand corrected: I just did another check and fixed some implementation on my side and realized that now onReady is indeed being called, only the error is still there.

Now it all makes way more sense, that nobody had reported it so far etc. - sorry guys!

[ryanburst]

I actually just opened a PR that should address this.

[maks-io]

I actually just opened a PR that should address this.

Nice, thank you!

[judocode]

I stand corrected: I just did another check and fixed some implementation on my side and realized that now onReady is indeed being called, only the error is still there.

What did you fix? I'm on 3.3.1 and I'm not getting any errors but onReady is not being called at all for me

[luwes]

fixed in #1970

@judocode what's your source url? some providers might not fire that event.