Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-19452] Extensions should default to the app's provisioning profile if not set

GitHub Issuen/a
TypeImprovement
PriorityMedium
StatusClosed
ResolutionFixed
Resolution Date2015-12-17T09:41:37.000+0000
Affected Version/sn/a
Fix Version/sRelease 5.2.0
ComponentsCLI, iOS
Labelsnotable, watchOS2
ReporterFokke Zandbergen
AssigneeChee Kiat Ng
Created2015-09-02T06:38:29.000+0000
Updated2016-02-22T16:41:28.000+0000

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.

Comments

  1. Fokke Zandbergen 2015-11-25

    PR: https://github.com/appcelerator/titanium_mobile/pull/7497 Tested on device
  2. Fokke Zandbergen 2015-12-17

    Backport: https://github.com/appcelerator/titanium_mobile/pull/7592
  3. Chee Kiat Ng 2015-12-17

    APPROVED. PRs merged.
  4. Eric Wieber 2016-02-22

    Verified fixed, using: MacOS 10.11.3 (15D21) Studio 4.5.0.201602170821 Ti SDK 5.2.0.v20160220080449 Appc NPM 4.2.3-2 Appc CLI 5.2.0-269 Alloy 1.7.33 Xcode 7.2 (7C68) Extensions now default to the parent building app's provisioning profile when no profile is set. A proper warning is shown on build. Tested with a default sample app and the default extension.

JSON Source