Closed LoopIssuer closed 11 months ago
Hey @LoopIssuer , this issue has been reported on Windows. On Android, can you share the full logs from logcat
? Also, make sure that you're on VideoKit 0.0.15.
Unfortunately, logcat is unavailable - we get only errors from users via analytics. We are using currently 0.0.15-alpha.6.
Could you please say something about this issue - is it blocker, application crashes?
Hey @LoopIssuer , can you upgrade to VideoKit 0.0.15? The session token handling was improved in the final release.
Also, this should never result in a crash.
Thank you. If no crash, then VideoKit is just not working in that case? Or maybe this error is only some kind of warning and everything is working?
That's correct. It throws an InvalidOperationException
in code that you can surround in try { ... } catch
Sorry, but please clarify, I don't understand last one: Am I correct because: a) VideoKit is just not working in that case b) this error is only some kind of warning and everything is working
Hey @LoopIssuer following up on this. If the token is invalid, then you will get an InvalidOperationException
when you call VideoKitRecorder.StartRecording
, MediaRecorder.Create
, CameraDevice.StartRunning
, or AudioDevice.StartRunning
. You can catch these errors with a try { } catch
block.
Thank you for the info :)
Hi We have noticed some of the logs on the analytics with this message:
Affected devices are so far: OPPO/CPH2385/OP571DL1 Android OS 12 / API-31 (SP1A.210812.016/S.R4T2.d1c72a-3591e) CPU ARM64
LGE/LM-G900TM/mcaymanlm Android OS 12 / API-31 (SKQ1.211103.001/6885120230801) CPU ARM64
Hard to say if this ends with some crash or sth like that. My question is - can this be an issue that blocks using Videokit, or maybe it is only warning or false error?
VideoKitToken.txt