Oleksandr1997
New Member
We are building the application on react.js with the use of conference stream logic. Currently, as soon as the component is mounted - it connects to the conference room and starts the playback of the stream, which can be streamed from both iOS and Android.
After that the user has the ability to start audio record from browser to the same room. For iOS devices we use playFirstVideo() when starting to publish.
The recording stream is stored in state. Than the user has the ability to mute this stream via this.state.recordingStream.muteAudio(), and unmute with .unmuteAudio()
All works perfectly well apart from iOS Safari, there - the record starts successfully, mute also works, but when I try to unmute again (via button onClick) - it no longer gives sound.
As a temporary solution, we stop recording each time, and start it again in iOS Safari, but would really like not to use such approach. Can you give any advice on what can be wrong with unmuteAudio on iOS Safari?
After that the user has the ability to start audio record from browser to the same room. For iOS devices we use playFirstVideo() when starting to publish.
The recording stream is stored in state. Than the user has the ability to mute this stream via this.state.recordingStream.muteAudio(), and unmute with .unmuteAudio()
All works perfectly well apart from iOS Safari, there - the record starts successfully, mute also works, but when I try to unmute again (via button onClick) - it no longer gives sound.
As a temporary solution, we stop recording each time, and start it again in iOS Safari, but would really like not to use such approach. Can you give any advice on what can be wrong with unmuteAudio on iOS Safari?
