All geek questions in one place

Cannot connect to example.com in an iOS corporate application

I have a serious problem. I am trying to make an enterprise live.By application using BetaBuilder, I follow the following steps:

myApp.ipa manifest.plist index.html

manifest.plist:

 <?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://example.com/ios/myapp.ipa</string> </dict> </array> <key>metadata</key> <dict> <key>bundle-identifier</key> <string>com.com.myapp</string> <key>bundle-version</key> <string>1.0</string> <key>kind</key> <string>software</string> <key>title</key> <string>Myapp</string> </dict> </dict> </array> </dict> </plist>

and index.html file:

 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0"> <title>Myapp - Beta Release</title> </head> <body> <div id="container"> <h1>iOS 4.0 Users:</h1> <div class="link"><a href="itms-services://?action=download-manifest&url=https://example.com/ios/manifest.plist">Tap Here to Install</a> </div> </div> </body> </html>

I even made an http link to https . But he always says: Cannot connect to example.com . What is wrong with the setup?

+4
source share
1 answer

Distribution of iOS distributions must be performed using SSL with a valid SSL certificate.

Now, to distribute OTA, you must follow these steps.

1) Provide a link to the created .plist file containing the manifest for downloading the application. This link MUST be serviced over SSL with a valid SSL certificate. An example of a valid .plist file is as follows:

 <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//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://[full download url].ipa</string> </dict> </array> <key>metadata</key> <dict> <key>bundle-identifier</key> <string><full bundle identifier></string> <key>bundle-version</key> <string>[version string]</string> <key>kind</key> <string>software</string> <key>title</key> <string>[software name]</string> </dict> </dict> </array> </dict> </plist>

2) The URL in the .plist file must be submitted from a valid SSL certificate.

Now I am not 100% of your server settings, but there is a possibility that the web server will not respond correctly to the .plist extension, as well as the .ipa extension. You must configure the web server to understand the following file extension: \ mime-type:

  • Extension: .plist

  • MimeType: application/xml

  • Extension: .ipa

  • MimeType: application/octet-stream

At first, we had a lot of problems with having our applications deployed over the air. The biggest hurdle is the SSL certificate and MimeTypes.

One final comment, I'm sure you have your own domain and arent using example.com in your links or plist files.

Greetings ..

+5
source

Source: https://habr.com/ru/post/974537/

More articles:


All Articles