Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24483] iOS: Unable to package with enterprise ad-hoc provision

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2017-03-20T17:01:26.000+0000
Affected Version/sRelease 6.0.2
Fix Version/sRelease 6.0.3
ComponentsiOS
Labelsn/a
ReporterEric Merriman
AssigneeChris Barber
Created2017-03-13T23:54:06.000+0000
Updated2017-05-15T14:36:24.000+0000

Description

Description:

Based on some customer feedback I believe we have an issue packaging using enterprise adhoc provisions. We will get an enterprise developer account and validate as soon as possible. I am unsure if this is limited to Studio builds and not the CLI as we don't have data to show it works from the CLI.

Steps to reproduce:

1) Attempt to package a project with an enterprise adhoc provision

Result:

Failure as seen in TIMOB-24444

Expected Result:

Build completes successfully

Comments

  1. Thomas Neerup 2017-03-14

    I can verify that using CLI results in the same error
  2. Chris Barber 2017-03-16

    Titanium SDK master PR: https://github.com/appcelerator/titanium_mobile/pull/8890 Titanium SDK 6_0_X PR: https://github.com/appcelerator/titanium_mobile/pull/8891 Note that you can no longer select ad hoc provisioning profiles for app store builds and vice versa. Observe that enterprise ad hoc provisioning profiles are now displayed in the ti info -t ios output. There is a flaw that I chose not to fix at this time where you can select a distribution cert that is not listed in the provisioning profile. The build will fail when Xcode signs the app. In the future, we should properly identify certs and filter out provisioning profiles that aren't associated to that cert. Ticket: TIMOB-24494.
  3. Chris Barber 2017-03-16

    Note that Studio needs to properly handle enterprise provisioning profiles. Here's the ticket: TISTUD-8729.
  4. Abir Mukherjee 2017-03-17

    Passed FR using this environment: NPM Version: 2.15.9 Node Version: 4.5.0 Mac OS: 10.12.3 Appc CLI: 6.1.0 Appc CLI NPM: 4.2.8 Appcelerator Studio, build: 4.8.1.201612050850 Xcode 8.2.1 Passed FR. I created an Adhoc build with an Apple Enterprise account using the CLI, and no errors were seen.
  5. Abir Mukherjee 2017-03-17

    Fixes are seen in this SDK: SDK 6.0.3.v20170317093820
  6. Michael Landeck 2017-03-21

    I have still the same error with my enterprise profile, just a different error message (works fine with 6.0.1): [INFO] : Packaging for Ad Hoc distribution [ERROR] : Failed to export archive to ipa [ERROR] : The selected provisioning profile doesn't appear to be a Ad Hoc provisioning profile or match the signing identity. [ERROR] : Please ensure you are using a valid Ad Hoc provisioning that is linked to the signing identity, then try again. [INFO] : Finished building the application in 38s 432ms Operating System Name = Mac OS X Version = 10.12.3 Architecture = 64bit # CPUs = 4 Memory = 17179869184 Node.js Node.js Version = 6.10.0 npm Version = 3.10.10 Titanium CLI CLI Version = 5.0.11 Titanium SDK SDK Version = 6.0.3.v20170317093820 SDK Path = /Users/ml/Library/Application Support/Titanium/mobilesdk/osx/6.0.3.v20170317093820 Target Platform = iphone
  7. Hans Knöchel 2017-03-21

    [~mlandeck] Did you use Studio or CLI?
  8. Chris Barber 2017-03-21

    [~mlandeck] If you're building from Studio, then it's possible Studio isn't displaying the valid list of provisioning profiles. I created TISTUD-8729 to address this. If you build using the CLI, then it should work.
  9. Michael Landeck 2017-03-21

    Hi Hans, i'm using Studio..
  10. Hans Knöchel 2017-03-21

    Ok, then it's what we suggested. You could use appc run -p ios -T dist-adhoc and select your correct profile from the CLI and we get the Studio fix ready asap. Sounds like a deal?
  11. Michael Landeck 2017-03-21

    Ok, thanks, sounds good.
  12. Alberto Marcone 2017-05-10

    this solution (and the update to 6.0.4) doesn't work on my install. I tried the "appc run -p ios -T dist-adhoc" and, after selecting identity and provisioning, I get the error: [INFO] Optimizing .plist and .png files [INFO] Invoking xcodebuild [INFO] Packaging for Ad Hoc distribution {color:red}[ERROR] Failed to export archive to ipa [ERROR] The selected provisioning profile "xxx (xxx)" is most likely not a valid Ad Hoc provisioning profile. [ERROR] Please ensure you are using a valid Ad Hoc provisioning that is linked to the signing identity, then try again.{color} [INFO] Finished building the application in 49s 423ms The provisioning is valid and it's linked to the signing identity, we used it before and I double checked it. macOS 10.12.4, Xcode 8.3.1, TiSDK 6.0.4
  13. Chris Barber 2017-05-10

    [~a.marcone] View the trace level log output and you'll see the exact command the build runs to export the IPA from the archive. You can copy and paste it to run it again and see the full error for yourself. The error is almost certainly a provisioning profile related problem.
  14. Alberto Marcone 2017-05-15

    you were right, I put the trace level and this is the exact error: [TRACE] 2017-05-15 16:00:37.875 xcodebuild[26823:15650404] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/hq/km1drj0141v1bf195s13yq740000gp/T/xxx_2017-05-15_16-00-37.873.xcdistributionlogs'. [TRACE] 1.2.840.113635.100.1.61 [TRACE] 2017-05-15 16:00:55.196 xcodebuild[26823:15650404] [MT] IDEDistribution: Step failed: : Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.} [TRACE] error: exportArchive: No applicable devices found. [TRACE] [TRACE] Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.} I found a thread on SO mentioning this ticket. I'm using TiSDK 6.0.4.
  15. Alberto Marcone 2017-05-15

    updating to Xcode 8.3.2 fixed this. Thank you

JSON Source