I uploaded iOS build from XCode 8.1 (macOS Sierra), it uploaded successfully but not reflected on iTunes connect
Then I tried same build uploading from Application Loader, it shown me error
"Redundant Binary Upload" error.
So I increased build number and tried uploading it from Application Loader, now it uploaded successfully again but not reflected on store.
Does anyone came across this issue ? Please let me know if I am missing something.
Note: I added all permissions and entitlements.
Usually it will take some time for the binary to be processed before you can select it in itunes connect.
Check your email, and wait for an email with this title
iTunes Connect: Version 8.8.8 (23) for My Awesome App has completed
processing.
Or if your binary have some problem, itunes connect will also contact you with this kind of email
iTunes Connect: Your app "My Awesome App" (Apple ID: 888xxx888) has
one or more issues
This usually happens when some entries are missing in Info.plist file.
Please ensure entries like below are included in Info.plist if your app uses them. (This is introduced in iOS 10 onwards)
NSBluetoothPeripheralUsageDescription
NSMicrophoneUsageDescription
NSCameraUsageDescription
NSPhotoLibraryUsageDescription
etc.
You may get an email from iTunesConnect as well with subject - "Your app has one or more issues".
Related
I want to add my first iOS application developed with Visual Studio 2017 Xamarin iOS. I created the new version for my app in the iTunes Connect, filled up all the information required. Then I went to the application loader to upload it and the process done successfully, but in the iTunes Connect no build appear. I reviewed my email and it said:
"Dear developer, We have discovered one or more issues with your
recent delivery for "E2EWorks Mobile". To process your delivery, the
following issues must be corrected: Missing Info.plist value - A
value for the Info.plist key 'CFBundleIconName' is missing in the
bundle 'com.e2eworks.e2eworksmobile'. 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 more information see
http://help.apple.com/xcode/mac/current/#/dev10510b1f7. Once these
issues have been corrected, you can then redeliver the corrected
binary. Regards, The App Store team"
I fixed all necessary things and rebuild application again but now application loader doesn't let me to upload again. I checked iTunes activity but no application is shown however submmit to review button is enabled. Under builds section it keeps saying: "Submit your builds using Xcode 6.0 or later, or Application Loader 3.0 or later."
Please your help.
Every upload of IPA's bundle to iTunes Connect requieres a unique and distinct CFBundleVersion string on info.plist, so any issue caused just after uploaded or rejected event that must be corrected, a new CFBundleVersion must be set. In my case it started with 1.0 and after correction, string changed to 1.0.1 (minor bugs fixed) and proceeded to build and uploaded again succesfully. I'm newbie in iOS stuffs.
I hope this help to anyone in similar situation!
I've recently written my first iOS app in swift using Xcode and am trying to get it into iTunes connect. I have set up the app record with the same identifier as in Xcode, archived the app and uploaded (again with Xcode). The uploader result says that's it's been successful (with the green tick) but in the iTunes connect under activity there is no sign of it. This is after waiting overnight.
Has anyone else had this problem recently? Also my understanding was that if there were errors the uploader normally identifies these (such as no app record found). Is there anything else I should be doing or is this something apple should be resolving?
I had the same issue and surprisingly I just had to wait. Unfortunately I can't tell you exactly how long to wait because I checked my build after a month and it was successfully uploaded to iTunes connect. Make sure to look into iTunes connect -> My Apps -> iOS App (App status) -> Build
It should look like this when it's done:
It might be due to a missing permission in info.plist file, you will receive an email for this on the email id registered with the account, if this happens.
Please check the email id for such a mail. It will be described there which permission is not mentioned in the info.plist.
You can then fix this and re-upload the build. Also, ensure that you have changed the build/version number else you will get an error that build with same version/build number already has already been uploaded.
So in case anyone else has this problem I 'solved' it by:
Not using the downloaded application uploader but by running it from the Xcode > Developer menu within Xcode itself. It showed in the activity part of iTunes connect immediately.
I was trying to upload a build(Version:2.1, Build:2.1.0) from Xcode 8. It failed with following error.
After 9-10 failed attempts, I succeeded once but that binary is not appearing on iTunes Connect. It's been 15 hours since and the binary is still not appearing on iTunes Connect.
So I decided to perform following steps:
Re-archive and submit the build(Version:2.1, Build:2.1.0) again. It says the same build already exists.(I can't see it on itunesconnect)
Re-archive and submit the build(Version:2.1, Build:2.1.1). In first 6-7 attempts, it gave the same error as shown in the screenshot. But at last, the build was submitted successfully. (I still can't see any build on iTunes Connect)
I contacted Apple support and here is the answer I got from them,
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data.
Once these issues have been corrected, you can then redeliver the corrected binary.
Applying this fix solved my problem. The binary get uploaded in the first attempt and it also has appeared in itunesConnect.
Check your email, Apple will send you keys(from info.plist like NSPhotoLibraryUsageDescription etc.) which you missed.
Just add all of them and fill up description in keys
Example :
NSCameraUsageDescription
Please allow the app to access your photo camera
NSLocationWhenInUseUsageDescription
App use Locations service
NSMicrophoneUsageDescription
Please allow the app to access your photo microphone
NSPhotoLibraryUsageDescription
Please allow the app to access your photo gallery
Try it using XCode 8... Open the Application Loader(Xcode -> Open Developer Tool -> Application Loader). Choose the build that you archived and then submit to the Apple Store.
Maybe, you need change the build version before do the step above.
It works for me. I hope that works for you!
While my build is uploading, it shows in iTunes Connect, but when uploading gets completed successfully the build no longer shows on iTunes Connect, it get vanished from there.
I tried with both XCode 8 and application loader. I added all required keys in info.plist for usage descriptions.
First of all, check the message from Apple. Recently I also faced same issue. The reason was pretty simple, I missed description keys in info.plist. These keys are mandatory in Xcode 8 + iOS 10 SDK
This app attempts to access privacy-sensitive data without a usage
description. The app's Info.plist must contain an
NSPhotoLibraryUsageDescription key with a string value explaining to
the user how the app uses this data.
This app attempts to access privacy-sensitive data without a usage
description. The app's Info.plist must contain an
NSBluetoothPeripheralUsageDescription key with a string value
explaining to the user how the app uses this data.
Additionally, I was also forced to include "Camera usage description key". I uploaded again with new bundle number, and build reflected in iTunes connect.
This is overcrowded question so this problem is multiple type of process you can try.
This processing step taking around 15 to 20 minutes as it usually does, now applications stay in processing for 24 hours or more at a time.
Try 1 - Upload new binary:
upload a new binary of the same application with an incremented build number.
Try 2 - Avoid using Bitcode
If you've enabled Bitcode in your application,This can be done by going to Setup: Project>Build Settings>All>Build Options and setting "Enable Bitcode" to NO after this you should recompile the app, archive and upload it again using iTunes Connect.
Try 3. Use Application Loader
use the Application Loader utility to upload a new build of your app. After the upload process finishes, your app should also get out of the "Processing" status.
Try 4. Use the latest Xcode.
iTunes Connect "Processing" issue and managed to solve it, using Latest Xcode to build and upload your app might just be the winning solution for your problems.
Try 5. Go to Contact
"Resources & Help" in iTunes Connect. Select "Contact Us".
There are 2 possibilities in this:
1. You are using outdated Xcode to upload. Try the latest one, because apple support stop working for old xcodes after launch of new xcode version.
Your permissions in plist are not available, like you may be using camera feature, photos feature, location feature but permissions are not given in plist so kindly add keys for the permissions in plist..
The best way to figure out about the issue is to check the email ID that is registered with Apple developer account, you must have received email from Apple about the missing component in code. That makes the build of application invalid, so check email first to figure out what exactly the main issue is. It clearly states the next steps. Most of the time above 2 issues are found when build is not appearing in iTunes.
We are trying to upload an updated version of the app to the store. The upload takes a long time and finally when its done, we receive the following WARNINGS.
... Checksum validation failed.
... Checksum validation failed.
Transporter was unable to update one or more software components. Please try again later.
The upload is anyway received by the Apple server and the status says "Waiting for review".
Upload has received and app is also approved.So i think there is no much problem with this.
I've ran into the same issue when I tried using the internet connection from my company, either using Application Loader, or Organizer.
In fact, the problem came from my company's firewall which was blocking some ports.
As it is written in Apple support, you may correct this problem by allowing access to the ports indicated in this file : https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf from page 6 to 8
I think you can ignore the warning. People who had that warning have had their apps approved by Apple. According to https://forums.adobe.com/message/5949439 it most probably has to do with version number. Here's a quote
Ignore it. Apple is just letting you know that the version number in
the app isn't the same as the version number in iTunes Connect. The
iTunes Connect version is what's displayed in iTunes/App Store.
I tried to remove these warnings by clean and Archive but could not. Finally I increase the "Bundle versions string, short" in the project's info.plist file and re-uploaded and successfully uploaded the app without warnings.
chec and note the version number in from ur binary details in itunes
delete the updated binary from itunes
setup for a new binary to upload
clean the project
make the bundle name and version name same on ur project(the same on u noted from ur binary details before deleting)
Rebuild
Archive
Validate
Distribute