Appcelerator studio won't start (no loading screen) -


i'm trying run appcelerator studio in desktop. amd athlon ii x4 640 3.00 ghz ram 4gb 64bit win 8.1 120gb ssd samsung 840 evo

so, in laptop i7 8gb ram etc.. run smoothly. when i'm trying start studio doesn't respond, not in task manager.
i'm using cli , work fine.. can't find log file. appc studio keep in workspace 1 have no create yet because can't open studio. run command appc platform start studio cmd nothing happens , message appears:

{"success":false,"description":"platform command usage: appcelerator platform <api> <method/arguments>"}

i uninstalled avast , check first blocked programs, nothing..

i disabled windows firewall too.

reinstalled studio many times using different versions of node. nothing.
, of course tried come in contact appc team can't....

i'm thinking 4gb ram limitation; if blocks program starting.

i try open program logged in , logout cli.

any idea? 1 same problem?
not stuck in loading screen studio try verify account , communicate server.
studio won't start @ all.
i'm sorry bad english.

sorry issue.

first - assuming running windows (linux no longer supported)

the cli command using appc platform not launch studio. used accessing platform apis , requires provide api use.

to launch studio cmd line on windows need cd appcelerator studio directory , run associated program. when installing studio, put icon on desktop, far easiest way start up.

your right ram limitation. while you'll find studio "run" extremely slow, once start using android / windows emulators etc. windows takes 1-2gb of ram on own, leaving little development tools.

our recommended configuration windows machines is: * windows 8.1 or higher * 16gb of ram

i think faster proc well.

we in process of updating our documentation on pre-reqs' bit misleading. while 4gb of ram suitable, talking 4gb of 'free memory' on top of else have running, not 4gb of total system memory.


Comments

Popular posts from this blog

javascript - jQuery: Add class depending on URL in the best way -

caching - How to check if a url path exists in the service worker cache -

Redirect to a HTTPS version using .htaccess -