I have a repeatable scenario where an L2CAP connection between two iPhones fails when activating a Bluetooth microphone that's paired with the same device. The only clue I'm getting is: cbncom[53050:2758629] [CoreBluetooth] WARNING: Unknown error: 708 This error number 708 is different from the ones I'm more familiar with (like 431) and has almost no hits when I search online. Can anyone tell me what this error code is, and/or how to prevent problems generally when BLE/L2CAP must coexist with Bluetooth Audio?

A while back I misclicked and added a tvOS version to my macOS app in App Store Connect. It's a bit of a hassle because some screens like "Ratings and Reviews" will often default to the nonexistent tvOS version and I have to manually switch it back to macOS. I am able to bring up the dialog to delete it: "Are you sure you want to delete this tvOS version?" When I press the Delete button it thinks for around 5 seconds and shows "An error has occurred. Try again later." I've tried this at various points in the last couple of months and it always has the same error. Does anyone know how I can delete this build?

I have some existing working code which creates a peer-to-peer AWDL connection using NSNetService. self.advertisingService = [[NSNetService alloc] initWithDomain:@"local." type:@"_http-alt._tcp" name:self.serviceName]; self.advertisingService.delegate = self; self.advertisingService.includesPeerToPeer = true; [self.advertisingService scheduleInRunLoop:self.runLoop forMode:NSDefaultRunLoopMode]; [self.advertisingService publishWithOptions:NSNetServiceListenForConnections]; Previously, self.runLoop was always [NSRunLoop mainRunLoop]. Now I am embedding this code in an application where the thread 1 does not offer a run loop. This means the above code no longer worked: I wouldn't even get the netServiceDidPublish: delegate callback. So instead I spawn an NSThread, create a run loop manually and supply a reference to it here (self.runLoop). This mostly works: now I correctly receive the netServiceDidPublish: callback. The problem is that I still never receive netService:didAcceptConnectionWithInputStream: when a connection occurs. Over on the connecting device, it is successfully obtaining the input and output streams and reaching the "Open" state for both. This new connection is never reflected here on the listening service. It feels likely that I have to tell something else to use the custom runloop but I can't tell what. Does anyone have any ideas?