I just wanted to know if i could upload my own app to AppStore. I want to download it in my mobile phone. Is there another possibility to do that?
Yes, it’s possible. Depending on your development environment, you may have to take a few extra steps.
-
To build something you can deploy to Apple’s App store, it has to be done from a Mac. If you have a Window’s PC, you can either look for a cheap used Mac Mini or use the MacInCloud service.
-
You have to have an Apple Developer account which has a $99 + tax USD fee per year. This is for all Apple developers. It’s paid to Apple. It’s not a Corona fee.
-
You have to learn about Apple certificates, bundle creation, provisioning. You have to setup your store entry for Apple’s App Store, which means writing descriptions, providing screen shots etc.
But Apple iOS is one of the OS’s that’s our main focus and Corona will produce the proper .ipa file needed to upload using Apple’s Application Uploader tool.
We have a guide in our documentation on this. It’s a bit dated, because we can’t keep updating our documentation every time Apple or Google makes a change to their services. There are plenty of tutorials that can be found on an Internet search on how to setup your Apple developer account, your App Store app entry and uploading the .ipa file to the store.
Rob
As of xcode 13.0 (installed on my mac yesterday with updates), applicationLoader is no longer available. The Apple documentation has been changed to say that apps need to be loaded through xcode.
What is the new procedure for Corona apps? The latest build still tries to start applicationLoader, which does not start, of course.
David
I was able to download an old version of ApplicationLoader from here (https://itunesconnect.apple.com/apploader/ApplicationLoader_3.1.dmg) and it worked, although it gave a warning about the API file. But I was able to add my latest update. I guess that is what we have to do now? Is there a recommendation for the future?
Will Apple remove the link to ApplicationLoader now that they do not recommend using it, or are they just removing it from Xcode (rhetorical question)?
Xcode 11 started rolling out over the past couple of days. Yes, they removed Application Loader in favor of building in uploading inside Xcode as a convenience for native developers.
You have two options as of now:
-
Find a version of Xcode 10 and save the Application Loader app to somewhere on your computer, such as your desktop.
-
Figure out how to use the command line tools that let you upload to the store.
Engineering has been alerted to this change and I’m sure at some the Corona build dialog box will be updated to use the command line tools to do this, but we’ve not gotten that completed yet.
Seems to me finding an older application loader download may be the best choice for now.
Rob
Thank you. If anyone has a newer version (than 3.1 I posted above) of ApplicationLoader to download, that would be great.
Command line tools seem like a great idea… but my experience with xcode command line tools has not been good, documentation not very helpful, but I will look at them, thanks for the suggestion.
From what I can tell so far, the command line tools all depend ultimately on altool, which is a tool within ApplicationLoader, thus no longer available, at least on my mac. This change makes a lot of blog recommendations out of date. But maybe someone else can find something.
It’s still on my Mac. You have to do “xcrun altool” to get it to run. There may be a need to setup an API key instead of using a username/password combination. One StackOverflow post I found went that route, but when I went to setup an API key, I was a little confused by what Apple’s intent was with regard to uploading. They said you could upload to TestFlight, but they didn’t say any thing about uploading to production.
Thank you, I do have xcrun altool. I just did not see it in the Xcode…Applications folder and not in finder search. Thank you! I will sort out how to use that.
The bash script here : https://stackoverflow.com/questions/57976017/how-to-upload-ipa-now-that-application-loader-is-no-longer-included-in-xcode-11 seems to work for me. It requires getting an API key, downloading it, putting it in ~/.private_keys/ and editing the script with the key ID and user IDs :
#!/bin/bash APPFILE=$1 set -euo pipefail # key is in ~/.appstoreconnect/private\_keys KEY="\<the key part of the AuthKey\_key.p8 file\>" ISSUER="\<YOUR ISSUER ID\>" xcrun altool --upload-app --type ios --file $APPFILE --apiKey $KEY --apiIssuer $ISSUERThank you, that is good to have. So far, the older ApplicationLoader seems to work fine, but if Apple disables that access, I will use altool. It is easy to set up, thank you.
It appears we may finally have some good news from Apple as far as uploading apps built for iOS 13! They have released a new MacOS app called Transporter which according to Apple "makes it easy to upload your binary to App Store Connect. "
Apple news article:
https://developer.apple.com/news/?id=10152019a
Mac App Store link:
https://apps.apple.com/us/app/transporter/id1450874784?mt=12
Nice!
Next daily build would use Transporter instead of Application Loader.
Using xcode 11.1 and corona 2019.3541 and receiving:
"Oct 18 03:38:16.556 No itunesConnect account info found: make sure you are signed into Application Loader (and have checked “Keep me signed in.”)"
"Oct 18 03:38:16.556 ERROR: Cannot Send To App Store: Only apps built with distribution profiles can be sent to the App Store. Choose a provisioning profile signed with an “iPhone Distribution” certificate and note that the provisioning profile used should not specify any devices (i.e. is not “ad hoc”).
"
I’m selecting the correct distribution profile but do not have application loader installed since it no longer comes with xcode.
I’ve installed transporter and signed into my account but it does not seem to help. Any ideas?
I have no idea if this is what’s happening with you, and I haven’t tried transporter yet, but I got a similar error when I had accidentally signed my provisioning profile with the wrong certificate. Might want to double check that…
I had tried the Transportet with the Corona version 2019.3540 and it was successful but haven’t been able to try it with the version 2019.3541 as my Corona is broken and can’t make it build. I’ll try one more time and let you know if it works.
Regarding to Provisioning errors, I had that kind of errors and I ended up deleting all the related entries from key chain, and doing everything from scratch.
This forum subject may help you: https://forums.coronalabs.com/topic/76100-ios-build-error/
The first error is very weird, but second one seems that certificate is wrong. Can you screenshot the certificate name ? (Certificate name is in parentheses after provision profile name in selection box)
I tried deleting all certificates and profiles and creating them all from scratch but it didnt help.
See attached screenshots.
Got it! We don’t support “Apple Development” certificates just yet. Please, select iOS distribution when issuing a certificate.
Thank you!