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.
Related
I don't remember this has happened to me before, but for some unknown reason my last app build does not appear in TestFlight. The archiving and upload went as usual with no problem. And if I try to make a new upload, it says there is already a build with this number (as expected).
Has anyone experienced the same issue and found a working solution?
Check email linked with apple account, you might have received email listing with issues apple found on your build which most of the times related to .plist file for any missing permission description. After removing issues do change the build Number as you cannot upload with the same build number as previous one.
Besides the reason mentioned by Ali there can be one more thing. Your application might be on processing for the time. Just go to:
Your application>TestFlight>Activity
Check if application with uploaded build version is there and status is in processing. It may take up to and hour or more before it come to your testing tab.
I could fix the problem by adding this key "App Uses Non-Exempt Encryption" in Info.plist
App Uses Non-Exempt Encryption = NO
We encountered the same issue and here is our breakdown of steps.
Important note - phone connects to BT device
Our steps: Solution is under 4. and 6.
Archive the app and upload it over Xcode successfully
Used automatic signing
Everything went smoothly, and Xcode showed a successful upload
Build never shows up on TestFlight
There are no emails about failed processing or any indication of what went wrong
Accidentally found that we’re missing Bluetooth privacy string in Info.plist
Added NSBluetoothAlwaysUsageDescription, archived, and uploaded again
Used automatic signing
Everything went smoothly, and Xcode showed a successful upload
Received an email from AppStoreConnect that Info.plist is missing NSBluetoothPeripheralUsageDescription
This is the first email I received stating something is wrong. Only after adding NSBluetoothAlwaysUsageDescription
Added NSBluetoothPeripheralUsageDescription, archived, and uploaded again
Used automatic signing
Everything went smoothly, and Xcode showed a successful upload
Build visible on TestFlight within several minutes
:party
The issue was that the app was crashing because it was missing the string. The app did not crash on our testing device because that string was once there and the system already asked the user for permission. The field was probably accidentaly deleted during development.
To find similar issues, try to delete the app from your device and install it again to see if it runs.
I have also faced this issue before, tried all the fixes had not received any mail from apple about what the issue is, but finally fixed the issue after making changes in the info.plist file the issue was that description was missing in info.plist file, mostly it occurs because of that check the file again.
I was also facing the error when I make a build and upload it to the app store it display successfully on Xcode. but the build was not appearing on the app store test flight. then I check my email where the app store team was indicating my issue clearly. in my case, my app name contains a white space on starting.
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".
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!
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
I want to know the basic steps for uploading my iPhone application to AppStore.
How do I make a provisioning profile using a certificate and what other settings do I need to do to upload an application?
I have just made an application on my iMac using Xcode and the iPhone SDK V2.2.1. What do I need to do for uploading it on the Apple iTunes store?
I am member of that and I have also a distribution certificate.
This arstechnica article describes the basic steps:
Start by visiting the program portal
and make sure that your developer
certificate is up to date. It expires
every six months and, if you haven't
requested that a new one be issued,
you cannot submit software to App
Store. For most people experiencing
the "pink upload of doom," though,
their certificates are already valid.
What next?
Open your Xcode project and check that
you've set the active SDK to one of
the device choices, like Device - 2.2.
Accidentally leaving the build
settings to Simulator can be a big
reason for the pink rejection. And
that happens more often than many
developers would care to admit.
Next, make sure that you've chosen a
build configuration that uses your
distribution (not your developer)
certificate. Check this by
double-clicking on your target in the
Groups & Files column on the left of
the project window. The Target Info
window will open. Click the Build tab
and review your Code Signing Identity.
It should be iPhone Distribution:
followed by your name or company name.
You may also want to confirm your
application identifier in the
Properties tab. Most likely, you'll
have set the identifier properly when
debugging with your developer
certificate, but it never hurts to
check.
The top-left of your project window
also confirms your settings and
configuration. It should read
something like "Device - 2.2 |
Distribution". This shows you the
active SDK and configuration.
If your settings are correct but you
still aren't getting that upload
finished properly, clean your builds.
Choose Build > Clean (Command-Shift-K)
and click Clean. Alternatively, you
can manually trash the build folder in
your Project from Finder. Once you've
cleaned, build again fresh.
If this does not produce an app that
when zipped properly loads to iTunes
Connect, quit and relaunch Xcode. I'm
not kidding. This one simple trick
solves more signing problems and "pink
rejections of doom" than any other
solution already mentioned.
Apple provides detailed, illustrated instructions covering every step of the process. Log in to the iPhone developer site and click the "program portal" link. In the program portal you'll find a link to the program portal user's guide, which is a really good reference and guide on this topic.
Check that your singing identity IN YOUR TARGET properties is correct. This one over-rides what you have in your project properties.
Also: I dunno if this is true - but I wasn't getting emails detailing my binary rejections when I did the "ready for binary upload" from a PC - but I DID get an email when I did this on the MAC
Xcode 9
If this is your first time to submit an app, I recommend going ahead and reading through the full Apple iTunes Connect documentation or reading one of the following tutorials:
How to Submit an iOS App to the App Store
How to Submit An App to Apple: From No Account to App Store
However, those materials are cumbersome when you just want a quick reminder of the steps. My answer to that is below:
Step 1: Create a new app in iTunes Connect
Sign in to iTunes Connect and go to My Apps. Then click the "+" button and choose New App.
Then fill out the basic information for a new app. The app bundle id needs to be the same as the one you are using in your Xcode project. There is probably a better was to name the SKU, but I've never needed it and I just use the bundle id.
Click Create and then go on to Step 2.
Step 2: Archive your app in Xcode
Choose the Generic iOS Device from the active scheme menu.
Then go to Product > Archive.
You may have to wait a little while for Xcode to finish archiving your project. After that you will be shown a dialog with your archived project. You can select Upload to the App Store... and follow the prompts.
I sometimes have to repeat this step a few times because I forgot to include something. Besides the upload wait, it isn't a big deal. Just keep doing it until you don't get any more errors.
Step 3: Finish filling out the iTunes Connect info
Back in iTunes Connect you will need to complete all the required information and resources.
Just go through all the menu options and make sure that you have everything entered that needs to be.
Step 4: Submit
In iTunes Connect, under your app's Prepare for Submission section, click Submit for Review. That's it. Give it about a week to be accepted (or rejected), but it might be faster.