Hello Matt, Thanks for your answer. Why does your app close the TCP connection in this context? Are you doing a send() while the window size is 0 on the device and the data does not reach the device, but your app assumes that it did and optimistically closes the connection? Our app closes the TCP connection because only few connections are allowed simultaneously, so we do not need to "occupy" the device unnecessarily. This a "good practice" sent by the manufacturer of the device. But I assume that we would have the same problem without closing the TCP connection right away. Because we need to close the connection anyway when the app is sent to the background, right? If you are experiencing this problem, and control the device you are sending data to, you could build in your own acknowledgement behavior. While this is tedious, it would at least allow you to know that the device is aking 65bytes etc... and that each packet of data was received. Sadly we do not control the device so we cannot build and acknowledgement system and are relying on the acknowledgement built-in the TCP protocol. Thanks,

Hi, Would this Apple crash report help? Thanks, Crash Report - https://developer.apple.com/forums/content/attachment/4a21518e-e05e-46ca-b5c6-2faba46400ec

Hello Cevin, You won't be able to register the same application on another account. The bundle ID has to be different. However you may transfer the ownership of the app from one account to another if needed. Best

Hello there, Has anyone figured out the cause of this crash? We are facing the same issue since iOS 14 (14.3 and 14.4) when using multipeer connectivity and MCNearbyServiceBrowser. Thanks!