Has anyone successfully submitted an iOS 9 app for TestFlight?

Same problem here - stuck in Processing... I am using Elcapitan so that might be the reason. What version of OSX are you using to build on?

Mine is in "Active" state for Internal Testing. I successfully uploaded the build on August 14. In the "External" column, I see "Submit for Beta App Review" grayed out.

ITunesConnect gives the following warning:
"External testing is not supported for builds that have been created with a beta version of Xcode, OS X, or iOS."

I'm using Yosemite latest, so I don't think this is related to the OS X version.

I still suspect that iTunesConnect cannot yet handle builds with some iOS 9 features in them (in my case, On-Demand Resources). Will try again tonight, but all builds for the last week are still in "Processing".

Interesting that at least someone is getting their builds through. Would be curious if you're using any of the new iOS 9 features.

I have been able to submit two builds using Xcode 7 DP4. I have not been able to submit any builds with DP5. I keep getting the dreaded "Invalid Swift Support - The bundle contains an invalid implementation of Swift..." error.

Uploaded and successfully tested app (internally) with TestFlight. However got a message that said I got "several warnings" but none would show up on log. Also got the strange missing push notifications entitlement but the app only uses local notifications! Apart from that all is good (lol).... Xcode 7 beta /Yosemite deployment target iOS 9 only.

It's a Watch app with bitcode enabled, if that's any help to you.

I finally managed to get an ios 9 TestFlight invite and download to my test device. I did two things:

1. deleted and re-downloaded the TestFlight app and
2. deleted an expired ios8 test build.

IMO, it's likely that the expired build was blocking things. As soon as I deleted it, the invite for the ios9 build came in.

Thanks to everyone submitting feedback.

Finally got one of my builds to go through after greatly reducing the number of on-demand resources I was including. This stopped the server from sending "your app name is longer than 64 letters" warning emails and got the build through the Processing step where they were previously stuck. Not a suitable workaround to ship the app, but at least lets us go further for now.

None of the remaining on-demand resources will successfully download on the devices, though. Still suspect that on-demand resources aren't working yet.

I'm still experiencing 'Processing' even after using the GM build. Anyone else having the same issue?

I enabled Bitcode at first and the binary size shot up, I now uploaded a second time with it disabled and it's still in 'Processing' state for several hours now.

Nope spent whole day yesterday trying. Mine is still stuck after multiple submissions 😟

I've been disabling both options at upload (symbolicating and bitcode) and gotten some builds to go through in the last couple of days, but the processing is still multi-hour.

Looks like External builds may have just started working. Submitted one a few minutes ago successfully without any errors. 🙂

I just got the email saying its ready, tried it and keep getting the same "invalid binary" error 😟

I am having the same issue. I have submitted 10 new builds, each one with some modification, but none of them is passing the processing phase. This is a pain.