Work around a Jitsi log handling crash (#22353)

pull/22358/head
Robin 2022-05-25 17:50:27 -04:00 committed by GitHub
parent 745140e9e7
commit 9c92f55afd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions

View File

@ -366,8 +366,12 @@ function joinConference(audioDevice?: string, videoDevice?: string) {
startAudioOnly, startAudioOnly,
startWithAudioMuted: audioDevice == null, startWithAudioMuted: audioDevice == null,
startWithVideoMuted: videoDevice == null, startWithVideoMuted: videoDevice == null,
// Request all log levels for inclusion in rageshakes // Request some log levels for inclusion in rageshakes
apiLogLevels: ["warn", "log", "error", "info", "debug"], // Ideally we would capture all possible log levels, but this can
// cause Jitsi Meet to try to post various circular data structures
// back over the iframe API, and therefore end up crashing
// https://github.com/jitsi/jitsi-meet/issues/11585
apiLogLevels: ["warn", "error"],
} as any, } as any,
jwt: jwt, jwt: jwt,
}; };