Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24534] iOS: Failed to export Adhoc/Enterprise archive to ipa (No applicable devices found)

GitHub Issuen/a
TypeBug
Priorityn/a
StatusOpen
ResolutionUnresolved
Affected Version/sn/a
Fix Version/sn/a
ComponentsiOS
Labelscb-tooling
ReporterDemostenes Garcia
AssigneeUnknown
Created2017-03-26T14:21:40.000+0000
Updated2020-01-31T20:52:19.000+0000

Description

If I try to export the project as an iOS Adhoc / Enterprise ipa, it gives the following error:
[ERROR] :  Failed to export archive to ipa
[ERROR] :  2017-03-25 16:47:25.761 xcodebuild[29128:87514] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/fr/nqly_t5n1f13l_k9hbm9vzb80000gn/T/App_2017-03-25_16-47-25.759.xcdistributionlogs'.
[ERROR] :  1.2.840.113635.100.1.61
[ERROR] :  2017-03-25 16:47:26.196 xcodebuild[29128:87514] [MT] IDEDistribution: Step failed: <IDEDistributionThinningStep: 0x7f8e3cd349e0>: Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}
[ERROR] :  error: exportArchive: No applicable devices found.
[ERROR] :

[ERROR] :  Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}
If I do the same over Xcode (by using the .xcodeproj file and archiving it), it works flawlessly. One thing to clarify is that I already added the device / certificates to the account/team and the computer, so that's not the issue.

Comments

  1. Hans Knöchel 2017-03-26

    Hey there! Do you use SDK 6.0.3.GA?
  2. Demostenes Garcia 2017-03-26

    No, using 6.0.2.GA. I will download 6.0.3.GA and retry again. Will keep you posted once I try.
  3. Demostenes Garcia 2017-03-26

    Tried to run it with 6.0.3.GA, but after setting 6.0.3.GA (and last build of 6.0.4) I get the following error:
       Rebuild failed:
       2017-03-26T19:03:06.488Z | ERROR  | Rebuild failed:
       node-pre-gyp info it worked if it ends with ok
       node-pre-gyp info using node-pre-gyp@0.6.29
       node-pre-gyp info using node@7.7.3 | darwin | x64
       node-pre-gyp info check checked for "/Users/demogar/Library/Application Support/Titanium/mobilesdk/osx/6.0.4.v20170324115015/node_modules/node-ios-device/binding/node-v51-darwin-x64/node_ios_device.node" (not found)
       node-pre-gyp http GET https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v1.1.0/node_ios_device-v1.1.0-node-v51-darwin-x64.tar.gz
       node-pre-gyp http 404 https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v1.1.0/node_ios_device-v1.1.0-node-v51-darwin-x64.tar.gz
       
    Looks like a library is missing, so I went to /6.0.4.v20170324115015/ and made npm install node-ios-device and it gives me the following error:
       > node-ios-device@1.1.0 install /Users/demogar/Library/Application Support/Titanium/mobilesdk/osx/6.0.4.v20170324115015/node_modules/ioslib/node_modules/node-ios-device
       > node-pre-gyp install --fallback-to-build
       
       node-pre-gyp ERR! Tried to download(404): https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v1.1.0/node_ios_device-v1.1.0-node-v51-darwin-x64.tar.gz
       node-pre-gyp ERR! Pre-built binaries not found for node-ios-device@1.1.0 and node@7.7.3 (node-v51 ABI) (falling back to source compile with node-gyp)
       
    The package is giving a 404 when trying to download it.
  4. Hans Knöchel 2017-03-26

    Node 7 is not officially supported so far, 4.7 is recommended I think. Also ensure to clear your build directory before.
  5. Abir Mukherjee 2017-03-27

    I had the same error when I was using Ruby that was managed by rvm. Starting with 6.0.2, Adhoc builds now use "xcode archive", which requires system Ruby. Try typing "rvm use system" on the command line, and then try packaging in that same window.
  6. Alberto Marcone 2017-05-15

    still happening in 6.0.4. Don't have *rvm* installed on my system. How did you solve it in the end? (I have node 5.6.0 installed.)
  7. Demostenes Garcia 2017-05-15

    I downloaded 6.0.3.GA and downgraded Node (as per recommendation) and the error disappeared.
  8. Alberto Marcone 2017-05-15

    ok! updating to Xcode 8.3.2 fixed this. Thank you

JSON Source