[ad_1]
Now we have an IOS utility which solely listens on a INADDR_ANY socket connection for inbound connection utilizing CFSocketCreate/CFSocketGetNative/CFSocketCreateRunLoopSource/CFStreamCreatePairWithSocket and so forth (to show debug info through HTTP).
(So it falls into the class “Listening for and accepting incoming TCP connections”).
If the primary incoming socket connection occurs on a brand new put in app we run into the error talked about above. As we do neither use Bonjour nor getpeername() I’m wondering the place the issue is. Clearly it does not matter how the dialog is closed, our program works. However it’s in fact annoying for us (QA is more durable) and our prospects.
Any thought what could possibly be the issue ?
I seemed into all of the questions associated right here, however I believe we aren’t utilizing one of many ‘banned’ APIs triggering the dialog
[ad_2]
