I was submitting an app to the iOS App Store a few days ago, and got this message from Xcode. Before I had time to resubmit it, Apple has already started reviewing my app. Is this something I need to worry about?
Edit: The app was accepted a few days later.
I had the same problem and Google led me here. From my understanding a checksum is used to ensure that the file Apple received is identical to the file you (thought you) uploaded to them.
I decided to delete my upload and try again. This worked and I didn't get the error message again. Here's what I actually did:
In iTunes Connect:
Manage Your Apps > [your app] > View Details of the New Version.
In the links near the top the right click on Binary Details then, on the next page, Reject This Binary. It says you'll have to prepare another upload but it's just another button to press.
Back on the View Details page just click 'ready for upload' in the top right. It might say something slightly different but I don't want to delete by upload to double check :P
You're now ready to upload a new binary.
In xcode:
Go to Window > Organizer > Archives and delete the archive you previously uploaded.
In the main window of xcode press cmd-option-shift-k to clean your build folder.
Make a new archive and upload it like you did before. Fingers crossed all goes well.
Related
My Xcode Version 8.2.1
I submitted my iOS app to iTunes Connect on yesterday but, the status is still showing “Processing” under Prerelease tab.
I found one link My prerelease app has been "processing" for over a week in iTunes Connect, what gives?
So, I changed the build version today and again uploaded .Today's Build is missing on iTunes Connect
Is this normal or is it a bug or I did something wrong? What’s my next option?
Thanks
It will take time to show your build on itunes connect. Some points you should cross check once before uploading again :-
1) If you are uploading build via Application Loader then check you version first. And I suggest you to upload it via xcode. Sometimes it happens binary get corrupt in "Payload" folder because there is some hidden files for eg .git or else. You should also check your Payload spelling for folder (Mistyping happens sometimes)
2) Check your email first , did you get any email from Apple. Sometimes it happens that our binary is not correct and further validation checked after binary upload. It shows in build section but after a while it is removed from there. You'll get mail regarding this.
3) Your build version should be greater then you uploaded previously.
Yes It is normal. Me too faced the same issue. So i upload the new build with different build number and it processing completed old and new build also.
The Reason behind it is the privacy issue in plist,
if u are using any UIImagePicker or any extra component so u must have to add key to plist.
Here is the some points to taken care.
1> Check all permission like location,photos,bluetooth if extra so remove it.
2> Add this if u using UIImagePicker NSPhotoLibraryUsageDescription
Photo Library Access Warning
I know there are a lot of questions about this already, but I am fairly certain my question has not been answered yet.
I uploaded a build of my iOS app via Application Loader, and that went well. I got to the end with a message of "Done", so I thought it was okay.
Then I went to check in iTunes Connect and I cannot see a build (not even under "Activity"). I waited for an hour and I retried uploading the build. In Application Loader I now get the error "Redundant Binary Upload", so that tells me that my build is somewhere in iTunes Connect, but I can't find it.
What could have gone wrong? Is this something that usually happens? How can I know when my build is "Processing", so I can continue with the release process?
If you have the email of developer account apple search emails. If you up to itunesconnect an ipa and you can´t see in 5 min Apple always send a mail with the problem some times bad missing icons on app, problems like "privacy-sensitive data without a usage description" or with push notifications disabled ... You must fix the problem, increase the build version and upload again.
Here an example:
Please be patient as it takes some time to process your build and show up on iTunes. Try checking the "Build" section from where you'll select the build in order to proceed and submit for review.
Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key
For older projects without assets catalog there will be issues while submitting to Appstore
In Project —> Target Properties - General tab—> App Icons and Launch Image. App Icons —> Select Use Asset catalog Then it will ask to convert (migrate) with an alert and creates a .xcassets file. Check the box to convert launch images too.
When you are done the App Icons Source and the Launch Images Source will have names in the dropdown list. Add the app icons and other icons to it
This is an issue in Appstore and I was facing the same issue. I have just increased the build version and uploaded a new build on Appstore. New uploaded build start showing in the activity tab.
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
I am getting a warning icon while trying to submit the app to App Store. I am using XCode 6.4 to submit the app directly to the app store from Organizer itself, I usually do like that only.
On clicking the warning icon, I am unable to see any reasons described. I tried with all the browsers for this.
I saw the below links also where they talk about beta-reports-active = 1 entitlement and I have made sure that it is present and also I am not using watch kit. Below is the snapshot of entitlements
Build warning
Build upload warning
So not sure what is the issue, the only thing that I did recently is that, since our certificate was expiring soon, I did a reset of the certificate using Xcode 7 (since it was easy to do it with Xcode 7). This ended up in having a profile automatically created by Xcode, now when I archive and try to submit, Xcode is picking this XC: profile.
Just wanted to know, if it is okay to submit even with this warning. Need to push a patch fix soon. Thanks in advance for the help.
After a couple of refresh of the screen the Warning went off, then in the next refresh, warning came back.Also I started seeing radio button names eg:"Manually release this version" as ITC.Manuall...... just crazy!!
Looked like something weird with the iTunes Connect site. In the next refresh where I got with no warning, I went ahead and submitted uh!!!...I couldn't run around with no clue :)
UPDATE: THE APP GOT APPROVED...HOOF!!!
I want to update my app. I have a new version of the app and now it says "Prepare for Submission".
Now I want to perform "Prepare for Upload" but I cannot find this in the new iTunes Connect.
I have tried to upload the app to iTunes using Application Loader and Xcode 5.1 but still the status hasn’t changed and when I click on "Submit For Review" I get the following error:
You must choose a build.
It is quite weird but let me show what I have learnt from this new iTunnesConnect layout.
Step 1: You should wait around 10 min to 20 min to see your uploaded binary file in the prerelease section. .
Step 2: After you wait a while (10-20 min) then you would see the below icon
Step 3: Then you could able to see that your binary is ready.
Step 4: Then click on plus (+) sign, you now could able to choose your binary and then click submit for review button to finalize.
Look for it here:
Here's the new binary I uploaded:
Then, don't forget to create a new version and then assign the new binary to it (after process is completed):
I had the same problem, and waited for more than 8 hours without any result. The plus-icon never showed up under the build section!
Then I saw a new (tax-agreement) contract that I had not signed. I signed it, waited for a few more minutes, and then the plus-icon showed up!
The reason could also be that you are still releasing binary with the old TestFlight SDK in it.
A few months ago TestFlight updated their service meaning that it is now included in iTunesConnect, previously a TestFlightSDK was included in the project and various codes needed to enable TestFlight for users. This is all now depreciated. This means if you release a new version of an app which still has the TestFlightSDK included your binary won't appear in iTunes Connect and you will receive an email like this:
We have discovered one or more issues with your recent delivery for "blahApp". To process your delivery, the following issues must be corrected:
TestFlight SDK - TestFlight no longer requires an SDK to enable beta testing, crash reporting and analytics. To continue using TestFlight, set up Beta Testing in iTunes Connect and remove references to the SDK from the following executables: blahApp.app/blahApp
Once these issues have been corrected, you can then redeliver the corrected binary.
You need to remove the TestFlightSDK and also all code linked to the old TestFlight. Once this is done the binary should start being picked up by iTunes Connect as the answer above states.
The tricky thing about this issue is that if you're like me the email could go through to your junk, to an old account or if you're working for a client and don't have access to their personal email it is tough to find. Apple give you no other indication that this is what's wrong.
Hope this helps people with this problem going forward
Just took 19 minutes. If you click the activity tab you can see that the upload is processing.
At this time of writing, binary submission should take only few minutes to appear in iTunesConnect. When my binary did not show up for hours, I can immediately tell that something is not right. Most of the answers I found resolved to waiting. This was not the case for me. I went to ask Apple support and I got the answer. My app was missing purpose string for one of my protected data class (for iOS 10 and later). Once I provided the usage description and resubmitted it, the binary shows up right away.
I thought someone else might be facing the same problem. For a complete list of protected data class that requires descriptions, check out this link: https://developer.apple.com/library/content/qa/qa1937/_index.html