Unity-Technologies/ROS-TCP-Connector

Support common interface messages in humble

Opened this issue · 0 comments

Describe the bug
The ROS2 distro Humble (https://docs.ros.org/en/humble/index.html) has updated common_interface messages. The TCP Connector throws an exception when attempting to deserialize, for example, MarkerMsg because the message in Humble has new fields.

To Reproduce
Steps to reproduce the behavior:

  1. Create a project that subscribe to a MarkerMsg topic (or MarkerArray).
  2. Publish a MarkerMsg message
  3. Observe an exception thrown in MessageDeserializer.cs

Console logs / stack traces
Please wrap in triple backticks (```) to make it easier to read.

Expected behavior
MarkerMsg (and MarkerArray) messages should desterilize without exceptions.

Screenshots
If applicable, add screenshots or videos to help explain your problem.

Environment (please complete the following information, where applicable):

  • Unity Version: [e.g. Unity 2021.3.2f1]
  • Unity machine OS + version: [e.g. Windows 10]
  • ROS machine OS + version: [e.g. Ubuntu 20.04, ROS Humble]
  • ROS–Unity communication: [e.g. Docker]
  • Branch or version: [e.g. v0.7.0]

Additional context
Running MessageGenerator tool on the Humble branch of common_interfaces repo fixes the problem.