TypeError: Cannot read property 'document' of null

[rodreiser]

The problem is occurring when i watch a second video in fullscreen mode. Here the Steps to reproduce this error:

• Watch the first video and enter in fullscreen
• Choose another video and watch in fullscreen

At the moment when i enter in fullscreen mode from the second video, the error is thrown and when i leave fullscreen the error is thrown again.

if i choose a third video, when i enter in fullscreen mode 2 errors are thrown and when i leave more 2 erros.

And this cycle goes on, video after video, always increasing 1 error.

The place where i embed the player is a react component. The player is embed in componentDidMount LifeCicle:

  componentDidMount() {
       this.lastFiredPosition = 0;

      kWidget.embed({
        targetId: this.playerId,
        wid: 'xxxxxx',
        uiconf_id: 'xxxxxxx',
        entry_id: this.props.kalturaVideoId,
        readyCallback: this.onPlayerReady,
      });
  }
  onPlayerReady = (ready) => {
    const kdp = this.playerDOM();
    kdp.kBind('doPause', this.onPause);
    kdp.kBind('doPlay', this.onPlay);
    kdp.kBind('playerPlayEnd', this.onPlayEnd);
    kdp.kBind('mediaReady', () => {
      if (this.props.position > MIN_SEEK_SECS) {
        kdp.sendNotification('doSeek', this.props.position);
      }
      kdp.kBind('playerUpdatePlayhead', this.onPlayerProgress);
      kdp.kUnbind('mediaReady');
    });
  };

and then when componentWillUnmount();

  componentWillUnmount() {
    kWidget.destroy(this.playerDOM());
  }

It appears that kWidget.destroy are not removing some listeners of enterfullscreen and leavefullscreen event.

Anyone have an idea of why this is happening?

We are using Kaltura SaaS

Thank you in advance

[kaltura-hooks]

Hi @rodreiser,

Thank for you reporting an issue and helping improve Kaltura!

To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):

• Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
  please provide as much details as possible.
• Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
  If self hosted, are you using the RPM or deb install?
• Packages installed.
  When using RPM, paste the output for:

	# rpm -qa \"kaltura*\"

For deb based systems:

	# dpkg -l \"kaltura-*\"

• If running a self hosted ENV - provide the MySQL server version used
• If running a self hosted ENV - is this a single all in 1 server or a cluster?
• If running a self hosted ENV, while making the problematic request, run:

	# tail -f /opt/kaltura/log/*.log /opt/kaltura/log/batch/*.log | grep -A 1 -B 1 --color \"ERR:\|PHP\|trace\|CRIT\|\[error\]\"

and paste the output.

• When relevant, provide any screenshots or screen recordings showing the issue you're experiencing.

For general troubleshooting see:
https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.13.0/doc/kaltura-packages-faq.md#troubleshooting-help

If you only have a general question rather than a bug report, please close this issue and post at:
http://forum.kaltura.org

Thank you in advance,

[itaykinnrot]

Thanks @rodreiser - we're checking

[joelworsham]

I'm also experiencing this issue

[hasentopf]

me too :-(

[amulgarg]

Hi @rodreiser , any update on this? This error is showing up frequently in our sentry logs