I am preparing an app for ad hoc distribution via Test Flight. I have stepped through (successfully) all of the preparatory steps in this Ray Wenderlich article already (https://www.raywenderlich.com/48750/testflight-sdk-tutorial), and I feel confident that the certificate, App ID, and Provisioning Profile are all created correctly and in proper working order. I am on the step in which you archive the project in Xcode. I have selected these settings during the archive process:
I choose to Export :
I choose "Save for Ad Hoc deployment" since our plan is to use Test Flight to distribute the app to our testers. I do believe this is the correct option for that (as opposed to "for enterprise deployment"):
This is the default setting, and I do not have a specific reason to change it, although I'd appreciate any insight you may have:
Again, default options for both of these. The first one is unchecked by default and the second one is checked by default:
When I get to this screen, the spinner spins seemingly forever:
The problem seems to be that once it gets to the part where it is compiling from bitcode it spins and spins and shows no signs of finishing. When I am building the app to run on a device connected to the MBP, it compiles quickly, usually within a few seconds. What could be causing this unresponsiveness?
I am facing the same problem. What my suggestion is just enable this check mark when export for iOS App Store Deployment. If you are exporting an adhoc build then do uncheck it. It will work fast.
I have better solution for this problem. Don't go for export option tomato iPA, try out as mentioned below:
just right click your Archive and select show in finder
Then again right click on resulted file in finder and select show package content
then from result open product folder --> Application folder --> and select ".app" file
Then simply add this .app file under apps of iTunes software on mac
After completing adding process right click on app icon in iTunes
and show in finder which will give you iPA file.
It would take only 5 minutes max.
I let this run for a long time (basically while I went out shopping). When I came back it was done. So for whatever reason this just takes a really long time to do.
That said, it was also the incorrect action. The way you add testers to TestFlight since Apple bought it is different. Now, instead of exporting and uploading an IPA file, you have to submit it to the store and let it be reviewed by Apple before you can add testers.
One more option is, You have to keep eye on which source code you have is taking small time and get archive process done quickly. So from next time you will have to open this particular source code and perform archive, after that open your working source code and then try archive for that. You will get that done fast for working code as well.
For me, I have kept 2 source code separately.
One for Xcode 7
Other for Xcode 8
So whenever I want to create ipa, I open this source code first and make archive then I close this code and perform archive for code I am currently working. This is bit lengthy process but surly it don't take that much of time as well as your system don't get hang.
You can disconnect your wifi wait a few minutes to reconnect again, and then it is ok
Related
I am trying to upload a new build to iTunesConnect from xCode, but every time I encounter this issue:
What is the problem? and how can I fix this?
Recently I started facing issues during upload progress and Xcode used to get stuck a lot and would eventually fail with the second error which you are seeing. Having fed up for a while, I switched to use Application Loader in XCode.
Way to use would be, first archive your app, once that is finished, you can spot Export option on the right hand side panel just below Upload to App Store option. After you select Export You will see different options. Select Save for iOS App Deployment. This will create a .ipa file and save it in your desired location.
Now, go to XCode -> Developer Tools -> Application Loader -> Deliver Your App -> Select the .ipa file where you had saved before.
This method has been helping me a lot and failed not even once for quite sometime. Hope it helps you as well.
This happens due to Apple server is not working correctly for now, try to upload it later or 1 day after, it will be uploaded successfully, it happens due to Apple's app server internal problem.
Also you can try to upload it through App Loader. but if apple's server is in trouble then uploaded binary may not shown in iTunesconnect.
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
Screencap of error window.
I'm trying to upload an archive to the app store in Xcode, and this is what's spit back at me. I'm not having any luck finding out what it's supposed to mean. Every other error I've encountered had at least some detail to go off of, but this time it just displays the error code number.
I believe I had a similar problem to this and solved it by uploading using the Application Loader opposed to the Organizer.
First export your archive.
Then open application loader in Xcode >
Open Developer Tools > Application Loader
Then click "Deliver Your App" and add your exported archive.
Have you tried -
Increasing the build number
Adding the relevant permissions to you Info.plist (camera permissions,
location etc)
Added the correct assets for app icons
Check your provisioning profile settings and make sure they are correct.
I've had more luck using Application Loader for submission so you might want to try that.
Hope this helps.
My connection was dropped while I am uploading the archive to the apps store.. and it showed Uploaded successfully with big green tick..
And also it goes to the app store and wait forever in the processing state. So I just uploaded it with the new build number and it's processed within less than 10 minutes.
but troubles are not over :(
then I couldn't select my latest build for test it still showed that stuck one..
What can I do for this ?
====================================================================
This has happened to me a few times already i.e. when a binary doesn't finish processing due to connection drop or other issues (on apple side).
Just upload a new build and use that build for release or test flight. Don't worry about the build that never finishes. Just ignore it and move on.
If you are still seeing build 2 as the latest under testfligth section, then logout, clear your browser cache, log back in and see. Clearly your build 3 is the latest one. itunesconnect is super flaky.
Use apple support as a last resort. They will take days to solve something as simple as this.
In my experience when the build stays greyed out and (processing) for longer than a few minutes it will stay forever like that. Best to just re-upload and wait for the new build to process. It does take a bit of time to show up for testing though.
These are the steps which I did to got build to the testflight internal testers
to show Export Compliance add below line
to info.plist
<key>ITSAppUsesNonExemptEncryption</key><false/>
change version no to different one (not the build no)
create archive and upload it without upload bitcode enable tick
I am using xcode 7.1 and trying to upload my app to the app store directly through xcode. While uploading I am getting a weird error:-
cannot verify client 3000
Note:- I recently made changes in the accounts (xcode preference section). Is this related to my error?
I also restart the xcode but issue still there?
I already checked this question on SO, but they say restart your xcode. But this does not solve my problem.
For my case,I got this error after selecting "Generic iOS Device" when archiving, however i plugged in my iPhone and selected it, then archived, I got no errors this time.(I also cleaned both Shift+cmd+k and Shift+alt+cmd+k before archiving)
I encountered the same issue the first time I tried to submit to app store with the target on my device.
What worked for me:
I retried a couple of minutes later without changing a thing and everything went smooth.
This is temporary apple server bug. Try it again OR Retry after some time it will fix the problem.
Thanks
There is no need to reinstall Xcode. Just wait a few minutes and try again and it will work.
I tried :
waiting days,
restarting,
deleting the developer account in
preferences,
submitting archives from a connected device,
submitting
archives from a iOS generic device.
Nothing worked.
I needed to:
create an archive (it was from a connected device),
in the organiser window select the export button (on the right hand side underneath the "Upload to App Store" button.
Select that the export is for app store distribution.
Wait.
Take a note of the location the .ipa file is saved to.
Go back to Xcode, then select the menu item Xcode > Open Developer Tool > Application Loader.
Select Deliver Your App, and select choose.
Navigate to your .ipa file noted above.
Select next, wait, next, check for any error message, send.
Hope this helps someone.
I got this error while uploading my distribution archive to App Store with selecting Distribution provisioning profile scheme -> Product -> Archive -> Upload to App Store. The error is based on I chose my real iphone device in Xcode by mistake. You need to choose "Generic iOS Device" and repeat same steps as I mentioned before.
You have to plug in your iPhone to your Mac and try to upload to AppStore again.
For some reason, validating the archive before uploading fixed the issue for me.
With Xcode 7.1, I could only make a successful build without bitcode. Try it out if everything else fails.
I resolved this by exporting ("export" in xcode archive organizer -> "to iOS App Store") and using the Application Loader instead of xcode to submit.
It is recurring. Seems to me like an internal error with apples identification service or so.
My definite solution:
Get yourself a cup of tea and try it again.
You can, of course, do some voodoo or change the target device or something, but re-trying after a while will do.
I have the same issue.
I did the below steps:
Step 1: Select Code Signing Identity for "Release"
Step 2 : Select Distribution profile
I tried to use Application Loader instead and it worked well. Maybe that helps
I've been having this problem since Xcode 7.1 (for more than a month). I did everything I could trying to solve this: restart Xcode, clean project, clean build folder, build with a device connected, reinstall Xcode multiple times, even formatting the whole disk and starting from scratch. None of this worked.
During this time my colleague was always able to upload the very same builds to App Store without any problem.
Curiously, what solved this problem for me was disconnecting my non-Apple wireless mouse.
I found this out when I tried to submit an app from my home computer and got the same error. I disconnected the mouse dongle, tried again and it went through.
I've verified this three times both on my home (MacBook Pro 2013) and work computer (Mac Mini 2014).
This leads me to believe that during the app submission process Apple may check if your environment is purely made by Apple or not, and may block your submission based on that. This would explain the "Cannot verify client" message.
This one worked for me:
Delete the Archive that failed during upload.
Clean the solution.
Rebuild the solution.
Archive the it.
Go to Xcode's Organizer, then Validate (this should be 'Successful').
Upload the build.
I'm working on creating an app for in house distribution enterprise level. I've created the app and tested hosting it on my own server and even getting the click to install working. Now though I have some updates to the app, I make the edits and I even see them in the simulator. When I build and archive the app things seem fine, then I go to the archived project in the organizer window, click the share button and distribute for enterprise, I enter details such as the ipa final url and the app title and then ok & save. Then I upload the app to my server and update any links to point to this new app. The click to install still works properly, but it installs the old version of the app. I've even tried this on a new device. Is there some step I'm mission that tells Xcode some version to build? If so, I don't get is how the simulator shows the update fine, but the archive that is built is not showing the latest code. The app I can find in the simulator dirs is 9.4MB in file size, but the one that is saved after build and archive is only 1.4MB (the update involves a lot of added images), so is the build for archive is not even getting the new files?
if a clean won't work, try completely removing the derived data folder.
the default location is in /Users/you/Library/Developer/Xcode/DerivedData . if you haven't played with the DerivedData location in preferences, this is likely where you'll find the sub-folder containing the cache.
when i encounter a situation similar to the original question (retaining items i've deleted, or similarly missing items i've added or holding onto project icons i've changed), i perform a clean on my project, close it, hit Delete… in the organizer, possibly even remove it from the organizer, possibly even remove from disk and then re-checkout from git if you have it under version control in this way, then re-open the project from scratch.
I figured it out and thought I should post it in case it helped someone else.
I cleaned the project.
Build > Clean - not 100% on what "Clean" is supposed to mean/do, but it allowed the project to build from the current files rather than the old files somehow.