livekit-api fails compiling because of missing `CLIENT_PROTOCOL_DATA_STREAM_V2`

[sdroege]

error[E0432]: unresolved import `livekit_common::CLIENT_PROTOCOL_DATA_STREAM_V2`
  --> ~/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/livekit-api-0.6.1/src/signal_client/mod.rs:67:38
   |
67 |     CLIENT_PROTOCOL_DATA_STREAM_RPC, CLIENT_PROTOCOL_DATA_STREAM_V2, CLIENT_PROTOCOL_DEFAULT,
   |                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `CLIENT_PROTOCOL_DATA_STREAM_V2` in the root
   |
help: a similar name exists in the module
   |
67 -     CLIENT_PROTOCOL_DATA_STREAM_RPC, CLIENT_PROTOCOL_DATA_STREAM_V2, CLIENT_PROTOCOL_DEFAULT,
67 +     CLIENT_PROTOCOL_DATA_STREAM_RPC, CLIENT_PROTOCOL_DATA_STREAM_RPC, CLIENT_PROTOCOL_DEFAULT,
   |

[Jeremmyy]

Ran into the same thing here. Had a dig, and it looks like a missing livekit-common publish.

Commit 557f702e ("Data streams v2", #1192) added ClientCapability, RemoteParticipantRegistry and CLIENT_PROTOCOL_DATA_STREAM_V2 to livekit-common/src/lib.rs, but livekit-common/Cargo.toml on main still reads version = "0.1.0", so the crate never got republished. crates.io is still serving 0.1.0, which doesn't have those three symbols.

Two published crates import them unconditionally:

• livekit-data-stream 0.1.1, at src/outgoing/manager.rs:17
• livekit-api 0.6.1, at src/signal_client/mod.rs:67

livekit-api 0.6.0 doesn't reference them, in case that helps narrow it down.

livekit 0.8.1 can't route around it, since it requires livekit-data-stream ^0.1.1 and 0.1.1 is the only version in that range.

I had a look at PR #1298 too. It touches 21 files, none of them under livekit-common, livekit-api, livekit-data-stream or livekit-protocol, so I don't think that release will clear it on its own.

Happy to open a PR with the version bump if that's all it needs. Just let me know.

For anyone else who lands here in the meantime, these pins work if you can stay on the 0.7.5x line:

cargo update -p livekit-data-stream --precise 0.1.0
cargo update -p livekit-datatrack   --precise 0.1.11
cargo update -p livekit-protocol    --precise 0.7.10

The last two go together: livekit-datatrack 0.1.12 and 0.1.13 require livekit-protocol 0.7.11 and 0.7.12, and wait_until_answered (added in 0.7.11) is a required field on ConnectWhatsAppCallRequest that livekit-api 0.5.6 never populates (see services/connector.rs:265).

That set builds against livekit 0.7.53 and passes our full suite here.

Thanks for the quick turnaround on the 0.8 line generally, it's been easy to follow.

[ladvoc]

Thank you for reporting this issue, livekit-common v0.1.1 has now been published to crates.io.