RPC transaction id mismatch #276

Closed
opened 2026-04-05 18:15:43 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @notpeelz on 8/31/2025

I'm messing around with the SolarXR protocol for a project and I noticed that the server doesn't reply to RPC messages using the transaction id that was specified by the client. This contradicts the behavior described in the protocol.

Current behavior:

  1. client sends:
RpcMessageHeader {
  tx_id: 1,
  message_type: RpcMessage::TrackingPauseStateRequest,
  message: TrackingPauseStateRequest {},
}
  1. server replies with:
RpcMessageHeader {
  tx_id: 17,
  message_type: RpcMessage::TrackingPauseStateResponse,
  message: TrackingPauseStateResponse {
    trackingPaused: false,
  },
}

Expected behavior:

The server replies with tx_id: 1.

*Originally created by @notpeelz on 8/31/2025* I'm messing around with the SolarXR protocol for a project and I noticed that the server doesn't reply to RPC messages using the transaction id that was specified by the client. This contradicts [the behavior described in the protocol](https://github.com/SlimeVR/SolarXR-Protocol/blob/df26226d104f75527a669e03879be675777885e3/schema/rpc.fbs#L87). Current behavior: 1. client sends: ``` RpcMessageHeader { tx_id: 1, message_type: RpcMessage::TrackingPauseStateRequest, message: TrackingPauseStateRequest {}, } ``` 2. server replies with: ``` RpcMessageHeader { tx_id: 17, message_type: RpcMessage::TrackingPauseStateResponse, message: TrackingPauseStateResponse { trackingPaused: false, }, } ``` Expected behavior: The server replies with `tx_id: 1`.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/SlimeVR-Server#276