Itunes Connect Archive stays in processing - app-store-connect

I uploaded an archive from XCode to iTunes Connect successfully. But the Archive stays in "Processing" Status for almost 2 days now without any change. I can't change the status, and need to update the archive for being available for testflight users.
Can anyone give me a helping hand on this?

Are you using Xcode 7?
If so, try not including Bitcode in your app. Mine then processed in less than 30 minutes (previous builds with Bitcode all 24hrs +)

Related

iOS app "Processing" in iTunes Connect

I uploaded my first iOS app today to iTunes Connect.
I uploaded it over xCode 7.2.1 and I see the app as "Processing" inside the "activity"-tab.
But under "AppStore"-tab for version 1.0 there is no app build visible. I only see the message that I should upload a build with xCode or Application Loader.
Is this normal or should I wait some time that the app is also showing up?
See the screenshots below:
Yes, this is perfectly normal. You just have to wait for it to finish processing (can take a few minutes or a few hours depending on Apple's traffic). Once it is done processing, it will appear in that builds section and you can select it as the version you want to submit. This is the same for TestFlight.
I recommend getting watchbuild and running it on your terminal so you can just get a notification on your computer when your build is done processing instead of having to keep checking App Store Connect.
It happened to me a couple of times. I just uploaded a new version (same code, just increased the version) and it was processed quite fast.
Just in case, the second time I kept the archiving dialog in the foreground.
This is normal. After uploading a build, iTunes Connect performs some processing to prepare it for TestFlight Distribution and App Store distribution.
The status of the build should go to ready after some time. Sometimes, this happens as fast as 15 minutes after uploading but can sometimes take 1 hour or longer. After the processing finishes, the build will become available to select for TestFlight betas and app submission.
Yes, this is perfectly normal. You just have to wait for it to finish processing (Can take a few minutes or a few hours depending on Apples traffic). Once it is done processing, it will appear in that builds section and you can select it as the version you want to submit. This is the same for testflight.
Additional from my personal experience (happened to me once and only once), if you submit the archive late at night on the last weekday or just before a public holiday, "sometimes" it might be processed on the next working day on the morning.
I'm at Indonesia (GMT +7), it is not uncommon for me to upload an archive around 7PM, and if it doesn't get processed in 15 minute, I usually just go home, and check it in the morning the next day. Because it happens a few time that if I upload too late, it get processed around 8AM the next morning.
I had this issue today, i tried all of the fixes suggested and found that you need to wait till the invitations are sent out. I think the servers were just very busy when i was trying to test my app.
It happened to me when I export Unity iOS build and upload it to AppStore there are more than 3 days waiting but still showing processing.
Finally, Many search things I found that Bitcode = NO here is the issue on my build I have Bitcode = YES once you change and set to NO and upload again your build it's not showing processing and it's working properly.

Appcelerator Titanium & Git - what are these random new uncommitted files?

In my Titanium project, I have been new uncommitted changes to following files being shown in my Git status:
plugins/ti.alloy/hooks/alloy.js
plugins/ti.alloy/hooks/deepclean.js
I've never seen or touched those files and someone else in my team got them as well randomly after an update some time ago.
Are these updates to the Titanium Alloy framework that should live in .gitignore? Or should I commit them?
Those files are changed with an update of Alloy (CLI). When you work with multiple people on the same app, it will be recommited every time someone works with a different Alloy version.
You can commit it without causing anything wrong, or you can also add them to gitignore without issues (not tested, but should not cause issues).

iTunes Connect Screenshots Continue to Fail

I'm trying to upload new images to iTunes Connect. However, they continue to fail. I've checked many many times now and no dice. The screenshot sizes match Apple's requirements. Saving it as a .jpg continues to fail. Saving it as a .png with no Alpha continues to fail. Spent most of my work day on here finding other solutions that I've tried and still fails.
Other things I tried was using different browsers, saving the image file as generic as possible (ex. 1.png, and I've tried using screenshots pulled from an actual device as well as the Xcode simulator.
I am trying to do this via a windows machine. Has anybody been able to successfully upload screenshots through iTunes Connect using a Windows machine? At this point that is the only thing I can think of as to why it continues to fail.
Try waiting... in my experience, iTunes connect is not all that reliable, and waiting a day solved the screenshot upload issue for me.
Also, if you have not already, open the screenshots in an image editor, and insure they are exactly the right size... I have found that my screenshots always end up a pixel to skinny for some reason.
Lastly, keep in mind new rules for the iPhone 6 and 6 Plus.

Change version release control in iTunes connect

I submitted an app update in iTunes Connect and set the version release control to Hold for Developer Release. I want to change it to release automatically (it is still waiting for review). Is this possible, and if so, how do I make this change?
I've torn through iTunes connect extensively and there doesn't seem to be a way to change an automatic release to Hold for Developer, or a Hold for Developer marked release to automatic release. It seems to be set upon creation of the version and uneditable.
There may be a way to do this by rejecting the binary and starting the process over, but I haven't had a chance to test this as I don't have any pending releases and nothing currently ready to be updated.
Funny, I came across this post yesterday because I needed to change this setting. Today, Apple updated iTunes Connect and it's now possible to change this option right on the binary page.
It seems that you can't, but if you want to you can go to rights and pricing and move the availability date to a later date. Users won't be able to download you app during that time, but the update won't be available to existing users either when new version gets approved.

Updating an iPad App with a Completely Different Architecture

I've been updating my iPad app very steadily now and the process has been fine. But in a month or so, I'm going to be upgrading it to a version that has a completely different architecture.
Both versions will be using the cache and db in very different ways to store the data it's pulling from a server.
Question: Will the Apple update process automatically delete all local data from my previous version upon installing the new version? Or, do I have to code this functionality in somewhere in my new version?
Example: Some files you download on Windows don't remove the data from "Application Data" or "Local Settings" upon uninstalling. I fear that this same scenario will happen on my iPad when upgrading my app to a completely new version. Is this the case?
Thanks,
Derek
No, the update process does not delete files that you have in the app's documents folder. They will still be there.
iPhone and iPad updates do not remove data from previous version installations of an app. Your app will have to detect (say, look for the current version number) the old databases, and either delete them, or perhaps better for the user, update them to the new format.
Make sure to somehow tag the new data format with a version number so your app can detect it, and not delete it.