My WatchKit 1.0 app, used UIDevice to pass the status of the iPhone to the Apple Watch andworked well. Now though, with xCode 7 and WatchKit 2 UIDevice is no longer available. Is therean alternative or do I need to completely rethink my Watch App?
RLKingSoftware
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
Last seen
User for
Post
Replies
Boosts
Views
Activity
So, I just read the latest news in the member center and it says:"Starting June 1, 2016 all apps submitted to the App Store must supportIPv6-only networking. Most apps will not require any changes becauseIPv6 is already supported by NSURLSession and CFNetwork APIs."While I don't have a major issue with this, outside of the fact that ipv6 is not supported by any of the major ISPs in my area. But, I am concernedabout one of my apps in particular which displays the ipv4 address internaland external. I can't switch this to ipv6 because it simply won't work on themajority of networks currently in use. Yes, I thought ahead and already havea code branch in the existing app to show ipv6 addresses but, it's not enabledbecause there is no way to test it.Any suggestions?