someone know how to fix it, or what previous version works?

It seems that the version 2.6.0 is not properly published on npm. You did a fix on gituhub to use the componentWillUnmount lifecycle hook instead of the componentDidUnmount that does not exist. Can you double check that?

We are using this library to create rooms that 3 people can join. Initially when all the 3 people join the room everything is fine. If some of the users will refresh to page though, then the user should be removed from the screen and then join again. But what happens is that the old stream remains frozen, a new stream joins and the 3rd one is like being kicked out.

This is the start of the session:
user_1 screen: u1 u2 u3
user_2 screen: u2 u1 u3
user_3 screen: u3 u1 u2

The user_2 is refreshing the page. One possible scenario will be:
user_1 screen: u1 u2(frozen) u2
user_2 screen: u2 u1 u3
user_3 screen: u3 u1 u2

This is a DOM snapshot before refresh:

<video autoplay="" id="video-undefined" style="transform: rotateY(180deg);"></video>
<video autoplay="" id="video-dpkfbvgujff2loxu_CAMERA_PCTXM"></video>
<video autoplay="" id="video-qdva5burkyo3azoq_CAMERA_WPKOS"></video>

and this is after refresh:

<video autoplay="" id="video-uhlvixevneoe1utf_CAMERA_RDETJ" style="transform: rotateY(180deg);"></video>
<video autoplay="" id="video-qdva5burkyo3azoq_CAMERA_WPKOS"></video>
<video autoplay="" id="video-gcwycld95y6fofwo_CAMERA_ZCFUS"></video>

The id video-qdva5burkyo3azoq_CAMERA_WPKOS should not be there after the refresh and instead the video-gcwycld95y6fofwo_CAMERA_ZCFUS should be in the second place and in the third place we should see another identifier

In some cases it seems that the state is being mutated not by invoking the the setState but by using the splice which can cause some side effects like in the deleteSubscriber function in the VideoRoomComponent.js

Is there an example react that I can use in order to find out if this is a problem of our implementation or if this is a problem of the open-vidu-call-react?

Hi there.

I'm testing this react library in order to add webrtc capabilities to a hybrid mobile application. As far as I know, the highest version of this library has a dependency on 16. Am I mistaken? If not... have you plans to build a release of the library for react 17? Thanks in advance.

Hello react team.
Do you have plan to develop similar to angular proeject?

This was odd. Pycharm detected an error on this line of StreamComponent.js due to the naked span tag.

It looks like a downstream dependency of eslint, prelude-ls, causes the naked span in this inline ternary operator to be picked up as utility from that library. This triggers an error there and throughout the rest of the component in the current release.

I don't understand exactly why but it can be resolved simply by adding an empty attribute to the span.

Could the dependency tree be updated as I am getting (production build)

Creating an optimized production build...
Failed to compile.

./src/index.css
Module build failed: BrowserslistError: Unknown browser query `dead`
    at Array.forEach (<anonymous>)

SO + googling indicates that a dependency uses a very old browserslist.
npm ls shows 1.7.7 and 2.11.3 versions used.

These versions are still compatible with each other, but openvidu-browser version must be updated as soon as possible to 2.28.x. This client using openvidu-browser 2.27.0 will become incompatible with the next release of openvidu-server

Please fix it.

Appears to be the same issue as OpenVidu/openvidu-tutorials#127.

Will offer a PR

The current version of the application, specifically the VideoRoomComponent.js has issues while sharing the screen with Firefox for Ubuntu in version 95.0.1 (64-bit), I'm not sure if this problem is present in other operating systems.

For me, the problem was fixed by changing the following lines, starting in line 397

- const videoSource = navigator.userAgent.indexOf('Firefox') !== -1 ? 'window' : 'screen';
const publisher = this.OV.initPublisher(
    undefined,
    {
-        videoSource: videoSource,
+        videoSource: 'screen',
        publishAudio: localUser.isAudioActive(),
        publishVideo: localUser.isVideoActive(),
        mirror: false,
    },

Would openvidu work well with the redux structure?

hello

Is there any sample sample for react hook?

hello i m getting a
Can't resolve '/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/assertThisInitialized'

is this project still being used?

Hi @pabloFuente . I'm facing a problem now.

./node_modules/openvidu-react/dist/components/VideoRoomComponent.js
Module not found: Can't resolve '/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/assertThisInitialized' in '/home/vagrant/workspace/openvidu-tutorials/openvidu-library-react/node_modules/openvidu-react/dist/components'

I checked out current (today's) master branch of openvidu-tutorials and I performed npm install in ./openvidu-tutorials/openvidu-library-react .
The head of ./node_modules/openvidu-react/dist/components/VideoRoomComponent.js was below:

import _classCallCheck from "/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/classCallCheck";
import _createClass from "/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/createClass";
import _possibleConstructorReturn from "/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/possibleConstructorReturn";
import _getPrototypeOf from "/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/getPrototypeOf";
import _inherits from "/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/inherits";
import _assertThisInitialized from "/home/pablo/Desktop/openvidu-call-react/library/node_modules/@babel/runtime/helpers/esm/assertThisInitialized";

And then, It's working well when I downgraded openvidu-react from 2.7.1 to 2.6.0.
The latest version seems that have a problem.
I hope this report will be of some help.

Best Regards,
Keisen.

Originally posted by @keisen in #5 (comment)