buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
Received onMixedAudioRawDataReceived
buffer :
buffer is printing empty and where that audio.pcm will be saved?
hey @kamalkumar77a could you guide us through how you fixed this issue, we are still encountering it.
also why are you generating jwt signatures if using the native sdk, there is no mention of generating signature in the github repo documentation @chunsiong.zoom
ok get it, so where in linux is the jwt signature being used for authentication, we have the linux sdk incorporated , also have logic of jwt generation working properly, how do we authenticate our linux sdk now
@kamalkumar77a Thanks for pining me about this. I pushed out an update that should resolve the issues that you’re seeing. Let me know if you continue to have issues after pulling the latest version.