Error when uploading to iTunesConnect - air

I am using Application Loader to upload my .ipa files (created with Adobe AIR v18) to iTunesConnect.
It's been working fine for months, but today I received two new errors:
The u option must have a non-empty value.
The password must have a non-empty value.
Can anyone shed some light on the issue?

I upgraded to Xcode 7.1 and that solved the problem!
Note: Xcode 7.1 comes with Application Loader 3.3.

You have 2 solutions:
1) Update your Xcode to 7.1 (but since you are not coding natively, use the solution #2 below)
or
2) Download and use the Application Loader v3.1 (Download link: https://itunespartner.apple.com/en/apps/tools ) to submit your IPA

Apart from low-belly's answer you can try to use XCode's built-in upload feature. If you go to the Organizer, just click on Upload to App Store:
This solved the problem for me in XCode 7.0.1.

Xcode 7.1 was downloading too slow (more than 4GB) and the update failed every time, so for now I downloaded the Application Loader 3.1 from iTunes Connect and it worked fine.
To download it you login into iTunes Connect -> Resources and Help -> click on View Tools (under the title Other Resources at the bottom of the page) and there is the download link.

I got the same error last night. Fixed it by signing out of Application Loader (3.6) and logging back in.

I got the same error with Application Loader 3.2. Submitting with Application Loader 3.0 (bundled with Xcode 6.2) or 3.1 (bundled with Xcode 6.4) solved the problem.

Related

Branch.io Deep linking not working on iOS 13+. It does not show pop-up to open application(Ionic 5, Capacitor)

I have added deep-linking integration in our app and using plugin capacitor-branch-deep-links. It is working till iOS 12.1 but in iOS 13+ it does not show a pop-up to open the application on a click of deep-link.
I have also tried forced uri redirect mode but none of these solutions are working.
https://help.branch.io/using-branch/docs/creating-a-deep-link#forced-redirections
Installed Dependencies:
Ionic 5.26.0
#capacitor/cli 2.4.5
#capacitor/core 2.4.5
#capacitor/ios 2.4.5
capacitor-branch-deep-links 3.0.0
After going through this link, I figured out that I was using the wrong Apple App Prefix and invalid Provisioning Profile Specifier. This correction fixed my issue. Though I am still not sure why it was working in iOS 12 with the wrong Apple App Prefix and Provision Profile

ITMS-90424: Invalid Swift Support

I am trying to upload my app to the app store. I can archive my app and successfully upload to App Store Connect, however, it keeps getting rejected with the following error message:
Dear Developer,
We identified one or more issues with a recent delivery for your app, "Retainer Tracker" 1.0 >>(8). Please correct the following issues, then upload again.
ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
Best regards,
The App Store Team
I've tried a bunch of diffrent fixes I've found online but still can't get it to work. Can anyone help?
The basic reason is your application using swift and your swiftsupport folder is empty. Let's move in detail
If your application using Xcode to make .ipa file and there is no third-party IDE involve to create Xcode project, you can fix this issue by upgrading your Xcode
If you are using some other IDE to make the Xcode project then please follow that link. I already give the answer to this question. Invalid Swift Support - The SwiftSupport folder is empty
The problem occurred right after I added a specific Swift Library
Doing the following fixed the issue in my case
Go to Targets > YourApp > Build Settings
Under Packaging:
Defines Module: Yes
Under Assets:
Always Embed Swift Standard Libraries: Yes
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
For us, our CICD pipeline was using an Ad-Hoc Provisioning Profile to distribute the ipa build to Testflight/AppStore.
We fixed this by using an App-Store Provisioning Profile instead.

Missing dSYM files in Crashlytics Today extension (Bitcode disabled)

The title of this question basically says it all. I enabled Crashlytics in my Today extension, and for some reasons, the dSYMs are not being uploaded, even though I'm not using Bitcode.
I tried uploading them manually (from ~/Library/Developer/Xcode/Derived Data/Timelines-evxmjnxmpmcivkavmpijzakaxkrp/Build/Products/Debug-iphoneos/Timelines.app.dSYM), but the web interface doesn't really give me any feedback. It shows this screen:
No matter how long I wait, once I refresh the page, it goes back to the 'upload dSYMS' screen.
I think the problem might be that the UUIDs of the missing dSYMs don't really match those that I found locally.
Some notes on my setup:
Xcode 8.2
Today extension running on iOS 10.2
Bitcode is not enabled.
Fabric and Crashlytics integration was done using CocoaPods.
Archive wasn't uploaded to App Store. I'm just testing it locally on my devices. But since the entry for crash reports was created in the web interface, I assume the automatic upload should work anyway.
My question basically is: how exactly can I upload the dSYMs manually? And, second one: how can I make the automatic upload of dSYMs work? Thank you.
It is described here completely ==> fabric.io.
As it said you can download it from activity tab in itunesconnect and then upload it to crashlytics website.

ERROR ITMS - 90167 No. app bundles found in the package on macOS Sierra

I am using Xcode 7.3.1 on macOS Sierra which I just updated yesterday.
Since I updated, I can't upload any more builds to Testflight; I always get this error message.
ERROR ITMS - 90167 No. app bundles found in the package
I see from research that this problem only happens in the macOS Sierra beta, but I worry it's going to continue through the final release
After a deep search and investigation, I finally decided that there is nothing wrong with our build. There was a problem when uploading our build with Apple iTunes Connect, which is that server denied uploading our build on Xcode 7.3.1 on macOS Sierra. But, uploading with Xcode 8 is working just fine. Just use the Application Loader from Xcode 8 if you are not ready for Migration to Xcode 8, or if some of your project's third party libraries don't support Swift 2.3.
So, how do I pass this?
Simply, just install two version on Xcode: one to continue your development.And one for uploading the submit.
Here is how : https://blogs.oracle.com/mobile/entry/how_to_install_multiple_xcodes
Create an archive from your Xcode 7.3.1 and export an .ipa with with your production profile. Then upload that .ipa via the Xcode 8 Application Loader. This is inside the Xcode app bundle: Xcode.app/Contents/Applications/Application Loader.app
You can also get to it inside of Xcode:
Xcode menu > Open Developer Tools > Application Loader
This is the only solution until Apple fixes it, believe me.

Processing failed in itunesconnect

I had archieved the xcode project and uploaded it into itunes connect. This is 5 time uploading, for internal testing. It shows the following error
I don't have any idea that why the error are showing, i'm using Xcode 7.2 . Can any one help to resolve this error, i stuck for more than a day.
Try with Application Loader.
sometimes i faced same issue with Xcode7.2 then will try upload app with Application Loader. it's worked fine.
For uploading app with Application Loader ....
Step-1) First create IPA of your App.and Export your IPA which is created with iOS App Store Deployment.
Step-2) Right Click on XCode(from dock) >> Open Developer tool >> Application Loader
Step-3) Choose IPA (which is saved for iOS App Store Deployment) and Next to upload. it will be take some small time and after few mins it will be show on itunes connect.
after few mins it will be show on itunes connect.it is very easy and faster uploding compare to xcode. Hope it Helps you!.
its currently a bug, many dev are facing it.
Also you can follow it here