Closed Tails closed 6 months ago
Specifically, the native trace seems to point to here:
Hey, we're currently linking libwebrtc statically. It has the drawback that you need to manually add the -ObjC linker flag, the simplest way is to use this .cargo/config here.
We're working on adding the ability to dynamically link libwebrtc so the onboarding/devex will be much easier/better
Wizard! I had been wrecking my brain for nights. Thank you a lot for the quick response.
For future reference, for anyone running 'cargo run' from the command line, be sure to prefix with RUSTFLAGS="-C link-args=-ObjC"
because it won't pick up the config from the Cargo.toml, also not after cleaning.
I have a relatively simple handler (Mac M2) that starts
livekit-server
in dev as a child process, and then uses the SDK to create a room, and finally tries to connect to the room and listen for room events. However, in the last step I get some trace error that seems to be coming from the PeerConnectionFactory ffi code running in the webrtc lib. I'm running 0.3.2 of livekit and livekit_api, and 1.6.1 of livekit-server (installed from brew).Here is the code:
And here is the trace:
What do you think this could be? It seems to be a problem in some signalling trying to inform a process about a codec (requirement) that is unrecognized, but I'm not sure.