Testflight support?

App ID 1125887847, bug report 27640183. Thanks!

It looks like uploading Message extension builds to iTunes Connect is broken in Xcode 8 Beta 4. I'm seeing ERROR ITMS-90534: "Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and iOS SDK or later. Don't submit apps built with beta software including beta OS X builds."

Filed bug report 27642234

27641737 🙂

Just checked External Testing again and my build has now reappeared with status In Beta App Review.

Thanks again everybody. Engineering has deployed a fix that should hopefully address these issues of the apps disappearing. Please let me know what your results are.

My builds just reappeared in the Testflight -> External Testing section with status "In Beta App Review" as well.

The state changed to "In Beta App Review" but it appears for every build that disappear, is this a new bugged state? because certanly there is no need to review older builds right?

Thanks

The three versions of my App that disappeared got approved for Beta Testing. I was able to add an external tester and that tester received the email when I started testing. That tester has not yet installed the App but it looks like it's working now @pdm.

Thanks

I'm seeing this problem too with B4

[Transporter Error Output]: ERROR ITMS-90534: "Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and iOS SDK or later. Don't submit apps built with beta software including beta OS X builds."

rdar://27663268 for this issue PDM

How are you guys uploading via TestFlight? Are you creating a dummy iOS app, that is bundled with your iMessage extension? Or is there a way to upload just the iMessage Extension that I am missing?

No need to create a dummy iOS app. Just archive your MessagesExtension, create an iOS app in iTunes Connect just like what you would do as usual for a normal iOS app, then upload it. The bundle id for this "iOS app" in iTunes Connect has to be the one for the non-existent dummy app (i.e. without the MessagesExtension suffix). It's a bit confusing at the moment, I hope they're introducing a much simpler way closer to the public release of iOS 10...

My apps seems to be stuck in "In Beta App Review" since yesterday. Anyone else have the same issue?

Yup, mine is still stuck in that stage as well...

That's not very promising, is it?

Quick update: The two builds that appeared "In Beta App Review" on Monday are still stuck in review. So what are the next steps? Xcode Beta 4 is not supported by TestFlight, so do we redownload Xcode Beta 3, downgrade the code to Beta 3 and upload again?

TestFlight supports Beta 4 as of yesterday:

https://developer.apple.com/testflight/release-notes/

I was going to test external TestFlight later today and will report here. My previous attempt worked before Beta 4 came out.

My build for external testing that was previously "In Beta App Review" just got approved.

That's great news! I've had less luck so far. The builds I've submitted on Monday are still "in review". I've uploaded a new build with Beta 4 yesterday, which is also still "in review".

I submitted a new build of an iMessage App last night. I got the internal testing TestFlight email right away when I selected the build.

My external TestFlight beta review finished this morning and I sent it to 4 new external testers and they've received the email.

So it looks like it's working fine for me - and it seems iOS 10 Public Beta is stable enough to recommend to my testers.

(I put this as a reply to original post since those replies were getting hard to navigate)

@pdm

My app has been stuck in 'In Beta Review' for 3 days now. I (maybe stupidly) submitted a new build to TestFlight and that build is now sitting in 'Waiting for Beta App Review'. I'm not sure if it can progress until the previous build has passed, or what?

I filed a bug for the first try: 27732523

Thanks

Hello artmin:

This is related but off subject to your question.

We too are trying to submit our app for testflight. We got a quick question that might be a stupid question but when you set the Bundle Identifier in the main "core" project, does your iTunes Connect app id match that or the Bundle Identifier set in the "Message Extension" info.plist?

We set the "Bundle Identifier" in the main project as "com.Site.AppName" and the "Bundle Identifier" in the "messageExtension" folder as "com.Site.AppName.messageextension". Is this what you did? We are stuck at the configuration part and there's no easy guide to follow.

Thanks, Henry

@ArchSquare - I have left them as the "default" - which does have the main project without the ".MessagesExtension" and the Message Extension part with the ".MessagesExtension"

I created this project explicitly as a MessageExtension project.

Hello Artmin:

Did you guys create an app id in the "certificiates, identifiers, profiles" in the portal and did you have to create a separate "extension" app id for the main app id?

Thanks, Henry

This is what I did.

1. Created a new project as type iMessage Application and typed in a product name. XCode gave me a bundle ID.
2. I went in the Developer site and under certificates, identifiers, profiles and under Identifies/App IDs - I used that XCode gave me
3. I then went into iTunesConnect, under My Apps, created a New App and it found the bundle ID I typed on the Developer Site.
4. <wrote some code>
5. Then I archived and submitted my App via Xcode. I had the MessageExtension scheme selected when I did this

Hope that helps.