We make software for humans. Custom Mac, Windows, iOS and Android solutions in HyperCard, MetaCard, and RunRev LiveCode
AirLaunch used to work fine but now it fails to install my app.
Starting with iOS 7, Apple began requiring a secure (SSL) server for over-the-air distributions. Installation will fail if the folder path to the download folder does not begin with "https". If you are uploading files to your own server, it must have a valid security certificate installed, and the path to your download folder must begin with "https".
How do I name the folder that AirLaunch creates for my files?
As of version 1.03, AirLaunch names its app folder based on the path you enter in the "App Download Folder" field. The folder name will be the last item in that path.
Note: Installations may fail to download if the folder name contains spaces or special characters like accents or other diacriticals, even if they are url-encoded. It's a good idea to always give the folder a one-word name with no special characters.
Early versions of AirLaunch accepted multiple-word folder names if they were url-encoded. This caused some problems, so AirLaunch now replaces spaces with underscores in folder names.
When installing an app on my device, the progress bar gets close to the end and then stalls or gives a message that the app can't be downloaded.
When iOS installs an app, it first downloads the file and then checks it for validity. If you see a progress bar when installing, it means AirLaunch worked but the validity check failed.
Some common reasons are:
- The app was compiled with an invalid or expired provisioning certificate
- The device ID was not entered in the developer portal on Apple's web site
- New devices were added in the developer portal but the profile was not refreshed in XCode
- The provisioning profile changed but the app was not recompiled with the new profile
The download link in the manifest has a nonstandard URL beginning with "itms- services://?action=download-manifest" and nothing happens when I enter the link in a browser.
The URL is a proprietary Apple scheme that only works to install apps on an iOS device. If you click the URL in a browser, nothing will happen or you will get an error.
My folder name is only one word but it still doesn't work.
Make sure the folder name does not contain any high-ASCII characters like accents, umlauts, or other special characters. Those can fail even though AirLaunch url-encodes the URL, especially in iOS 5.1.
My server does nothing or gives a 404 "File not found" error when I tap on the HTML link.
The server probably doesn't recognize Apple's proprietary URL, so it doesn't know what to do with the link. You'll need to add these extensions and mime types to the server list:
- .plist - text/xml
- .ipa - application/octet-stream
Can I use AirLaunch without an Apple developer account?
No. An iOS app requires a valid developer provisioning certificate to run on your device. Apple won't allow a non-provisioned app to install and AirLaunch can't overcome that restriction.
Can I use AirLaunch to update my app in the App Store?
No. Only Apple can release products to the App Store, and all submissions must go through their approval process. No third-party product can bypass that.
Can I use AirLaunch with applications built with other tools?
AirLaunch 1.03 has been updated to work with any iOS app built with any development tool (XCode, Flash, etc.) This is experimental right now, so if you try it, please let us know how it goes.
The exported custom HTML file includes two wildcard entries. Are there any other wildcard options available?
Yes. AirLaunch 1.032 added two new wildcard entries you can use. These will insert the current app bundle ID and version number when the HTML file is built. You will need to add them manually to your custom template if you want to use them: