itunesconnect

I've been using TestFlight for a while but this is the first time I'm submitting a build for beta testing directly from iTunesConnect since Apple bought TestFlight itself. I've been experiencing a weird behaviour (or maybe just the Apple's expected behaviour). I've added the user to my team (they've admin role), and I've selected them as part of the TestFlight tester in the dedicated panel. I've uploaded a build, switched the TestFlight Beta Testing on in the Build tab and selected the Internal Testers (just one in the screenshot below) I would like to receive that build. Then...nothing

After a recent submission I have gotten the following error: Invalid Signature - the nested app bundle (FooBar.app/Contents/Frameworks/GData.framework) is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information. Invalid Signature - the nested app bundle (FooBar.app/Contents/Frameworks/Growl.framework) is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more

My scenario I wrote an iOS app for a client. The project is almost over and now it's time for them to put it in the App Store. I've been sending them development builds throughout the development process. Those builds had a bundle id based on my company and my client's project like so: com.mycompany.clientname.projectname . I signed those Ad Hoc builds with an Ad Hoc Distribution Provisioning Profile that I created in my own Provisioning Portal account. Now that it's time to go to the App Store, I need to do a Release Build and send that for them to sign with their own App Store Distribution

I cannot select the latest version I have uploaded to seed to beta in external testing. First of all whenever I upload a build two version appearing, that have upload time difference of 5 to 15 minutes between them. One of them gets changed from processing to normal available state, but other does not. But now selecting the available build also selects the processing one and my selection is blocked and I cannot select the OK button because probably my selection is blocked by the processing one. I think it is UI frontend issue at itunesconnect side but it could be something I am doing wrong.

Im able to submit my app through Xcode 6.3.2 perfectly fine. Validation and analyzing pass perfectly. Once it successfully submits to the app store though I get an email from Apple: "Dear developer, We have discovered one or more issues with your recent delivery for "App". To process your delivery, the following issues must be corrected: Invalid Signature - Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target

See the picture. My app is "Ready for Sale", and I have a new version. Do I have to upload a version at 1.0.1? The version I want to upload is 1.3.7. iOS version is disabled: You can only have one released version and one pending version per platform. In your case you have a pending 0.2.2 release, so you can’t add another. What you can do is go into that release and change the version number to your desired version (1.3.7) and then upload a build for it. You can change the pending version numbers as you have already a version is pending to release i.e. "0.2.2". Hope this will work for you. 来源：

I uploaded a binary but before submitting it for review I realized that the Product Name in the Build Settings wasn't correct. I fixed the issue and tried to upload the binary again, but ran into the version 1.x already exists issue while doing that. So I thought I'd just submit this, manually reject it and upload the fixed one. But with the latest changes in iTunesConnect, like a lot of other stuff, the option to reject my binary seems to be tactfully hidden or completely missing. How do I reject my binary in the latest (Sep 14) iTunesConnect dashboard? Or what's the new process to make such