lukasIO

Interesting thought! I think it's a great way to further simplify state handling, but actually only in case `identity` is already known ahead of participant connections (I'm not sure how...

sure, moving it into `RTCEngine` seems like a good idea, as this already has some reconnect logic in it!

@davidzhao I thought about reusing the reconnectPolicy, but felt it's more predictable if initial reconnect attempts can be configured separately. Only downside is that currently there's no way to report...

maybe the work in https://github.com/livekit/client-sdk-js/pull/446 could serve as a workaround for this issue on edge, although not sure if that makes a difference at all if the autoplay is blocked...

on which iOS version do you see this failing? (and is there any error being thrown?)

this sounds like you didn't allow the website to use microphone/camera! make sure to test it on a secure host, it probably won't work for iOS if you use `http`...

@karthikSirsikar does it work for you ? just tried to reproduce the issue you mentioned (before deleting) when not publishing, but couldn't reproduce it

hm. it shouldn't create a feedback loop when calling `attach`. does the feedback loop also happen when running the sample ? (the sample also uses `attach`)

i meant the one in this repo, started with `yarn sample`

Coming back to this: Could it be that what you were seeing was the fact that `echoCancellation` doesn't work with webAudio? Or worded differently: does the loopback also happen when...