Unable to package for Ad Hoc distribution because of a Node error below. I can build for everything else (simulator, iOS device or App Store). Was getting the same error before upgrading to the release candidate.
[TRACE] : ** BUILD SUCCEEDED **
[INFO] : Finished building the application in 17s 374ms
[INFO] : Packaging for Ad Hoc distribution
/usr/local/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:181
throw e;
^
Error: EISDIR, illegal operation on a directory '/'
at fs.mkdirSync (fs.js:642:18)
at Object.mkdirSyncRecursive (/Users/danwilson/Library/Application Support/Titanium/mobilesdk/osx/3.1.1.v20130523143543/node_modules/wrench/lib/wrench.js:335:12)
at exports.copyFileSync (/Users/danwilson/Library/Application Support/Titanium/mobilesdk/osx/3.1.1.v20130523143543/node_modules/node-appc/lib/fs.js:133:9)
at /Users/danwilson/Library/Application Support/Titanium/mobilesdk/osx/3.1.1.v20130523143543/iphone/cli/hooks/package.js:124:12
at exithandler (child_process.js:635:7)
at EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Socket.
(child_process.js:948:11)
---------------------------------------------
at exports.execFile (child_process.js:691:9)
at exports.exec (child_process.js:578:18)
at cli.addHook.post (/Users/danwilson/Library/Application Support/Titanium/mobilesdk/osx/3.1.1.v20130523143543/iphone/cli/hooks/package.js:111:6)
at /usr/local/lib/node_modules/titanium/lib/cli.js:110:12
at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:486:21
at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:185:13
at iterate (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:108:13)
at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:119:25
http://developer.appcelerator.com/question/152848/node-error-when-packaging-for-ad-hoc
Hello Dan, Were you able to correct this issue? Is only occurring on this one app or does it happen for all apps? Would you mind testing this for us on a test app to determine if this is a unique problem with your app or a problem with something else? Thanks, Carter
I have just confirmed that it is only this app that is having this problems. Is there anything from this error that you can point me in the right direction to solve this? Will the entire trace level log help? Thanks, -=Dan
Hi Dan, Hmm, that is quite peculiar. I am going to move this to Ti-Mobile to see if the engineers have any insight into this and they can then ask for any more pertinent information that they need. I believe Mauro meant to do this but never got around to it. Sorry for the wait and thanks for your patience. Would you also mind providing the full trace log as an attachment? Thanks again, Carter
I'm unable to add an attachment. I was removed from being the reporter, so I don't have permissions.
Sorry about that, would you mind sending them to me at clathrop@appcelerator.com? I will attach them myself. Thanks, Carter
Is there any new status on this bug? I'm unable to deploy new versions of my app because of this bug. Can someone point me in the right direction to help in troubleshooting or investigating?
Hello Dan, I have updated the ticket to blocker status, and I will be sure to send an email to engineering to see when they can get to this. Thanks for your patience. Best, Carter
Hi Dan, The issue looks similar to what's reported in TIMOB-13822. A couple of questions: 1. Do you have symbol links defined in the specific project? 2. Could you try updating to the latest 3.1.1.GA of SDK and 3.1.1 of CLI to see if it helps? If it's indeed a duplicate of TIMOB-13822, the problem should be addressed in the latest update. Thanks.
Michael, 1. No. I don't have any symlinks in this project. I do however move files around through a script that also purges the build directory. This project is used to build several very similar apps. Each has different graphical assets as well as some slight differences in the configuration (tiapp.xml), including the name of the app, etc. No sure if that is related or not. 2. I've already tried the new 3.1.1.GA with the same exact result. Please let me know what other information might be helpful for you. Thanks
Hi Dan, could you try the following? 1. In Studio, run Help > Studio > Clear Log File; 2. Open Preferences > Studio > Troubleshooting page, change Debug Level to All, and make the entry "com.aptana.core/debug/shell" checked; 2. Restart Studio and package for ad hoc to re-create the problem; 3. Run Help > Studio > View Log File; 4. Scroll to the end of the file and look for two lines, one "Working directory" and one right before saying "Process: "; from the command line, cd into the working directory and then copy-and-paste the full command after "Process: ". This should produce the same error but with more debug output. Attaching it here could help. Thanks.
(removed logs in comment and attached to ticket)
Michael, Just realized that the comment didn't accept the entire log. I don't have permissions to attach anything either. How you would like me to get the entire log to you?
Dan, Go ahead and send me the log file at clathrop@appcelerator.com. I will attach myself. Thanks for providing the info :) Regards, Carter
The CLI officially supports node v0.8.22.
Dustin, I believe I was at 0.8.22 when I first encountered this error and I upgraded to hopefully resolve it. I'm running v0.10.8. Should I downgrade?
I just downgraded to 0.8.22 and got the same exact error. I'll email Carter the new log file.
Thanks for the clarification.
Is there anything I can do to speed up work on this bug? This is really hindering my Ad Hoc testing. I just released a new version of my app with a significant bug because I wasn't able to send this out to my usual beta testers. I'd like to help out in any way I can.
@Dan Wilson, what are you specifying as the output directory? Does the path already exist? Are the permissions correct?
@Chris, my "Specify Location" indicates "/tmp" as the output directory. And yes, permissions are correct.
Pull request: https://github.com/appcelerator/node-appc/pull/51
To test, from the node-appc directory, run:
./forge test fsTested with [~cbarber], CLI 3.2.0-alpha, and node 0.10.13 closing.