[TIMOB-17509] Android SDK not loading due to EPERM failure

GitHub Issue	n/a
Type	Bug
Priority	High
Status	Closed
Resolution	Fixed
Resolution Date	2015-08-26T21:43:18.000+0000
Affected Version/s	n/a
Fix Version/s	Release 5.0.0
Components	Android, CLI
Labels	n/a
Reporter	Eduardo Gomez
Assignee	Feon Sua Xin Miao
Created	2014-07-18T21:55:45.000+0000
Updated	2017-03-16T22:49:04.000+0000

Description

Issue description

After upgrading Appcelerator Studio the Android SDK isn't properly detected. This prevents developers to deploy applications. Forgive me if this is a dupe of another ticket.

Steps to reproduce

On Appcelerator Dashboard tab hit "Android SDK" to complete setup process (AppcStudio_InstallingAndroid_1.jpg).

Use Platform Configurations dialog to install required SDKs (2.3.3 is checked. AppcStudio_InstallingAndroid_2.jpg).

Upon completion everything seems Ok. AppcStudio_InstallingAndroid_3.jpg

A popup over windows remains static saying API 10 must be installed and suddenly Android isn't fully loaded (AppcStudio_InstallingAndroid_4.jpg).

Attachments

File	Date	Size
AppcStudio_InstallingAndroid_1.jpg	2014-07-18T21:55:45.000+0000	245282
AppcStudio_InstallingAndroid_2.jpg	2014-07-18T21:55:45.000+0000	195877
AppcStudio_InstallingAndroid_3.jpg	2014-07-18T21:55:45.000+0000	172762
AppcStudio_InstallingAndroid_4.jpg	2014-07-18T21:55:45.000+0000	189199
AppcStudioData.txt	2014-07-18T21:55:45.000+0000	281281
MacOSX_1.png	2014-07-18T21:59:03.000+0000	93147
MacOSX_2.png	2014-07-18T21:59:03.000+0000	125295

Comments

Ingo Muschenetz 2014-07-18

A few questions: 1) What is the output of "ti info"? 2) There are a number of suspicious networking errors. I don't believe the Android SDK downloaded fully.

   npm ERR! SyntaxError: Unexpected token <
   npm ERR! 
   npm ERR! <?xml version="1.0" encoding="utf-8"?>
   npm ERR! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   npm ERR!  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   npm ERR! <html>
   npm ERR!   <head>
   npm ERR!     <title>200 OK</title>
   npm ERR!   </head>
   npm ERR!   <body>
   npm ERR!     <h1>Error 200 OK</h1>
   npm ERR!     <p>OK</p>
   npm ERR!     <h3>Guru Meditation:</h3>
   npm ERR!     <p>XID: 724797158</p>
   npm ERR!     <hr>
   npm ERR!     <p>Varnish cache server</p>
   npm ERR!   </body>
   npm ERR! </html>
   npm ERR! 
   npm ERR!     at Object.parse (native)
   npm ERR!     at RegClient.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:241:23)
   npm ERR!     at Request.self.callback (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:123:22)
   npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
   npm ERR!     at Request.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:893:14)
   npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
   npm ERR!     at IncomingMessage.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:844:12)
   npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
   npm ERR!     at _stream_readable.js:920:16
   npm ERR!     at process._tickCallback (node.js:415:13)
   npm ERR! If you need help, you may report this *entire* log,
   npm ERR! including the npm and node versions, at:
   npm ERR!     <http://github.com/isaacs/npm/issues>;

Are they running as Admin?

   npm ERR! System Windows_NT 6.1.7600
   npm ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "titanium" "--color" "false"
   npm ERR! cwd C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Appcelerator
   npm ERR! node -v v0.10.25
   npm ERR! npm -v 1.3.24
   npm ERR! path C:\Users\josedejesus\AppData\Roaming\npm\node_modules\titanium\node_modules\moment\lang\el.js
   npm ERR! fstream_path C:\Users\josedejesus\AppData\Roaming\npm\node_modules\titanium\node_modules\moment\lang\el.js
   npm ERR! fstream_type File
   npm ERR! fstream_class FileWriter
   npm ERR! code ENOENT
   npm ERR! errno 34
   npm ERR! fstream_stack C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
   npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
   npm ERR! Error: EPERM, open 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Appcelerator\npm-debug.log'
   npm ERR!  { [Error: EPERM, open 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Appcelerator\npm-debug.log']
   npm ERR!   errno: 50,
   npm ERR!   code: 'EPERM',
   npm ERR!   path: 'C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Appcelerator\\npm-debug.log' }
   npm ERR! 
   npm ERR! Please try running this command again as root/Administrator.

   !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2014-07-08 13:24:34.652
   !MESSAGE Connection to http://download.appcelerator.com/appcelerator/appc-studio/standalone/update/stable/p2.index failed on download.appcelerator.com. Retry attempt 0 started
   !STACK 0
   java.net.UnknownHostException: download.appcelerator.com

   !ENTRY com.aptana.core.epl 2 0 2014-07-15 21:58:12.458
   !MESSAGE Connection to https://dl-ssl.google.com/android/repository/sys-img/android/sysimg_x86-16_r01.zip failed on dl-ssl.google.com. Retry attempt 0 started
   !STACK 0
   java.net.UnknownHostException: dl-ssl.google.com

Eduardo Gomez 2014-07-20

1) ti info output: https://gist.github.com/egomez99/ad40831dff7a7491b2dc 2) It turns out the Android installation was incomplete due Firewall restrictions. Logs from SDK manager revealed the following (despite the fact Studio shows on the configuration details "The Android SDK is installed correctly!"): Failed to fetch URL https://dl-ssl.google.com/android/repository/sys-img/x86/addon-x86.xml/addon.xml, reason: IO Unknown Host dl-ssl.google.com 3) About their account it does seem to have administrative priviledges (since is listed as Administrator user). Should they just give themselves permissions to that particular folder? In regards to the issue reported on Mac OSX, I will attach logs as soon as I have them. Thanks.
Ingo Muschenetz 2014-07-21

[~egomez] #1 is this issue, supposedly solved in 3.2.3: TIMOB-16074. [~cbarber] they appear to be continuing to get it in 3.3.0.GA. Thoughts?
Chris Barber 2014-07-22

[~egomez] Regarding the EPERM issue from the gist, this most certainly is a permission issue. They will need to go into the security settings for the "Archivos comunes" folder and fix the permissions.
Ingo Muschenetz 2014-07-22

[~cbarber] I would still like us to fail more gracefully in this circumstance.
Chris Barber 2014-07-22

[~ingo] There are currently 81 places across the CLI, SDK, and node-appc where we read a directory and that does NOT include 3rd party dependencies. That's a lot of places to add try/catches to.
Ingo Muschenetz 2014-07-22

Sure, but I can't imagine that all of them are as likely to have permission issues. There must be some likely culprits (i.e. ones that have purposely failed before and have reports) that we could start with.
Chris Barber 2014-07-22

[~ingo] Sounds like we need a new ticket.
Ingo Muschenetz 2014-08-18

[~pinnamuri] yes, please move.
Feon Sua Xin Miao 2015-07-08

PR: https://github.com/appcelerator/titanium_mobile/pull/6963 On Windows, to test: 1. Set permissions on C:\Program Files\Common Files to Administrator only 2. Run ti info 3. The process shouldn't crash with Error: EPERM
Praveen Innamuri 2015-08-26

PR merged to master.
Lee Morris 2017-03-16

Closing ticket as fixed.

JSON Source