View source for Support for iOS and tvOS

=Support for iOS=

==Introduction==

If this page is in a crude state, it’s because it’s a quick brain dump of experiences taking a simple (QQuickView + <span class="caps">QML</span>, minimal UI) app from Linux &amp; OS X Desktop to iOS, and written in the hope it will be useful to other developers with Qt/Desktop experience who are quite unfamiliar with “mobile” and iOS and Xcode. Please feel free to edit mercilessly. This page doesn’t (yet) describe App Store submissions.

==Prerequisites==

* You’ll need an iOS device.
* To deploy an application onto an iOS device, you’ll need a key (or “team provisioning profile” as Apple calls it) from Apple to sign the executables. The easiest way to get this is probably to register on the [https://developer.apple.com/programs/ios/ Apple iOS Developer Program] ''[developer.apple.com]''. A yearly fee must be paid.
* You need Xcode, and therefore a Mac running OS X.
* You need the iOS device connected to your Mac via the provided <span class="caps">USB</span>.
* You need to “Provision Your iOS Device for Development”: this can be done from the xcode device organizer: https://developer.apple.com/library/ios/recipes/xcode_help-devices_organizer/articles/provision_device_for_development-generic.html
* You need a Qt x.x.x for iOS <span class="caps">SDK</span> (note that this also includes the OS X support; whereas if you download the Qt x.x.x for Mac <span class="caps">SDK</span>, it’s just the OS X stuff. Hence the considerably larger size of the iOS <span class="caps">SDK</span>).

(If you’re happy just programming Xcode’s iOS device simulators then you just need a Xcode and a Mac running OS X; there’s no need to register as an iOS developer for that. Be warned the simulator performance characteristics are significantly different from real HW!)

==Workflow (''not'' using QtCreator)==

===Preparation===

Assuming you have a Qt project which builds for desktop from a qmake .pro file, you should be able to get an iOS build by:

* Get the right tools in your path: You’ll find the iOS Qt <span class="caps">SDK</span> has both (e.g for Qt 5.3.1) 5.3/clang_64/bin/ and 5.3/ios/bin . The clang_64 one is for OS X; make sure it’s the iOS version of the tools is in your path for the below.
* Open the resulting myproject.xcodeproj in Xcode.
* The first time you do this, you’ll probably need to create a myproject.xcworkspace workspace file to contain the project (c.f Visual Studio’s “solutions” which contain projects). But once you’ve done that you can forget about it.
* When qmake runs it also creates an Info.plist file (<span class="caps">XML</span>) which contains a great many interesting settings. While these can be tweaked from within Xcode, this isn’t recommended as the next qmake run will obliterate any changes. Instead, it is better to have a script make any needed changes which can be run after a qmake. (There may be some <span class="caps">QMAKE</span>_ macros which set certain plist properties too.)
* If you rerun the qmake, it’s a good idea to close the xcode project.

===Info.plist===

Useful settings (can be got into the qmake-generated Info.plist using sed/regexps/xslt transforms… whatever works for you):

===Deploying===

* In Xcode, hit the big “arrow” icon top left of xcode to “Build and then run the current scheme”. If all goes well (assuming no compile errors), you’ll get (if your target isn’t a simulator) a dialog “codesign wants to sign using key” (you can opt to always allow this) and it’ll deploy to the device (physical or simulator) you have selected just to the right of that arrow icon. Your application should start up on the device in a short while.
* If Xcode doesn’t seem to be “seeing” your iOS device, some combination/escalation of unplug/replug , restart Xcode, restart Mac generally fixes it.
* Any logging to stdout/stderr from your app appears in a window in Xcode, which is handy.

==Other considerations about the iOS environment==

Stuff you need to know:

===Files on iOS devices===

* iOS apps run in a “sandbox” where they keep their data. They don’t get to mess with other apps data. When the app is uninstalled, the entire sandbox contents is deleted. There are some [https://developer.apple.com/library/ios/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html important conventions to be aware of] ''[developer.apple.com]''.
* You can transfer files to and from a Mac (using iTunes) to that sandbox if the app has enabled “file sharing” (see above mention re Info.plist).
* Such file transferring does seem to be individual files. You can’t select a folder and have that and all it’s contained files and subfolders be transferred. Solutions probably involve “container files” like tar or zip… more on this [http://forum.qt.io/viewthread/41012/#174257 here] ''[qt.io]''.

===https support===

* The iOS platform does not expose OpenSSL as a public library. The Qt for iOS distribution does not contain OpenSSL.
* Qt for iOS supports <span class="caps">REST</span> over https using the following <span class="caps">API</span>:
** C++: QNetworkAccessManager
** <span class="caps">QML</span>: XMLHttpRequest
* Overriding certificate errors is not supported with the current implementation.
* Qt for iOS does not support <span class="caps">QSSLS</span>ocket out of the box. It’s possible to build and link OpenSSL manually. See <span class="caps">QTBUG</span>-3689.

===“Installers” for iOS===

The workflow described above refers to deploying an app to a <span class="caps">USB</span>-attached iOS device.<br /> If you want to send an “installer” for an app to someone remote with an iOS device (NB must be one which has your “team provisioning profile”):

* In xcode, there is a “Product” menu with “Archive” on it (NB need to have iOS device selected as build target, not a simulator).
* That creates an archive in the Organizer window’s Archives tab.
* Select the archive and hit the “Distribute” button.
* This brings up a dialog where you get to select “Save for Enterprise or Ad Hoc Deployment” then “use iOS Team Provisioning Profile”, and then save a .ipa file (an “iOS application archive file” apparently).
* Send the ipa file to the intended user.
* If they double-click the ipa file it should open iTunes’ to install or update the app on the device (when iTune’s “apply” is hit).

===General===

* If you’re used to developing for desktop platforms, you may find the ratio of “graphics power” (OpenGL rendering power) to “compute power” somewhat skewed (towards graphics) compared to your previous experience.

===Categories:===

* [[:Category:Qt-Supported-Platforms|Qt Supported Platforms]]