MacID for OS X reconnection procedure

As MacID becomes more popular, more and more people in offices are using it.

This is awesome, but in an environment like this it really shows up an issue where MacID has to “ping” everything nearby to reconnect to your device.

I really wish I didn’t have to do this, but there are a couple of issues with Bluetooth on OS X that mean I have to.

  1. The APIs are meant to allow apps to search only for devices that have a specific service. Unfortunately this just doesn’t work, I’ve spoken to other devs and they’ve had the same issue.
  2. Apps are also meant to be able to save a device’s identifier to reconnect to it at a later date. This works, until iOS changes its identifier, which happens randomly. I suspect this is something to do with protecting users’ privacy, but it makes reconnecting difficult.

As you can imagine, both of these issues present a problem. The only solution to which is to scan for everything and then try and figure out which is the right device.

Every new version of OS X I check if this has been fixed so I can at least search for just devices that are advertising the right services but unfortunately that hasn’t happened yet.

5 thoughts on “MacID for OS X reconnection procedure”

  1. I presume this would be why multiple “MacID[xxx]: xxx disconnected with error: (null)” entries are found in console? And why random devices are appearing briefly in my Bluetooth menu from time to time?

      1. Thanks. I would be happy if there was an option to disable these logs completely.

        It would be good to keep the Bluetooth connection alive in sleep mode (if possible), so the Unlock request would appear almost immediately.

        Otherwise MacID is really good app.

Leave a Reply

Your email address will not be published. Required fields are marked *