Thanks for the reply.
Just to give context I am a full stack Swift developer and I am building a library to ensure my development devices (iPhone, Apple Watch, etc...) can find my development Swift Server (Vapor, Hummingbird, etc...)
https://github.com/brightdigit/Sublimation
I have successfully been able to transition from other solutions to using Bonjour to advertise the ip address of the server using NWTxtRecord.
My next goal was to use SwiftNIO:
https://swiftpackageindex.com/apple/swift-nio-transport-services/1.20.0/documentation/niotransportservices/niotsconnectionbootstrap
as opposed to NWListener. It was using that which I ran into the previous issues mentioned (never getting a complete message). I then tried it as you see in the test code and noticed the requirement for using cancel. These messages are typically pretty small (encoded Protobuf) around 500 - 2000 bytes.
For both NWListener and SwiftNIO:
In no cases did the server crash, in fact the server would log correct that it did send the message.
I did try using just receive and I had the same issue.
and now for the bad news which makes this all mute....
The Apple Watch cannot using the Networking API.
This renders the whole argument which results in me going to back to using NWListener only via NWTXTRecord.
Again thanks for the reply if I'm missing something, let me know.
Post
Replies
Boosts
Views
Activity
Thanks Mr.Frameworks Engineer!
I filled FB9568384 in August 2021. I totally understand. I think what's difficult is the documentation says it should display a number pad and the number pad is used in various Apple applications:
Settings - Change Passcode
Settings - Profile - Phone Number Entry
Workout - App Fitness+ Code entry
So it seems to me it's covered somewhere in the current design, just not available to developers in UIKit and SwiftUI regardless of what documentation says. If it is not covered by the current design then the documentation should be updated as well rather mislead developers. Let me know if I should file an additional feedback regarding documentation.
Thanks,
Leo