issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-2300
|
Alloy: Cannot create migration files with the same name
|
I cannot generate more than one migration file in Titanium Studio using the Alloy Feature plugin. I receive the warning: " A Migration 'book' already exists." However, all migration files have the same base name only the datetime changes. Reproduction: Create a new Alloy project in Titanium Studio. Perform the steps twice with the same migration name: # Right-click on your project in App or Project Explorer. # Select New > Alloy Migration. The New Migration dialog box will appear. # In the Migration name textbox, enter the name of the migration. # Click the OK button.
| 3 |
train
|
TISTUD-2301
|
Pass in multiple IP addresses to debugger command
|
During the packaging of an app for debugging on device, we need to amend the request with a list of the current IP addresses assigned to the machine (excluding loopback addresses) Format: host:port:id:hosts where hosts will be coma separated values. For iOS on device debugging, this is going to be "::id:ip,ip,ip,ip"
| 8 |
train
|
TISTUD-2307
|
Detect Alloy project on import and set project nature accordingly
|
On project import, Studio should detect whether the project is an Alloy project or a traditional project and set the nature accordingly. Scanning for the presence of files (e.g. /app/config.json) might be sufficient. The Alloy team might have better thoughts on reliable detection.
| 8 |
train
|
TISTUD-2311
|
Studio: Build for device and packaging show a list of simulators instead of SDK.
|
While investigating issues discovered with Xcode 4.5, it became clear that what we were seeing as a bug where the SDK scripts were ignoring what was set as iOS SDK during Studio build for device or packaging was actually Studio displaying a list of simulator versions. This option should show either the actual list of SDK versions. The result of setting something other than an available SDK is that the setting is ignored. Since this is a list of emulators, this happens nearly every build (unless you choose a version where you have both simulator and SDK). This is not a regression, it occurs in many previous versions. Steps to reproduce: 1) Ensure xcode-select path and Studio preference are in sync. (refresh and restart Studio if required) 2) run terminal command "xcodebuild -showsdks" for later comparison 3) Create a new project in Studio and attempt to build for device. 4) Note pull-down options Result: Pull-down contains a list of simulators. Check the xcodebuild results which should be something like: {code} OS X SDKs: Mac OS X 10.7 -sdk macosx10.7 OS X 10.8 -sdk macosx10.8 iOS SDKs: iOS 6.0 -sdk iphoneos6.0 iOS Simulator SDKs: Simulator - iOS 5.0 -sdk iphonesimulator5.0 Simulator - iOS 5.1 -sdk iphonesimulator5.1 Simulator - iOS 6.0 -sdk iphonesimulator6.0 {code} Expected: A list of SDKs.
| 5 |
train
|
TISTUD-2316
|
Project Explorer: can't copy/paste files from project explorer to filesystem
|
Cannot copy/paste files from Project Explorer to Finder. Screenshot attached. Error is: 'The items on the Clipboard can't be pasted to this location. One or more of the items may have been deleted or are no longer available' Steps to Reproduce: 1. Select a file in the project explorer. 2. Press 'Copy'. 3. Click on the Desktop, press 'Paste'. Actual Result: OS Error, file not found. Expected Result: File should be copied pasted.
| 8 |
train
|
TISTUD-2318
|
When Android Device debugging is ready, Studio should display a prompt to start the app on the device
|
Currently, when the device is ready for debug, the only indicator is in the Console log (which is not very noticeable). Ideally, we should start the app like when we debug on emulator. But if that's not feasible, we should display a prompt to users to start the app like: "Application installed. Launch the app from the device to start debugging" We should accompany this with a checkbox that essentially says "Don't ask me again". Using the device debugging for the first time, I was unaware I had to start the app.
| 5 |
train
|
TISTUD-2321
|
Change Android debug/run on device launch configuration names
|
Currently, both the Android install on the device and debug on device are both using the same launch configuration type : Titanium Android Application Installer". The name doesn't really apply to Debug on device, since "Application Installer" implies something different. I suggest changing it to "Titanium Android On Device"
| 5 |
train
|
TISTUD-2322
|
Canceling Android Emulator/Application Installer processes does not stop/remove process from Debug view
|
During failed attempts to start debugging on both android debugger and device, I am left with multiple launch entries in the Debug view that appear to be running. When I try to cancel/stop the processes, it does nothing. The emulators and devices have been killed or disconnected. See screenshot. There are no errors in the error log
| 8 |
train
|
TISTUD-2325
|
"Configure Workspace Settings..." linked to the last opened preference page
|
Link is directed to a different window in Titanium Studio 3.0.0 This is a regression, this does not affect Studio 2.1.2. Steps to Reproduce: 1. Create Ti.Mobile Project 2. Right Click on created project and select Properties 3. Select "Formatter"and click on "Configure Workspace Settings..." Actual Result: iOS Certification and Provisioning window. Expected Result: Should open the global formatter preference page window.
| 5 |
train
|
TISTUD-2326
|
Fail to write metadata for properties.index in Windows Environment.
|
Creating default Ti.Mobile Project, Fails to write metadata for properties.index This is a regression. Steps to Reproduce: 1. Create default Titanium Mobile Project 2. Click on tiapp.xml Actual Result: Could not write Metadata Expected Result: tiapp.xml code.
| 3 |
train
|
TISTUD-2327
|
iOS debug on device should be one debug launch configuration
|
When debugging on device, Studio launches two launch configurations (see screenshot). This makes it confusing to the user since the first launch configuration (Install on device) finishes and terminates, and another launch configuration is launched. There should only be one launch configuration and it should contain both the app installation and debug processes
| 8 |
train
|
TISTUD-2331
|
Upgrade to JIRA 5 broke our JIRA support
|
Apparently we've upgraded to JIRA 5 this weekend, which is breaking our JIRA support (at the very least, our unit test is now failing). We likley need to move to using the JIRA 5 REST API.
| 13 |
train
|
TISTUD-2333
|
Android Device Debugger: Failure to launch Android emulator
|
The following issue results from trying to debug on emulator on android in Windows 7: {noformat} [INFO] logfile = C:\Users\qatester\My Documents\Titanium_Studio_Workspace\android1\build.log [DEBUG] C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py emulator android1 C:\SDK C:\Users\qatester\My Documents\Titanium_Studio_Workspace\android1 com.shastaqa.android1 8 WVGA854 armeabi-v7a [TRACE] app property, ti.ui.defaultunit : system [INFO] Launching Android emulator...one moment [DEBUG] From: C:\SDK\tools\emulator.exe [DEBUG] SDCard: C:\Users\qatester\.titanium\android2.sdcard [DEBUG] AVD ID: 8 [DEBUG] AVD Skin: WVGA854 [DEBUG] SDK: C:\SDK [DEBUG] C:\SDK\platform-tools\adb.exe start-server [ERROR] Invalid switch - /tmp\temp-android-tool\lib\x86 [ERROR] The syntax of the command is incorrect. [ERROR] Exception occured while building Android project: [ERROR] Traceback (most recent call last): [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py", line 2258, in <module> [ERROR] builder.run_emulator(avd_id, avd_skin, avd_name, avd_abi, add_args) [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py", line 485, in run_emulator [ERROR] avd_name = self.create_avd(avd_id, avd_skin, avd_abi) [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\builder.py", line 408, in create_avd [ERROR] available_avds = avd.get_avds(self.sdk) [ERROR] File "C:\Users\qatester\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20120924114913\android\avd.py", line 23, in get_avds [ERROR] for line in run.run([sdk.get_android(),'list','target'],debug=False).split("\n"): [ERROR] AttributeError: 'NoneType' object has no attribute 'split' {noformat} Steps to reproduce: 1. Create a new Android project. 2. Debug on emulator. Expected result: Android emulator should begin and debugging should proceed normally. Actual result: Process throws the above error then tries to relaunch the fastdev server.
| 8 |
train
|
TISTUD-2335
|
iOS device debugging logging messages does not honor console log level
|
The log messages during iOS device debugging does not get filtered properly. Steps: 1. Set the log level to Debug 2. Run the device debugging that outputs Trace and Debug messages Expected Results: Only Debug messages are displayed Actual Results: Both Trace and debug message are displayed
| 8 |
train
|
TISTUD-2340
|
Validate app icon in tiapp.xml
|
Restrict the icon to standard app store guidelines.
| 8 |
train
|
TISTUD-2341
|
'Web Browser Editor' Shows 'Eclipse' icon on top right side.
|
'Web Browser Editor' Shows 'Eclipse' icon on top right corner, Should be replaced by 'Appcelerator' icon and on click it should open the Appcelerator web site. Steps to Reproduce: 1. Open Titanium Studio 2. Click on 'Window' Menu bar and Select 'Show View' 3. Click ' Web Browser Editor' Actual Result: The Web Browser Editor opens with an Eclipse icon on top right corner. On click it's Opens the Eclipse Web Site. Expected Result: Appcelerator Icon. On click opens Appcelerator Web Site.
| 5 |
train
|
TISTUD-2344
|
Alloy templates should denote "beta"
|
The Alloy templates should be displayed as follows: Alloy (Beta) The tag/category and the template title/description should also denote "beta"
| 3 |
train
|
TISTUD-2345
|
Display deprecation status of JS CA proposals
|
We currently do not show any sort of indicator that a particular method/property/type/event is deprecated in our CA proposals and popup. JDT uses a strikethrough overlay on the proposal icon, and in the additional info popup, it shows "Deprecated" in bold at the top followed by the text after the @deprecated tag all in italics.
| 8 |
train
|
TISTUD-2346
|
Add our project shortcuts to File > New in Debug Perspective
|
While in the debug perspective, the file > New menu does not contain the usual options (Titanium Project, Titanium Module, Web Project, etc.). Steps to reproduce: 1. Open Titanium Studio 2. Switch to the Debug Perspective (Window > Open Perspective > Debug) 3. Open the New Menu Dropdown (File > New) Expected result: This menu should match the Studio Perspective's choices. Actual result: Only the generic Project and File choices appear.
| 3 |
train
|
TISTUD-2347
|
Debugger: Process does not always gain focus when session is launched
|
In Debug Perspective, the app thread/process does not always gain focus when session is launched. This is intermittent, and is more likely to occur if there are previously existing terminated debugging sessions in the thread view. This is a usability issue because the debugger controls cannot be active unless the correct thread is selected. See screenshots. Steps to Reproduce: 1. Launch a debugging session. 2. When a breakpoint is hit, click on a line (in Debug View) that is different than the default selected thread. 3. Repeat step 1. Actual Result: Intermittently the correct thread in the Debug View is not selected when the first breakpoint is hit. Expected Result: The correct thread should always be selected whenever a debugging session is launched and the first breakpoint is hit. The debugger controls should be active (e.g., Step Into, Step Over, etc.).
| 8 |
train
|
TISTUD-2355
|
Doubled Copy/Edit/Delete/Paste right-click menu entries
|
I'm often seeing doubled entries for simple cut/copy/paste/delete entries in the right-click context menu in the Project Explorer.
| 8 |
train
|
TISTUD-2356
|
Update iOS device debugging status to display an animated 'start app' image
|
When performing the debug on iOS device using the wizard, the status will be displayed as the app is built and installed. When the 'Start app' step is the current step, we need to remove the step control and replace it with an animated gif of an app starting on a device.
| 8 |
train
|
TISTUD-2357
|
Project Wizard: Template names offset in Ubuntu 12.04
|
Template names are off center in the new project wizard, see screenshot for more details. Steps to reproduce: 1. Open the new Titanium project wizard (File > New > Titanium Project) 2. Click on one of the templates Expected result: Template name should be centered under template image. Actual results: Template names are offset under their associated images.
| 5 |
train
|
TISTUD-2358
|
Debug on iOS device wizard status prompts users to switch perspective while the wizard is up
|
We should suppress the perspective switch only until the debugger actually connects to the device
| 5 |
train
|
TISTUD-2363
|
Allow iOS debug session without app build
|
In the iOS debug on device wizard, add a checkbox that states "Use previous build". If it is checked, the build parameter UI is disabled and the user can proceed with the wizard. Doing so will re-use the last used app key and ip-address associated with the launch configuration
| 8 |
train
|
TISTUD-2364
|
Allow iOS and Android debug on device wizard to launch in background
|
Add a checkbox to the iOS debug on device wizard to "Run in the background". Upon finish, the launch configuration will behave similar to performing an iOS debug on device launch shortcut
| 8 |
train
|
TISTUD-2365
|
Display a set of instructions when launching Android "Debug on Device"
|
Debugging on Device is a multi-step process, and we should guide the user through the steps. Once the user presses the "debug on device" command, pop up a dialog that shows the four steps: * Build application * Installing on Device * Launch app on device (waiting for connection) Suggest having a wizard page that appears when launching. The page will describe the four steps (1-4), and can help to resolve any setup issues.
| 8 |
train
|
TISTUD-2368
|
For Android module builds on Windows, set an Ant property pointing to the Python plugin's executable
|
cf. TIMOB-11119 Currently, if a Studio user on Windows creates an Android module project and then tries to package it, it will fail if there is no Python interpreter found. Since we ship with an interpreter, it would nice if we could let the module's ant build script know where that packaged python executable is located. Via TIMOB-11119, Bill will change the build.xml for modules to become aware of a property named "python.exec" which should be the full path to a python.exe (including "python.exe" -- not just the directory.) For this Studio ticket, please just pass the AntRunner a -Dpython.exec=... (the full path to the .exe). Thank you!
| 5 |
train
|
TISTUD-2370
|
iOS Device Debugger: iOS "Debug on Device" wizard has broken link
|
The iOS "Debug on Device" wizard more information and Help button links have no effect when clicked. When I copy the link from the more information anchor, it copies "More Information" into the clipboard. Steps to reproduce: 1. Create a Titanium Project. 2. Debug on iOS device. 3. Click the more information button on the iOS "Debug on Device" wizard. Expected result: Link should open to a more information page. Actual result: Nothing happens, and no link is present to copy. Note: This also happens for the "help" button in the lower left.
| 3 |
train
|
TISTUD-2372
|
Device Debugger: intermittent can't delete debug sessions
|
See attachment. When repeatedly launching debug sessions on device, the terminated debug sessions are left behind, but can't be deleted.
| 5 |
train
|
TISTUD-2377
|
iOS Device Debugger Wizard: spelling error 'wasnt'
|
In iOS Debug on Device progress wizard, 'wasn't' is spelled as 'wasnt'. See screenshot. Steps to Reproduce: 1. Launch iOS Debug on Device Session. Actual Result: Wizard contains missspelling. Expected Result: No misspelling.
| 1 |
train
|
TISTUD-2380
|
Windows 7: Preferences: Could not detect a path to the Xcode folder
|
Windows 7 Preferences > Titanium Studio > Titanium menu displays error: Could not detect a path to the Xcode folder Note: Xcode is not supported on Windows 7. Steps to Reproduce: 1. Open Titanium Studio in Windows 7 (possibly Ubuntu). 2. Go to Preferences > Titanium Studio > Titanium. Actual Result: Xcode path error. Expected Result: No mention of Xcode.
| 3 |
train
|
TISTUD-2382
|
Change in Titanium SDK preference is not reflected in New Titanium Project wizard
|
In the new Titianium Project wizard, if the SDK path is modified in preferences through 'Set-up/Configure SDKs' link, then the new wizard still shows the list of SDKs from previous path. The list should be re-loaded in this case.
| 5 |
train
|
TISTUD-2383
|
Studio: Alloy installation error in Studio 3.0 in Ubuntu 12.04
|
Steps To Reproduce: 1. Download Titanium Studio 2.1.2 2. Upgrade Studio to 3.0 using instructions in https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager link. 3. Restart Studio. Actual: Error Message appears "Launching Studio Portal.." and "failed to Install Alloy" [Refer Screenshot and Logs] An internal error SwigDirector_CefHandler_HandleBeforeCreated appears. Expected: Installation and Launching of Studio must occur without any error.
| 8 |
train
|
TISTUD-2384
|
Android: Add 'debug on android device' option in context menu list
|
This is not a regression bug. Steps to reproduce: 1)Open Titanium Studio. 2)Open/Create a Titanium Mobile project -> Android 3)Open context menu by right clicking on that project in Titanium Studio. 4)Observe that debug as -> 'android device' icon is unavailable. Actual result: In context menu list, debug as -> 'android device' icon is unavailable. Expected result: In context menu list, debug as ->'android device' icon should be available. Screenshots attached.
| 8 |
train
|
TISTUD-2388
|
Studio: "Failed to execute runnable" error appears while running app in debug mode on android device.
|
Steps To Reproduce: 1. Upgrade Titanium Studio to 3.0.0.201210021936 release. 2. Create any Default Project. 3. Connect to Android Device using USB. 4. Run app on device in debug mode. Actual: Error appears while running in debug mode. Refer Log file. App Installer does not start. Expected: No error must appear. App must get installed on device.
| 8 |
train
|
TISTUD-2396
|
Android: Installing app with sdk 2.1.3 and older throwing exception with studio version 3.0
|
This issue is occurring with studio version 3.0.0 only. With studio 2.1.2 , this issue is not coming up. When app is installed with studio 3.0.0 and sdk 3.0+ , it is successfully installed. But with older sdks 2.1.3 , 2.1.2 and further , console freezes while installation after the following statement "[INFO] Installing application on device" and studio log throws an exception(attached with the bug). Steps to reproduce 1. Take the studio version 3.0 + and titanium sdk 2.1.3GA 2. Make a sample app and install it on the android device Expected result: 2. App should get installed to android device Actual result: 2. App do not gets installed on device. An exception is thrown in the studio logs(attached with bug).
| 5 |
train
|
TISTUD-2393
|
Keep the focus in the editor when console generates error output
|
h2. Actual results Output to the console causes focus to switch to the console pane rather than the code pane. h2. Expected results Focus should stay where you put it (e.g. in the code window). h2. Steps to reproduce # Build an app for the Android emulator # Click in the code window # As soon as new log info is output, focus goes to the console pane This happens when building for both iOS Simulator and Android emulator. But the behavior is much more annoying when working with Android. ADB seems to continually output logging info so you can get into this battle with Studio where you click in the code window and by the time you type a character, focus has switched back to the console. So you click, focus changes, your text goes to the wrong spot.
| 8 |
train
|
TISTUD-2395
|
Titanium SDK Release Notes has giant text, update table formatting
|
Release Notes pop-up has giant text, we need to update the table formatting. Note: The affected text was removed from the release notes in 2.1.3 as a work-around. TIDOC-838 Steps to Reproduce: 1. Remove latest stable SDK and check for stable SDK updates to bring up Release Notes. Actual Result: Some text is giant in the table sections. Expected Result: Table should be formatted.
| 3 |
train
|
TISTUD-2399
|
Project Explorer: Publish icon active when it shouldn't be
|
In Project Explorer, if there are no projects, the Publish icon is still active (regression), however no entries are available (correct). See screenshots. No log info. Steps to Reproduce: 1. Open Titanium Studio. 2. View the Project Explorer. Make sure there are no projects in the explorer. Actual Result: Publish icon is incorrectly active (but no list appears when clicked, as expected). Expected Result: Publish icon should be grayed-out.
| 5 |
train
|
TISTUD-2400
|
Unpublish Node.ACS service menu is disbled even though the Node.ACS app is published
|
1. Create a Node.ACS project; 2. Create a Node.ACS method in the project; 3. Publish the app using Publish > Deploy App; 4. Select Publish > Unpublish Node.ACS Service. Expected result: item "0.1.0" appears under the pull-over menu. Actual result: no menu item appears under Unpublish Node.ACS Service menu.
| 5 |
train
|
TISTUD-2402
|
Node.ACS: New > Node.ACS Service menu item exists if project already has a service
|
If a titanium project contains a node.acs service, and the user selects project right-click > New, Node.ACS Service appears as a menu entry. As a further complication, when New > Node.ACS Service is selected, the New > Node.ACS Method dialog is invoked instead. Steps to Reproduce: 1. Create a titanium mobile project. 2. Right-click > New > Node.ACS Service to create service. 3. Right-click > New again. Actual Result: New > Node.ACS Service exists as a menu item when the project already has a service. Expected Result: Menu item should not exist. 4. Actually click on New > Node.ACS Service. Actual Result: New > Node.ACS Method dialog is invoked, which is not correct. Expected Result: Either a new service should be created, or a dialog indicating a service already exists.
| 3 |
train
|
TISTUD-2405
|
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 |
train
|
TISTUD-2406
|
Update Android device debugging status to display an animated 'start app' image
|
When performing the debug on Android device using the wizard, the status will be displayed as the app is built and installed. When the 'Start app' step is the current step, we need to remove the step control and replace it with an animated gif of an app starting on a device.
| 5 |
train
|
TISTUD-2408
|
Android device debugger :'debug on android device' page displays text related to ios device debugging.
|
This is not a regression bug. Precondition: Connect an android device (preferably Google nexus 4.0.4) Steps to reproduce: 1)Open Titanium Studio. 2)Open/Create a Titanium Mobile project -> Android device. 3)Click on 'debug' icon-> android device. 4)Observe that a new window launches ( debug on android device) . Actual result: On 'debug on android device' page, "debug titanium application on an iOS device." is displayed ( screen shot attached) Expected result: Android debugging page shouldn't display anything related to iOS device .
| 1 |
train
|
TISTUD-2409
|
Even the Appcelerator Titanium CLI package is successfully installed still after every Titanium Studio restart same update prompt appears at the bottom.
|
This is not a regression bug. Precondition: Install iOS device debugging support from Xcode. Steps to reproduce: 1)Open Titanium Studio. 2)Click on Help -> check for titanium updates. 3)Select Appcelerator Titanium CLI package - update. 4)Wait till installation finishes. 5)After receiving a prompt at the bottom that titanium updates is successfully installed ...click on file -> restart. Actual result: Even the Appcelerator Titanium CLI package is successfully installed still after every Titanium Studio restart same update prompt appears at the bottom. Expected result: Appcelerator Titanium CLI package should be installed and no prompt should appear if Appcelerator Titanium CLI package is successfully installed.
| 5 |
train
|
TISTUD-2410
|
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 |
train
|
TISTUD-2419
|
Allow Android debug session without app re-build
|
In the Android debug on device wizard, add a checkbox that states "Use previous build". If it is checked, the build parameter UI is disabled and the user can proceed with the wizard. Doing so will re-use the last used app associated with the launch configuration
| 8 |
train
|
TISTUD-2421
|
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 |
train
|
TISTUD-2422
|
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 |
train
|
TISTUD-2423
|
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 |
train
|
TISTUD-2424
|
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 |
train
|
TISTUD-2425
|
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 |
train
|
TISTUD-2426
|
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 |
train
|
TISTUD-2427
|
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 |
train
|
TISTUD-2428
|
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 |
train
|
TISTUD-2430
|
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 |
train
|
TISTUD-2431
|
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 |
train
|
TISTUD-2435
|
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 |
train
|
TISTUD-2436
|
"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 |
train
|
TISTUD-2438
|
Titanium Studio starts with warnings in the log file
|
Found this is my log after updating to Titanium Studio 3.1.0 and only on my Mac running 10.8.2 so far: {code} !ENTRY org.eclipse.osgi 2 0 2012-10-09 09:04:35.633 !MESSAGE While loading class "com.aptana.webserver.core.IServer", thread "Thread[Worker-6,5,main]" timed out waiting (5040ms) for thread "Thread[Worker-10,5,main]" to finish starting bundle "com.aptana.webserver.core_3.0.0.1347887896 [134]". To avoid deadlock, thread "Thread[Worker-6,5,main]" is proceeding but "com.aptana.webserver.core.IServer" may not be fully initialized. !STACK 0 org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.aptana.webserver.core_3.0.0.1347887896.jar" by thread "Worker-10". org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.acs.core.ACSCorePlugin$ACCSInitializer.run(ACSCorePlugin.java:159) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException ... 16 more Root exception: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.acs.core.ACSCorePlugin$ACCSInitializer.run(ACSCorePlugin.java:159) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.osgi 2 0 2012-10-09 09:04:40.638 !MESSAGE While loading class "com.aptana.webserver.core.WebServerCorePlugin", thread "Thread[Worker-6,5,main]" timed out waiting (5000ms) for thread "Thread[Worker-10,5,main]" to finish starting bundle "com.aptana.webserver.core_3.0.0.1347887896 [134]". To avoid deadlock, thread "Thread[Worker-6,5,main]" is proceeding but "com.aptana.webserver.core.WebServerCorePlugin" may not be fully initialized. !STACK 0 org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.aptana.webserver.core_3.0.0.1347887896.jar" by thread "Worker-10". org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.acs.core.ACSCorePlugin.getServerManager(ACSCorePlugin.java:131) com.appcelerator.titanium.acs.core.ACSCorePlugin$ACCSInitializer.run(ACSCorePlugin.java:166) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException ... 17 more Root exception: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.acs.core.ACSCorePlugin.getServerManager(ACSCorePlugin.java:131) com.appcelerator.titanium.acs.core.ACSCorePlugin$ACCSInitializer.run(ACSCorePlugin.java:166) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Steps to reproduce: 1. Load Titanium Studio Expected result: Studio should start without issue. Actual result: Studio starts with the above issue.
| 5 |
train
|
TISTUD-2439
|
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 |
train
|
TISTUD-2441
|
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 |
train
|
TISTUD-2442
|
3.0.0 DMG installer has small background image
|
The dmg installer background image is not displaying properly. See screenshot
| 2 |
train
|
TISTUD-2443
|
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 |
train
|
TISTUD-2446
|
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 |
train
|
TISTUD-2447
|
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 |
train
|
TISTUD-2452
|
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 |
train
|
TISTUD-2453
|
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 |
train
|
TISTUD-2454
|
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 |
train
|
TISTUD-2457
|
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 |
train
|
TISTUD-2459
|
No templates available outside the default one for Titanium project
|
All the templates are missing except for the default ones for each project type.
| 5 |
train
|
TISTUD-2460
|
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 |
train
|
TISTUD-2465
|
Titanium CLI is never used in Studio 3.0
|
We're passing in titanium.bypassNewCLI=true by accident in the TitaniumStudio.ini file.
| 1 |
train
|
TISTUD-2467
|
Android Device Debugger: implement console output in studio
|
Titanium Studio console output fails to display device output. Steps to Reproduce: 1. Create default project, add sample code (and breakpoints): {code} Ti.API.info('INFO LOGGED'); var x = 0; // breakpoint {code} 2. Run 'debug' on Android Device. Port forward message should appear on console. 3. Launch app from device. Actual Result: Titanium Studio console fails to display the console output. Expected Result: Titanium Studio console should display 'INFO LOGGED'.
| 8 |
train
|
TISTUD-2472
|
Titanium Studio-ubuntu 12.04 & 10.04: new project top bar text is not properly aligned
|
Steps to reproduce : 1.Launch titanium Studio. 2.File >New > Titanium Project . (screenshot attached) Actual Result: Project template view is not properly aligned.
| 5 |
train
|
TISTUD-2475
|
CLI: Unable to install CLI in Windows 7
|
While trying to update to CLI 3.0.2 on Windows 7 in Titanium Studio, build: 3.1.0.201210102007 the Installing Titanium Updates window gets to the line: {code}npm http 304 https://registry.npmjs.org/deep-equal {code} before hanging and will not progress further. This is a regression as the previous update installed without issue. Steps to reproduce: 1. Start Titanium Studio on Windows 7 2. Run the automatic update for CLI 3.0.2 Expected result: The CLI update should correctly install. Actual result: The updater pauses on the above line (I waited an hour with no progress). Manual install outside studio worked (command line install).
| 8 |
train
|
TISTUD-2476
|
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 |
train
|
TISTUD-2478
|
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 |
train
|
TISTUD-2485
|
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 |
train
|
TISTUD-2487
|
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 |
train
|
TISTUD-2490
|
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 |
train
|
TISTUD-2492
|
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 |
train
|
TISTUD-2494
|
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 |
train
|
TISTUD-2495
|
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 |
train
|
TISTUD-2496
|
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 |
train
|
TISTUD-2497
|
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 |
train
|
TISTUD-2498
|
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 |
train
|
TISTUD-2499
|
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 |
train
|
TISTUD-2500
|
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 |
train
|
TISTUD-2504
|
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 |
train
|
TISTUD-2507
|
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 |
train
|
TISTUD-2508
|
Titanium Updates: warn user if installing SDK or Module will overwrite existing content
|
If a user installs and SDK from url, or installs a module from the dashboard, any content on disk in the same location will be overwritten without prompt. User should be prompted before overwrite. Steps to Reproduce: 1. Update SDK from URL, or install a module from the dashboard. 2. Perform the same action again, using same URL/module. Actual Result: Download/install and overwrite of content without warning prompt. Expected Result: Warning to user about existing content, ability to cancel beforehand.
| 5 |
train
|
TISTUD-2509
|
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 |
train
|
TISTUD-2512
|
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 |
train
|
TISTUD-2513
|
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 |
train
|
TISTUD-2514
|
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 |
train
|
TISTUD-2515
|
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 |
train
|
TISTUD-2518
|
Cannot start an iOS debug-on-device session using the new CLI
|
Using the latest Titanium CLI (version 3.0.5), and the latest Titanium SDK (version 3.1.0.v20121014171713), the launch for debug on iOS device fails.
| 13 |
train
|
TISTUD-2519
|
"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 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.