iOS 7.1 Requires Ad-Hoc Installs To Be Over HTTPS

So, sometime in the future, Apple will release iOS 7.1. This new version includes an important change for BetaBuilder users: the Web server that hosts your deployment files now has to be accessible over HTTPS.

Normal HTTP installs will fail. The latest version of BetaBuilder includes a warning to this effect.

Also important – you cannot use a self-signed certificate unless the device trusts the CA it came from. You either need to use a ‘real’ SSL certificate or you need to import and trust the certificate on any devices that will install the app.

So – if you upgrade to 7.1 or are using the beta and cannot install apps with BetaBuilder anymore, this is probably what’s going on.


15 Comments so far. Leave a comment below.
  1. Clawoo,

    Hi there! Is there a command line flag, checkbox, or anything similar to allow the user to disable the HTTPS alert?

    I am using BetaBuilder in an automated build system where it’s being called from the command line and we’re still using http for the time being (which will change once we get up on it with iOS7.1) and the alert stops the process.


    • Hunter,

      Currently there is not but I’m pushing out another update that does have this option.

      In the meantime, you may want to go back to the previous version of the app (this was the only change so you don’t lose any other features).

      That update should be out relatively soon – Apple’s been approving Mac apps pretty quickly recently.

  2. RI,

    thanks for the heads up!
    there are no apple docs on this, you are one of the only warnings out there on this issue besides an error message if your device is on the 7.1 beta :-/

  3. bianca,

    can i use something like
    i have tried like this, but it doesn’t work.
    when i tried the dropbox’s https link, it works.
    can you help me figure out why the IP doesn’t work?
    thanks a lot

    • Hunter,

      You can’t have an SSL certificate that works against an IP address. SSL certificates require a named host.

      • Joey,

        an SSL certificate does not work against an IP address. I have do it successful:
        1, download apache_2.2.8-win32-x86-openssl-0.9.8g.msi
        2, create server.key, server.crt, and ca.crt by openssl
        3, config the apache
        4, send ca.crt to device and install it
        5, create a html file that include [click] , put it into apahce’s DocumentRoot
        5,click the link on a device

      • Hunter,

        Correct, SSL requires a hostname. This is not unique to iOS’s handling of it, it’s the way SSL works.

  4. Mauricio,

    You were one of the first in telling everybody about this new “Apple´s feature”. Thank you.
    Unfortunately, everybody bumped on it a few days ago.

    I´m trying to solve this new problem for internal deployment and testing.
    I was successful creating an Internal CA certificate, and a SSL one with it. The host is a local IIS referenced as hostname.domain. I installed the CA certificate on the host and configured the HTTPS for the site (hostname.domain) with the SSL certificate. I tested on MacOS Safari client and it could not verified the site until I installed the CA certificate in the keychain. This means that SSL Certificate and CA are working correctly for the host name…
    Then I e-mailed me the CA certificate and installed in my ipad. It is showed as a profile with one certificate, Trusted.
    Unfortunately Ipad´s Safari keeps telling me that cannot verify the identity of the hostname.domain, and if I continue to the page accepting it, the OTA download fails with the message “Cannot connect to hostname.domain”

    Any idea of what is missing?

  5. Mauricio,

    oops! ipad´s clock was 3 month back. It had been configured that way because of a test case and Safari was giving no clue on why the certificate rejection.

    ipad´s chrome suggest me to check the ipad´s clock.

    Thank you, anyway.

    Here is a nice explanation on how to create self-signed o Custom CA certificates, but check the clock!!!

  6. Good morning,

    To make a long story short; I have an iOs 8 app that’s been running for a while. On one of the screens I have a for loop that breaks in release mode but works in debug builds (f… knows why).

    When using release IPA builds with the BetaBuilder website everything works fine as far as the installer is concerned. But when I deploy a debug version either the installation fails, or absolutely nothing happens. Debugging over the cable from my Dev machine works for both Debug and Release.

    Do you have any idea why this would happen?



    • Hunter,

      Sorry, we’re not able to help debug issues like that – local device issues. I’d recommend posting in the Apple Developer Forums.

  7. dylan,

    Just a heads up for those using Corona or similar and not working directly from Xcode, you need these steps to get things working:

    1. Create a directory called “Payload”
    2. Copy app file into Payload
    3. Zip Payload directory (must be done on a Mac)
    4. Rename zip file as appname.ipa

  8. chor thongthip,


    i’ve bought BetaBuilder yesterday and can’t find any solution to solve the problem to upload the app.

    I’ve a https server but don’t know how to make a “real” SSL certificate.

    Please make a Tutorial how to solve this Problem, or delete the app from AppStore, because it didn’t goes with saying.

Add Your Comments


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <ol> <ul> <li> <strong>

Your email is never published nor shared.