Closed Tech-Dex closed 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.
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.
No issues related to that, other than that you'll be disabling callstats.
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.
If you don't set an amplitude key amplitude wont be used at all. How are you setting it?
Right now I am not setting it:
const configOverwrite = {
startWithAudioMuted: true,
hiddenPremeetingButtons: ['microphone'],
callStatsID: '',
callStatsSecret: '',
};
@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.
Add the following to your overrides:
analytics: {
amplitudeAPPKey: ''
}
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](https://user-images.githubusercontent.com/44111988/186887777-6489693e-9a11-47b8-90cd-a6cf0f328a16.png)
Code: