issuekey stringlengths 8 11 | title stringlengths 16 187 | description stringlengths 10 20k ⌀ | storypoint int64 1 40 | split_mark stringclasses 1
value |
|---|---|---|---|---|
TISTUD-2522 | 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='... | 3 | train |
TISTUD-2524 | Unable to install project on device - CLI path is not being located. | An Exception error during project installation, could not locate the CLI path. See an attachment. Tried to run 2.1.3 - the same error | 8 | train |
TISTUD-2568 | No logs are shown in Studio when building Mobile Web using the new CLI | When builds are run in TiStudio, via the new CLI, for iOS and Android, build logs show up in the console window as expected. This does not happen for mobileweb. Mobileweb shows absolutely nothing in the console window. The build process is working, but it is showing no output, which could be critical for developers deb... | 8 | train |
TISTUD-2527 | 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.' '... | 5 | train |
TISTUD-2531 | 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. ... | 5 | train |
TISTUD-2535 | 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 !ME... | 5 | train |
TISTUD-2537 | content-assist: Doc pages show broken links | When testing the deprecation fixes in SDK, I noticed that studio is now displaying links (yay!) except that they don't go anywhere (boo!). Specifically, Studio used to strip out tags, so we didn't bother to in the JSCA. So links to Titanium types, for example, show up as something like this: {code} <a href="Tita... | 8 | train |
TISTUD-2538 | NPM: npm install not validated on studio startup | When studio first starts, the npm is not prompted to install if it is not installed, this will prevent Alloy, CLI, and ACS from installing. Note this is not a typical use case and npm is assumed to be installed along with node.js. This is an improvement that would make studio a bit more robust. Studio Error Log: ... | 5 | train |
TISTUD-2539 | JS Parser Validation: Failed to parse file Cannot recover from the syntax error | Saw this in the log. I created two projects, inserted two breakpoints, and ran both in android device. They were default projects, one with an extra event listener. Log: {code} !ENTRY com.aptana.editor.js 4 0 2012-10-16 15:29:36.290 !MESSAGE (Build 3.0.0.201210151149) [ERROR] Failed to parse file:/Users/dhyde/... | 3 | train |
TISTUD-2540 | 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 !S... | 8 | train |
TISTUD-2541 | 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 Re... | 5 | train |
TISTUD-2545 | 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 t... | 5 | train |
TISTUD-2542 | Android Device Debugger: empty project console view appears | When android debug on device is run, the empty project console view blocks the console log view. Does this empty view serve a purpose? Steps to Reproduce: 1. Debug in Android Device. Actual Result: Empty project console view appears, no console log output, appears broken. Expected Result: Console log ... | 5 | train |
TISTUD-2544 | No Alloy templates appear in Titanium project wizard when the alloy installation path differs from default | Gabe has an issue where alloy is getting installed into /opt/local/bin and /opt/local/lib/node_modules instead of the default /usr/local directory, probably due to the $PATH he has set in the system. When that happened, opening New > Titanium Project would show no Alloy project templates, even after we created symlinks... | 8 | train |
TISTUD-2546 | 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 al... | 5 | train |
TISTUD-2549 | Sync common preferences between Studio and titanium CLI | I'm not sure if CLI wants us to be setting global values in config to match or not, but I'm guessing by default we should sync up the values for things like Android SDK path. If a user sets the path in Titanium Studio we should pass that along to the CLI to store as well. We may also need to do the reverse on startup -... | 8 | train |
TISTUD-2550 | 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 mat... | 8 | train |
TISTUD-2553 | 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 u... | 5 | train |
TISTUD-2559 | 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: ... | 8 | train |
TISTUD-2561 | 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/Deskt... | 8 | train |
TISTUD-2562 | 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 '/us... | 5 | train |
TISTUD-2563 | Add extension point for contributing programmatic project templates | Currently we "hack" in support for alloy templates by registering templates programmatically during an IStartup. We really should have a way to register templates using some extension point so that they get loaded on-demand when we gather up templates. Using an IStartup is hacky and forces the alloy UI plugin to load o... | 8 | train |
TISTUD-2564 | 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 mod... | 8 | train |
TISTUD-2565 | 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 gui... | 8 | train |
TISTUD-2569 | 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 s... | 3 | train |
TISTUD-2570 | 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. {... | 8 | train |
TISTUD-2573 | Studio should not ask for password when updating Titanium SDK | This is a regression. Steps to reproduce: 1. Remove 2.1.3 SDK from the Titanium SDK folder; 2. Run Help > Check for Titanium Updates; 3. If there are other updates (CLI/Alloy/ACS) shown in the dialog, uncheck them to leave only Titanium SDK checked; 4. Click Install. Expected result: Studio should install S... | 3 | train |
TISTUD-2575 | 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 sud... | 5 | train |
TISTUD-2576 | 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 h... | 13 | train |
TISTUD-2577 | Troubleshooting: add select and deselect all to debug specific component | Troubleshooting: add select and deselect all to debug specific component checkboxes | 5 | train |
TISTUD-2578 | 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... | 13 | train |
TISTUD-2582 | 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 | train |
TISTUD-2587 | 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... | 13 | train |
TISTUD-2590 | Progress view appears on the right instead of at the bottom in simple Studio perspective | When in simple Studio perspective, clicking on the progress indicator in the status bar opens Progress view to the right of the editor area, instead of below the editor area like the extended Studio perspective has. We should set the placeholder for the views in the simple perspective. | 5 | train |
TISTUD-2591 | Webserver core plugin starting too slowly | After updating from Studio 2.1.2 to the latest 3.0.0 RC, I saw the following exception in the log after restart: {code} !ENTRY org.eclipse.osgi 2 0 2012-10-20 18:30:17.474 !MESSAGE While loading class "com.aptana.webserver.core.IServerManager", thread "Thread[Worker-13,5,main]" timed out waiting (5001ms) for threa... | 5 | train |
TISTUD-2592 | 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... | 8 | train |
TISTUD-2593 | 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 ... | 3 | train |
TISTUD-2594 | 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 sh... | 8 | train |
TISTUD-2599 | 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.app... | 8 | train |
TISTUD-2600 | 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 | train |
TISTUD-2602 | 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 | train |
TISTUD-2603 | 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 | train |
TISTUD-2604 | 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 | train |
TISTUD-2605 | 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 ... | 8 | train |
TISTUD-2606 | 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 | train |
TISTUD-2607 | 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 | train |
TISTUD-2612 | Clicking Titanium Update toast while 'titanium' cli is being installed in Terminal hangs Studio | I started up Titanium Studio with Node.JS installed. On startup, it began installing 'titanium' CLI automatically in a Terminal view (off to the right, rather than along to bottom right like a console). While it was running, the Titanium SDK Update toast popped up. I clicked it. It hangs the IDE for around a minute. It... | 5 | train |
TISTUD-2614 | 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" "-... | 3 | train |
TISTUD-2615 | Node ACS success URL says "OK" | After publishing a Node.ACS to the server I get a confirmation which normally has the URL where the service is located. Instead I get an OK link that does not lead anywhere. This is a regression as this functionality worked in 3.0.0. Steps to reproduce: 1. Create a Node.acs service (attached to a project or on i... | 3 | train |
TISTUD-2616 | 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 descripti... | 8 | train |
TISTUD-2620 | 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 f... | 5 | train |
TISTUD-2621 | 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/... | 8 | train |
TISTUD-2622 | 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://d... | 5 | train |
TISTUD-2625 | 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.20121... | 5 | train |
TISTUD-2626 | 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 | train |
TISTUD-2629 | 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... | 2 | train |
TISTUD-2630 | 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 pr... | 5 | train |
TISTUD-2632 | 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. cha... | 8 | train |
TISTUD-2633 | 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: Wi... | 5 | train |
TISTUD-2634 | 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 studi... | 5 | train |
TISTUD-2636 | Windows 7 Installer takes 10 seconds to load | Running titaniumstudio.exe installer takes 10 seconds to launch with no ui action. | 5 | train |
TISTUD-2643 | 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... | 5 | train |
TISTUD-2644 | 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.20121022... | 3 | train |
TISTUD-2645 | 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 | train |
TISTUD-2646 | 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 | train |
TISTUD-2647 | Window type is used as global namespace for all JS files | We explicitly make use of "Window" as the assumed global namespace for all JS files. This is only correct if the file is intended to be run inside a browser. With the use of TiMobile JS and Node.JS, in that environment, "Global" is the type we should be querying - not Window. We may need to alter indexing/CA to d... | 8 | train |
TISTUD-2650 | Studio locks when packaging a MobileWeb app | When packaging a MobileWeb app using the Packaging Wizard, the Studio locks and the progress bar is showing that the process is waiting. The only way to get out of it is to restart. | 8 | train |
TISTUD-2653 | Dashboard: Configure: MobileWeb: configure link open general browser settings instead of mobileweb runtime settings | Dashboard > Configure > MobileWeb > 'here' opens General Browser Preferences instead of MobileWeb sdk runtime preferences. | 3 | train |
TISTUD-2654 | Android: pass in jdk bin to python scripts | If jdk bin is not on the path, the android build scripts will fail. Studio needs to pass in this variable to the python scripts so the user does not have to set the path. Build Console: {code} [INFO] logfile = C:\Users\tester\Desktop\TISTUD-RC\workspace\Project\build.log [INFO] Building Project for Android .... | 5 | train |
TISTUD-2666 | Content overlay - icon, description etc for Denso turbo brand | null | 8 | train |
TISTUD-2676 | Windows installer: installer shows old splash screen on startup. | The Titanium Studio 3.0.0.201210271747 installer shows the old splash screen before loading the new installer. Steps to reproduce: 1. Install Titanium Studio on Windows 7. Expected results: The install should flash the new splash screen. Actual results: The installer flashes the old splash screen. | 2 | train |
TISTUD-2677 | Run Diagnostic Test: improve diagnostics to include more fields and better format for testing | Currently the diagnostic log needs a core set of fields at the top that can be used for bug environments (see this bug environment for ideal/suggested/proposed example). Suggested Top Fields: {code} Host OS: Mac OS X Host OS Version: Mountain Lion 10.8.2 // different format w/new info Android SDK Version: r20.... | 8 | train |
TISTUD-2678 | JSCodeScanner: Token not mapped: 7 warnings in log for large text file | When a large file is edited in Studio, there are many of these warnings in the log: {code} !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"Close Window"<< !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE... | 8 | train |
TISTUD-2679 | Unhandled event loop exception Java heap space crash and freeze when editing large file | Editing the large attached file reliably crashes and freezes studio. 3 system crash logs attached. Studio often will crash when it reloads after the first crash. This does not occur with Studio 2.1.2, but there is some slow-down. Steps to Reproduce: 1. Edit large attached file in studio. 2. Scroll top to b... | 8 | train |
TISTUD-2688 | iOS: Ti.API: some console logging calls with array args do not print array to console | Some console logging calls with array args do not print array to console. The cases are: Ti.API.log('freeform', ['arg0', 'arg1']) and Ti.API.timestamp(['arg0', 'arg1']) This does not occur in MobileWeb or Android. This is a parity issue. This does not occur to other array printing calls in iOS. This is... | 8 | train |
TISTUD-2689 | Project Explorer: file not visible when pasted into project from filesystem until after project refresh | If a file is pasted into a project from the filesystem, the file is not visible until the project is refreshed. This is a regression. This did not occur in Studio 2.1.2. No errors in log. Steps to Reproduce: 1. Create a Titanium Project. 2. View in Project Explorer. 3. Copy/Paste a .js file from the filesyst... | 5 | train |
TISTUD-2694 | Adopt AppDirect call with more module information | We want to utilize more information from the AppDirect call: -Module url -publish date -developer name -description -overview | 5 | train |
TISTUD-2695 | Adopt AppDirect call to compare version numbers correctly | We want to utilize the formatted version information from the AppDirect call The new format would be: Multiple versions: [{"name":"Admob module","productType":"MODULE","status":"ACTIVE","url":""," imageUrl":"","version": {"ios": "1.3","android: "2.0.1"} ] Single version for all platforms: [{"name":"Admob modu... | 5 | train |
TISTUD-2696 | Adopt AppDirect module uuid field | The AppDirect call now returns module ids. We need to compare the module ids with the ones returned from the modulesInfo portal call to properly label modules with the status buttons. | 5 | train |
TISTUD-2698 | Console: no colors on new lines in debug output | Console: no colors on new lines in debug output (see screenshot). Steps to Reproduce: 1. Run code: {code} Ti.API.trace('line0\nline1\nline2\nline3'); Ti.API.trace(['Ti.API TRACE', 'ARG1', 'ARG2']); Ti.API.debug('line0\nline1\nline2\nline3'); Ti.API.debug(['Ti.API DEBUG', 'ARG1', 'ARG2']); Ti.API.inf... | 8 | train |
TISTUD-2699 | Add CLI command support for packaging a iOS Titanium Module | Add support for the packaging command via the CLI extension. V1: {code} project-dir/build.py Working directory: [project-dir] {code} V2: {code} titanium build --package [project-dir] {code} | 8 | train |
TISTUD-2713 | CLI: remove UI for switching build scripts, should be command line only | Remove UI in Preferences > Titanium to toggle CLI. CLI should be command line only as per Ingo. | 3 | train |
TISTUD-2714 | Change the wizard image in Update wizard to look like an installer image | null | 8 | train |
TISTUD-2715 | Add user id field to the password sudo page in Update wizard | null | 3 | train |
TISTUD-2716 | Changing focus to AppExplorer with Node.ACS project calls acs list ~20 times | Steps: 1. Create a Node.ACS project 2. Open the App Explorer 3. Enable troubleshooting for all debug/error messages 4. Change the focus from an editor to the App Explorer Expected Results: At most one call to acs list Actual Results: 20 calls of the following: !ENTRY com.aptana.core 1 0 2012-11-05 15:51:... | 8 | train |
TISTUD-2717 | NPE when running on iOS device | When Clayton tested in Mac OS 10.8.2 using Titanium Studio, build: 3.1.0.201211021811, he saw the following error when building for device: {code} !ENTRY org.eclipse.core.jobs 4 2 2012-11-05 14:11:58.663 !MESSAGE An internal error occurred during: "Launching Titanium iOS on Device - IOS_no_ACS (1)". !STACK 0 java.... | 2 | train |
TISTUD-2718 | Improve the first page of Update wizard | 1. Grey out 'Titanium SDK' field in the installer main page to indicate that it is mandatory and as the user can not de-select it and add " (required)" to the text. This should only apply to the case where user doesn't have a SDK installed; if a SDK already exists, the field will be de-selectable. 2. The text of Nod... | 5 | train |
TISTUD-2720 | Titanium Updates: change sudo prompt to mock system modal dialog | Change studio 3.0.1 sudo prompt to a modal dialog (that existed in studio 3.0.0). This is a regression, studio 3.0.0 had a nice system-style dialog. See screenshots. Steps to Reproduce: 1. Uninstall the CLI (or ACS, Alloy, NodeJS). 2. Open Studio. Take Titanium Updates. Actual Result: Sudo prompt appear... | 5 | train |
TISTUD-2726 | Windows 8: Errors running builder 'Studio Unified Builder' on project,URI is not absolute | While testing TISTUD-2625 on Windows I ran hit this error: {code} Errors occurred during the build. Errors running builder 'Studio Unified Builder' on project 'RSS Reader'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'SDK213'. URI is not absolute Errors running builder 'Studio ... | 5 | train |
TISTUD-2730 | The toast popup after successfully installing npm packages should show version numbers | When NodeJS is not installed on the system along with our npm packages, the update dialog will show N/A in the version column since we don't have a way to query for version without npm. That is OK; however, after they are installed, we should display the versions in the toast since now we could query for them. | 5 | train |
TISTUD-2733 | Investigate if we can create local npm package with all dependencies | From Chris: "npm pack can create a tarball that we can use to install. Need to investigate if this also includes dependencies underneath it.“ | 8 | train |
TISTUD-2735 | Alloy: add alloy icon to alloy project context menu commands | Alloy project context menu commands are missing the alloy icon. In contrast, Node.ACS project context commands have the Node.ACS icons. The current behavior looks odd. Steps to Reproduce: 1. Create Alloy project. 2. Right click on the project and select 'New'. Actual Result: Alloy commands have no icon, ar... | 5 | train |
TISTUD-2739 | Have a separate update site for Node.ACS feature | We want the base Titanium Studio continue to include Node.ACS feature, but have a separate update site defined for Node.ACS so it could update on its own without updating the whole Studio. We should also verify it will still work when later on we update Studio overall. | 3 | train |
TISTUD-2741 | Node.ACS Service: publish does not include save prompt | When publishing a node.acs service from a titanium app, there is no prompt to save dirty files. Steps to Reproduce: 1. Create Titanium app. 2. Create New Node.ACS Service within Titanium app (project right-click > New > Service). 3. Edit acs <main>.js or package.json file without saving. 4. Publish > Node.ACS ... | 5 | train |
TISTUD-2743 | Node.ACS: Can not import removed Node.ACS project | After removing (but not deleting) an ACS Node project that has been published from the workspace, Titanium studio can not import the project. The import project wizard does not have an ACS project choice, and trying to promote the folder to a project throws the following error: {code} !ENTRY org.eclipse.ui 4 0 2012-1... | 5 | train |
TISTUD-2744 | Node.JS: allow studio to recover from failed node updates | Allow studio to recover from failed node.js module updates. For example: {code} I updated the cli at the same time as updating studio and the cli update failed, resulting in a missing /usr/local/bin/titanium alias. Any further runtime-related studio commands started to fail (run on simulator). Checking for updat... | 5 | train |
TISTUD-2746 | Node.ACS: open main js file and json file when project is first created | Node.ACS: open main js file and json file when project is first created. This applies both to a Node.ACS Project and Titanium Project with New Node.ACS Service. This is usability and parity issue with Titanium Projects as app.js and tiapp.xml open when a Titanium Project is first created. Steps to Reproduce: ... | 5 | train |
TISTUD-2748 | Node.ACS: Publish: deployment options lack icons | Node.ACS Project and Service Publish deployment options lack icons. See screenshots. The only exception is Node.ACS Service does have an icon. This is a parity issue as all other Titanium deployment options have icons. Steps to Reproduce: 1. Create Node.ACS Project or Service. 2. Select Publish > ... Ac... | 2 | train |
TISTUD-2750 | Improve the iOS debug on device build error message prompt | When an iOS debug on device session fails due to a fatal "Check dependencies" error, we display a generic message that tells the user to look at the console in order to understand what went wrong. Once TIMOB-11710 is done, we'll be able to easily grab the error reason from the launch error-stream and display that to ... | 5 | train |
TISTUD-2752 | Make the Node.ACS server Run configuration private | The discussion stemmed from parity on having Run > Run Configuration... menu for Node.ACS project. We decided to implement the following two things: 1. Make the launch configuration for running local Node.ACS server private; 2. Add "Edit Node.ACS Server Settings..." under Run menu to allow user to edit the server s... | 2 | train |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.