William Emfinger

Update: I have confirmed that the error reported above occurs when parsing the `nav_msgs::Path` and not the `sensor_msgs::PointCloud2`. When only subscribing to the `sensor_msgs::PointCloud2` the app works fine - no...

Further Update: I've confirmed that the same errors occur when receiving Path data / Image data on Windows - so it is not specific to the android bson library I...

Update: I am able to receive on all platforms (Windows, Mac, Android - haven't tested linux): * `sensor_msgs/PointCloud2` * `tf2_msgs/TFMessage` * `nav_msgs/Path` Windows and Mac: * `sensor_msgs/Image` - but only...

Even better :)

Hmm, wouldn't it be easier (since they don't affect layout much) for that to happen internally within the layout routine? :)

I see this too in our project - happens for me when the app is refreshed and a snackbar is created by a service before the app is fully initialized

``` JS: **** App Resume Event **** JS: **** App Suspended Event **** JS: making service JS: Adding characteristics to service! JS: **** App Resume Event **** 10-08 11:54:24.272 30829...

Was this ever solved? Looking to move from bluedroid to NimBLE and would like to use esp-nimble-cpp but we definitely need multiple services. If this is close and still valid...

@h2zero i've noticed (on esp-idf `v5.2.1`) that the `ble_store_clear()` doesn't work as expected - I still get too many bonded device errors even though every time i enter pairing mode...

I'm not sure why this says the build is failing but I'm able to run my own code as well as the examples from [ros/common_tutorials](https://github.com/ros/common_tutorials)