ClockSync net::ERR_NAME_NOT_RESOLVED about jitsi-meet-react-sdk

[saghul]

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

[saghul]

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]

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.

[Tech-Dex]

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.

[saghul]

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

[Tech-Dex]

Right now I am not setting it:

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

[Tech-Dex]

@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]

Add the following to your overrides:

analytics: {
    amplitudeAPPKey: ''
}