id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
711 |
TISTUD-2405
|
10/06/2012 00:46:34
|
Node.ACS: Run > Local Node.ACS Server fails, unable to locate package.json
|
If a titanium project with node.acs service enabled is run as local server, it fails with error: {code} [ERROR] received on caught exception = Error: ENOENT, no such file or directory '/Users/dhyde/Desktop/TISTUD-NIGHTLY/titanium_studio_workspace/MyProject/package.json' [ERROR] Error: ENOENT, no such file or directory '/Users/dhyde/Desktop/TISTUD-NIGHTLY/titanium_studio_workspace/MyProject/package.json' at Object.fs.openSync [as openSync] (fs.js:338:18) at Object.fs.readFileSync [as readFileSync] (fs.js:182:15) at main (/usr/local/lib/node_modules/acs/lib/nettle.js:219:39) at Object.<anonymous> (/usr/local/lib/node_modules/acs/lib/nettle.js:302:1) at Module.Module._compile [as _compile] (module.js:449:26) at Object.Module._extensions..js [as .js] (module.js:467:10) at Module.Module.load [as load] (module.js:356:32) at Function.Module._load [as _load] (module.js:312:12) at Module.Module.require [as require] (module.js:362:17) at require (module.js:378:17) {code} Note, when project was created, error was generated: TISTUD-2397 Steps to Reproduce: 1. Create titanium project. 2. Enable node.acs service, project right-click > new > node.acs service. 3. Select Run > Local Node.ACS Server. Actual Result: Fail. Expected Result: Success, proper error message, or a way of preventing the menu item from working if it is known that it will fail when run.
| 5 |
712 |
TISTUD-2410
|
10/06/2012 12:00:23
|
Titanium Studio- Wrong project launching information in the form of " launching ... "is mentioned at the bottom of Titanium Studio taskbar.
|
Steps to reproduce: 1)Open Titanium Studio. 2)Open/Create a Titanium Mobile project -> Android device. 3)Click on 'debug' icon-> android device. 4)Wait till process completes. Exit from debug perspective. 5)After sometime ...notice that at the bottom ( Ti studio task-bar launching previous project is displayed) screenshot attached. Actual result: Launching ...last run project gives wrong notion to the user.
| 5 |
713 |
TISTUD-2421
|
10/08/2012 22:57:32
|
Node.ACS Method: new method dialog refers to method as 'service' in two locations
|
In the node.acs new method dialog, the default text is 'service_name' when it should be 'method_name', and instructions say 'enter a name for your new service' when it should be 'enter a name for your new method'. Steps to Reproduce: 1. Create a Titanium Project. 2. Right click project > New > Node.ACS Service (and enter unique name). 3. Right click project > New > Node.ACS Method. Actual Result: New Method dialog appears as in screenshot with two semantic errors. Expected Result: Instructions and example text should refer to 'methods', not 'services'.
| 3 |
714 |
TISTUD-2422
|
10/08/2012 23:25:32
|
Node.ACS Method: 'new method' overwrites dirty js file without prompt
|
If a node.acs project has a dirty main js file, and New > Node.ACS Method is called, there is no save prompt and any changes are overwritten and auto-saved. Steps to Reproduce: 1. Create Node.ACS Project. 2. Edit main <project_name>.js file and add a few lines of code without saving. 3. Right click on project > New > Node.ACS Method to create method (set name, press ok). Actual Result: New method is added to js file without save prompt, previous user edits are overwritten. Expected Result: Save prompt, then add method to js file (or cancel).
| 5 |
715 |
TISTUD-2423
|
10/08/2012 23:36:24
|
Node.ACS: failure to create new service results in empty project files created
|
If a node.acs service fails to create, a titanium project still contains empty node.acs service folders when there should be none. Steps to Reproduce: The goal of these steps is to create a service in a project that already exists, the bug may occur after step 2 if a service was already created at some point in time using the current my.appcelerator.com login. 1. Create Titanium Project. 2. Right click project > New > Node.ACS Service (name service the default name). 3. Delete project, repeat steps 1-2. Actual Result: Project fails to create, but project/acs/service exists. Expected Result: Project fails to create, and no evidence of any new folders should exist.
| 3 |
716 |
TISTUD-2424
|
10/09/2012 01:23:31
|
Move splash progress bar to the right hand side
|
With the new splash screen layout, there is blank empty space to the right hand side of the splash screen when logging in. We should move the progress bar to that area to make it more equally spaced
| 5 |
717 |
TISTUD-2425
|
10/09/2012 01:27:37
|
Preferences: Default Android SDK Google API list missing version numbers
|
Android SDK preferences no longer list google api version number, cannot select screen type nor deploy to emulator. Steps to Reproduce: 1. Open Studio. 2. View preferences > titanium studio > titanium > default android sdk. Actual Result: google apis have no version numbers, cannot build to emulator or select screen type Expected Result: version numbers, can build to emulator, can select screen type Related Build Error: {code} This launch uses a V8 Android Runtime, which require Android 2.2 SDK and above. Please edit your launch configuration to select a compatible SDK. {code}
| 5 |
718 |
TISTUD-2426
|
10/09/2012 01:39:43
|
CLI Updates: change CLI update stream name from titanium to Titanium CLI
|
Currently the CLI update release notes lists the CLI stream as 'titanium'. Suggest naming it Titanium CLI or something the same quality as the sdk updates, including standard documentation. See screenshots. Steps to Reproduce: 1. Clean install titanium studio 3.0. 2. Check for Titanium updates. Actual Result: CLI is 'titanium', documentation is minimal. Expected Result: CLI release notes should be same quality as sdk release notes. For example the stream could be called Titanium CLI, and there could be more documentation.
| 3 |
719 |
TISTUD-2427
|
10/09/2012 05:29:26
|
Blank input in Help > 'Install specific titanium SDK from URL' should display the right message
|
This is not a regression bug . I have recreated this bug with Titanium 2.1.2 and 2.1.3 also. Steps to reproduce: 1)Open Titanium Studio. 2)Help >'Install specific titanium SDK ' > > 'install from URL'. 3)Without entering anything in the text-box, press 'finish tab. Actual result: 'Your Titanium SDKs have been updated' pop up window is appearing. Expected Result: Titanium Studio should display right message.
| 3 |
720 |
TISTUD-2428
|
10/09/2012 05:35:19
|
Set the "platform" property as 'optional' at the plugin element in tiapp XSD
|
Got a request from CLI team to add two optional attributes to the plugin element.
| 3 |
721 |
TISTUD-2430
|
10/09/2012 11:00:42
|
Studio: 'CSSCompiler' object has no attribute 'code' error appears while distribution of app using "Distribute - Apple iTunes Store" option.
|
This is a Regression issue. Steps To Reproduce: 1. Create a default app. 2. Distribute app using "Distribute - Apple iTunes Store" option. Actual: Console throws error "'CSSCompiler' object has no attribute 'code'" Expected: No error must appear.
| 8 |
722 |
TISTUD-2431
|
10/09/2012 11:06:04
|
Titanium Studio: Unable to package mobile web project with latest studio using 2.1.3 GA or previous SDKs.
|
This is a regression bug. 1.Launch Titanium Studio. 2.Create > Titanium Project > Titanium Classic > Default > Next 3.Select Deployment target as > Mobile Web. 4.Select finish. 5.Select 'Publish' that project as > 'package - Mobile web.' 6.Select option : Copy mobile web app to a local file system. and browse to any desired folder path. 7.Make sure you have selected SDK as 2.1.3 GA or previous SDKs. P.S : Please refer screenshot as it saying 'please check error log file. but there is no data in log file.
| 13 |
723 |
TISTUD-2434
|
10/09/2012 12:25:29
|
Titanium Studio: Make the alert box which appears at the bottom in yellow colour non-resizable
|
This is a regression bug. Steps to reproduce: 1.Launch Titanium Studio. 2.Go to Dashboard > Configure > Android > Update Android SDK. 3. Wait till a confirmation pop up appears . 4. scroll your mouse pointer on that popup, observe that you can drag its size and change it as you wish. Actual Result: User can re-size the alert window (appearing in yellow colour at the right -hand-side -bottom of Titanium studio). Expected Result: Alert wind can't be altered. P.S. It happens with all sort of alert messages which are appearing in yellow colour at the right -hand-side -bottom of Titanium studio.
| 0 |
724 |
TISTUD-2435
|
10/09/2012 12:43:47
|
Show a better error message when swapping radio button in "Install specificTitanium SDKs" window
|
This is not a regression bug . I have recreated this bug with Titanium 2.1.2 and 2.1.3 also. Steps to reproduce: 1)Open Titanium Studio. 2)Help >'Install specific titanium SDK ' > 'install from URL'. 3)Click on radio button - "Install from Update Stream" 4)Again click on radio button - 'install from URL'. 5)Observe the error. (screenshot attached) Actual result: Without entering any text , "Invalid URL" is displayed. Expected Result: "Invalid URL" error should appear only after entering wrong text.
| 3 |
725 |
TISTUD-2436
|
10/09/2012 16:04:52
|
"Project description file is out of sync" when creating an Alloy project
|
Reproduce: * Create a new Alloy project in studio (any alloy template) * fill in the appropriate values in the project creation fields * click "finish" I am repeatedly greeted by the error in this screenshot ("hwg" was the project name i used): https://img.skitch.com/20121009-g6um8pnc6wyeh5ex9riee32wdk.jpg
| 5 |
726 |
TISTUD-2439
|
10/09/2012 18:01:50
|
Titanium Studio 3.0 RC crashes on launch
|
RC studio crashes on install. Steps to Reproduce: 1. Either run studio 3.0 from installer or update from 2.1.2. Actual Result: Crash. Expected Result: Run.
| 5 |
727 |
TISTUD-2441
|
10/09/2012 18:47:28
|
CLI Updates: add CLI update stream release notes docs
|
Currently the CLI update release notes lists the CLI stream as 'titanium'. Suggest naming it Titanium CLI or something the same quality as the sdk updates, including standard documentation. See screenshots. Steps to Reproduce: 1. Clean install titanium studio 3.0. 2. Check for Titanium updates. Actual Result: CLI is 'titanium', documentation is minimal. Expected Result: CLI release notes should be same quality as sdk release notes. For example the stream could be called Titanium CLI, and there could be more documentation.
| 5 |
728 |
TISTUD-2442
|
10/09/2012 19:27:16
|
3.0.0 DMG installer has small background image
|
The dmg installer background image is not displaying properly. See screenshot
| 2 |
729 |
TISTUD-2443
|
10/09/2012 19:39:09
|
iOS debug on device does not handle build errors
|
When performing the debug on iOS device, the wizard displays the status of the debug operation. If the build fails (certificate/provisioning mismatch, syntax errors), the wizard seems to continue to wait for the build to finish. The wizard should display an error if the build fails
| 8 |
730 |
TISTUD-2446
|
10/09/2012 21:26:55
|
ACS fails to install if Studio is installed in a location with a space in the filepath
|
I started studio, and it tried to install acs with an error in the terminal. See screenshot. It seems the path needs to be in quotes, since the default install directory for Studio is /Applications/Titanium Studio
| 3 |
731 |
TISTUD-2447
|
10/09/2012 21:30:25
|
Consolidate all the 'Do not show this again' messages preferences
|
The Studio now has a 'Clear' option in its main preference page. The user can reset all the 'do not show again' hidden messages and have them re-appear when needed. We should consolidate all the areas where we have a dedicated preference for a specific message, and use this preference key to store and check for the property. (for example, the NodeACS deploy menu shows one of those messages) See DialogUtils#openIgnoreMessageDialogInformation
| 8 |
732 |
TISTUD-2452
|
10/09/2012 23:10:53
|
Open "app/views/index.xml" instead of "Resources/app.js" by default with Alloy apps
|
It would be nice if when a developer created a new Alloy app through Studio that it would open the **app/views/index.xml** instead of the **Resource/app.js**. The app.js should not even be modified as it is overwritten on every build.
| 5 |
733 |
TISTUD-2453
|
10/09/2012 23:19:19
|
Fail to install Alloy
|
Alloy is not being installed properly when the Studio is launched. We are getting error code 128 on one of the git clones that the installation performs. Attaching the install log and the npm error log.
| 8 |
734 |
TISTUD-2454
|
10/10/2012 01:12:42
|
Disable Publish > View Node.ACS Service menu when all the versions of the app are unpublished
|
After un-publishing the service, the action is still enabled and opens a "503 Service Unavailable" page. It should be disabled.
| 3 |
735 |
TISTUD-2457
|
10/10/2012 01:21:05
|
Deploying to android device does not work in Rhino
|
Running on device does not work in android. Steps to reproduce: 1. Open a titanium mobile project in studio with android support 2. Select the rhino runtime 3. Try to install on an android device: Run the 'Android Device' from the run submenu. Expected Behavior: The app should install onto device Actual Behavior: An error dialog pops up with the message "Only V8 debugging is supported"
| 5 |
736 |
TISTUD-2460
|
10/10/2012 02:33:31
|
A CLI 'clean' command failure
|
When cleaning a project, we fallback to the legacy 'clean' implementation instead of utilizing the CLI 'clean' command, which fails with this error: {code} !ENTRY com.aptana.core 1 0 2012-10-09 18:24:30.952 !MESSAGE (Build 3.0.0.201210090117) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/titanium" "--no-banner" "--no-colors" "--no-prompt" "clean" "--project-dir" "/Users/shalom/Documents/Titanium_Studio_Workspace/TestProject" Working directory: /Users/shalom/Documents/Titanium_Studio_Workspace/TestProject Environment: {APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-WbQTZ6/Render, Apple_Ubiquity_Message=/tmp/launch-fvLLoE/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, DISPLAY=/tmp/launch-OVTsGw/org.x:0, HOME=/Users/shalom, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=shalom, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin, PWD=/Users/shalom/Documents/Titanium_Studio_Workspace/TestProject, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-v7O0NA/Listeners, TMPDIR=/var/folders/zj/8xjj6knx6wn1qvljm8sn879m0000gq/T/, USER=shalom, __CF_USER_TEXT_ENCODING=0x1F7:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI} !ENTRY com.appcelerator.titanium.mobile 4 0 2012-10-09 18:24:31.718 !MESSAGE (Build 3.0.0.201210090117) [ERROR] Error cleaning the project. A manual clean will be performed. {code}
| 3 |
737 |
TISTUD-2465
|
10/10/2012 23:49:20
|
Titanium CLI is never used in Studio 3.0
|
We're passing in titanium.bypassNewCLI=true by accident in the TitaniumStudio.ini file.
| 1 |
738 |
TISTUD-2476
|
10/11/2012 16:49:56
|
preview.appcelerator.com: linux downloads have broken links
|
preview.appcelerator.com linux installer downloads have broken links. http://preview.appcelerator.com/appcelerator/studio/standalone/install/rc/titanium.linux.gtk.x86.zip Not Found The requested URL /appcelerator/studio/standalone/install/rc/titanium.linux.gtk.x86.zip was not found on this server. http://preview.appcelerator.com/appcelerator/studio/standalone/install/rc/titanium.linux.gtk.x86_64.zip Not Found The requested URL /appcelerator/studio/standalone/install/rc/titanium.linux.gtk.x86_64.zip was not found on this server.
| 5 |
739 |
TISTUD-2478
|
10/11/2012 18:59:01
|
Add Alloy and ACS to our "Check for Titanium Updates" process
|
Currently we're checking Titanium CLI for update at startup, but not for Alloy and Node.ACS, so user would have to manually run "sudo npm install ..." from command line to update. We should add them to the check-for-update process as well.
| 8 |
740 |
TISTUD-2479
|
10/11/2012 20:05:44
|
Reduce on device debug messages
|
When comparing the log messages between on device debugging and emulator debugging, there is a large amount of log messages. We need to investigate if we should filter out certain messages and reduce the clutter
| 0 |
741 |
TISTUD-2485
|
10/11/2012 22:07:36
|
Help: add mechanism to display cli alloy and node acs version installed from studio
|
Add ability for user to view installed CLI version from studio. Suggest using Help > Titanium Studio > Run Diagnostics. Currently the user cannot view the cli version in studio, must be checked from command line using: npm view titanium version
| 5 |
742 |
TISTUD-2487
|
10/11/2012 23:05:56
|
CLI Updates: show error if cli update fails
|
Help > Check for Titanium Updates always shows need for a CLI update even it was already installed (the install failed). Steps to Reproduce: 1. Run Help > Check for Titanium Updates and install CLI. At this point there is a failure due to related issue, will go away in future. Actual Result: No error messages. Expected Result: Should have error message.
| 5 |
743 |
TISTUD-2490
|
10/12/2012 00:22:17
|
Saving tiapp.xml in KitchenSink freezes studio, must force quit
|
Right after importing Samples > Kitchen Sink, if you edit the tiapp.xml by changing the sdk from 2.1.1 to 3.0.0.X and save, studio will freeze and must be force-closed. This does not occur in Studio 2.1.2, this is a regression. Steps to Reproduce: 1. Import KitchenSink from the Samples view. 2. As soon as it imports, open tiapp.xml and set the sdk version to the latest 3.0.0.X and save the changes. Actual Result: Studio freezes. Expected Result: Studio continues to function.
| 8 |
744 |
TISTUD-2492
|
10/12/2012 09:44:20
|
Error in logs when logged off and logged back in studio.
|
This is not a Regression issue. It occurred in studio 2.1.2 as well Steps To Reproduce: 1. On a clean machine install the Titanium Studio 3.0 for the first time. 2. Use default options to install the Studio 3.0 windows installer. 3. Open Studio and login 4. Logout User from bottom right. 5. Restart Studio by login into appc account. Actual: Observe Errors in Log."An error occurred while executing a database query" followed by ShutdownException appears. Expected: No error in logs must appear.
| 2 |
745 |
TISTUD-2494
|
10/12/2012 22:50:46
|
During clean install of Studio, user is bombarded with a number of errors for Node.ACS, Alloy and NodeJS
|
During a clean install, I got the following errors/windows for Studio (see screenshot). The errors complain about "NPM not installed", which means nothing to the new user, and there's a prompt for install NodeJS (which would install NPM). What should happen is the Alloy and Node.ACS jobs should check for NPM/NodeJS, if it's not installed, it should be able to register as listeners to a NodeJS notifier. When the NodeJS install is complete, it can notify the listening jobs to restart their installations
| 8 |
746 |
TISTUD-2495
|
10/12/2012 22:53:19
|
NodeJS installation prompt should provide more context
|
On a clean install of Studio, the user is prompted to install NodeJS. For a majority of Studio users, NodeJS is unfamiliar to them and its association with Studio. We should provide more context on why we're installing NodeJS - It's a requirement for CLI/Studio
| 3 |
747 |
TISTUD-2496
|
10/12/2012 23:00:24
|
Dashboard Modules: canceling module install during download still shows as module installed
|
In the dashboard > explore > my modules section, if you click 'install' on a module, then immediately 'cancel' the operation, the module shows as Installed. Steps to Reproduce: 1. Load dashboard in studio. 2. Click explore > my modules (see screenshot). 3. Click install, then immediately click cancel while the module is downloading/fetching. Actual Result: Module displays as installed when it isn't. There is no installed module folder in the titanium folder. Expected Result: Action cancels, module shows as not installed in dashboard UI (i.e., displays 'Install').
| 8 |
748 |
TISTUD-2497
|
10/12/2012 23:25:32
|
Dashboard Modules: no success dialog when module installation complete
|
In the dashboard > explore > my modules section, if you click 'install' on a module, then wait for it to install, there is no success dialog. Steps to Reproduce: 1. Load dashboard in studio. 2. Click explore > my modules, and install the jira module (or another free module). Actual Result: No success dialog. Expected Result: Success dialog.
| 5 |
749 |
TISTUD-2498
|
10/12/2012 23:29:25
|
Dashboard Modules: clicking installed installs module again
|
In the dashboard > explore > my modules section, if you click 'installed' on a module that is already installed, it installs again. Steps to Reproduce: 1. Load dashboard in studio. 2. Click explore > my modules, and click 'Installed' on a module that is already installed. Actual Result: Installs again. Expected Result: It shouldn't install again.
| 5 |
750 |
TISTUD-2499
|
10/12/2012 23:33:58
|
Dashboard Modules: module updates don't show up
|
In the dashboard > explore > my modules > updates section, there are no updates available. Steps to Reproduce: 1. Load dashboard in studio. 2. Click explore > my modules, and click 'Install' to install a module. 3. Edit the module folder to lower the version. i.e., change /Users/dhyde/Library/Application Support/Titanium/modules/iphone/ti.jira/1.2.1 to /Users/dhyde/Library/Application Support/Titanium/modules/iphone/ti.jira/1.2.0 and change the manifest file to lower the version as well 4. Click the updates tab in dashboard my modules. Actual Result: No updates available. Expected Result: The edited module should show as needing an update.
| 5 |
751 |
TISTUD-2500
|
10/12/2012 23:38:49
|
Dashboard Modules: module shows as not installed when it is installed
|
In the dashboard > explore > my modules section, modules that are installed are listed as not installed (i.e., they prompt user to 'Install'). Steps to Reproduce: 1. Load dashboard in studio. 2. Click explore > my modules, and install a module. 3. Reload the dashboard and view my modules. Actual Result: Module shows as not installed (says 'Install'). Expected Result: Module should be 'Installed'.
| 3 |
752 |
TISTUD-2504
|
10/13/2012 12:08:54
|
Installer: "Uninstalling path" while installation does not appear on Windows 7
|
This is a Regression issue. Works fine in 2.1.2 Studio. Steps To Reproduce: 1. Install Titanium Studio 3.0 installer 2. Try uninstalling same from Control Panel Actual: Observe that while uninstalling "Uninstalling path" appears blank. [Refer Screenshot] Expected: path must appear correctly.
| 5 |
753 |
TISTUD-2507
|
10/13/2012 19:39:37
|
Titanium Updates: user keeps getting prompted for updates even after they are installed
|
If the user updates (Help > Titanium Updates) CLI, Alloy, and ACS, none of the updates are recognized as being installed, and the user is still prompted for updates, even after studio restart. Steps to Reproduce: 1. Help > Check for Titanium Updates and take all updates (CLI, Alloy, ACS). 2. Check again. Actual Result: Updates are still available, though they were already installed. Expected Result: No updates available, they were already installed.
| 8 |
754 |
TISTUD-2509
|
10/13/2012 22:11:36
|
Find Bar: select-all with full screen of text maximizes find bar height, blocks editor
|
In a clean workspace, if you select-all text in a file that contains more lines than the screen height, and invoke the find bar, the find bar height will maximize and block all other content in the editor. This is not a regression. Note that eclipse uses a pop-up for find. Steps to Reproduce: 1. Clean workspace (delete metadata) for reliable reproduction, or proceed. 2. Create a new titanium project (for example). 3. Open app.js and select all text (command + a on osx). 4. Invoke the find bar (command + f on osx). Actual Result: The find bar height takes up the full editor screen height, blocks the editor. Expected Result: A limit on the Find Bar height. Suggest using the same height as if no text is selected, as the find bar contains a vertical scroll control.
| 5 |
755 |
TISTUD-2512
|
10/14/2012 17:38:36
|
Alloy: Updates: add Alloy update stream release notes docs
|
Include standard documentation for alloy release notes as with the sdk. See screenshots. Steps to Reproduce: 1. Uninstall alloy or have an old version of alloy. 2. Check for Titanium updates. Actual Result: Documentation is minimal. Expected Result: alloy release notes should be same quality as sdk release notes.
| 8 |
756 |
TISTUD-2513
|
10/14/2012 17:41:50
|
Node.ACS: Updates: add Node.ACS update stream release notes docs
|
Include standard documentation for node.acs release notes as with the sdk. See screenshots. Steps to Reproduce: 1. Uninstall node.acs or have an old version of alloy. 2. Check for Titanium updates. Actual Result: Documentation is minimal. Expected Result: node.acs release notes should be same quality as sdk release notes.
| 5 |
757 |
TISTUD-2514
|
10/14/2012 18:24:55
|
iOS Simulator: studio not passing in simulator version, simulator fails to launch
|
When a project is run in iPhone Simulator, no simulator version is passed in, so the process terminates and the simulator fails to launch. Simulator runs correctly in SDK 2.1.3.GA. When the same command is run from the command line, there is a missing version error. studio command: {code} "/usr/local/bin/titanium" "--no-banner" "--no-colors" "--no-prompt" "build" "--platform" "iphone" "--sdk" "3.0.0.v20121013142429" "--log-level" "trace" "--target" "simulator" "--ios-version" "6.0" "--sim-version" "" {code} cli error: {code} DHydeMBP:~ dhyde$ "/usr/local/bin/titanium" "--no-banner" "--no-colors" "--no-prompt" "build" "--platform" "iphone" "--sdk" "3.0.0.v20121013142429" "--log-level" "trace" "--target" "simulator" "--ios-version" "6.0" "--sim-version" "" { '0': '[', '1': 'E', '2': 'R', '3': 'R', '4': 'O', '5': 'R', '6': ']', '7': ' ', '8': 'I', '9': 'n', '10': 'v', '11': 'a', '12': 'l', '13': 'i', '14': 'd', '15': ' ', '16': '-', '17': '-', '18': 'i', '19': 'o', '20': 's', '21': '-', '22': 'v', '23': 'e', '24': 'r', '25': 's', '26': 'i', '27': 'o', '28': 'n', '29': ' ', '30': 'v', '31': 'a', '32': 'l', '33': 'u', '34': 'e', '35': ' ', '36': '\'', '37': '6', '38': '\'', '39': '\n' } Accepted values: 6.0 {code} Steps to Reproduce: 1. Run a project in iPhone Simulator. Actual Result: Terminate, no launch. Expected Result: simulator launches.
| 5 |
758 |
TISTUD-2515
|
10/14/2012 18:30:15
|
Android Emulator: Application Installer abnormal process termination. Process exit value was 1
|
When a project is run in Android Emulator, the process terminates and the emulator fails to launch. When the same command is run from the command line, there is an error. This does not occur in Studio 2.1.2, this is a regression. correct studio 2.1.2 command for comparison: {code} "/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py" "emulator" "MyProject" "/Users/dhyde/Desktop/android/android-sdk-macosx" "/Users/dhyde/Desktop/TISTUD-STABLE/TISTUD-STABLE-2.1.2/workspace/MyProject" "com.appcelerator.myproject" "2" "WVGA854" {code} broken studio 3.0.0 studio command: {code} "/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py" "emulator" "MyProject" "/Users/dhyde/Desktop/android/android-sdk-macosx" "/Users/dhyde/Desktop/TISTUD-RC/workspace/MyProject" "com.appcelerator.myproject" "Google Inc.:Google APIs:8" "WVGA854" "armeabi" "" {code} console error: {code} DHydeMBP:~ dhyde$ "/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py" "emulator" "MyProject" "/Users/dhyde/Desktop/android/android-sdk-macosx" "/Users/dhyde/Desktop/TISTUD-RC/workspace/MyProject" "com.appcelerator.myproject" "Google Inc.:Google APIs:8" "WVGA854" "armeabi" "" [INFO] logfile = /Users/dhyde/Desktop/TISTUD-RC/workspace/MyProject/build.log [DEBUG] /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py emulator MyProject /Users/dhyde/Desktop/android/android-sdk-macosx /Users/dhyde/Desktop/TISTUD-RC/workspace/MyProject com.appcelerator.myproject Google Inc.:Google APIs:8 WVGA854 armeabi [TRACE] app property, acs-oauth-secret-production : 2bF4wIg5R1jyZgpho9T1KK0O7DaZEAGH [TRACE] app property, acs-oauth-key-production : 77o6QwCZEO42wzQGzEHHpyQdKvT9iUBC [TRACE] app property, acs-api-key-production : gscwbUg86rxKwZ7riRYdgc69UHcPwDly [TRACE] app property, acs-oauth-secret-development : wOXlhxKgcO6iAP3kZoWFdPvIb8BY3K6P [TRACE] app property, acs-oauth-key-development : F2BYLghq7GT3Ov8QVNkegHpliDthe0AV [TRACE] app property, acs-api-key-development : cVUhhCNDUwFgElVEcNxgVeCfsr1v2PiP [TRACE] app property, ti.ui.defaultunit : system [INFO] Launching Android emulator...one moment [DEBUG] From: /Users/dhyde/Desktop/android/android-sdk-macosx/tools/emulator [DEBUG] SDCard: /Users/dhyde/.titanium/android2.sdcard [DEBUG] AVD Name: Google Inc.:Google APIs:8 [DEBUG] SDK: /Users/dhyde/Desktop/android/android-sdk-macosx [DEBUG] /Users/dhyde/Desktop/android/android-sdk-macosx/tools/emulator -avd Google Inc.:Google APIs:8 -port 5560 -sdcard /Users/dhyde/.titanium/android2.sdcard -logcat *:d,*,TiAPI:V -no-boot-anim -partition-size 128 WVGA854 armeabi PANIC: Could not open: /Users/dhyde/.android/avd/Google Inc.:Google APIs:8.ini[DEBUG] signal caught: 3 [DEBUG] calling emulator kill on 60498 [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py", line 2360, in <module> [ERROR] builder.run_emulator(avd_id, avd_skin, avd_name, avd_abi, add_args) [ERROR] File "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py", line 624, in run_emulator [ERROR] handler(3,None) [ERROR] File "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121013142429/android/builder.py", line 609, in handler [ERROR] os.kill(p.pid, signal.SIGTERM) [ERROR] OSError: [Errno 3] No such process {code} Steps to Reproduce: 1. Run a project in Android Emulator. Actual Result: Terminate, no launch. Expected Result: emulator launches.
| 5 |
759 |
TISTUD-2519
|
10/15/2012 09:17:58
|
"Failed to install Titanium" and "failed to install ACS" errors are coming during updates installation
|
If the user updates (Help > Titanium Updates) CLI, Alloy, and ACS, none of the updates are recognized as being installed, and the user is still prompted for updates, even after studio restart. Steps to Reproduce: 1. Help > Check for Titanium Updates and take all updates (CLI,ACS). 2. Select all the updates and press "install". Actual Result: Unable to install updates Error prompt is coming . Screenshots and logs are attached. Expected Result: User should be able to install updates.
| 13 |
760 |
TISTUD-2522
|
10/15/2012 16:32:25
|
Error thrown while updating CLI in Ubuntu 12.04
|
When trying to install updates in Ubuntu 12.04 I get the following error: {code} !ENTRY com.appcelerator.titanium.update 4 4 2012-10-15 08:25:56.113 !MESSAGE Error encountered during update !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2012-10-15 08:25:56.113 !MESSAGE Cannot run program "gksudo --message='Titanium Studio would like to install Titanium CLI.'": java.io.IOException: error=2, No such file or directory !STACK 0 java.io.IOException: Cannot run program "gksudo --message='Titanium Studio would like to install Titanium CLI.'": java.io.IOException: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) at com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327) at com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322) at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273) at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235) at com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.install(NodePackageManager.java:112) at com.appcelerator.titanium.update.TitaniumNPMRelease.install(TitaniumNPMRelease.java:37) at com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:561) at com.appcelerator.titanium.update.TitaniumSDKUpdater.access$1(TitaniumSDKUpdater.java:510) at com.appcelerator.titanium.update.TitaniumSDKUpdater$2.run(TitaniumSDKUpdater.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.<init>(UNIXProcess.java:164) at java.lang.ProcessImpl.start(ProcessImpl.java:81) at java.lang.ProcessBuilder.start(ProcessBuilder.java:468) ... 10 more {code} Steps to reproduce: 1. Start Titanium Studio 2. Attempt to install the new CLI through the toast popup (or Help > Check for Titanium Updates) Expected result: The Titanium CLI should correctly install into Titanium Studio. Actual result: The above error.
| 3 |
761 |
TISTUD-2527
|
10/15/2012 21:18:39
|
CLI: cli not prompted for install on studio startup
|
When studio first starts, the cli is not prompted to update, but alloy and node.acs are. NPM Installer Log: {code} DHydeMBP:workspace dhyde$ '/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/plugins/com.aptana.libraries_3.0.0.1346444124/os/macosx/cocoa sudo' '--prompt=Titanium Studio would like to install acs.' '/usr/local/bin/npm' '-g' 'install' 'acs' 2>&1 | tee install.log DHydeMBP:workspace dhyde$ '/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/plugins/com.aptana.libraries_3.0.0.1346444124/os/macosx/cocoa sudo' '--prompt=Titanium Studio would like to install alloy.' '/usr/local/bin/npm' '-g' 'install' 'alloy' 2>&1 | tee install.log {code} Steps to Reproduce: 1. Uninstall titanium cli (i.e. delete titanium folder from npm folder). 2. Start studio. Actual Result: No prompt to install cli. However, there are prompts to install alloy and acs. Expected Result: Prompt to install titanium cli if it is not installed (along with alloy and acs).
| 5 |
762 |
TISTUD-2531
|
10/16/2012 01:12:53
|
Titanium Updates: cancelled updates that were successful have false error message
|
If the user takes a CLI, Alloy, or Node.ACS update, and cancels the process using the 'Cancel' button after entering the system password in the prompt, the update will be successful (just as with SDK updates, this is ideal behavior), but there is a failure message. There should be a success message as with the SDK. See screenshots. Steps to Reproduce: 1. Update either CLI, Node.ACS, or Alloy from Studio (Check for Titanium Updates). 2. After entering user password for install prompt, cancel the install using the 'Cancel' button in the process dialog. Actual Result: Fail message, and fail dialog, fail messages in log. Expected Result: The installation was successful, which is ideal because we don't want half-installed software, and there should be a success toast in the lower-right corner, as with SDK downloads that are cancelled late during the extraction process.
| 5 |
763 |
TISTUD-2535
|
10/16/2012 17:29:02
|
Titanium Project: new project caused error Problems occurred while refreshing local changes
|
When creating a new titanium project, I received an error that I could not reproduce on further attempts: error: {code} !ENTRY org.eclipse.core.resources 4 1 2012-10-16 09:21:00.473 !MESSAGE Problems occurred while refreshing local changes !SUBENTRY 1 org.eclipse.core.resources 4 1 2012-10-16 09:21:00.473 !MESSAGE Problems occurred while refreshing local changes !STACK 1 org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system. at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904) at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1663) at org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:167) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: The project description file (.project) for 'MyProject' is missing. This file contains important information about the project. The project will not function properly until this file is restored. !SUBENTRY 2 org.eclipse.core.resources 4 271 2012-10-16 09:21:00.475 !MESSAGE Errors occurred while refreshing resources with the local file system. !SUBENTRY 3 org.eclipse.core.resources 4 567 2012-10-16 09:21:00.475 !MESSAGE The project description file (.project) for 'MyProject' is missing. This file contains important information about the project. The project will not function properly until this file is restored. {code} Steps to Reproduce: 1. Create a Titanium Project. Actual Result: Error. Expected Result: New Titanium Project.
| 5 |
764 |
TISTUD-2540
|
10/17/2012 00:58:19
|
WARNING: Prevented recursive attempt to activate part com.aptana.editor.js while still in the middle of activating part com.aptana.editor.text
|
Saw this in the log. Created a default project and ran in a android device debugger. Log: {code} !ENTRY org.eclipse.ui.workbench 4 0 2012-10-16 16:43:38.751 !MESSAGE WARNING: Prevented recursive attempt to activate part com.aptana.editor.js while still in the middle of activating part com.aptana.editor.text !STACK 0 java.lang.RuntimeException: WARNING: Prevented recursive attempt to activate part com.aptana.editor.js while still in the middle of activating part com.aptana.editor.text at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3586) at org.eclipse.ui.internal.WorkbenchPage.internalActivate(WorkbenchPage.java:691) at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:663) at org.eclipse.ui.internal.WorkbenchPage.makeActive(WorkbenchPage.java:1324) at org.eclipse.ui.internal.WorkbenchPage.bringToTop(WorkbenchPage.java:918) at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:270) at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(SourceLookupFacility.java:219) at org.eclipse.debug.ui.DebugUITools.displaySource(DebugUITools.java:973) at org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter$SourceDisplayJob.runInUIThread(StackFrameSourceDisplayAdapter.java:157) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:364) at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:463) at org.eclipse.ui.texteditor.AbstractTextEditor.handleEditorInputChanged(AbstractTextEditor.java:4757) at org.eclipse.ui.texteditor.StatusTextEditor.handleEditorInputChanged(StatusTextEditor.java:267) at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.handleEditorInputChanged(AbstractDecoratedTextEditor.java:1474) at com.aptana.editor.common.internal.AbstractFoldingEditor.handleEditorInputChanged(AbstractFoldingEditor.java:252) at org.eclipse.ui.texteditor.AbstractTextEditor.sanityCheckState(AbstractTextEditor.java:4887) at org.eclipse.ui.texteditor.StatusTextEditor.sanityCheckState(StatusTextEditor.java:257) at org.eclipse.ui.texteditor.AbstractTextEditor.safelySanityCheckState(AbstractTextEditor.java:4865) at org.eclipse.ui.texteditor.AbstractTextEditor$ActivationListener.handleActivation(AbstractTextEditor.java:984) at org.eclipse.ui.texteditor.AbstractTextEditor$ActivationListener.partActivated(AbstractTextEditor.java:941) at org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:72) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:57) at org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:70) at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:187) at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:306) at org.eclipse.ui.internal.WWinPartService.updateActivePart(WWinPartService.java:134) at org.eclipse.ui.internal.WWinPartService.access$0(WWinPartService.java:125) at org.eclipse.ui.internal.WWinPartService$WWinListener.partDeactivated(WWinPartService.java:50) at org.eclipse.ui.internal.PartListenerList2$4.run(PartListenerList2.java:115) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:55) at org.eclipse.ui.internal.PartListenerList2.firePartDeactivated(PartListenerList2.java:113) at org.eclipse.ui.internal.PartService.firePartDeactivated(PartService.java:242) at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:300) at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:57) at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3636) at org.eclipse.ui.internal.WorkbenchPage.internalActivate(WorkbenchPage.java:691) at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:663) at org.eclipse.ui.internal.WorkbenchPage.makeActive(WorkbenchPage.java:1324) at org.eclipse.ui.internal.WorkbenchPage.updateActivePart(WorkbenchPage.java:1304) at org.eclipse.ui.internal.WorkbenchPage.updateVisibility(WorkbenchPage.java:3779) at org.eclipse.ui.internal.WorkbenchPage.setPerspective(WorkbenchPage.java:3719) at org.eclipse.ui.internal.WorkbenchPage.busySetPerspective(WorkbenchPage.java:1115) at org.eclipse.ui.internal.WorkbenchPage.access$16(WorkbenchPage.java:1099) at org.eclipse.ui.internal.WorkbenchPage$19.run(WorkbenchPage.java:3814) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.setPerspective(WorkbenchPage.java:3812) at org.eclipse.ui.internal.Workbench.showPerspective(Workbench.java:2795) at org.eclipse.debug.internal.ui.launchConfigurations.PerspectiveManager.switchToPerspective(PerspectiveManager.java:316) at org.eclipse.debug.internal.ui.launchConfigurations.PerspectiveManager$4.runInUIThread(PerspectiveManager.java:395) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 8 |
765 |
TISTUD-2541
|
10/17/2012 01:06:45
|
Android Device Debugger: console log process not terminated in debug view
|
When debug process thread is terminated, the console log process is not terminated, and the entire session process is not terminated. Steps to Reproduce: 1. Debug in Android Device (default project w/one breakpoint). 2. When breakpoint is hit, and thread is selected in debug view, press 'terminate'. Actual Result: Console log process is still active. Session process is still active. Expected Result: All associated session processes should be terminated. Console log process and session should be terminated.
| 5 |
766 |
TISTUD-2545
|
10/17/2012 01:22:29
|
Titanium: Project Creation - When you create the default app with ACS enabled, the guid in the tiapp.xml does not match with the guid in my.appcelerator.com
|
Details: If you create the default Titanium app with ACS enabled from Studio, the guid in the tiapp.xml does not match with the guid in my.appcelerator.com \\ \\ If you create the default Titanium app *without* ACS enabled, then the guid in the tiapp.xml will match with the guid in my.appcelerator.com \\ \\ Steps to reproduce: 1. Create default Titanium app with ACS enabled 2. Go to my.appcelerator.com and find your app 3. Click on *App Details* link \\ \\ Actual: The guid in the tiapp.xml does not match with the guid in my.appcelerator.com (see tiapp_xml.png and my_apps.png). And if you go to my.appcelerator.com/app/<guid_in_tiapp>, the my apps page does not recognize it (see no_guid.png) \\ \\ Expected: The guids generated in Studio should match guid in the my apps page.
| 5 |
767 |
TISTUD-2546
|
10/17/2012 08:07:53
|
Add File > New > Node.ACS Project to the simple Studio perspective
|
This is not a regression issue. Steps To Reproduce: 1. Download 2.1.2 studio installer and upgrade it to 3.0 2. Delete plugin files from /usr/local/lib/node_modules folder. 3. Go to Help > Check for Titanium Updates. From the window install, alloy, CLI and acs updates. Actual: After successful installation of all plugins, File > New > Node.ACS option does not appear. Expected: File > New > Node.ACS option must appear.
| 5 |
768 |
TISTUD-2550
|
10/17/2012 18:45:11
|
Issue install using NPM to install within Titanium Studio in Windows 7
|
The following is shown in the NPM Installer Window during start up: {code} qatester@QATESTER-CH1 ~/My Documents/Titanium_Studio_Workspace $ "c:\Program Files (x86)\nodejs\npm.CMD" -g install titanium > install.log | type install.log c:\Program Files (x86)\nodejs\npm.CMD: line 1: unexpected EOF while looking for matching `'' c:\Program Files (x86)\nodejs\npm.CMD: line 7: syntax error: unexpected end of file install.log is ./install.log qatester@QATESTER-CH1 ~/My Documents/Titanium_Studio_Workspace $ "c:\Program Files (x86)\nodejs\npm.CMD" -g install alloy > install.log | type install.log install.log is ./install.log c:\Program Files (x86)\nodejs\npm.CMD: line 1: unexpected EOF while looking for matching `'' c:\Program Files (x86)\nodejs\npm.CMD: line 7: syntax error: unexpected end of file qatester@QATESTER-CH1 ~/My Documents/Titanium_Studio_Workspace $ "c:\Program Files (x86)\nodejs\npm.CMD" -g install acs > install.log | type install.log c:\Program Files (x86)\nodejs\npm.CMD: line 1: unexpected EOF while looking for matching `'' c:\Program Files (x86)\nodejs\npm.CMD: line 7: syntax error: unexpected end of file install.log is ./install.log {code} The ./install.log contains no data, blank file with 0kb size. This looks like a failed install for Titanium CLI, ACS and Alloy. Steps to reproduce: 1. Without Titanium, ACS, or Alloy installed start Titanium Studio. Expected results: Plugins should be correctly installed. Actual results: The above issue.
| 8 |
769 |
TISTUD-2553
|
10/17/2012 22:27:59
|
Titanium Updates: update menu appeared with no entries
|
An update prompt appeared in the lower right corner of studio, when the titanium updates menu came up, it did not contain any entries. See screenshot. See log. This is intermittent. Steps to Reproduce: 1. Open Titanium Studio. 2. Wait for updates prompt in lower right corner. 3. Click on it to bring up the updates menu. Actual Result: No entries. Expected Result: Should contain the update that initiated the prompt.
| 5 |
770 |
TISTUD-2559
|
10/18/2012 15:57:20
|
Studio: Preferences: takes 3 seconds to load default android sdk and screen types
|
Preferences > Titanium Studio > Titanium > Default Android SDK takes 3 seconds to load. This is a regression. Steps to Reproduce: 1. Run Preferences > Titanium Studio > Titanium > Default Android SDK takes 3 seconds to load. Actual Result: 3 seconds to load, initially looks broken. Expected Result: Instant load. Note: As per Shalom, here is the command-line arg to get this preferences info: titanium info -o json
| 8 |
771 |
TISTUD-2561
|
10/18/2012 17:14:36
|
Titanium Updates: Unhandled event loop exception after installing updates
|
After installing alloy, get log exception: {code} !ENTRY com.aptana.core 1 0 2012-10-18 09:06:49.822 !MESSAGE (Build 3.0.0.201210172118) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/npm" "-p" "list" "alloy" "-g" Working directory: null Environment: {ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8b, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk-macosx, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-EeKGAL/Render, Apple_Ubiquity_Message=/tmp/launch-SW45KT/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-9CZqFn/ServiceProcessSocket, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dhyde/Desktop/android/android-sdk-macosx/tools:/Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools, PWD=/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/TitaniumStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-0sLjqp/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI, redirectErrorStream=} !ENTRY com.aptana.core 1 0 2012-10-18 09:06:49.842 !MESSAGE (Build 3.0.0.201210172118) [INFO] com.aptana.core/debug/shell Searching for titanium in PATH locations: /usr/bin, /bin, /usr/sbin, /sbin, /usr/local/bin, /Users/dhyde/Desktop/android/android-sdk-macosx/tools, /Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools !ENTRY com.aptana.core 1 0 2012-10-18 09:06:49.843 !MESSAGE (Build 3.0.0.201210172118) [INFO] com.aptana.core/debug/shell Found executable on PATH: /usr/local/bin/titanium !ENTRY org.eclipse.ui 4 0 2012-10-18 09:07:46.255 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at java.lang.String.<init>(String.java:210) at com.aptana.terminal.internal.emulator.ThemedTextLineRenderer.drawLine(ThemedTextLineRenderer.java:95) at org.eclipse.tm.internal.terminal.textcanvas.TextCanvas.drawLine(TextCanvas.java:343) at org.eclipse.tm.internal.terminal.textcanvas.GridCanvas.paint(GridCanvas.java:80) at org.eclipse.tm.internal.terminal.textcanvas.VirtualCanvas$1.handleEvent(VirtualCanvas.java:48) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Control.drawWidget(Control.java:1244) at org.eclipse.swt.widgets.Canvas.drawWidget(Canvas.java:163) at org.eclipse.swt.widgets.Widget.drawRect(Widget.java:740) at org.eclipse.swt.widgets.Canvas.drawRect(Canvas.java:158) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5449) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSView.displayIfNeeded(NSView.java:142) at org.eclipse.swt.widgets.Control.update(Control.java:4890) at org.eclipse.swt.widgets.Control.update(Control.java:4876) at org.eclipse.tm.internal.terminal.textcanvas.VirtualCanvas.repaint(VirtualCanvas.java:145) at org.eclipse.tm.internal.terminal.textcanvas.TextCanvas.repaintRange(TextCanvas.java:340) at org.eclipse.tm.internal.terminal.textcanvas.TextCanvas$1.rangeChanged(TextCanvas.java:96) at org.eclipse.tm.internal.terminal.textcanvas.AbstractTextCanvasModel.fireCellRangeChanged(AbstractTextCanvasModel.java:60) at org.eclipse.tm.internal.terminal.textcanvas.AbstractTextCanvasModel.updateCursor(AbstractTextCanvasModel.java:183) at org.eclipse.tm.internal.terminal.textcanvas.AbstractTextCanvasModel.update(AbstractTextCanvasModel.java:118) at org.eclipse.tm.internal.terminal.textcanvas.PollingTextCanvasModel$1.run(PollingTextCanvasModel.java:28) at org.eclipse.swt.widgets.Display.runTimers(Display.java:4106) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3604) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} Steps to Reproduce: 1. Install alloy. 2. View log. Actual Result: Exception. Expected Result: No exceptions.
| 8 |
772 |
TISTUD-2562
|
10/18/2012 17:31:13
|
Titanium Updates: inform user all updates will be installed on studio launch
|
Entering user password on studio launch once installs all titanium updates regardless of user wishes. If the prompt is going to install everything, it should message that to the user. NMP Installer Log: {code} DHydeMBP:workspace dhyde$ read -s PASSWORD DHydeMBP:workspace dhyde$ echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'acs' 2>&1 | tee install.log npm http GET https://registry.npmjs.org/acs echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'alloy' 2>&1 | tee install.log echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'titanium' 2>&1 | tee install.log read -s PASSWORD npm http 304 https://registry.npmjs.org/acs npm http GET https://registry.npmjs.org/colors/0.6.0-1 npm http GET https://registry.npmjs.org/commander/0.6.1 npm http GET https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.4 npm http GET https://registry.npmjs.org/connect/2.3.5 npm http GET https://registry.npmjs.org/express/2.5.11 npm http GET https://registry.npmjs.org/ejs/0.8.0 npm http GET https://registry.npmjs.org/log4js/0.5.1 npm http GET https://registry.npmjs.org/longjohn/0.0.3 npm http GET https://registry.npmjs.org/pkginfo/0.2.2 npm http GET https://registry.npmjs.org/fstream/0.1.18 npm http GET https://registry.npmjs.org/connect-mongo/0.1.9 npm http GET https://registry.npmjs.org/node-uuid/1.3.3 npm http GET https://registry.npmjs.org/wrench/1.3.9 npm http GET https://registry.npmjs.org/mkdirp/0.3.3 npm http GET https://registry.npmjs.org/tar/0.1.13 npm http GET https://registry.npmjs.org/socket.io/0.9.6 npm http GET https://registry.npmjs.org/temp/0.4.0 npm http GET https://registry.npmjs.org/underscore/1.3.3 npm http GET https://registry.npmjs.org/uglify-js/1.3.2 npm http 304 https://registry.npmjs.org/colors/0.6.0-1 npm http 304 https://registry.npmjs.org/commander/0.6.1 npm http 304 https://registry.npmjs.org/connect/2.3.5 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/express/2.5.11 npm http 304 https://registry.npmjs.org/ejs/0.8.0 npm http 304 https://registry.npmjs.org/log4js/0.5.1 npm http 304 https://registry.npmjs.org/longjohn/0.0.3 npm http 304 https://registry.npmjs.org/pkginfo/0.2.2 npm http 304 https://registry.npmjs.org/fstream/0.1.18 npm http 304 https://registry.npmjs.org/connect-mongo/0.1.9 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/mkdirp/0.3.3 npm http 200 https://registry.npmjs.org/node-uuid/1.3.3 npm http 304 https://registry.npmjs.org/wrench/1.3.9 npm http GET https://registry.npmjs.org/node-uuid/-/node-uuid-1.3.3.tgz npm http 304 https://registry.npmjs.org/tar/0.1.13 npm http 304 https://registry.npmjs.org/socket.io/0.9.6 npm http 200 https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.4 npm http 304 https://registry.npmjs.org/underscore/1.3.3 npm http 304 https://registry.npmjs.org/temp/0.4.0 npm http 200 https://registry.npmjs.org/node-uuid/-/node-uuid-1.3.3.tgz npm http 304 https://registry.npmjs.org/uglify-js/1.3.2 npm http GET https://registry.npmjs.org/rimraf npm http GET https://registry.npmjs.org/graceful-fs npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/mongodb npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/policyfile/0.0.4 npm http GET https://registry.npmjs.org/block-stream npm http GET https://registry.npmjs.org/connect npm http GET https://registry.npmjs.org/redis/0.6.7 npm http GET https://registry.npmjs.org/mkdirp/0.3.0 npm http GET https://registry.npmjs.org/qs npm http GET https://registry.npmjs.org/socket.io-client/0.9.6 npm http GET https://registry.npmjs.org/mime/1.2.4 npm http GET https://registry.npmjs.org/async/0.1.15 npm http GET https://registry.npmjs.org/qs/0.4.2 npm http GET https://registry.npmjs.org/formidable/1.0.11 npm http GET https://registry.npmjs.org/crc/0.2.0 npm http GET https://registry.npmjs.org/cookie/0.0.4 npm http GET https://registry.npmjs.org/bytes/0.0.1 npm http GET https://registry.npmjs.org/fresh/0.0.1 npm http GET https://registry.npmjs.org/range-parser/0.0.4 npm http GET https://registry.npmjs.org/debug npm http 304 https://registry.npmjs.org/rimraf npm http 304 https://registry.npmjs.org/graceful-fs npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/mongodb npm http 304 https://registry.npmjs.org/policyfile/0.0.4 npm http 304 https://registry.npmjs.org/block-stream npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/connect npm http 304 https://registry.npmjs.org/redis/0.6.7 npm WARN package.json [email protected] No README.md file found! npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/qs npm http 304 https://registry.npmjs.org/mkdirp/0.3.0 npm http 304 https://registry.npmjs.org/socket.io-client/0.9.6 npm http 304 https://registry.npmjs.org/mime/1.2.4 npm http 304 https://registry.npmjs.org/async/0.1.15 npm http 304 https://registry.npmjs.org/formidable/1.0.11 npm http 304 https://registry.npmjs.org/cookie/0.0.4 npm http 304 https://registry.npmjs.org/bytes/0.0.1 npm http 304 https://registry.npmjs.org/qs/0.4.2 npm http 304 https://registry.npmjs.org/crc/0.2.0 npm http 304 https://registry.npmjs.org/fresh/0.0.1 npm http 304 https://registry.npmjs.org/range-parser/0.0.4 npm http 304 https://registry.npmjs.org/debug npm http GET https://registry.npmjs.org/formidable npm http GET https://registry.npmjs.org/bson/0.0.4 npm http GET https://registry.npmjs.org/uglify-js/1.2.5 npm http GET https://registry.npmjs.org/ws npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2 npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1 npm http 304 https://registry.npmjs.org/formidable npm http 304 https://registry.npmjs.org/bson/0.0.4 npm WARN package.json [email protected] No README.md file found! > [email protected] install /usr/local/lib/node_modules/acs/node_modules/connect-mongo/node_modules/mongodb/node_modules/bson > node install.js npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1 ================================================================================ = = = To install with C++ bson parser do <npm install mongodb --mongodb:native> = = = ================================================================================ npm http 304 https://registry.npmjs.org/uglify-js/1.2.5 npm http 304 https://registry.npmjs.org/ws npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2 npm http GET https://registry.npmjs.org/zeparser/0.0.5 npm http GET https://registry.npmjs.org/tinycolor npm http GET https://registry.npmjs.org/options npm http 304 https://registry.npmjs.org/zeparser/0.0.5 npm http 304 https://registry.npmjs.org/tinycolor npm http 304 https://registry.npmjs.org/options > [email protected] install /usr/local/lib/node_modules/acs/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws > node install.js [ws v0.4.22] Attempting to compile blazing fast native extensions. [ws v0.4.22] Native extension compilation successful! /usr/local/bin/acs -> /usr/local/lib/node_modules/acs/bin/acs [email protected] /usr/local/lib/node_modules/acs ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected], [email protected], [email protected]) ├── [email protected] ([email protected], [email protected]) ├── [email protected] ([email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], formida [email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected]) ├── [email protected] ([email protected]) └── [email protected] ([email protected], [email protected], [email protected]) DHydeMBP:workspace dhyde$ echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'alloy' 2>&1 | tee install.log npm http GET https://registry.npmjs.org/alloy npm http 304 https://registry.npmjs.org/alloy npm http GET https://registry.npmjs.org/colors/0.6.0-1 npm http GET https://registry.npmjs.org/pkginfo/0.2.2 npm http GET https://registry.npmjs.org/commander/0.6.1 npm http GET https://registry.npmjs.org/wrench/1.3.9 npm http GET https://registry.npmjs.org/xmldom/0.1.13 npm http GET https://registry.npmjs.org/jsonlint/1.5.1 npm http GET https://registry.npmjs.org/stripcolorcodes/0.1.0 npm http GET https://registry.npmjs.org/jake npm http 304 https://registry.npmjs.org/colors/0.6.0-1 npm http 304 https://registry.npmjs.org/pkginfo/0.2.2 npm http 304 https://registry.npmjs.org/jsonlint/1.5.1 npm http 304 https://registry.npmjs.org/xmldom/0.1.13 npm http 304 https://registry.npmjs.org/commander/0.6.1 npm http 304 https://registry.npmjs.org/wrench/1.3.9 npm http 304 https://registry.npmjs.org/stripcolorcodes/0.1.0 npm http 304 https://registry.npmjs.org/jake npm http GET https://registry.npmjs.org/minimatch npm http GET https://registry.npmjs.org/utilities npm http GET https://registry.npmjs.org/nomnom npm http GET https://registry.npmjs.org/JSV npm http 304 https://registry.npmjs.org/minimatch npm http 304 https://registry.npmjs.org/utilities npm http GET https://registry.npmjs.org/lru-cache npm http 304 https://registry.npmjs.org/nomnom npm http 304 https://registry.npmjs.org/JSV npm http GET https://registry.npmjs.org/underscore npm http GET https://registry.npmjs.org/colors npm http 304 https://registry.npmjs.org/lru-cache npm http 304 https://registry.npmjs.org/underscore npm http 304 https://registry.npmjs.org/colors /usr/local/bin/alloy -> /usr/local/lib/node_modules/alloy/bin/alloy [email protected] /usr/local/lib/node_modules/alloy ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected], [email protected]) └── [email protected] ([email protected], [email protected]) DHydeMBP:workspace dhyde$ echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'titanium' 2>&1 | tee install.log npm http GET https://registry.npmjs.org/titanium npm http 304 https://registry.npmjs.org/titanium npm http GET https://registry.npmjs.org/colors npm http GET https://registry.npmjs.org/async npm http GET https://registry.npmjs.org/longjohn npm http GET https://registry.npmjs.org/node-appc npm http GET https://registry.npmjs.org/temp/0.4.0 npm http GET https://registry.npmjs.org/prompt npm http GET https://registry.npmjs.org/semver npm http GET https://registry.npmjs.org/wrench npm http GET https://registry.npmjs.org/request npm http GET https://registry.npmjs.org/winston npm http GET https://registry.npmjs.org/revalidator npm http GET https://registry.npmjs.org/sprintf npm http 304 https://registry.npmjs.org/colors npm http 304 https://registry.npmjs.org/async npm http 304 https://registry.npmjs.org/longjohn npm http 304 https://registry.npmjs.org/node-appc npm http 304 https://registry.npmjs.org/temp/0.4.0 npm http 304 https://registry.npmjs.org/prompt npm http 304 https://registry.npmjs.org/semver npm http 304 https://registry.npmjs.org/wrench npm http 304 https://registry.npmjs.org/request npm http 304 https://registry.npmjs.org/winston npm http 304 https://registry.npmjs.org/sprintf npm http 200 https://registry.npmjs.org/revalidator npm http GET https://registry.npmjs.org/revalidator/-/revalidator-0.1.3.tgz npm http 200 https://registry.npmjs.org/revalidator/-/revalidator-0.1.3.tgz npm http GET https://registry.npmjs.org/read npm http GET https://registry.npmjs.org/utile npm http GET https://registry.npmjs.org/pkginfo npm http GET https://registry.npmjs.org/cycle npm http GET https://registry.npmjs.org/eyes npm http GET https://registry.npmjs.org/pkginfo npm http GET https://registry.npmjs.org/stack-trace npm http GET https://registry.npmjs.org/node-uuid npm http GET https://registry.npmjs.org/uglify-js npm http GET https://registry.npmjs.org/xmldom/0.1.11 npm http 304 https://registry.npmjs.org/read npm http 304 https://registry.npmjs.org/utile npm http 304 https://registry.npmjs.org/pkginfo npm http 304 https://registry.npmjs.org/cycle npm http 304 https://registry.npmjs.org/eyes npm http 304 https://registry.npmjs.org/pkginfo npm http 304 https://registry.npmjs.org/stack-trace npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/uglify-js npm http 304 https://registry.npmjs.org/xmldom/0.1.11 npm http GET https://registry.npmjs.org/mute-stream npm http GET https://registry.npmjs.org/deep-equal npm http GET https://registry.npmjs.org/rimraf npm http GET https://registry.npmjs.org/i npm http GET https://registry.npmjs.org/mkdirp npm http GET https://registry.npmjs.org/ncp npm http 200 https://registry.npmjs.org/node-uuid npm http 304 https://registry.npmjs.org/mkdirp npm http 304 https://registry.npmjs.org/ncp npm http 304 https://registry.npmjs.org/mute-stream npm http 304 https://registry.npmjs.org/deep-equal npm http 304 https://registry.npmjs.org/rimraf npm http 304 https://registry.npmjs.org/i /usr/local/bin/titanium -> /usr/local/lib/node_modules/titanium/bin/titanium [email protected] /usr/local/lib/node_modules/titanium ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected], [email protected], [email protected], [email protected]) ├── [email protected] ([email protected], [email protected], [email protected]) └── [email protected] ([email protected], [email protected], [email protected]) DHydeMBP:workspace dhyde$ read -s PASSWORD DHydeMBP:workspace dhyde$ {code} Steps to Reproduce: 1. Uninstall cli, alloy, and acs. 2. Load studio and enter user password on prompt. Actual Result: Everything is installed, not just the prompted update. Expected Result: Each update is installed one by one, and user enters password for each.
| 5 |
773 |
TISTUD-2564
|
10/18/2012 18:49:56
|
TiStudio: Project - If you create the default Titanium project, then the ti.cloud module will not appear in the tiapp.xml
|
Details: After creating the default Titanium app, the ti.cloud module does not appear in the tiapp.xml even though the ACS server is returning the 200 success in the log. The issue still appears with SDK 2.1.3 \\ \\ Steps to reproduce: 1. Open TiStudio and create the default Titanium app \\ \\ Actual: ti.cloud module does not appear in the tiapp.xml (see tiapp.png) and ACS is not enabled for app even though 200 success code is returned (see studio_log.txt). \\ \\ But, if I try to *Enable Cloud Services* again, I get the 400 error code (see error.png) \\ \\ Expected: After creating the default app, you should be able to see the ti.cloud module in tiapp.
| 8 |
774 |
TISTUD-2565
|
10/18/2012 22:40:50
|
Portal Module info call needs to return module guids
|
The appdirect call to return the module updates info now contains module guids so we can map the modules to the installed modules. Unfortunately the current portal call to retrieve module info does not contain guids. The call needs to return multiple guids for modules with both iOS and android components, since the guids may differ in those instances.
| 8 |
775 |
TISTUD-2569
|
10/19/2012 02:37:48
|
Alloy templates do not show up after alloy is installed until Studio restarts
|
Steps to reproduce: 1. Uninstall alloy (sudo npm uninstall -g alloy); 2. Start Studio and allow it to install alloy; 3. Open File > New > Titanium Project. Expected result: alloy templates should appear. Actual result: no alloy templates appear. Workaround: restarting Studio and then repeat step 3 would see alloy templates.
| 3 |
776 |
TISTUD-2570
|
10/19/2012 03:30:40
|
Installer: full installer links should always have content
|
http://preview.appcelerator.com/studio/ full installers for mac and windows are dead: http://preview.appcelerator.com/appcelerator/studio/standalone/install/rc/Titanium_Studio.exe {code} Not Found The requested URL /appcelerator/studio/standalone/install/rc/Titanium_Studio.exe was not found on this server. {code} http://preview.appcelerator.com/appcelerator/studio/standalone/install/rc/Titanium_Studio.dmg {code} Not Found The requested URL /appcelerator/studio/standalone/install/rc/Titanium_Studio.dmg was not found on this server. {code} Steps to Reproduce: 1. Go to http://preview.appcelerator.com/studio/ 2. Download the full installers for Windows 7 and OSX. Actual Result: Dead links. Expected Result: Alive links.
| 8 |
777 |
TISTUD-2575
|
10/19/2012 15:41:14
|
Use same sudo prompt UI for Node and npm packages
|
On a clean install we get prompted to install Node. After accepting we get a sudo prompt from cocoasudo. After that finishes we then get a prompt to install acs using a different prompt UI (but again for sudo password). We should have a consistent UI for prompting the sudo password. Additionally, since less than my sudo password expiration time passed between the two, hopefully I wouldn't even get prompted (for my password, but maybe for acceptance) the second time.
| 5 |
778 |
TISTUD-2576
|
10/19/2012 15:45:11
|
Unify the handling of installing and updating processes
|
Our handling of installing requirements are pretty inconsistent. We have the Titanium SDK Updater which checks on startup for updates to Titanium SDK, titanium CLI, alloy, and acs. But we also have separate IStartup checks for acs and alloy. Additionally our check for Node is done entirely separately. Ideally we'd have the check for updates _always_ run regardless of prefs. And we should have the notion of required installs versus optional (so user can ignore updates that aren't required, but must install/update required things).
| 13 |
779 |
TISTUD-2577
|
10/19/2012 17:55:17
|
Troubleshooting: add select and deselect all to debug specific component
|
Troubleshooting: add select and deselect all to debug specific component checkboxes
| 5 |
780 |
TISTUD-2578
|
10/19/2012 18:01:44
|
System Password Prompt: add parity with native password prompt
|
System Password Prompt: add parity with native password prompt. The native prompt allows the user to enter a different user name. It's not clear to the user if this is a system prompt. Steps to Reproduce: 1. Uninstall the CLI. 2. Restart studio. Actual Result: Prompt appears, is different than system prompt. Expected Result: Clearly defined system prompt similar to os prompt.
| 13 |
781 |
TISTUD-2579
|
10/19/2012 18:06:00
|
TiStudio should not copy the app.png and README from Alloy templates
|
Alloy added an app.png file and a README to each template that is used by TiStudio to display an icon and additional information about Alloy templates. While these files are present in the templates, they should not be copied into the created project.
| 0 |
782 |
TISTUD-2582
|
10/20/2012 01:19:05
|
First Launch : After installing the 32-bit zip on Ubuntu 12.04, when launching for the first time I received an error opening dashboard
|
Steps to reproduce: 1. I downloaded and installed the 32-bit zip version of Ti Studio 2. I then logged in and upon login, an error dialog was presented. Actual result: *See screenshots* Expected result: Ti Studio launches normally
| 5 |
783 |
TISTUD-2587
|
10/20/2012 07:21:44
|
Updates: prevent incomplete updates from occurring
|
When I updated the RC stream, I received an incomplete update. As per Ingo: It's just a rsync Basically, I would have it rsync everything but the content.jar file (or whatever that file is now), and then do a separate script to just do that one. Error: {code} An error occurred while collecting items to be installed session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Artifact not found: osgi.bundle,com.appcelerator.titanium.alloy.core,2.2.0.201210181648. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.alloy.core_2.2.0.201210181648.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.alloy.ui,2.2.0.201210181648. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.alloy.ui_2.2.0.201210181648.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.core,2.2.0.1350579241. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.core_2.2.0.1350579241.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.mobile,1.0.0.1350601983. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.mobile_1.0.0.1350601983.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.nodejs.core,1.0.0.1350601983. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.nodejs.core_1.0.0.1350601983.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.rcp,3.0.0.201210181724. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.rcp_3.0.0.201210181724.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.rcp.studio,1.0.0.201210181724. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.rcp.studio_1.0.0.201210181724.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.studio.rcp.override,1.0.0.201210181724. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.studio.rcp.override_1.0.0.201210181724.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.ui,1.1.0.1350584625. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.ui_1.1.0.1350584625.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.update,2.1.1.1350601983. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.update_2.1.1.1350601983.jar Artifact not found: osgi.bundle,com.aptana.core,3.3.0.1350601913. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.aptana.core_3.3.0.1350601913.jar Artifact not found: osgi.bundle,com.aptana.projects,3.0.0.1350595577. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.aptana.projects_3.0.0.1350595577.jar Artifact not found: osgi.bundle,com.aptana.usage,3.0.0.1350601913. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.aptana.usage_3.0.0.1350601913.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.acs.feature,3.0.0.201210181647-3--59D39CEDB5. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.acs.feature_3.0.0.201210181647-3--59D39CEDB5.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.alloy.feature,3.0.0.201210181648-53-77357535J5FBJ. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.alloy.feature_3.0.0.201210181648-53-77357535J5FBJ.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.feature,3.0.0.1350601983-7M7G-7SOZPXKOA_nP0ZwxQG7ILQJ. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.feature_3.0.0.1350601983-7M7G-7SOZPXKOA_nP0ZwxQG7ILQJ.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.feature.rcp,3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.feature.rcp_3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz.jar Artifact not found: binary,com.appcelerator.titanium.feature.rcp_root,3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/binary/com.appcelerator.titanium.feature.rcp_root_3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz Artifact not found: binary,com.appcelerator.titanium.rcp.product.root.feature_root,3.0.0.201210181724-18102012172652. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/binary/com.appcelerator.titanium.rcp.product.root.feature_root_3.0.0.201210181724-18102012172652 Artifact not found: binary,com.appcelerator.titanium.rcp.product_root.cocoa.macosx.x86,3.0.0.201210181724-18102012172652. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/binary/com.appcelerator.titanium.rcp.product_root.cocoa.macosx.x86_3.0.0.201210181724-18102012172652 Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.studio,3.0.0.1350601983-7N7717oKYgjBpqpV. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.studio_3.0.0.1350601983-7N7717oKYgjBpqpV.jar Artifact not found: org.eclipse.update.feature,com.aptana.feature,3.3.0.1350601913-BP7P8IBeaqBuJCM6s1DC44EXt-dS. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.aptana.feature_3.3.0.1350601913-BP7P8IBeaqBuJCM6s1DC44EXt-dS.jar Artifact not found: org.eclipse.update.feature,com.aptana.php.feature,3.3.0.201210181636-7J7E-7IOTVbd_UIT. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.aptana.php.feature_3.3.0.201210181636-7J7E-7IOTVbd_UIT.jar Artifact not found: org.eclipse.update.feature,org.radrails.rails,3.3.0.201210181635-7e-7Q7f5CZXYCHUY. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/org.radrails.rails_3.3.0.201210181635-7e-7Q7f5CZXYCHUY.jar {code}
| 13 |
784 |
TISTUD-2592
|
10/21/2012 03:36:26
|
Creating a Node.ACS project with a name that's already published produces error
|
Steps to reproduce: 1. Create a Node.ACS project; 2. Create a Node.ACS method in the project; 3. Deploy the app; 4. Delete the project; 5. Repeat Step 1. This produces an error popup shown in the screenshot and the following entry in the Studio log: {code} !SUBENTRY 1 com.aptana.projects 4 0 2012-10-20 19:34:42.524 !MESSAGE !STACK 0 java.lang.reflect.InvocationTargetException at com.appcelerator.titanium.acs.internal.ui.wizards.NewNodeACSProjectWizard.createNewProject(NewNodeACSProjectWizard.java:187) at com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326) at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: org.eclipse.core.commands.ExecutionException: ... 6 more Root exception: org.eclipse.core.commands.ExecutionException: at com.appcelerator.titanium.acs.internal.ui.wizards.NewNodeACSProjectWizard.createNewProject(NewNodeACSProjectWizard.java:187) at com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326) at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code}
| 8 |
785 |
TISTUD-2593
|
10/21/2012 04:45:40
|
Unused NLS messages in the log after starting Studio
|
Seeing the following in the log on Linux: {code} SESSION 2012-10-20 20:42:16.068 ----------------------------------------------- eclipse.buildId=3.0.0.201210200240 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.102 !MESSAGE NLS unused message: <<<<<<< in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: ACCSStartup_Install_Nettle_Job in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: ACCSStartup_Login_ACCS_Task in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: >>>>>>> in: com.appcelerator.titanium.acs.internal.ui.messages {code} Look like a merge conflict that wasn't resolved.
| 3 |
786 |
TISTUD-2594
|
10/21/2012 18:44:39
|
After Update, An exception occurred in the script. Error name: Type Error
|
After updating to the latest version, I get the following error from the dashboard: "An exception occurred in the script. Error name: Type Error. Error description: Object doesn't support this property or method. Error number: -2146827850. Error message: Object doesn't support this property or method" Log file shows: {code} !ENTRY com.aptana.portal.ui 4 0 2012-10-21 10:17:58.740 !MESSAGE (Build 2.1.2.201208301612) [ERROR] wrong number of arguments !STACK 0 java.lang.IllegalArgumentException: wrong number of arguments at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:101) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:137) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:121) at com.aptana.portal.ui.internal.BrowserWrapper$2.function(BrowserWrapper.java:51) at org.eclipse.swt.browser.WebSite.Invoke(WebSite.java:773) at org.eclipse.swt.browser.WebSite$7.method6(WebSite.java:129) at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) at com.aptana.git.ui.GitUIPlugin$GitInstallationValidatorJob.runInUIThread(GitUIPlugin.java:181) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 8 |
787 |
TISTUD-2599
|
10/22/2012 00:31:03
|
Remove "Aptana" from header of Titanium update stream index pages
|
The Titanium Studio update streams have "Aptana" in the header of the page leading to confusion. It should be replaced with "Appcelerator" * http://preview.appcelerator.com/appcelerator/studio/standalone/update/stable/ * http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/ * http://preview.appcelerator.com/appcelerator/studio/standalone/update/beta/ * http://preview.appcelerator.com/appcelerator/studio/standalone/update/nightly/
| 8 |
788 |
TISTUD-2600
|
10/22/2012 00:33:55
|
Add more space above "Enable Cloud" checkbox
|
This seems more an issue on Windows, but the text and the checkbox in the "Enable Cloud" section of the new project wizard are extremely close. There should be some vertical space there.
| 2 |
789 |
TISTUD-2602
|
10/22/2012 00:48:11
|
Indent the checkbox for the new CLI in the preference page
|
The rest of the checkboxes align with the fields. This label and checkbox should sit underneath the path field
| 2 |
790 |
TISTUD-2603
|
10/22/2012 00:54:43
|
Only display the "Install JDT" link when making an Android module
|
When creating a new Android module, if you do not have the JDT tools installed, Studio will ask you to install them. However, it should only display this link _when_ you have selected the Android radio button. I think I would also put it on the same link as the "Configure SDKs" link, perhaps separated by a pipe (|)
| 3 |
791 |
TISTUD-2604
|
10/22/2012 02:14:23
|
Windows requirements check for JDK keeps on asking to install JDK
|
(from Ingo) I'm noticing some weird behavior where I do the JDK and Android install, and then it acts as if it didn't work-still showing me the '?' Over the android and re-prompting to download the JDK. Once I restart, it goes away.
| 5 |
792 |
TISTUD-2605
|
10/22/2012 09:23:48
|
Titanium Updates on Linux: the installation is shown to be successful although it failed
|
This issue is specific on Ubuntu 12.04. If the user updates (Help > Titanium Updates) CLI, Alloy, and ACS, none of the updates are recognized as being installed, and the user is still prompted for updates, even after studio restart. Steps to Reproduce: 1. Help > Check for Titanium Updates and take all updates (CLI, Alloy, ACS). 2. Check again. Actual Result: Updates are still available, though they were already installed. Expected Result: No updates available, they were already installed.
| 8 |
793 |
TISTUD-2606
|
10/22/2012 11:53:58
|
Studio: "Computing SDK Info" problem appears in Windows 7 on restarting Studio
|
Steps To Reproduce: 1. Update studio to latest 3.0 version. 2. Now after accepting all prompts restart studio. Actual: "Computing SDK Info" or 'o while seeking ' exception appears. kindly refer Screenshot and log file. Expected: No error should appear.
| 3 |
794 |
TISTUD-2607
|
10/22/2012 13:20:06
|
Alloy: "java.lang.reflect.InvocationTargetException" internal error appears on windows 7
|
Steps To Reproduce: 1. On 3.0 latest version studio, try creating Alloy Default Project. Actual: "java.lang.reflect.InvocationTargetException" internal error appears on windows 7. Kindly refer screenshot and logs. Expected: No error must appear.
| 5 |
795 |
TISTUD-2614
|
10/22/2012 23:42:01
|
Node.ACS: Unpublish Node.ACS Service does not remove service from production
|
Node.ACS: Unpublish Node.ACS Service does not remove service from production. Log: {code} !ENTRY com.aptana.core 1 0 2012-10-22 15:31:51.779 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "unpublish" "Node.ACS" "-v" "0.1.0" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace/Node.ACS Environment: {ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8b, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk-macosx, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-EeKGAL/Render, Apple_Ubiquity_Message=/tmp/launch-SW45KT/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-9CZqFn/ServiceProcessSocket, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dhyde/Desktop/android/android-sdk-macosx/tools:/Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools, PWD=/Users/dhyde/Desktop/TISTUD-RC/workspace/Node.ACS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-0sLjqp/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} {code} Steps to Reproduce: 1. Create Node.ACS Project. 2. Publish > Deploy App. 3. Publish > Unpublish Node.ACS Service. 4. Publish > View Node.ACS Service or reenter weblink to service. Actual Result: Link is still there, app is still in production. Expected Result: Should be unable to view app service or enter website, link should be dead.
| 3 |
796 |
TISTUD-2616
|
10/23/2012 08:14:35
|
Studio Dashboard: "default" and "Default Project" does not give clear information about Alloy and Project unless description is read.
|
Steps To Reproduce: 1. On dashboard on studio 3.0, navigate to Develop tab. 2. Notice "default" and "Default Project" & "two-tabbed" and "Tabbed Application" names. Actual: User does not get clear information from names that one is alloy project and another one is Titanium project unless he reads the description below. Expected: Naming convention or icon corresponding must suggest type of Project.
| 8 |
797 |
TISTUD-2620
|
10/23/2012 13:50:39
|
Mobile Web: After successful packaging of mobile web project , the alert goes away very quickly and hence user sometimes doesn't know that packaging has done.
|
This defect is specific to Ubuntu 12.04. Steps to reproduce: 1.Launch Titanium Studio. 2. Create a titanium project. 3.Create a mobile web module. 4.Package that module in the project. 5. After packaging the module , package the mobile web project and save it to a desired location. 6.Observe the notification for "successful packaging" Actual Result: The duration for successful packaging prompt for mobile web project is too short to relise the user that the process has been completed.
| 5 |
798 |
TISTUD-2621
|
10/23/2012 14:20:47
|
About box shows "%product.name" instead of correct text for non-English versions of Studio
|
If a user is _not_ using English as the default language, they will see an issue whereby Studio is not properly replacing the About Box text and the names in the menu. h3. Steps to reproduce: # Edit your Studio configuration file (TitaniumStudio.ini, see http://docs.appcelerator.com/titanium/2.1/index.html#!/guide/Adding_Command-Line_Options) # add the option -nl pt_PT, i.e.:\\ {code} -startup ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.1.101.v20120109-1504 -nl pt_PT --launcher.XXMaxPermSize 256m {code} # Save the file # Start Studio. You will notice a few odd things, as shown in the screenshots ## The menu bar says %productName ## The %productName menu also has some missing replacements ## The help menu shows "Aptana" not "Titanium" ## The about box is wrong h3. Workaround Instead of using -nl pt_PT above, use -nl en
| 8 |
799 |
TISTUD-2622
|
10/23/2012 14:30:16
|
If About Box text is not properly replaced, Studio reports build # as "null"
|
If a user is _not_ using English as the default language, they will see an issue whereby Studio is not properly replacing the About Box text and the names in the menu. It then reports the build as "null" in the log file. h3. Steps to reproduce: # Edit your Studio configuration file (TitaniumStudio.ini, see http://docs.appcelerator.com/titanium/2.1/index.html#!/guide/Adding_Command-Line_Options) # add the option -nl pt_PT, i.e.:\\ {code} -startup ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.1.101.v20120109-1504 -nl pt_PT --launcher.XXMaxPermSize 256m {code} # Save the file # Start Studio. You will notice a few odd things ## The menu bar says %productName ## The log file will have things like (Build null) ## You won't be prompted for the newest versions of the SDK--you'll get 1.7.5 as the latest. Sample log file: {code}!ENTRY com.aptana.core 1 0 2012-10-23 06:13:05.830 !MESSAGE (Build null) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/bin/git" "symbolic-ref" "-q" "HEAD" Working directory: /Users/ingo/Documents/Projects/Aptana/KitchenSinkOld Environment: null {code} h3. Workaround Instead of using -nl pt_PT above, use -nl en
| 5 |
800 |
TISTUD-2625
|
10/23/2012 18:54:51
|
Node.ACS: space in project name causes Errors running builder 'Studio Unified Builder' on project java.lang.IllegalArgumentException
|
Creating Node.ACS project fails with: Error: {code} Errors occurred during the build. Errors running builder 'Studio Unified Builder' on project 'Node.ACS Project 1044'. java.lang.IllegalArgumentException {code} log: {code} !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.526 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "new" "Node.ACS Project 1044" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace Environment: {ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8b, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk-macosx, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-EeKGAL/Render, Apple_Ubiquity_Message=/tmp/launch-SW45KT/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-9CZqFn/ServiceProcessSocket, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dhyde/Desktop/android/android-sdk-macosx/tools:/Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools, PWD=/Users/dhyde/Desktop/TISTUD-RC/workspace, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-0sLjqp/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.850 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Searching for git in PATH locations: /usr/bin, /bin, /usr/sbin, /sbin, /usr/local/bin, /Users/dhyde/Desktop/android/android-sdk-macosx/tools, /Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.851 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/bin/git" "--version" Working directory: null Environment: null !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.894 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Found executable on PATH: /usr/bin/git !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.895 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/bin/git" "rev-parse" "--git-dir" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace/Node.ACS Project 1044 Environment: null !ENTRY com.aptana.editor.common 1 0 2012-10-23 10:44:31.235 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.editor.common/debug/presentation Initiating presentation reconciling for region at offset 0, length 590 in document of length 590 !ENTRY com.aptana.portal.ui 1 0 2012-10-23 10:44:31.284 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.portal.ui/debug/startpage Notifying the portal with: if (typeof(eventsDispatcher) !== undefined) eventsDispatcher.notify('{"event":"recentFiles","eventType":"changed","data":""}'); !ENTRY com.aptana.core 1 0 2012-10-23 10:44:31.300 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/firefox Check location /Users/dhyde/Library/Application Support/Firefox/ for default profile !ENTRY com.aptana.core 1 0 2012-10-23 10:44:31.303 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/firefox Profiles found: /Users/dhyde/Library/Application Support/Firefox/Profiles/kc9gfhqn.default !ENTRY com.aptana.core 1 0 2012-10-23 10:44:31.303 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/firefox Default profile was found at /Users/dhyde/Library/Application Support/Firefox/Profiles/kc9gfhqn.default !ENTRY org.eclipse.core.resources 4 2 2012-10-23 10:44:31.322 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException at java.net.URI.create(URI.java:841) at java.net.URI.resolve(URI.java:1027) at com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.determineMainFileURI(ACSCompileParticipant.java:211) at com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.buildFile(ACSCompileParticipant.java:88) at com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) at com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:525) at com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:436) at com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:413) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:307) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.net.URISyntaxException: Illegal character in path at index 10: ./Node.ACS Project 1044.js at java.net.URI$Parser.fail(URI.java:2810) at java.net.URI$Parser.checkChars(URI.java:2983) at java.net.URI$Parser.parseHierarchical(URI.java:3067) at java.net.URI$Parser.parse(URI.java:3025) at java.net.URI.<init>(URI.java:577) at java.net.URI.create(URI.java:839) ... 21 more !ENTRY org.eclipse.core.resources 4 75 2012-10-23 10:44:31.345 !MESSAGE Errors occurred during the build. !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-10-23 10:44:31.345 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'Node.ACS Project 1044'. !STACK 0 java.lang.IllegalArgumentException at java.net.URI.create(URI.java:841) at java.net.URI.resolve(URI.java:1027) at com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.determineMainFileURI(ACSCompileParticipant.java:211) at com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.buildFile(ACSCompileParticipant.java:88) at com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) at com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:525) at com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:436) at com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:413) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:307) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.net.URISyntaxException: Illegal character in path at index 10: ./Node.ACS Project 1044.js at java.net.URI$Parser.fail(URI.java:2810) at java.net.URI$Parser.checkChars(URI.java:2983) at java.net.URI$Parser.parseHierarchical(URI.java:3067) at java.net.URI$Parser.parse(URI.java:3025) at java.net.URI.<init>(URI.java:577) at java.net.URI.create(URI.java:839) ... 21 more {code} Steps to Reproduce: 1. Create Node.ACS project. Actual Result: Fail. Expected Result: Success.
| 5 |
801 |
TISTUD-2626
|
10/23/2012 19:40:36
|
Dashboard: Alloy templates should appear first in Templates section
|
Add a new section on the bottom, call it Alloy Templates, put the alloy templates there. The current UI is incomplete.
| 8 |
802 |
TISTUD-2629
|
10/23/2012 21:51:58
|
TiStudio: node.ACS - Tail log is using -v to specify node.ACS app version instead of -a
|
Steps to reproduce: 1. In TiStudio, create a node.ACS project 2. Publish the project 3. Right-click on the project and go to Node.ACS > Tail Logs > 0.1.0 \\ \\ Actual: Terminal console would return the following: {code} acs logcat monkeyNode -v 0.1.0 0.9.24 {code} \\ \\ Expected: Instead of -v to specify app version, -a should be used instead: {code} $ acs logcat -h Function: Tail the log entries output from your app. If no appname provided it can run in project dir or with -d to specify a project dir. 'logcat -h' for more options. Usage: logcat [options] [appname] Options: -h, --help output usage information -a, --appversion <version> App version --interval <interval> Set refresh inteval for logcat {code} \\ \\ Note: To work around this, use *acs logcat -a <APP_VERSION>*
| 2 |
803 |
TISTUD-2630
|
10/23/2012 22:27:41
|
Preferences: closing titanium preferences before android sdk list loads throws exception
|
Preferences: closing titanium preferences before android sdk list loads throws exception. Error: {code} An internal error has occurred. java.lang.NullPointerException {code} Steps to Reproduce: 1. Open Titanium Studio > Titanium preferences. 2. When android sdk is still loading in the sdk list, close preferences window. Actual Result: Error. Expected Result: Window closes without error.
| 5 |
804 |
TISTUD-2632
|
10/23/2012 23:08:59
|
Editing and saving tiapp.xml while project is indexing hangs Studio
|
Importing KitchenSink, changing the sdk version, and saving the change in tiapp.xml while the project is indexing results in save failure. Studio hangs during this scenario. Core exceptions in log, out of sync. Could be related to TISTUD-2490. Steps to Reproduce: 1. Import KitchenSink from the samples. 2. change the sdk version in tiapp.xml and save. Actual Result: Fail to save. Expected Result: Save.
| 8 |
805 |
TISTUD-2633
|
10/24/2012 00:25:33
|
Studio: Ubuntu- Node permission dialogs for acs and alloy install are transparent.
|
While testing the dev preview on Linux, I was prompted for permission to install acs, CLI, and alloy. Each had a window in a window with a transparent background. See images attached. Steps to reproduce: 1) Install the dev preview studio version 2) If not prompted, click "check for titanium updates" Result: Window appears for each permission request with transparent background. Expected: Beautiful dialogs
| 5 |
806 |
TISTUD-2634
|
10/24/2012 00:31:02
|
Studio: Ubuntu- npm install displays some odd characters during install
|
While testing the dev preview, during the npm installs, the dialog displays many odd things that seem to correlate to the console output you would see when running from the command-line. During one of the installs, as the attached image shows, some odd characters are displayed. Steps to reproduce: 1) Install studio dev preview version 2) Check for titanium updates 3) Grant permission for install 4) watch progress Result: Odd characters shown Expected: No odd characters.
| 5 |
807 |
TISTUD-2643
|
10/25/2012 00:21:28
|
Android Distribution Wizard: android sdk preferences not respected
|
Android Distribution Wizard: android sdk preferences not respected, lists other android sdk. The android sdk preferences are correct, and the run configuration menu for packaging is correct, but the package > distribute android wizard lists the wrong android sdk. This is a regression. Does not occur in Studio 2.1.2. Steps to Reproduce: 1. Set Android SDK in preferences. 2. Clear existing distribution run configurations. 3. Packaging > Android Distribution. Actual Result: Wizard lists different android sdk than in the preferences, or what would appear if a new distribution run config were created. Expected Result: Android Publishing wizard android sdk should match preferences and new distribution run config entry.
| 5 |
808 |
TISTUD-2644
|
10/25/2012 03:16:47
|
Node.JS: node module commands in empty /usr/bin/ folders are falsely detected by studio
|
Node.JS: node module commands in empty /usr/bin/ folders are falsely detected by studio. Manifests as null pointer exception when creating alloy project, etc. Note that npm is usually installed in /usr/local/bin Log: {code} !ENTRY com.aptana.core 1 0 2012-10-24 17:30:12.917\ !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process:\ Process: "/usr/bin/alloy" "new" "/Users/gtavridis/Documents/Titanium Studio Workspace/testapp5" "default"\ Working directory: null\ Environment: \{ANALYTICS_SOURCE=studio, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-pwIDrd/Render, Apple_Ubiquity_Message=/tmp/launch-iPVDau/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer, DISPLAY=/tmp/launch-Kdr69A/org.x:0, HOME=/Users/gtavridis, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=gtavridis, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin, PWD=/Applications/Titanium_Studio/TitaniumStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-D3IT5p/Listeners, TMPDIR=/var/folders/6g/7gkd364s4bd3_rq7891qgt000000gp/T/, USER=gtavridis, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI\}\ \ !ENTRY com.aptana.projects 2 0 2012-10-24 17:30:40.252\ !MESSAGE Internal error: \ !STACK 1\ org.eclipse.core.runtime.CoreException: \ at com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:253)\ at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)\ at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)\ at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304)\ at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)\ Caused by: java.lang.reflect.InvocationTargetException\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:310)\ at com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249)\ ... 4 more\ Caused by: org.eclipse.core.runtime.CoreException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:344)\ at com.appcelerator.titanium.mobile.ui.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:118)\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:306)\ ... 5 more\ Caused by: java.io.IOException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)\ at com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327)\ at com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322)\ at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273)\ at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235)\ at com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:202)\ at com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:108)\ at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$AlloyTemplate.apply(AlloyTemplateInstaller.java:79)\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341)\ ... 7 more\ Caused by: java.io.IOException: error=13, Permission denied\ at java.lang.UNIXProcess.forkAndExec(Native Method)\ at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)\ at java.lang.ProcessImpl.start(ProcessImpl.java:91)\ at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)\ ... 15 more\ !SUBENTRY 1 com.aptana.projects 4 0 2012-10-24 17:30:40.255\ !MESSAGE \ !STACK 0\ java.lang.reflect.InvocationTargetException\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:310)\ at com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249)\ at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)\ at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)\ at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304)\ at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)\ Caused by: org.eclipse.core.runtime.CoreException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:344)\ at com.appcelerator.titanium.mobile.ui.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:118)\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:306)\ ... 5 more\ Caused by: java.io.IOException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)\ at com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327)\ at com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322)\ at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273)\ at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235)\ at com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:202)\ at com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:108)\ at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$AlloyTemplate.apply(AlloyTemplateInstaller.java:79)\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341)\ ... 7 more\ Caused by: java.io.IOException: error=13, Permission denied\ at java.lang.UNIXProcess.forkAndExec(Native Method)\ at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)\ at java.lang.ProcessImpl.start(ProcessImpl.java:91)\ at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)\ ... 15 more\ Root exception:\ org.eclipse.core.runtime.CoreException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:344)\ at com.appcelerator.titanium.mobile.ui.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:118)\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:306)\ at com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249)\ at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)\ at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)\ at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304)\ at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)\ Caused by: java.io.IOException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)\ at com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327)\ at com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322)\ at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273)\ at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235)\ at com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:202)\ at com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:108)\ at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$AlloyTemplate.apply(AlloyTemplateInstaller.java:79)\ at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341)\ ... 7 more\ Caused by: java.io.IOException: error=13, Permission denied\ at java.lang.UNIXProcess.forkAndExec(Native Method)\ at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)\ at java.lang.ProcessImpl.start(ProcessImpl.java:91)\ at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)\ ... 15 more\ {code} Steps to Reproduce: 1. Create an empty folder in the following locations: "/usr/bin/alloy" "/usr/bin/npm" "/usr/bin/acs" "/usr/bin/titanium" 2. Try to run studio, create these projects, check for titanium updates, or enable the cli. Actual Result: Fail with permission error. Expected Result: Studio should ignore these false files and run existing npm packages.
| 3 |
809 |
TISTUD-2645
|
10/25/2012 18:41:49
|
JS Content assist is only looking up members of Window for global namespace
|
When we lookup globals for Content Assist we explicitly look for members of Window. This is wrong, because we also need to look up members of it's supertype Global.
| 5 |
810 |
TISTUD-2646
|
10/25/2012 18:42:27
|
JS Content Assist doesn't contain ECMAScript 5 types/properties
|
There are no entries for things like JSON.parse, JSON.stringify, Date.now, etc in our metadata. We need to add metadata for the new items added in ECMAScript 5. See http://kangax.github.com/es5-compat-table/ and http://www.ecma-international.org/ecma-262/5.1
| 20 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.