Tester not able to install app using testFlight - ios

An internal user who could install and test a couple of early versions of my app, can't install the new version on her device. I didn't change certificates/profiles in the new version. This is her experience with the new version:
The download has been unsuccessful, so I cannot try the current version of the app. It shows the update in Test Flight (version 1.3.2 (6)), and shows it downloading, but then I get an error message that says "Unable to Download App: myApp".
What can be the cause of this problem?

This kind of problem occurs because of the size of your IPA file. I faced the same issue.
If it is above 50mb then try to download it through your WI-fi not from your mobile connection.
For best practices, we should always download an IPA file through wifi to avoid this kind of issues.
It helped me.
Hope it works for someone else also.

In my case was because the user for some reason was unchecked in iTunes Connect.
I checked the user and I sent the invitation again and the user could already download the app

Related

App upload with Application loader

I have tried to upload app using Application Loader on Mac.
An upload is succeed however there is not any app in iTunes Connect in my app.
Version and SkuID and AppleID is match between app information in iTunes Connect and the app which is uploaded using Application Loader.
so causing of that, I cannot complete 'submit for review'.
Could you help me please?
Thank you for any further help.
succeed upload app
there is not appearance
Binary on iTunes connect is corrupted. To resolve this, check your binary is compatible with Ios 10.
Please use this link for permission in plist file then try to upload new build with new build version.
iOS 10 - Changes in asking permissions of Camera, microphone and Photo Library causing application to crash
https://i.stack.imgur.com/aY8RG.png
If it's not resolved , please contact iTunes connect support to find out the exact reason. They will reply on mailbox with exact reason of binary corruption. Then needful actions to resolve issue.
https://www.apple.com/itunes/go/itunesconnect/contactus
The problem was to use XCode 5.1.
When I use XCode 6.2, everything went thought well.
Use Application Loader with XCode after 6.
Thank you for everyone.

Unable to upload new build on iTunes Connect

I have already gone through various similar questions asked here on Stack Overflow and also on other blogs. Unfortunately, none of those solutions are resolving my issue.
After doing a lot of search & when I was not able to solve my issue, I decided to ask you all.
I will explain scenario briefly. I have already uploaded iOS application for beta testing on iTunes Connect. My app's current status in iTunes Connect is "Expired" as 30 days testing period is over. I did few source code modifications and I want to make this updated application available for testers. Therefore, I tried to upload new build version for the app.
What I did is -
App version (Bundle versions string.short) - Not modified (1.0)
Bundle version - Modified from "1.1" to "1.1.1"
Build the application
Submitted application - Window -> Organizer -> Submit
Even though I did it properly, I am getting error as in below -
Can anyone of you please help me to understand where I might be doing mistake? Any help is appreciated.
Edit 1:
I tried to use build version 1.2/ 1.2.1 as well. Also I tried to upload a complete new app record in iTunes Connect with app version 2.0 and build version 2.1.0/ 210, but everytime got same error.
Edit 2:
My app's current status in iTunes Connect is "Expired". Will it matter while uploading new build version for same app? If yes, what could be the best solution for such issue?
Finally my issue got resolved. Along with modifying the Build version and keeping the Bundle version as it is, we need to check for few build settings whether they are set properly.
I was missing them and that is why I was not able to upload updated version of my application to iTunes Connect.
Please, refer below screen shot for these Build Setting.
You can find complete blog here - iOS 8 Beta testing with TestFlight
This helped me and I hope this will help few others.

xcode 6 upload app with error: iTunes Store operation failed Error Description not available

When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...

Application Loader stuck at "Authenticating with the iTunes store" when uploading an iOS app

We have been trying to submit an app to the iTunes store using Application Loader for three days and keep getting stuck at the "Authenticating with the iTunes store" step.
We have read many forums (including stackoverflow) and tried what was suggested:
making a new provisioning profile
using different or multiple versions of Application Loader
changing proxy settings
rebooting the Mac
uploading at a different time of the day, etc.
We have even left it running overnight and have not had success with getting past this step. Unfortunately, no feedback is given about what the issue may be, and we have not gotten any error messages. We have submitted multiple apps without any difficulty in the past but are completely stuck this time!
How were you able to solve it?
This only started happening to me today (May 2017) and no answers in this thread solved my issue. The resolution for me was from here;
https://forums.developer.apple.com/thread/76803
Open Terminal. Change to home directory,
cd ~
Move the current transporter directory,
mv .itmstransporter/ .old_itmstransporter/
Invoke the following file to let Transporter update itself.
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
Wait till it updates, then open Xcode and attempt upload.
You have to agree to a new sign up in Application Loader. Select "Application Loader" under the "Xcode -> Open Developer Tool" menu (the first menu to the right of the Apple in the menu bar). Once you open Application Loader there will be a prompt to agree to new terms and then to login again into your iTunes account. After this any upload method will work.
Just wait. In a few minutes all will be ok.
Dec 10th 2019, Xcode Version 11.2.1, MacOS X 10.15.1
I was facing exactly same issue yesterday and I thought it might be network issues, at least it looks like so. But this morning I had tried couple different networks and several VPN connections, none of them is working!
The highest voted answer here asks me to reset a cache folder named .itmstransporter under my home dir, the run a program iTMSTransporter under a specific folder, but I can't find both of them.
But soon I figured that it is the cache folder for the people who uses the legacy uploader program: Application Loader, which is deprecated by Apple and can be no longer found in Xcode 11. Then I found that the latest Xcode has located iTMSTransporter here:
/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter
And its cache folder is here:
/Users/your_user_name/Library/Caches/com.apple.amp.itmstransporter/
I removed my existed cache folder, and run iTMSTransporter without any parameter, it soon started to output logs and download a bunch of files, and finished in 2 or 3 minutes. Then I tried again to upload my ipa file, it works!!!
CONCLUTION:
Either the old Application Loader, or the latest Xcode, uses a Java program iTMSTransporter to process the ipa file uploading.
To function correctly, iTMSTransporter requires a set of jar files downloaded from Internet and cached in your local folder.
If your cache is somehow broken, or doesn't exist at all, directly invoking iTMSTransporter with functional parameters such as --upload-app in our case, iTMSTransporter DOES NOT WARN YOU, NOR FIX CACHE BY ITSELF, it just gets stuck there, SAYS NOTHING AT ALL! (Whoever wrote this iTMSTransporter, you seriously need to improve your programming sense).
Invoking iTMSTransporter without any parameter fixes the cache.
A functional cache is about 65MB, at Dec 10th 2019 with Xcode Version 11.2.1 (11B500)
I was stuck at "Authenticating with the iTunes Store" today. I had used the same version and build number as a previous submission. After I updated the build number, the upload went fine. I don't know if it's related, or if it was a coincidence.
I had the same issue for months, I just removed hotspot shield and private tunnel applications from my computer and tried to upload my app and everything worked just fine. so I suggest if you have installed any VPN application on your computer, remove the application and then try uploading your app from either application loader or xcode's organizer.
Try answer mentioned in this Reference Link, it really worked for me and for others as well.
Mentioning answer here as well.
Open Terminal and run:
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
iTMSTransporter will then update itself, then you can try uploading in XCode again or via application loader.
There is no magic fix. Itunes is just working bad. Lately is having more and more issues and it takes more and more to update and send an ipa to the store.
I had this issue with AppLoader and Xcode organiser too and after trying multiple times it just went through.
Changing network connection helped.
Turned off wifi on my phone
Enabled 3G
Created HotSpot
Connected my mac to the hotspot and got through the authetication issue
In my case, I hadn't agreed to the newest Developer Agreement. Just run Application Loader once, click on [Accept] to agree, then quit the Application Loader and the Upload to App Store should work fine.
Following worked for me.
Open another instance of Application Loader.
( Select "Application Loader" under the "Xcode -> Open Developer Tool" menu)
"Agree" to the terms.
After completing Step 2. First instance of Application Loader proceeded to the next step and build got submitted.
I have also encounter the same issue. One possible solution is to go to Xcode -> Preferences -> Accounts and from the left menu select on App ID then click on the View Details and tap on the refresh button. while reloading you will get following error
The selected team's agent, 'ADMIN NAME' must agree to the latest
Program License Agreement.
If you will not get above error, Following solution will not work.
It means that you need to login into the developer account using Admin login and accept that latest agreement.
Then you will be able to upload binary on the app store.
The updated answer for Xcode 11.x.x and Transporter application, open terminal:
rm -rf ~/.itmstransporter/
"/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter"
Wait a while
Problem solved!
I'm running MacOS Mojave 10.14.6, Xcode 11.3.1 and Transporter 1.1.1, and always got stuck at the Authentication with App Store stage, no matter how long I wait, I tried uploading using Xcode, using xcrun altool, Transporter, nada.
Finally I got it working by exporting the ipa file to a new Macbook (10.15.3, Xcode 11.3.1, Transporter 1.1.1), and used the Transporter app to upload it there.
The key difference is the Transporter tool on my new Macbook asked for a 6-digit code as authentication while the old Macbook did not, I suspect the authentication token on my old device expired but the system didn't ask for a new one when trying to upload the app. I had 2-FA enabled.
So I think forcing a manual re-authentication when you upload the app is the answer, the only other difference is the MacOS version, but I didn't test if it'll make a difference.
I solved the problem by removing ~/Library/Caches/com.apple.amp.itmstransporter.
For safety, renaming will be better,
cd ~/Library/Caches
mv com.apple.amp.itmstransporter com.apple.amp.itmstransporter.old
Then, xcrun altool uploaded my ipa successfully.
By the way, I'm using Xcode 11.x & 12.2, macOS Catalina.
In 2020 Dec, the fix did finally worked for me was restarting my mac.
Today I ran into this issue, on Xcode 11.2.1 I solved it by going to Xcode -> Preferences -> Accounts -> Tapped on the '-' next to my Apple ID, then signed in again. This fixed it for me!
In April 21, 2021, I followed #DawnSong's answer, outlined in the image below but I also restarted my Mac and voila it worked.
Spec
Xcode 12.4
macOS Big Sur 11.2.3
You may try to relogin your ITC account via Application Loader.
Just try a different Internet connection. I tried all the solutions above but none worked. However, when I tried using my cellular connection (instead of my DSL connection that stands behind a firewall), it worked immediately.
It might be a network issue. If you are running inside a virtual machine (e.g. VMWare or VirtualBox), try setting the network adapter mode from the default NAT to Bridged.
All i did was duplicate my Application Loader.app in /Applications and
ran both Application loaders at the same time.
this solution is out there, it used to work for me, but today not even that! what I did and worked is that (2 instances) + uploading with XCode (organizer). Had to try a couple of times and it worked.
hope this helps someone, this bug has been there for quite a lot of time now() an apple doesn't seem to care too much
Another reason could be that you have changed the machine from which you're submitting the app. Or the user account on the machine. The new machine may lack the private key and/or certificate for the App Store. Although a certificate with the correct name is displayed in Xcode.
In this case, go to https://developer.apple.com -> certificates, use the plus sign (+) to add a new certificate (distribution), and follow the steps to request a certificate for the private key on your current machine. After installing the certificate, authentication may work.
For me I tried almost all the suggestions given above but the problem still reoccurred after the first success in uploading to App store. Until I found this website. In summary, do the following
Open terminal
Run this command:
rm -rf ~/.itmstransporter/
“/Applications/Xcode.app/Contents/Applications/Application
Loader.app/Contents/itms/bin/iTMSTransporter”
Note: this command(which is different from others above) will delete your ITMSTansporter folder and create a new one and ensure that xcode is quitted before running this command.
3. Start Xcode and all should be well.
Using Xcode 12.3 Distribute App and xcodebuild both got stuck today at this point.
I finally was able to solve this. Peeking around my system I found 3 versions of iTMSTransporter.
Printing the version of each using ./iTMSTransporter -version gives the following results:
/Applications/Transporter.app/Contents/itms/bin/ has version 2.0.0
/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/bin/ has version 2.1.0
/usr/local/itms/bin/ has version version 1.9.3
So it looks that old version in /usr/local/itms was used by Xcode. After deleting /usr/local/itms I was able to upload my binary within Xcode 12.2 and using the xcodebuild command line tool.
Check your firewall
Network settings - (Check with network admin, usually they have blocked apple services unknowingly)
Check your system data/time.
I had same sort of issue, I resolved it by getting direct access to internet.
Also check Application Loader logs to see at which point it gets stuck.
I think I followed all the approaches given, but none worked for me.
My own approach that seems to work for me is to go thru the initial steps to upload a binary, then, after selecting the binary, do NOT click Send; instead close the window, and in the new window that will appear, start anew: hopefully it will go thru.
Found the solution:
I was uploading the build, Every activity went well except “Authenticating with the iTunes store”.
I disconnected my LAN cable and Connected my MAC with my mobile hotspot. and authentication problem was solved. If you have a limited internet plan then as soon as you pass authentication stage, again connect your LAN so that it will upload the app from you LAN cable's internet connection.
my upload failed each time when I uncheck the "include bitcode" option when uploading. So I checked the "include bitcode" option and upload went well.
Check your Firewall, If it is "On" then just Off it, then try

An error occurred talking to the iTunes Store : message while validating App

I am trying to submit an app to the apple store via Xcode 4's in-built application loader. I created an archive, then went to itunes connect and made sure the app status is ready to upload. Then when I come to xcode and do 'Validate' or 'Submit', I just get the following message:
An error occurred talking to the iTunes Store
No details are given. Any ideas?
Update: I used the classic Application loader and submitted my app. No idea what the real issue was.
My mbp now run Xcode4.2(4D199) on Lion, I installed the latest java for Lion. And finally I sovled this issue.
Many guys said, he can used the old Application Loader app to upload the apps. so I guess the problem is the latest Application Loader app(2.4.1 (190)), and the fact told me I am right
Okie, in short words:
Here is the solution:
I hope you guys do not delete the old Xcode(4.1). We Should pick up the old version Application Loader app.
cd /Contents/Resources/Packages
cp ApplicationLoader.pkg ~/Desktop/
Now, you get the ApplicationLoader package.
Install the old one.
Tips: you can remove the latest Application Loader app in path: /Developer/Applications/Utilities/ or just remane it.
That's All.
Hope this way can help you and enjoy the new Xcode4.2. Also hope apple developer can saw this problem and test the latest Application Loader app more.
If your target has any spaces or special characters, remove them as they can sometimes cause this error.
It sounds like a connectivity or temporary network issue. I would check your network connection and try a bit later.

Resources