Integrate a WatchKit App Built in Xcode


This guide covers how to integrate a WatchKit app built in Xcode with your Titanium application as well as information about sharing data between the extension and application.  This guide does not cover how to develop a WatchKit app. Currently, the Titanium SDK supports WatchKit apps that are built in Xcode and run on watchOS 2.

A WatchKit app contains a specialized app extension that runs on either the Apple Watch or iOS device, depending on the watchOS version.  The WatchKit app allows the user to access data from your application on their Apple Watch.


  • Appcelerator CLI 5.0 or greater
  • Titanium SDK 5.0 or greater
  • Xcode 7 or greater
  • Xcode Command-Line Tools
  • Paired iOS devices must run iOS 9.0 or greater

As of SDK 6.0.0, the watchOS 1 template and all related code are no longer supported. See TIMOB-20083 for details.


Create an Apple Watch Application

Using Studio

To create an Apple Watch application:

  1. Open the project's tiapp.xml file in the Overview tab.
  2. Under the Apple watchOS 2 App section, click Create New...
  3. A dialog will prompt you for the name of the application.  Enter a name for the watch application, then click OK.

Studio will generate a new Xcode WatchKit project in the Titaniuim project's extensions folder and updates the ios extensions element in the tiapp.xml file.  Open the Xcode project's <NAME>.xcodeproj to start developing the watch application.


Using the CLI

To create an Apple Watch application, run the following command from the Titanium project that will include the watch application: 

appc new -t applewatch -n <WATCH_APP_NAME> --template watchos2

If you omit the --template option, the CLI will create a watchOS 2 project by default.

The CLI will generate a new Xcode WatchKit project in the Titaniuim project's extensions folder and updates the ios extensions element in the tiapp.xml file.  Open the Xcode project's <NAME>.xcodeproj to start developing the watch application.

Share Data Between the Application and Extension

For watchOS 2 extensions (or later), use the Watch Connectivity Framework and the Titanium.WatchSession APIs to transfer files and data between the watch and iOS application, respectively.

Setup a Session

To setup a Watch Connectivity session, the watch application needs to check if the paired device supports Watch Connectivity sessions before retrieving a default session and activating it.  Activating the session opens a channel between the paired devices.

if ([WCSession isSupported]) {
    watchSession = [WCSession defaultSession];
    watchSession.delegate = self;
    [watchSession activateSession];

In the Titanium application, you must also check to see if the paried devices supports Watch Connectivity sessions with the Titanium.WatchSession.isSupported property, then call the Titanium.WatchSession.activateSession() method to activate the session allowing messages to be transferred between devices.

if (Ti.WatchSession.isSupported) {

To check if the session is activated and the paired watch application is reachable, use the following APIs.  Some APIs require that the applications are in a reachable state.

Watch Connectivity Framework API Titanium.WatchSession API Description
Ti.WatchSession.isSupported Checks to see if the paired device supports Watch Connectivity sessions.
reachable Ti.WatchSession.isReachable Checks to see if the paired devices share a Watch Connectivity session and both applications are in the foreground.
-sessionReachabilityDidChange: Ti.WatchSession.reachabilitychanged Called or fired when the reachability state changes on the paired device.

Transfer Data

The Watch Connectivity framework provides a few different ways to exchange data between the iOS device and watch.

Transfer Files

Besides data, you can transfer files between the paired devices. Use the following APIs to transfer files:

Watch Connectivity Framework API Titanium.WatchSession API Description
-transferFile:metadata: Ti.WatchSession.transferFile() Transfers a file to the paired device in the background.
-session:didReceiveFile: Ti.WatchSession.receivefile Called or fired when the device receives a file transfer from the paired device.
-session:didFinishFileTransfer:error:  Ti.WatchSession.finishfiletransfer Called or fired when the transfer completes (successfully or not) on the paired device.


Provisioning Profiles

Before deploying a watchOS application to a device or creating a package for distribution, you need to create provisioning profiles for both the WatchKit application and WatchKit extension. You may either add the watch device to an existing provisioning profile or create separate provisioning profiles. Separate provisioning profiles will be needed if you want to support push notifications.

For directions on creating a provisioning profile, see Deploying to iOS devices or Distributing iOS apps.

After you create your provisioning profiles and add them to Xcode, you need to add the UUID of the provisioning profiles to the tiapp.xml file.

Using Studio:

  1. Open the tiapp.xml file in the Overview tab.
  2. Under the Apple watchOS 2 App section, click Configure Provisioning Profiles...
  3. In the Configure Targets step, verify both the Watch App and WatchApp Extension are checked, then click Next.
  4. For each distribution target, select in drop-down the provisioning profile you want to use for the WatchApp and WatchApp extension.


Using a Text Editor:

  1. Open the tiapp.xml file.
  2. Locate the extensions element under the ios element.
  3. Xcode 8 requires the Team-ID of your app to be set in order to link the different app targets. Add the Team-ID of your app into the team-id element
  4. Under the extensions element, you should see two target elements.  One is for the WatchKit extension (target name should contain the Extension) and the other is for the WatchKit app (target name should not contain Extension.
  5. Under each target element, you should see three self-closing elements: devicesdist-appstore and dist-adhoc.  Add the UUID of the provisioning profile as node text for each deployment type.

    1. devices: Add the UUID of the development provisioning profile

    2. dist-appstore: Add the UUID of the app store distribution provisioning profile

    3. dist-adhoc: Add the UUID of the ad hoc distribution provisioning profile 

The example below add the development provisioning profiles to the file.

    <!-- Required for Xcode 8 and later (Titanium SDK 5.5.0+) -->
      <extension projectPath="extensions/foo/foo.xcodeproj">
        <target name="foo WatchApp Extension">
        <target name="foo WatchApp">

Run the Project

To run the project, just build and launch the project like you would any other Titanium project, but for the WatchKit app, add the --launch-watch-app or --launch-watch-app-only flags to launch the watch application with or without the iOS application, respectively.

For Studio, use the run command from the launch options toolbar. If you want to run the watch application on a simulator, in the Target drop-down, select a 9.0 or greater simulator that has a paired watch target.


For the CLI, execute appc run -p ios with the additional build options.

appc run -p ios --launch-watch-app

If you have more than one watch application extensions, specify the watch application to launch with the --watch-app-name <APP_NAME> option.

If you want to specify the watch simulator, use the --watch-device-id <UDID> option.

Package the Application

To package the application with the extension, just package the project like you would any other Titanium application.  For Studio, use the package command from the launch options toolbar, and for the CLI, execute appc run command with the package options.

Further Reading

iOS Developer Library: Apple Watch Programming Guide

Related Links