“Apple Maps Guides”

So, I've restored onto my iPhone 6 and started getting back into the phone.When I'm on the Apple ID screen, select Sign In with Your Apple ID then select Use different Apple IDs for iCloud and iTunes? and then enter the information - the Next button is never enabled, and no way to continue.Anyone else having the same problem? I'm sure just doing it later would likely work, it's just the on-boarding workflow that's busted.

Hello,In my app I use a NSURLConnection to upload some content. Everything works fine except when I reopen the app after like one hour.On my personal wifi, everything is fine, but when I connect using my operator data plan (I never observed any issue like this on other apps), the first NSURLConnection times out. If I try again, the operation succeeds.I use a standard NSURLConnection.NSURLConnection *connection = [[NSURLConnection alloc] initWithRequest:request delegate:delegate];Using[NSURLConnection sendAsynchronousRequest:request...]also leads to a timeout.On another thread on the Apple developer forum somebody suggested to run a packet trace, which I did. The request does not seem to be sent.I'm a bit out of ideas, do you have one ?Thanks a lot!

I'm trying to do a simple app to mess with the sensors of Apple Watch. With Xcode 7 I can run the project and the app installs on the watch. But I can't debug the app (the app not starts itself).It's something too early yet?

According to the docs and some tests I just ran, interface objects in watchOS 2.0 are still write-only. I'm wondering what the reasoning behind this is now the code excutes on the watch, and therefore there's no longer a round trip to the phone. WatchKit developers have traditionally had to keep track of UI state manually due to this restriction imposed by the old architecture, but now the architecture has changed it seems a little strange to keep those restrictions in place. Could someone from Apple please comment on this?Also, it also seems a little strange that new watch app projects in Xcode still have seperate groups and targets for the interface and the code. Is this likely to change in a future beta?