Unable to upload app to iTunes Connect - iTunes Store operation failed. Authentication timeout
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm trying to upload my app to iTunes Connect with Xcode. I chose product > archive, choose my account, it compiles and when I try to upload it hand for a long time on:
Uploading Archive
Sending API usage to iTunes Connect...
Then it shows an error message:
I've restarted Xcode and the entire machine but still it keeps repeating itself.
What's wrong here?
ios xcode itunesconnect
add a comment |
I'm trying to upload my app to iTunes Connect with Xcode. I chose product > archive, choose my account, it compiles and when I try to upload it hand for a long time on:
Uploading Archive
Sending API usage to iTunes Connect...
Then it shows an error message:
I've restarted Xcode and the entire machine but still it keeps repeating itself.
What's wrong here?
ios xcode itunesconnect
1
Have you tried Application Loader? In case of an error it shows much more details.
– Stefan
Jan 27 '16 at 21:25
1
Wow - having the same exact issue today trying to validate an archive. I just upgraded to El Captain and XCode 7.2.... what gives? Have been trying the past 3 hours same results... restarted XCode as instructed..did not help... what a piece of crappy software....I resisted upgrading for as long as I could anticipating these kinds of issues...
– Moonwalker
Jan 29 '16 at 17:04
I added a possible answer..
– Moonwalker
Jan 29 '16 at 19:50
add a comment |
I'm trying to upload my app to iTunes Connect with Xcode. I chose product > archive, choose my account, it compiles and when I try to upload it hand for a long time on:
Uploading Archive
Sending API usage to iTunes Connect...
Then it shows an error message:
I've restarted Xcode and the entire machine but still it keeps repeating itself.
What's wrong here?
ios xcode itunesconnect
I'm trying to upload my app to iTunes Connect with Xcode. I chose product > archive, choose my account, it compiles and when I try to upload it hand for a long time on:
Uploading Archive
Sending API usage to iTunes Connect...
Then it shows an error message:
I've restarted Xcode and the entire machine but still it keeps repeating itself.
What's wrong here?
ios xcode itunesconnect
ios xcode itunesconnect
edited Mar 11 '16 at 14:59
Joshua Pinter
25.6k9145175
25.6k9145175
asked Jan 27 '16 at 20:39
developer82developer82
5,6741454106
5,6741454106
1
Have you tried Application Loader? In case of an error it shows much more details.
– Stefan
Jan 27 '16 at 21:25
1
Wow - having the same exact issue today trying to validate an archive. I just upgraded to El Captain and XCode 7.2.... what gives? Have been trying the past 3 hours same results... restarted XCode as instructed..did not help... what a piece of crappy software....I resisted upgrading for as long as I could anticipating these kinds of issues...
– Moonwalker
Jan 29 '16 at 17:04
I added a possible answer..
– Moonwalker
Jan 29 '16 at 19:50
add a comment |
1
Have you tried Application Loader? In case of an error it shows much more details.
– Stefan
Jan 27 '16 at 21:25
1
Wow - having the same exact issue today trying to validate an archive. I just upgraded to El Captain and XCode 7.2.... what gives? Have been trying the past 3 hours same results... restarted XCode as instructed..did not help... what a piece of crappy software....I resisted upgrading for as long as I could anticipating these kinds of issues...
– Moonwalker
Jan 29 '16 at 17:04
I added a possible answer..
– Moonwalker
Jan 29 '16 at 19:50
1
1
Have you tried Application Loader? In case of an error it shows much more details.
– Stefan
Jan 27 '16 at 21:25
Have you tried Application Loader? In case of an error it shows much more details.
– Stefan
Jan 27 '16 at 21:25
1
1
Wow - having the same exact issue today trying to validate an archive. I just upgraded to El Captain and XCode 7.2.... what gives? Have been trying the past 3 hours same results... restarted XCode as instructed..did not help... what a piece of crappy software....I resisted upgrading for as long as I could anticipating these kinds of issues...
– Moonwalker
Jan 29 '16 at 17:04
Wow - having the same exact issue today trying to validate an archive. I just upgraded to El Captain and XCode 7.2.... what gives? Have been trying the past 3 hours same results... restarted XCode as instructed..did not help... what a piece of crappy software....I resisted upgrading for as long as I could anticipating these kinds of issues...
– Moonwalker
Jan 29 '16 at 17:04
I added a possible answer..
– Moonwalker
Jan 29 '16 at 19:50
I added a possible answer..
– Moonwalker
Jan 29 '16 at 19:50
add a comment |
8 Answers
8
active
oldest
votes
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
add a comment |
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
add a comment |
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
add a comment |
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode
> Open Developer Tool
> Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
add a comment |
Here the solution that helped in Xcode 8, summary screen:
this not worked for me
– Guru
Oct 16 '16 at 17:11
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
add a comment |
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
add a comment |
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
add a comment |
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
add a comment |
protected by Mogsdad Apr 19 '16 at 14:52
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
add a comment |
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
add a comment |
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
answered Feb 5 '16 at 21:19
user1210182user1210182
43539
43539
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
add a comment |
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
Strange but true. I had continual problems uploading with errors until I disconnected any iDevices. Then, like a hot knife through warm butter my app went on it's merry way to magic hq. This should be the accepted answer as it fixes the problem in Xcode without having to use an additional tool.
– stephenhouser
May 11 '16 at 0:29
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This worked for me as well. The main reason I think is that XCode still builds the app for the specific phone (not for the general selection) even though the phone is not selected. Or, XCode uses the Development signing identity to sign the ipa and thus it fails. Very weird thought
– Jad Salhani
May 14 '16 at 13:44
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
This solved the "rsync failed" error during the upload.
– Kaan
Jun 10 '16 at 13:16
add a comment |
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
add a comment |
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
add a comment |
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
answered Jan 27 '16 at 21:53
developer82developer82
5,6741454106
5,6741454106
add a comment |
add a comment |
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
add a comment |
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
add a comment |
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
edited Jan 29 '16 at 19:11
answered Jan 29 '16 at 18:56
MoonwalkerMoonwalker
1,65731829
1,65731829
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
add a comment |
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
After about 10 failed upload attempts, I finally started Googlin' again and this worked first try. Too bad I don't know what "include bitcode" means haha
– dwilt
Sep 9 '16 at 16:47
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store. developer.apple.com/library/content/documentation/IDEs/…
– 1800 INFORMATION
Mar 8 '17 at 3:56
add a comment |
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode
> Open Developer Tool
> Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
add a comment |
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode
> Open Developer Tool
> Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
add a comment |
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode
> Open Developer Tool
> Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode
> Open Developer Tool
> Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
edited Apr 7 '16 at 5:31
Cesare
4,60985086
4,60985086
answered Jan 30 '16 at 1:21
J. DoeJ. Doe
812
812
add a comment |
add a comment |
Here the solution that helped in Xcode 8, summary screen:
this not worked for me
– Guru
Oct 16 '16 at 17:11
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
add a comment |
Here the solution that helped in Xcode 8, summary screen:
this not worked for me
– Guru
Oct 16 '16 at 17:11
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
add a comment |
Here the solution that helped in Xcode 8, summary screen:
Here the solution that helped in Xcode 8, summary screen:
answered Oct 16 '16 at 17:02
bora89bora89
1,8111712
1,8111712
this not worked for me
– Guru
Oct 16 '16 at 17:11
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
add a comment |
this not worked for me
– Guru
Oct 16 '16 at 17:11
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
this not worked for me
– Guru
Oct 16 '16 at 17:11
this not worked for me
– Guru
Oct 16 '16 at 17:11
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
Solved if you have error like archive upload error -23690, thank you.
– Alessandro Ornano
Jun 19 '17 at 16:56
add a comment |
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
add a comment |
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
add a comment |
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
edited Jul 14 '16 at 12:31
answered Feb 2 '16 at 23:06
zeeawanzeeawan
4,30613842
4,30613842
add a comment |
add a comment |
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
add a comment |
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
add a comment |
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
answered Feb 2 '16 at 10:13
ZaEeM ZaFaRZaEeM ZaFaR
1,3051320
1,3051320
add a comment |
add a comment |
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
add a comment |
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
add a comment |
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
answered Nov 15 '17 at 14:01
J. RothJ. Roth
414
414
add a comment |
add a comment |
protected by Mogsdad Apr 19 '16 at 14:52
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
Have you tried Application Loader? In case of an error it shows much more details.
– Stefan
Jan 27 '16 at 21:25
1
Wow - having the same exact issue today trying to validate an archive. I just upgraded to El Captain and XCode 7.2.... what gives? Have been trying the past 3 hours same results... restarted XCode as instructed..did not help... what a piece of crappy software....I resisted upgrading for as long as I could anticipating these kinds of issues...
– Moonwalker
Jan 29 '16 at 17:04
I added a possible answer..
– Moonwalker
Jan 29 '16 at 19:50