Builds don't show up on iTunes Connect Test Flight - ios

I am trying to upload an app onto test flight, but for some reason, after I get the "Successfully Uploaded to app store message", on the Builds tab no builds show and it is empty.
Is the service currently down or something? Because according to Xcode, the builds are uploaded (I get an error when I try to upload the project twice saying the build exists).

Related

issue submitting app for review - already submitted

So i have uploaded the app via xcode however when i go to submit the app via appstoreconnect.apple.com i get the following error.
but when i go to re-upload it, seems it is already uploaded. So what have I missed.
It says it has been delivered - is there a processing time?
The answer is right on the screen in the image you uploaded. You've already uploaded a binary with the same BUILD #.
Log into iTunes Connect and either select the uploaded build... it will take a few minutes to process before it is available, OR if you have invalidated that and are uploading a new one. Go to you Project in Xcode and on the General Tab for the Target, bump the build number.

iOS Build does not show up when submitting an app for a review in App Store Connect

I uploaded the app successfully via Xcode to App Store Connect. This is not the first time when I'm pushing out an update or an App, I followed the same steps I did in my previous apps/updates. I archived -> validated and distributed.
The app build shows up in App Store Versions under Activity as Prepare for Submission but it doesn't show up in the Build section under the AppStore tab.
I have searched this error and most of the folks got an email with some bug or missing file required in the binary. But I haven't received anything in the email associated with this account.

Ios - the itunes connect showed no build in test flight after i use application loader to upload my ipa

i am using the application loader to upload my ipa to the ios, however after i upload it does not show anything to enable me to check the status or see any build in the test flight, i uploaded yesterday and now still not able to test flight with anyone. Morever after i reupload and it wrote that the application already existing online and unable to upload, anyone face the same issue with me?

Xamarin iOS App Stuck with "invisible" build

I'm publishing my first Xamarin.iOS app to the store. I've set up my distribution profiles, set up the app on iTunes connect, and all seems well. I published my app for archiving and then successfully uploaded via the Application Loader.
What's broke is that iTunes Connect doesn't see my app - it says I still need to upload via Xcode or Application Loader... but when I try to upload my IPA (again) via the Application loader ("sign and distribute" via Xamarin), I get the error "ERROR ITMS-4238: "Redundant Binary Upload. There already exists a binary upload with build version '1.0' for train '1.0'" at SoftwareAssets/PreReleaseSoftwareAsset."
I don't see an option in ITunesConnect to delete this build and start over with another version, and it won't let me Submit for Review because it doesn't see the build as being uploaded.
I've opened a ticket with Apple over a week ago and haven't heard back. I know I could go with a different AppId but for all I know I'll hit the same wall. Anybody been down this road?
UPDATE #1
I've created version 1.1 of my app and uploaded it successfully to ITC. I see it in the Builds section (still don't see 1.0) but I can't add a new version of the app to "link" this build to because v1.0 is still "Preparing to Submit"
Apps - unable to create v1.1 while v1.0 is "Preparing to Submit."
Builds - v1.0 is not visible, but if I try to reupload ITC says it's there
UPDATE #2
I was able to link v1.0 of my app store submission to v1.1 build and submit the app for review. I don't know if this will go through or not, but it was at least submitted. I am now also able to "reject" this version, but if I do this I'm unable to add another version still (if I wanted to get a clean v1.1).
Each build you upload must have a unique build number. So if you upload 1.0 then the next must be 1.1 etc. What I do is keep the internal test builds with an extra .1 at the end so my internal would be 1.1.1, 1.1.2 etc and then I'll push 1.2 to the store when ready. You can also change the version number on your App's settings on iTunes Connect. They wont reject it as it's just the build number.

Select Version to Test is empty in Internal Testing iTunes?

I uploaded my App successfully to the iTunes store. But now i need to test the app using TestFlight. for this i added some Internal Testers. But when i clicked on Select Version to Test The latest build is not showing up in the list. I don't know why?.
I also verified my Build 11 on the iTunes. It shows that there are no testers available for this build.
How can i add Testers to Build 11 ?
you can click (Not Available for testing) --> save , then (select version to test ) select your new version , fill the informations, then click save and start testing .
I faced same issue. I Uploaded builds were in queueing and its showing "Processing" , “After builds are uploaded they will go through a processing state before they can be used.” .
Now you try this select a "Internal Testers," making a change, and saving immediately clear the queue: The latest build was now active and available for testing.
Update: At this point, all beta are off. It seems "processing" happens when Apple quietly upgrades iTunes Connect and there's nothing you can do about it.
Look at here for more info My prerelease app has been "processing" for over a week in iTunes Connect, what gives?
According to screenshots i think your latest build is in Processing state to upload.It take some time(10-20 minutes) to complete to upload on store.
once it complete
select the build then click on save button
after then open testflight your latest build automatically updated there no need to set again their.
set your internal or external testers and press SAVE on test flight.
if u already added testers press edit and remove previously added testers and save it. then again add testers and press save(it will send a new notification mail to the testers for the new build)
your new build is ready for testing.

Resources