Specific Lovense LUSH3 causing exception (and Hush and Lapis) about buttplug HOT 9 OPEN

the one which doesn't work also has a couple of extra generic type characteristics, like the manufacturer name

from buttplug.

the same issue happens with my relatively new Lapis toy. It has the same extra services and the same extra characteristics, although the error is very slightly different.

from buttplug.

Maybe the "questionable assumptions" are not valid, although i don't know enough about Bluetooth to know:

    fn check_discovered(&mut self) {
        // It's time for QUESTIONABLE ASSUMPTIONS.
        //
        // For sake of being lazy, we don't want to fire device connection until
        // we have all of our services and characteristics. We assume that
        // set_characteristics should be called once for every entry in the
        // service map. Once that's done, we're filled out enough and can send
        // back a Connected reply to the waiting future with all of the
        // characteristic info in it.
        if !self.services.values().any(|service| !service.discovered) {
            if self.connected_future_state.is_none() {
                panic!("We should still have a future at this point!");
            }

from buttplug.

This is the log from before the error. This is actually the log from a relatively new Lovense Lapis.

from buttplug.

I note that the required service is the right one (starting 553000001) and the characteristics that it finds are also the right ones.

from buttplug.

Now i've seen a similar thing happen with the one that works. I am on a MacBook Air 7.2, running MacOS 10.15.7

It seems unlikely but could the machine be failing to service something in time?

nevertheless, the newer toys (including my Hush as well) all cause the problem during connection, while the older one does not.

from buttplug.