-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Won't build. #1
Comments
You're right the NSNetService class has been marked __WATCHOS_PROHIBITED in the Foundation reference. That is really strange since in Apple's watchOS documentation there is a reference to the NSNetService class: https://developer.apple.com/library/watchos/documentation/Cocoa/Reference/Foundation/Classes/NSNetService_Class/index.html#//apple_ref/c/tdef/NSNetServiceOptions |
I found this. It looks like it might be deliberate. |
I'm looking at using this for tvOS because Apple have not included MultipeerConnectivity and I really need to be able to set up adhoc networks. I'm hoping your framework will work on tvOS. |
It looks like Apple removed NSNetServices and its friends on watchOS which is really disappointing (maybe I can try to build around that by using some CoreFoundation classes or even some POSIX classes like CFSocket if those are even available on watchOS. However, on the upside, a tvOS framework looks promising because NSNetService is available on it. Hopefully, I can look at the programming reference soon and get a browser and advertiser UI going and fully support it, along with the launch of the framework |
I'll fork and remove the WatchOS stuff there. I'll also see if I can get tvOS going. |
I've opened the project in Xcode 7 or 7.1, and attempted to build the iOS app (I'd like to see the framework functioning before I try integrating it).
I am unable to build because when Xcode tries to build the MultipeerCocoaWatchOS framework (presumably for the Watch app), it fails with errors on every reference to NSNetService, as if Foundation isn't available.
The text was updated successfully, but these errors were encountered: