IOBluetoothDeviceOpenRFCOMMChannelAsync and Leopard
IOBluetoothDeviceOpenRFCOMMChannelAsync and Leopard
- Subject: IOBluetoothDeviceOpenRFCOMMChannelAsync and Leopard
- From: Daniel Birns <email@hidden>
- Date: Mon, 19 May 2008 20:56:29 -0700
| Hi,
An earlier thread mentioned getting MACH_SEND_INVALID_DEST more often in Leopard.
I can't be sure it's more often (I have both systems), but we do sometimes get this a lot. I really don't want to have to "wait 3 memorial seconds" (as was suggested in the previous thread) after closing bluetooth to do an open. That would basically break our app.
I should mention that it's a bogus error: using the very same arguments works as often as not. In fact the problem usually occurs when we reopen a device that we just closed.
Our architecture opens all available bt devices, opens them, exchanges some information and closes them, presenting this info to the user. The user then picks a device which it re-opens. Sometimes this process is automated, so that closing and reopening the same device can happen immediately upon finalization of the close. This is when we most frequently get this error.
--Daniel |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden