Closed corinnaj closed 2 years ago
Hey @corinnaj, do you know if this fix did actually work?
This was one of the bugs we found when we realised why we had to wait for a while before sending some messages. Part of the problem was that iirc the state was not reset correctly, meaning it would wait for a timeout if the first message was not a heartbeat but a data message. I think it might be worth merging this, even though we also fixed the problem on Unitys side. Maybe a quick test on Mac would make sense first
This should fix the problem when we cannot connect after sending i.e. "createObstacle" or "sendMotor" too early. Messages will still not be queued on the device to be processed after a connection is achieved, clients should thus poll until a connection is established (after the first syn ack is sent) before sending data of their own.