Here is the response:
[Dict]
[Key] get-task-allow
[Value]
[Bool] false
[Key] com.apple.developer.team-identifier
[Value]
[String] DNSTESXL8W
[Key] application-identifier
[Value]
[String] DNSTESXL8W.com.zebra.printersetup
tnuzzo
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Sorry I hadn't seen your reply.
We are using a custom protocol. The calls we have are using a UDP socket to broadcast the request msg. If the IP address is in the Multicast address the discovery request msg is broadcast on, it becomes a UDP multicast discovery. If the directed IP address is directed, it becomes the UDP directed broadcast etc..
What is interesting is, within our app, even if we enter the DNS or IP address directly, it still won't allow the connection to continue with iOS 16. All works fine on released version (even when device is using iOS 16).
Hopefully that is what you are looking for. I'll watch to see if you need more detail than that.