Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-19452

Extensions should default to the app's provisioning profile if not set

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Release 5.2.0
    • Component/s: CLI, iOS
    • Labels:
    • Environment:

      SDK 5.0.0.v20150901212316

    • Story Points:
      3
    • Sprint:
      2015 Sprint 25 SDK

      Description

      Right now when you don't have provisioning profiles set up for your extensions you will get an error like:

      [ERROR] iOS extension "appc-sample-ti500" target "<device>" is missing the appc-sample-ti500 WatchApp Extension provisioning profile UUID in tiapp.xml.
       
      <ti:app xmlns:ti="http://ti.appcelerator.org">
          <ios>
              <extensions>
                  <extension projectPath="extensions/appc-sample-ti500/appc-sample-ti500.xcodeproj">
                      <target name="appc-sample-ti500 WatchApp Extension">
                          <provisioning-profiles>
                              <device>PROVISIONING PROFILE UUID</device>
                          </provisioning-profiles>
                      </target>
                  </extension>
              </extensions>
          </ios>
      </ti:app>
      

      However, it's perfectly fine to use a wildcard app id provisioning profile for both the app, watch-app and extension.

      My suggestion would be to maybe warn, but still continue and use the provisioning profile selected for the app for the watch-app and extensions as well.

      For sample apps e.g. then all we need to ask is for them to add the Apple Watch to their wildcard, if they haven't already done so. Instead of giving them the impression that they need to go through the hassle of creating all these profiles and adding them to tiapp.xml.

        Attachments

          Activity

            People

            • Assignee:
              cng Chee Kiat Ng (Inactive)
              Reporter:
              fokkezb Fokke Zandbergen
              Reviewer:
              Chee Kiat Ng (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                  Git Source Code