jitsi / jitsi-meet-react-sdk

React SDK for Jitsi Meet
Apache License 2.0
65 stars 36 forks source link

ClockSync net::ERR_NAME_NOT_RESOLVED #22

Closed Tech-Dex closed 2 years ago

Tech-Dex commented 2 years ago

Hello.

I am trying to use the very basics and I am facing a weird issue. In short terms: sometimes jitsi react sdk works without any problem and sometimes it doesn't.

I think the below image provides most of the details you'll need: image

Code:

const configOverwrite = {
    startWithAudioMuted: true,
    hiddenPremeetingButtons: ['microphone'],
  };

const userInfo = {
    displayName: auth.user.username,
    email: auth.user.email,
  };

const handleExitMeeting = () => {
    navigator('/');
  };

<JitsiMeeting
              roomName={searchParams.get('roomName')}
              getIFrameRef={(node) => (node.style.height = conferenceHeight)}
              onReadyToClose={() => handleExitMeeting()}
              configOverwrite={configOverwrite}
              userInfo={userInfo}
              spinner={() => {
                return <Spinner animation="border" />;
              }}
            />
saghul commented 2 years ago

That's due to the default callstats integration. Is it set for your domain? You can disable it by overriding callStatsID and callStatsSecret with the empty string.

Tech-Dex commented 2 years ago

Hello @saghul. Yes, it is set on a domain. My initial thought was that is a issue related to time zones differences. Are there any issues in the future with empty strings for callStats*? I will try this and I am sorry for bothering you, thank you a lot.

saghul commented 2 years ago

No issues related to that, other than that you'll be disabling callstats.

Tech-Dex commented 1 year ago

Hello @saghul .

I am sorry to reopen this but I have one more question around amplitude. Right now it seems like the above behaviour is produced by a CORS error ( I think, I am not sure of it ) and sometimes the call will work and sometimes will fail. Is there any way to avoid this issue? I found that in the config.js there is a key "amplitudeAPPKey" and I tried to set it to an empty string but this will result in a constant error.

image
saghul commented 1 year ago

If you don't set an amplitude key amplitude wont be used at all. How are you setting it?

Tech-Dex commented 1 year ago

Right now I am not setting it:

  const configOverwrite = {
    startWithAudioMuted: true,
    hiddenPremeetingButtons: ['microphone'],
    callStatsID: '',
    callStatsSecret: '',
  };
Tech-Dex commented 1 year ago

@saghul Sorry to bother you again. Any idea around the above issue? Something that will allow me not to do that call? I still can't get over it.

saghul commented 1 year ago

Add the following to your overrides:

analytics: {
    amplitudeAPPKey: ''
}