Release beta version, install IPA and apk online via web page

Many times we need to publish a beta version, if released as an installation package, let testers install themselves, many times is very difficult, especially the iOS version, most people do not know how to install other than AppStore.

Automated deployment can be achieved through web-based installation, and terminal testing users only need to download the installation via the page. You can also eliminate the process of sending the package to the Publisher, share a link address, and click the link to complete the installation.

Android version is very good processing, only need to deploy a static file server, Android devices can download and install their own. Here are the main instructions on how to install iOS online.

The steps for iOS online installation are simply to deploy an HTTPS file server (Nginx), generate a good OpenSSL certificate, and sign the app with a adhoc or Enterprise version certificate. This allows the user to install by simply visiting the page via Safari. To illustrate, apps signed with an Enterprise version certificate cannot be uploaded to the App Store, but any device can download and install the app. Apps signed by Adhoc require Udid of the end user device to be added to the signed. Mobileprovision in order to install. Users who are not joined to the Udid are not able to install.

The steps are as follows:

1. Deploy an HTTPS server. Here we use Nginx (also can use Apache's httpd). Note You must be an HTTPS server, or you will not be able to start the iOS installation feature.

Install Nginx on Linux can refer to here, need to install some dependent libraries (such as Pcre).

OpenSSL requires a 0.9.8 version, not a 1.0 version. The compiler configuration for Nginx is as follows:

./configure--with-http_ssl_module--with-openssl=.. /openssl-0.9.8zhmakemake Install

2, Nginx configuration as follows (the key to see the HTTPS part)

User root;worker_processes 1; #error_log logs/error.log; #error_log logs/error.log notice; #error_log Logs/error.log I NFO; #pid logs/nginx.pid;events {worker_connections 1024;}    HTTP {include mime.types;    Default_type Application/octet-stream;  #log_format Main ' $remote _addr-$remote _user [$time _local] "$request" ' # ' $status $body _bytes_sent    "$http _referer" ' # ' "$http _user_agent" "$http _x_forwarded_for";    #access_log Logs/access.log Main;    Sendfile on;    #tcp_nopush on;    #keepalive_timeout 0;    Keepalive_timeout 65;    #gzip on;        server {Listen 80;        server_name 127.0.0.1;        #charset Koi8-r;        #access_log Logs/host.access.log Main;            location/ios_test {root/mnt/langresser/download/;        Index index.html index.htm;        }location/ipa_test {alias/mnt/langresser/download/;add_header content-dispositoin "attachment";} #eRror_page 404/404.html;        # REDIRECT Server error pages to the static page/50x.html # Error_page 502 503 504/50x.html;        Location =/50x.html {root html; } # Proxy The PHP scripts to Apache listening on 127.0.0.1:80 # #location ~ \.php$ {# ProX        Y_pass http://127.0.0.1;        #} # Pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # #location ~ \.php$ {        # root HTML;        # Fastcgi_pass 127.0.0.1:9000;        # Fastcgi_index index.php;        # Fastcgi_param Script_filename/scripts$fastcgi_script_name;        # include Fastcgi_params; #} # Deny access to. htaccess files, if Apache ' s document Root # concurs with Nginx ' s one # #l        ocation ~/\.ht {# deny all; #}} # Another virtual host using mix of ip-, name-, and port-based configuration # #server {# Listen 8000;    # Listen somename:8080;    # server_name somename alias Another.alias;    # location/{# root HTML;    # index index.html index.htm;        #} #} # HTTPS Server # server {listen 443 SSL;        server_name 127.0.0.1;ssl on;        SSL_CERTIFICATE/USR/LOCAL/NGINX/CONF/SERVER.CRT;    Ssl_certificate_key/usr/local/nginx/conf/server_nopwd.key; #autoindex on; #autoindex_exact_size off; Location/ios {root/mnt/langresser/download/;index index.html index.htm;}    Location/ipa {alias/mnt/langresser/download/;add_header content-dispositoin "attachment";}}    # Ssl_session_cache shared:ssl:1m;    # ssl_session_timeout 5m; # ssl_ciphers high:!anull:!    MD5;    # ssl_prefer_server_ciphers on;    # location/{# root HTML;    # index index.html index.htm; #    }    # }}

3. When the IPA is generated, it generates a manifest.plist at the same time. This is going to make some changes, primarily the server IP address. Examples are as follows:

<?xml version= "1.0" encoding= "UTF-8"? ><! DOCTYPE plist Public "-//apple//dtd plist 1.0//en" "Http://www.apple.com/DTDs/PropertyList-1.0.dtd" ><plist Version= "1.0" ><dict><key>items</key><array><dict><key>assets</key ><array><dict><key>kind</key><string>software-package</string><key >url</key><string>https://127.0.0.1/ipa/thirtysix.ipa</string></dict><dict> <key>kind</key><string>display-image</string><key>url</key><string> https://127.0.0.1/ipa/thirtysix57.png</string></dict><dict><key>kind</key>< string>full-size-image</string><key>url</key><string>https://127.0.0.1/ipa/ Thirtysixfull.png</string></dict></array><key>metadata</key><dict><key >bundle-identifier</key><string>com.jzsj.thirtysix</string><key>bundle-version</key><string>1.0</string><key>kind</key><string> Software</string><key>title</key><string> 36 meters </string></dict></dict> </array></dict></plist>

4, a test page as follows (index.html, configured in Nginx)

<! DOCTYPE html>

5, after the configuration, after the deployment of an Nginx server, the user in Safari access to the corresponding IP address (note to access through HTTPS, do not enter the IP address directly, because the default is HTTP) can see the index.html page. The user installs and trusts the certificate (the HTTPS certificate) first, and then clicks the corresponding link to invoke the operating system's service to automatically download the installation app.

Release beta version, install IPA and apk online via web page