Here's what's happening when my iPad beta testers are installing a new revision using Testflight. They...
Delete the current version of their iPad app.
Install the new revision of the app on their iPad from the TestFlight email.
Open the app.
A Testflight screen then appears saying there is a new version of the app and asking if they would like to install it. If the user reinstalls the app, the same screen reappears when they open the app.
They've already installed the new version. Is this a Testflight bug or am I doing something wrong?
See my answer at Can't Install xCode 4.3 beta apps using TestFlight for a related issue that was solved by switching services.
Related
Uploading to App Store Connect works fine until publishing for review with the App Store.
On xcode 11.3 Beta, the most up to date.
Email includes;
ITMS-90745: Invalid Toolchain - Your app was built with a version of
Xcode or SDK that is not yet supported. For information about the
supported version of Xcode or SDK for App Store submissions, view
Apple Developer News and Updates (https://developer.apple.com/news/).
I can upload just fine and use TestFlight just fine.
What is the max x-code version for uploading binary to the app store?
You are using a beta version for uploading apps to the app store.
Since Apple doesn't provide support for beta builds on the app store, you need to upload using xcode 10 until xcode 11 comes out of beta.
The beta allows testing through testflight but your binary will always be rejected whilst on a new beta.
Tl;dr. Always use the most up to date version available on the Mac App Store when wanting to upload to the app store.
User Xcode 11.2.1 GM. Hope it will work.
I just upgraded to Mojave 10.14.1's full version, and I've been having trouble uploading my app to App Store Connect.
I get the following error, which I have seen on many other SO questions:
Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 9 or later, macOS, and iOS SDK or later. Don't submit apps built with beta software including beta macOS builds.
I am using the full version of Xcode (10.1) that released earlier today and the full version of Mojave. How do I get rid of this warning so I can upload to App Store Connect?
I've got it to work now. I assume something was slow at Apple's end in authenticating Xcode 10.1 and Mojave 10.14.1. I reuploaded the same build I was trying to do yesterday and now it is working.
I have uploaded app on appstore tested on for ios 7.0 and 8.0. Now I brought new iphone 6 (iOS 8.1.2) and downloaded same app from appstore. When I open it, its get hang on first screen. But when I am running same app from Xcode its working fine. Help me if anyone knows.
You need to update Xcode to 6.1 and also use updated versions of frameworks or third party you are using.
I installed the latest iOS update (5.1.1) on my development iPhone. In Xcode, I now get the error "Could not support development". Xcode says that I'm up-to-date on the latest SDK. How can I fix this? I'm using Xcode 4.3.2 (4E2002).
Go to your organizer and make sure you have a green dot next to the device you are using. If not click Use For Development.
I'm new to iOS development. I just installed Xcode 3.2.4 and the iOS 4.1 SDK on my Intel iMac running Snow Leopard. According to the docs, I first need to create a development profile by specifying a device (which in my case is an iPod touch 4G), but the Organizer window that I open up after starting Xcode comes up fully blank.
Screenshot 1: http://img15.imageshack.us/i/screenshot20110305at104.png/
In addition to that, when I click on "Create a new Xcode project for Mac OS X or iPhone OS" on the Xcode welcome screen, I do not have an option to start a new "Cocoa Touch" project.
Screenshot 2: http://img18.imageshack.us/i/screenshot20110305at110.png/
It sounds like you may not have the iOS SDK installed, or installed properly. Also, most developers will have upgraded to Xcode 3.2.5 a long time ago, so we won't be able to accurately compare what you're seeing to our own installations. Let me strongly suggest that you download the latest iOS SDK and install that. Once you get the current SDK installed, I think both issues that you're asking about will go away.