We are unable to process your request

You can (could have?) use TestFlight and let them help out during the process, or you can distribute via Ad-hoc.Otherwise, there are no links until it's approved and in the store.◅▻

At what point in the process does it quit, exactly?Did you try deleting old archives?Did you restart your computer?How much free space on your hard drive?Which version version OS X?◅▻

So am I - I went into iTC for one of my apps, read the blurbs on Campaign links, and then walked thru the process to get the sample link shown above.This is on the assumption that a followup will be done later in iTC when that app enables that process there.Otherwise, I agree it seems to be a catch-22 - might want to file a bug against the process to help enlighten the backend.◅▻

I'm having the same problem. I've tried this with two different aps under two different developer accounts, but on the same computer.Exact same failure.The archives passes validation.I can successfully submit via the Application Loader but not Xcode.It quits during the upload to the app store.All old archives deleted.Computer restarted.100+ gbytes free10.10.3 xcode Version 6.3.2 (6D2105)Heres the start of the report:Process: Xcode [462]Path: /Applications/Xcode.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 6.3.2 (7718)Build Info: IDEFrameworks-7718000000000000~2App Item ID: 497799835App External ID: 812404257Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [462]User ID: 501Date/Time: 2015-06-17 10:36:02.105 -0700OS Version: Mac OS X 10.10.3 (14D136)Report Version: 11Anonymous UUID: 982D33B4-5316-78B0-8604-E0291FBFA3B0Time Awake Since Boot: 470 secondsCrashed Thread: 16 Dispatch queue: NSOperationQueue 0x7f891cd12f50 :: NSOperation 0x7f891d33a360 (QOS: USER_INITIATE

Shared groups will need to be reworked but I think how shared groups worked originally shows a great deal about the extention lifecycle for new and old apps will work on watchOS 2.0Shared groups relied on the process running in the same contianer to share data. Since the WatchKit Extention is moving to the watch and running in its own process the shared groups functionality is broken. Apple is explicitly saying apps that used shared groups will need to be reworked but understanding the underlying reason why makes me confident that any watch app that was using an iOS only framework or library will have that funtionality break in watchOS 2.0 if the watch app has not been reworked.However, I am confident that developers will be given plenty of time to submit watchOS 2.0 apps before its offical launch.

I noticed this as well. It looks like something is broken in the new security features of networking conections in iOS 9 and watchOS 2.0 (they made a lot of security changes)In my case NSURLConnection was requesting an SSL version of the network resource if port 443 was open even if it wasn't responding to requests.

To kinda expand on adeeb's reponse. Watching the complication WWDC session videos it seems that apple is strongly discouraging complications that update in minutes and really want developers to try hard to minimze the number of times the complication updates.The WatchConnectivity session talked breifly about budgeting and how often you can request updates and I was shocked to hear that even if the iOS app is doing all the work in the background you'll only be able to send update requests to the complication Clock Face twice an hour, otherwise you'll exaust your budget. I'm not entirely sure if locally scheduled wakes will allow you a larger budget but I'd imagine it would be less or it would count towards the same twice and hour update.

In order to properly generate an apns cert you need to do the following:1. Generate an apns request plist from your mdm and save it locally2. Go to https://identity.apple.com/pushcert/3. Sign in with the apple id that you want to use to generate the apns cert with4. Click on 'create a certificate'5. Agree to the terms and conditions (if you already haven't)6. Upload the locally saved plist and add any notes7. Click 'download' to download the newly created apns certificate8. Upload the apns certificate to your mdmDone!

I use Application Loader too, but in itunes connect the app is processing and doesnt change this status.

Having the same issue with the same backtrace. Xcode 6.3.2/Yosemite 10.10.3I was able to upload the app using Application Loader. The upload was successfull, but I recieved the warning The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.It looks like the Xcode crash occurs when trying to present a warning on a thread other than the main thread. Perhaps it is this warning?-Steve

I'm having the same issue. It crashes immediately when the status shows Upload Archive. I've tried about 20 times, rebooted 5 times and nothing works. Same process worked yesterday and the past few years. Yosemite 10.10.3, Xcode 6.3.2

This is the crash report :Process: Xcode [570]Path: /Applications/Xcode.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 6.3.2 (7718)Build Info: IDEFrameworks-7718000000000000~2App Item ID: 497799835App External ID: 812404257Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [570]User ID: 501Date/Time: 2015-06-17 13:55:50.417 -0500OS Version: Mac OS X 10.10.3 (14D136)Report Version: 11Anonymous UUID: 62FC1C66-70DA-161C-D548-575494D67226Time Awake Since Boot: 710 secondsCrashed Thread: 17 Dispatch queue: NSOperationQueue 0x7f808b240380 :: NSOperation 0x7f808b13c930 (QOS: USER_INITIATED)Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Application Specific Information:ProductBuildVersion: 6D2105ASSERTION FAILURE in /SourceCache/IDEFrameworks/IDEFrameworks-7718/IDEFoundation/Issues/IDEIssueManager.m:457Details: This method must only be called on the main threadObject: <IDEIssueManager>Method: +_issueProviderInfoThread:

Giebler, if the user interacts with the watch app there is no budgeting, it is only background processes and local or remote notifications that are budgeted at what sounds like twice per hour. So if I user changed projects in the watch app you can get the shared instance of CLKComplicationServer and extend or invalidate the timeline without any issues.