Request failed with http status code 503

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?

I want to take advantage of the new UI testing features in Xcode 7. However it's forcing me to upgrade my project to Swift 2. I'm guessing Swift 2 apps can't be submitted yet? How can I make use of Xcode 7 on a project which mixes Swift and Objective-C code while still keeping it able to submit.

I've seen several stories posted in 2014 that Apple looked like they were going to allow developers to generate promo codes for in app purchases.http://www.macrumors.com/2014/05/15/developers-promo-codes-in-app-purchase/But I haven't seen any evidence of this. I have a free app with a subscription model using non-renewing subscriptions to access the data.I would love to be able to offer a free trial of a couple days like Android IAP allows so that users can see what is to offer, or barring this, a promo code to a subscription. From what I can tell, Apple does allow trials for auto-renewing newsstand apps, but ours doesn't fit that.And somehow EA got permission to give out IAP promo codes, but us smaller developers don't have that option.

Sometimes when I use my app on watch OS 2 i get this :image : https://s3.amazonaws.com/f.cl.ly/items/3P3P2R3s1p0N0I2G2P2e/IMG_4553.jpgAnd my app freeze :/How can I do to reconnect the watch ?

i have been given my redemption code but when i click to download, the app store opens but nothing happens?

Tue Jun 9 10:16:45 2015*** Panic Report ***panic(cpu 1 caller 0xffffff80079df68a): Kernel trap at 0xffffff7f8849bc44, type 14=page fault, registers:CR0: 0x000000008001003b, CR2: 0x0000000000000028, CR3: 0x000000000a7f9000, CR4: 0x00000000001627e0RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffffffffd258bc, RDX: 0x0000000000000000RSP: 0xffffff9112e2be80, RBP: 0xffffff9112e2bec0, RSI: 0x0000000000000001, RDI: 0xffffff8018956a18R8: 0xffffff801892a000, R9: 0x0000000000000001, R10: 0x0000000000000000, R11: 0x0000000000000006R12: 0xffffff80d8b7b000, R13: 0xffffff801aa4f700, R14: 0xffffff80d8b7b000, R15: 0xffffff801abe7840RFL: 0x0000000000010282, RIP: 0xffffff7f8849bc44, CS: 0x0000000000000008, SS: 0x0000000000000000Fault CR2: 0x0000000000000028, Error code: 0x0000000000000002, Fault CPU: 0x1, PL: 0Backtrace (CPU 1), Frame : Return Address0xffffff9112e2bb10 : 0xffffff80078f16e10xffffff9112e2bb90 : 0xffffff80079df68a0xffffff9112e2bd70 : 0xffffff80079fcb830xffffff9112e2bd90 : 0xffffff7f8849bc440x

XCode crashes when I fetch the provisioning profiles and continues to crash when opening any project (because it is going and checking the provisioning profiles).This first occurred when adding provisioning profiles and linking my account (in Xcode) to the developer portal.I opened issue 21220696 in the apple bug reporter but have not recieved an response.I can reproduce this issue every time.Here is the video of it happening. https://www.youtube.com/watch?v=TEaN6UnO59wThis is occuring on Xcode Version 6.3.2 (6D2105) & 10.10.3 (14D136)Here is the crash debug: https://gist.github.com/cdesch/86058dd98f22774d36bb

When I get a regular SMS text I only get the option to Dismiss. And after if I go into messages on my Watch the SMS Text will not show in the list. I have also tried starting a new SMS text from the Watch only to have it try and fail sending an iMessage. This is only happining when recieving or starting them from the Watch, all texts and imessages work as they should on the iPhone. Anyone else having this issue?