these indicate it connected to another peer named “theSERVER”… there is NO SUCH device. Earlier in the day I DID have an instance that identified itself as such, but that was removed, and the code deleted. I have even rebooted ALL the devices (mac, Ipad and iPhone)
The instance named “iPAD” was also from a since removed instance (Mac running in iOS mode)
The lines with “xxxdidRecieve” were also deleted hours ago.
How can I find an kill these invisible (yet responsive instances)… like I said, I have rebooted everything, Activity monitor doesn’t seem to show them
I have run the app (the ones with invalid names, and newer versions) on a real mac, a real iphone, a real ipad, and various simulator devices.
I have shutdown everything, right now there is no simulator running, the real iphone and ipad are powered off, the app is running as “My Mac (designed for iPad)” (one instance ONLY)
and those rogue processes are responding to invite requests, as well as sending their init messages
So the ONLY place these rogue processes can exist is somewhere on the MAC. I have rebooted Xcode, rebooted the entire computer and yet they still persist.
I even went into Activity monitor and shutdown any BT related process…
I would have thought that would NOT be the case since these sessions should be fluid, coming and going based on the designated app, and other devices. If a device “goes away” its connection should as well. I have changed the ServiceID so I have a clean instance to work with, and this one is behaving exactly as I would expect. If I connect two (or more devices) and then terminate the app on one of them, the others get a notification that “that device has left the building”
Could it have anything to do with the ip routing table being cached. I don’t use a Mac anymore so can’t check but do remember from my unix days that the iptable would cache things and old names would show up because the mac address and IP was the same.