Tag Archives: appcelerator

MacBook Air: How to Update Node.js Tips, Tricks and Tutorials 14 MAR 2017

Ugh. I needed to fire up the loan MacBook Air to do an iOS compile of my recently completed Appcelerator app. Naturally, I started off on the wrong foot by not recalling the MacBook’s password (luckily I found that I had mailed it to myself some time ago, so I did eventually get in). Then Appcelerator moaned that it needed an update, which failed because it needed a newer version of Node.js to be installed.

So off to Google I once more marched, the result of which I am now jotting down here as a future reminder: How to Update Node.js on a MacBook Air.

As it turns out, updating node.js is a pretty quick affair: First, fire up a terminal (which again I needed to march over to Google in order to learn how to do), and then run the following commands:

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

Note the use of sudo to run these commands. Essentially we are first force clearing the npm cache, then installing and upgrading node to the latest version.

Related Link: MacBook Air | Node.js

Appcelerator and Android Bug: Invalid “–device-id” value “XYZ” Tips, Tricks and Tutorials 10 JAN 2017

Working in Appcelerator Studio, I was trying to compile and run the Android app that I’m developing on a Lenovo A7600-H tablet hooked up to my Windows 10 laptop via USB.

Developer Options’ USB debugging checkbox was turned on (remember, if it isn’t already showing – and it shouldn’t be – you can open up Developer Options as a Settings menu option by clicking 7 times on the Build Number item tucked away behind the About Phone/Tablet settings menu option), and the USB computer connection was set to MTP media device/files option.

However, the run process kept aborting with the following error message: Invalid “–device-id” value “XYZ” where XYZ was a label associated with the hooked up device.

As it turns out, the problem is actually one of authentication or rather authorization – essentially the device doesn’t trust the PC that it is currently plugged into. So to resolve, I turned off the “USB debugging” setting, clicked on the “Revoke USB debugging authorizations” menu option below that, and then turned USB debugging back on. The tablet asked me if it was okay to allow the computer connection, and after confirming on the device and then returning to Appcelerator Studio to compile and run, the Invalid –device-id issue was gone.

So, worth jotting down for future reference then.

Solved: Appcelerator Build Error: “EPERM, operation not permitted” Tips, Tricks and Tutorials 27 MAY 2016

Sigh, I really do not enjoy building Apps. Anyway, the latest roadblock to hit me after being asked to quickly unlock the previously locked orientation on one of our Appcelerator-built mobile apps, required me to boot up Appcelerator Studio, make the code tweak and then run an Android build – only to be stopped in my tracks by a glaring compiler error that read:

“EPERM, operation not permitted”.

After a bit of tearing my hair out, Googling, and just general despair, the solution to this problem revealed itself… the damn antivirus was interfering here!

So a quick trip to the Avast! antivirus control panel in order to turn off all the active monitoring, a restart of the build process, and voilà… my app change was done.

So just jotting this down here in case I run into this issue again. (Also, don’t forget to turn you Antivirus back on again when you are done!)

Avast Active Protection settings window above appcelerator studio

Related Link: Appcelerator | Avast!