Titanium JIRA Archive
Appcelerator Daemon (DAEMON)

[DAEMON-206] Appcelerator Studio not detecting iOS after upgrading

GitHub Issuen/a
Resolution Date2017-12-11T17:33:16.000+0000
Affected Version/sAppc Daemon 1.0.0
Fix Version/sAppc Daemon 1.1.0
ReporterAlberto Marcone
AssigneeChris Barber


After upgrading Xcode, Appcelerator Studio and node, I can't run any application from Appcelerator Studio. The Run/Debug buttons have disappeared, whenever I click on anything concerning iOS, I get the error: !MESSAGE An internal error occurred during: "Loading Provisioning Profiles...". !STACK 0 java.lang.NullPointerException Attached some of the weird things happening + the logs. I already tried uninstalling Appcelerator Studio, it didn't change anything (besides losing all of my configurations)


Schermata 2017-12-11 alle 16.39.17.png2017-12-11T15:40:09.000+000031952
Schermata 2017-12-11 alle 16.39.38.png2017-12-11T15:40:10.000+0000340400
Schermata 2017-12-11 alle 16.39.44.png2017-12-11T15:40:12.000+000042960


  1. Ewan Harris 2017-12-11

  2. Alberto Marcone 2017-12-11

    [^diagnostic] attached the files! The appc ti info contains info that I can't share (clients certificates), but this is the gist of it: Operating System Name = Mac OS X Version = 10.12.6 Architecture = 64bit # CPUs = 4 Memory = 8.0GB Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.0.14 node-appc Version = 0.2.41
  3. Ewan Harris 2017-12-11

  4. Alberto Marcone 2017-12-11

    I sent you an email with the requested file. I had a look at that ticket but the node version doesn't look too new, it's the recommended 8.9.1.
  5. Ewan Harris 2017-12-11

    [~a.marcone] Unfortunately there's a couple issues in that ticket I should have been more specific, your node version is fine :) I was referring to the URI malformed error but the dump file you sent shows that it's different, I'l move this ticket to the correct project
  6. Chris Barber 2017-12-11

    [~eharris] Yes, this issue is fixed by DAEMON-205 which is in ioslib@2.0.4. Resolving this a fixed.
  7. Alberto Marcone 2017-12-11

    great! what can I do to get it fixed on my side?
  8. Chris Barber 2017-12-11

    [~a.marcone] So, that's a little complicated. We don't support upgraded packages inside a release, but it is possible. From a clean folder, you can npm i ioslib && cp -R node_modules/ioslib ~/.appcelerator/install/7.0.0/package/node_modules/.
  9. Alberto Marcone 2017-12-12

    this didn't work. {quote}➜ npm i ioslib && cp -R node_modules/ioslib ~/.appcelerator/install/7.0.0/package/node_modules/ npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years. > node-ios-device@1.4.0 install /private/tmp/fix/node_modules/node-ios-device > node ./bin/run.js node-pre-gyp install --fallback-to-build [node-ios-device] Success: "/private/tmp/fix/node_modules/node-ios-device/binding/node-v57-darwin-x64/node_ios_device.node" is installed via remote npm WARN saveError ENOENT: no such file or directory, open '/private/tmp/fix/package.json' npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN enoent ENOENT: no such file or directory, open '/private/tmp/fix/package.json' npm WARN fixxx No description npm WARN fixxx No repository field. npm WARN fixxx No README data npm WARN fixxx No license field.{quote}
  10. Ewan Harris 2017-12-12

    [~a.marcone] Do the steps below work? I believe the above might fail due to changes made around npm install walking up a directory tree looking for a package.json is the current directory doesn't have one

    Stop the daemon appc appcd stop

    cd into the appcelerator package cd ~/.appcelerator/install/7.0.0/package

    Install the update npm install ioslib@next

    Reopen Studio

JSON Source