issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-4310
|
Add the chromium plugins to the Node ACS feature
|
Once development is completed, add the new chromium plugins into the Node ACS feature to include them in the build.
| 3 |
train
|
TISTUD-4311
|
iOS: Packaging - Appstore distribution not possible via Studio if Adhoc Distribution is done first
|
Packaging App via Studio for Adhoc Distribution first will cause subsequent attempts to package for Appstore to fail. Studio will continue to send the command including "dist-adhoc". This results in inaccurate info presented in the console, as well as an incorrect toast saying the app store build was successful and complete. However, packaging for Appstore before Adhoc will succeed as expected and the project can be seen in Xcode organizer with Studio console output [INFO] : Build type: production [INFO] : Building for target: dist-appstore Packaging via CLI works as expected, and running a "dist-appstore" build command on an affected project works as expected, and seems to set the project correctly, so presumably the project could then be packaged for appstore in Studio as expected Test steps: 1. Create a project 2. Distribute - Adhoc/Enterprise 3. Distribute - Apple iTunes Store Actual result: After step 3 {code} [INFO] : Build type: production [INFO] : Building for target: dist-adhoc {code} At completion, Toast saying success and complete. Expected result: Building for target: dist-appstore The project should be placed in the archive section of the Xcode organizer
| 5 |
train
|
TISTUD-4312
|
Create launch shortcut to debug on Node ASC local server
|
Right-click on a Node.ACS resource should display "Debug As... -> Node.ACS Local Server" (like the run as), and should create a debug launch configuration on and launch. Existing launch configurations for the same projects should be re-used.
| 5 |
train
|
TISTUD-4314
|
Upon startup, Titanium Studio calls npm install checks 2 times
|
Studio runs the Titanium npm checks twice, doubling the amount of time needed to display available updates and increases the amount of network interactions. See the log
| 5 |
train
|
TISTUD-4318
|
Dashboard: Mobile Web Configuration is not getting configured
|
Dashboard >> Mobile web Configuration not getting configured Steps followed: 1. Dashboard >> Mobile Web Configuration >> Click here to open browser preferences 2. Preferences >> Studio >> Platforms >> Mobile Web >> Web Browser (set the desired browser Chrome, Firefox, IE or Default System Browser from the available drop down menu) >> Apply >> Ok Expected Result: The Mobile web Configuration get configured so as to change the red cross icon to green tick icon. Actual Result: Mobile web Configuration not getting configured and its icon remains to 'red cross' even after following the configuration steps. The logs do not give any specific description for the above behavior Please refer the attached screen shots for further reference.
| 8 |
train
|
TISTUD-4321
|
Only prompt user for overwrite when installing a Titanium SDK that already exists
|
I'm not sure if we really intend to prompt or not, but every time a user installs/updates the SDK through Studio they will get an overwrite prompt about 3/4 in to the process because we overwrite existing modules with the same ones from the new SDK (in other words, it seems like modules aren't underneath the SDK version folder, but are shared). The prompt itself makes it so you force user interaction to finish the install, but it also can scare the user into thinking we're blowing something away. Do we really want to prompt if the normal use case is that some files will get overwritten? Maybe the files getting overwritten don't really need to? (i.e. the modules have the exact same content, so we don't even need to copy them over - which maybe we can get by comparing an MD5 hash recursively and filtering out files that already exist in the destination?)
| 5 |
train
|
TISTUD-4323
|
Include ENV in diagnostic logs
|
We can have users turn on their troubleshooting prefs to get details on individual commands we run including the ENv we set up, but it may be easier for us to just spit out the "default" ENV in the diagnostic log which would typically get attached to a bug report made through Studio.
| 5 |
train
|
TISTUD-4325
|
Node.ACS Project: deleting project results in Problems encountered while deleting resources
|
Node.ACS Project: deleting project results in Problems encountered while deleting resources: {code} !ENTRY org.eclipse.ltk.ui.refactoring 4 10000 2013-04-18 14:48:28.568 !MESSAGE Internal Error !STACK 1 org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. org.eclipse.core.internal.resources.Resource.delete(Resource.java:793) org.eclipse.core.internal.resources.Project.delete(Project.java:344) org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:132) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Contains: Could not delete 'C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj'. org.eclipse.core.runtime.CoreException: Problems encountered while deleting files. org.eclipse.core.internal.filesystem.local.LocalFile.delete(LocalFile.java:125) org.eclipse.core.internal.resources.ResourceTree.internalDeleteProject(ResourceTree.java:437) org.eclipse.core.internal.resources.ResourceTree.standardDeleteProject(ResourceTree.java:837) org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1945) org.eclipse.core.internal.resources.Resource.delete(Resource.java:780) org.eclipse.core.internal.resources.Project.delete(Project.java:344) org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:132) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Contains: Could not delete: C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj. Contains: Could not delete 'C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj'. !SUBENTRY 1 org.eclipse.core.resources 4 273 2013-04-18 14:48:28.568 !MESSAGE Problems encountered while deleting resources. !SUBENTRY 2 org.eclipse.core.resources 4 273 2013-04-18 14:48:28.568 !MESSAGE Could not delete 'C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj'. !STACK 1 org.eclipse.core.runtime.CoreException: Problems encountered while deleting files. org.eclipse.core.internal.filesystem.local.LocalFile.delete(LocalFile.java:125) org.eclipse.core.internal.resources.ResourceTree.internalDeleteProject(ResourceTree.java:437) org.eclipse.core.internal.resources.ResourceTree.standardDeleteProject(ResourceTree.java:837) org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1945) org.eclipse.core.internal.resources.Resource.delete(Resource.java:780) org.eclipse.core.internal.resources.Project.delete(Project.java:344) org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:132) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Contains: Could not delete: C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj. !SUBENTRY 3 org.eclipse.core.filesystem 4 273 2013-04-18 14:48:28.568 !MESSAGE Problems encountered while deleting files. !SUBENTRY 4 org.eclipse.core.filesystem 4 273 2013-04-18 14:48:28.568 !MESSAGE Could not delete: C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj. !SUBENTRY 2 org.eclipse.core.resources 4 273 2013-04-18 14:48:28.568 !MESSAGE Could not delete 'C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj'. !ENTRY org.eclipse.core.resources 4 273 2013-04-18 14:48:28.568 !MESSAGE Problems encountered while deleting resources. !SUBENTRY 1 org.eclipse.core.resources 4 273 2013-04-18 14:48:28.568 !MESSAGE Could not delete 'C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj'. !STACK 1 org.eclipse.core.runtime.CoreException: Problems encountered while deleting files. org.eclipse.core.internal.filesystem.local.LocalFile.delete(LocalFile.java:125) org.eclipse.core.internal.resources.ResourceTree.internalDeleteProject(ResourceTree.java:437) org.eclipse.core.internal.resources.ResourceTree.standardDeleteProject(ResourceTree.java:837) org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1945) org.eclipse.core.internal.resources.Resource.delete(Resource.java:780) org.eclipse.core.internal.resources.Project.delete(Project.java:344) org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:132) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Contains: Could not delete: C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj. !SUBENTRY 2 org.eclipse.core.filesystem 4 273 2013-04-18 14:48:28.568 !MESSAGE Problems encountered while deleting files. !SUBENTRY 3 org.eclipse.core.filesystem 4 273 2013-04-18 14:48:28.568 !MESSAGE Could not delete: C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj. !SUBENTRY 1 org.eclipse.core.resources 4 273 2013-04-18 14:48:28.568 !MESSAGE Could not delete 'C:\Users\ASUS\Documents\Titanium_Studio_Workspace\jjj'. {code} Test Steps: 1. Delete Node.ACS Project.
| 5 |
train
|
TISTUD-4333
|
If git commit fails, don't close commit dialog and then show error dialog. Show error in the commit dialog so user can make changes and retry
|
If a user has a pre-commit hook that may fail the commit (or there's some other issue that causes a commit to fail) we used to ignore it. Now we pop an error dialog after the commit dialog closes and the commit fails. In my case, I have a pre-commit hook that enforces updated copyrights. I need it to not close the commit dialog (so I don't have to re-open), retain my commit message, and refresh it's file listings (because the hook also modifies files).
| 5 |
train
|
TISTUD-5093
|
Studio auto-formatter doesnt like negative numbers in alloy .tss
|
Negative integers break the formatter and show errors in .tss files. This should be allowed. Converting to string solves problem but becomes inconsistent with the rest of the code.
| 5 |
train
|
TISTUD-4336
|
New Classic Project: intermittent freeze when classic templates load
|
New Classic Project: intermittent freeze when classic templates load. This happens when the Classic templates are first opened in the new project wizard. It can be repeated by closing the new project wizard and trying again. This is intermittent. This made studio unresponsive to the os on one occasion. A freeze or hang happens almost every time Classic templates are first invoked. See logs. Test Steps: 1. Open Appcelerator Studio. 2. New > Mobile Project. 3. Click 'Classic'. Actual Result: Frequent intermittent freeze or hang from a few seconds to indefinitely.
| 8 |
train
|
TISTUD-4337
|
Display the Node.ACS debug shortcut and previous configurations in the Project Explorer toolbar
|
Like we do with the Run Node.ACS, have the Debug Node.ACS populated under the debug icon in the Project Explorer toolbar.
| 5 |
train
|
TISTUD-4343
|
iOS Ad-Hoc Packaging Wizard: default height obfuscates new fields
|
iOS Ad-Hoc Packaging Wizard: default height obfuscates new fields. See screenshot. Test Steps: 1. Package > iOS Ad-Hoc. Actual Result: Bottom field cut-off by default.
| 5 |
train
|
TISTUD-4930
|
Alloy compiler does not support linked folders in workspace
|
I re-use a lot of Alloy widgets and hold these in a shared folder. I normally use `ln -s` to link these folders into projects and that works great. Titanium Studio however, also has an option for `Link to alternate location (Linked Folder)` when creating a new folder. I thought I might try, but discovered it does not work. The Alloy compiler exits with an error saying it cannot find the files: {code} [ERROR] widget "nl.fokkezb.loading" view "widget" does not exist. [ERROR] The following paths were inspected: [ERROR] /Users/zandbergen/Documents/Titanium/VerhaaltjesApp/app/widgets/nl.fokkezb.loading/views/ios/widget [ERROR] /Users/zandbergen/Documents/Titanium/VerhaaltjesApp/app/widgets/nl.fokkezb.loading/views/widget [ERROR] /usr/local/lib/node_modules/alloy/widgets/nl.fokkezb.loading/views/ios/widget [ERROR] /usr/local/lib/node_modules/alloy/widgets/nl.fokkezb.loading/views/widget MacBook:VerhaaltjesApp zandbergen$ {code}
| 5 |
train
|
TISTUD-4356
|
Create com.appcelerator.titanium.windows.core and com.appcelerator.titanium.windows.ui plugins
|
Create the core and UI plugins that will hold our windows phone support code. Add the plugins to the titanium feature. Add a filter to only install them on win32.
| 3 |
train
|
TISTUD-4357
|
Add IMobilePlatform extension stub for windows phone
|
Add IMobilePlatform extension stub (just basic name "Windows Phone"/id "windows"? - check with platform for the id they'll be using/sdk support check) (core)
| 3 |
train
|
TISTUD-4359
|
Add Preference page for Windows Phone
|
Add the preference page extension, add a preference page that includes a path to the windows phone SDK.
| 3 |
train
|
TISTUD-4360
|
Add MobilePlatformUI extension for Windows Phone
|
Define the pref page id, pointers to the 12x12 and 16x16 icons for modules table.
| 2 |
train
|
TISTUD-4361
|
Add 16x16 and 12x12 icons for Windows Phone platform
|
16x16 enabled icon 16x16 disabled icon 12x12 enabled icon (may be shrunk version of 16x16)
| 3 |
train
|
TISTUD-4362
|
Add 16x16 packaging icon for Windows Phone
|
16x16, typically platform icon with box
| 5 |
train
|
TISTUD-4363
|
Add 48x48 packaging wizard banner image for Windows Phone
|
package wizard header (48x48, typically large platform icon in box)
| 5 |
train
|
TISTUD-4364
|
Add 16x16 device launch icon for Windows Phone
|
device launch (16x16, typically device with small platform overlay on bottom right)
| 3 |
train
|
TISTUD-4365
|
Add 16x16 simulator launch icon for Windows Phone
|
simulator launch (16x16, typically same as icon used in modules table and user agent)
| 3 |
train
|
TISTUD-4366
|
Add launch config type for running on simulator for Windows Phone
|
Add extension for org.eclipse.debug.core.launchConfigurationTypes, does not include defining/implementing the launch delegate or shortcut.
| 2 |
train
|
TISTUD-4367
|
Add launch delegate for run on Windows Phone simulator
|
Add extension for org.eclipse.debug.core.launchDelegates. Hook to the launch config type defined by TISTUD-4366. Adding support to command helper(s) defined in IMobilePlatform extension (TISTUD-4357) for running.
| 5 |
train
|
TISTUD-4368
|
Add Launch config tab group for run on Windows Phone simulator
|
Add extension for org.eclipse.debug.ui.launchConfigurationTabGroups. Hook to the launch config type defined by TISTUD-4366. Typically need to subclass an standard titanium tab group base class, add a tab class. Tab class will define any Windows Phone specific arguments we need (currently unknown).
| 5 |
train
|
TISTUD-4369
|
Add Launch shortcut for run on Windows Phone simulator
|
Add extension for org.eclipse.debug.ui.launchShortcuts. Hook to the launch config type defined by TISTUD-4366. typically just define launch config type id we're tied to in extension and subclass of AbstractTitaniumLaunchShortcut; enablement expression (isWindows8Project); label/description strings; pointer to icon
| 5 |
train
|
TISTUD-4370
|
Add launch config type for running on Windows Phone device
|
Add extension for org.eclipse.debug.core.launchConfigurationTypes, does not include defining/implementing the launch delegate or shortcut.
| 2 |
train
|
TISTUD-4371
|
Add launch delegate for run on Windows Phone device
|
Add extension for org.eclipse.debug.core.launchDelegates. Hook to the launch config type defined by TISTUD-4370. Adding support to command helper(s) defined in IMobilePlatform extension (TISTUD-4357) for running.
| 5 |
train
|
TISTUD-4372
|
Add Launch config tab group for run on Windows Phone device
|
Add extension for org.eclipse.debug.ui.launchConfigurationTabGroups. Hook to the launch config type defined by TISTUD-4370. Typically need to subclass an standard titanium tab group base class, add a tab class. Tab class will define any Windows Phone specific arguments we need (currently unknown).
| 8 |
train
|
TISTUD-4373
|
Add Launch shortcut for run on Windows Phone device
|
Add extension for org.eclipse.debug.ui.launchShortcuts. Hook to the launch config type defined by TISTUD-4370. typically just define launch config type id we're tied to in extension and subclass of AbstractTitaniumLaunchShortcut; enablement expression (isWindows8Project); label/description strings; pointer to icon
| 5 |
train
|
TISTUD-4375
|
Add launch config type for packaging a Windows Phone app
|
Add extension for org.eclipse.debug.core.launchConfigurationTypes, does not include defining/implementing the launch delegate or shortcut.
| 2 |
train
|
TISTUD-4376
|
Add Launch config tab group for packaging a Windows Phone app
|
Add extension for org.eclipse.debug.ui.launchConfigurationTabGroups. Hook to the launch config type defined by TISTUD-4375. Typically need to subclass an standard titanium tab group base class, add a tab class. Tab class will define any Windows Phone specific arguments we need (currently unknown).
| 8 |
train
|
TISTUD-4377
|
Add launch delegate for packaging Windows Phone app
|
Add extension for org.eclipse.ui.commands with an id, a handler. Implement the handler that will open a packaging wizard. The wizard will use the banner image defined in TISTUD-4363. The wizard will step user through the values/options required to package an app.
| 5 |
train
|
TISTUD-4378
|
Add launch config type image for running on simulator for Windows Phone
|
Add extension for org.eclipse.debug.ui.launchConfigurationTypeImages - refers to launch config type id and icon path.
| 2 |
train
|
TISTUD-4379
|
Add launch config type image for running on Windows Phone device
|
Add extension for org.eclipse.debug.ui.launchConfigurationTypeImages - refers to launch config type id and icon path.
| 2 |
train
|
TISTUD-4380
|
Add launch config type image for packaging a Windows Phone app
|
Add extension for org.eclipse.debug.ui.launchConfigurationTypeImages - refers to launch config type id and icon path.
| 2 |
train
|
TISTUD-4381
|
Add Launch shortcut for packaging a Windows Phone app
|
Add extension for org.eclipse.debug.ui.launchShortcuts. Hook to the launch config type defined by TISTUD-4375. typically just define launch config type id we're tied to in extension and subclass of AbstractTitaniumLaunchShortcut; enablement expression (isWindows8Project); label/description strings; pointer to icon
| 5 |
train
|
TISTUD-4389
|
Dashboard: Windows: MobileWeb App Launch text doesn't read well due to background color
|
Dashboard: Windows: MobileWeb App Launch text doesn't read well due to background color. See screenshot. The background color of the button is dark gray on OS X, so the text is readable in that case. However, on Windows the background color is light gray, so the white text has no contrast and is largely unreadable. Test Steps: 1. Open Studio. 2. Open Dashboard. 3. Get Started > Mobile Web App. Actual Result: 'Launch recently created project' text is not visible due to contrast with background.
| 5 |
train
|
TISTUD-4394
|
Code Processor: release notes lists Appcelerator twice
|
Code Processor: release notes lists Appcelerator twice. See screenshot. Test Steps: 1. Uninstall Code Processor. 2. Check for Appcelerator Updates. 3. View Release Notes. Actual Result: Appcelerator listed twice.
| 3 |
train
|
TISTUD-4395
|
Code Processor: 1.0.0 not updated if 0.3.2 installed
|
Code Processor: 1.0.0 not updated if 0.3.2 installed. Works from the command line. Test Steps: 1. Install Code Processor 0.3.2. 2. Check for Appcelerator Updates. Actual Result: No updates found. Expected Result: Code Processor 1.0.0 installs.
| 5 |
train
|
TISTUD-4396
|
Samples: double-click should expand folder node in Samples view
|
Samples: double-click fails to expand folder node in samples view. Double-click functions correctly for folder nodes in the Project Explorer. Test Steps: 1. Double-click Samples View 'Appcelerator' folder. Actual Result: Folder fails to expand and collapse.
| 5 |
train
|
TISTUD-4397
|
Appcelerator Updates: uninstalled Titanium SDK not updated until restart
|
Appcelerator Updates: uninstalled Titanium SDK not updated until restart. The NPM packages all update instantly when they are uninstalled. This is a parity issue. Test Steps: 1. Open Appcelerator Studio. 2. Delete Stable Titanium SDK. 3. Check for Appcelerator Updates. Actual Result: No updates found. Must restart Studio to get Titanium SDK update.
| 5 |
train
|
TISTUD-4406
|
Proxy Splash: settings do not populate based on preferences
|
Proxy Splash: settings do not populate based on preferences. Also, when you switch between proxy types in the proxy splash, the fields all have the same values, as if only one proxy type can be set at a time. See screenshots. The proxy splash is intended to allow the user to edit the proxy preferences without logging-in. Currently it is not pre-populated with the values in the preferences. Test Steps: 1. Edit proxy preferences (Preferences > General > Network Connections). Here is the qe test proxy for example: Connect: 50.17.15.139 Port: 8080 Username: qetester Password: lynx64-fixer 2. Log out of Studio and Relaunch. 3. Open proxy splash menu. Actual Result: The proxy splash menu does not reflect the preferences. This gives the impression there is no proxy setup. This is a false impression. This is a bug.
| 5 |
train
|
TISTUD-4430
|
Remove the 'Clear SD Card' option from the BlackBerry's Simulator launch configuration dialog
|
This option is no longer supported with the BlackBerry CLI, so we need to remove this checkbox.
| 5 |
train
|
TISTUD-4443
|
Projects: non-default location results in creation problems internal error
|
This happens in both Ti Studio and AppC Studio from latest GA to the nightly (current nightly: 3.1.1.201304292203). Steps: 1. Create a new mobile project 2. Make sure the location is not the default location 3. ERROR - http://www.screencast.com/t/2bBWaHAMWa2Z Note that this happens to me when trying an Alloy project and non-alloy project.
| 5 |
train
|
TISTUD-4448
|
Move Run > BlackBerry Device action to BlackBerry plugin(s)
|
This involves moving the launch shortcut and related classes for contributing the Run > BlackBerry Device action to BlackBerry's own plugins.
| 8 |
train
|
TISTUD-4450
|
Alloy debugger maps to the wrong source in a specific case
|
This one got discovered after investigating an issue reported by a user at http://developer.appcelerator.com/question/151251/alloy-debugging-files-in-lib-and-widgets---problems Seems like the Studio does not map to the right file in some specific cases.
| 8 |
train
|
TISTUD-4454
|
NullPointerException when creating a Module project
|
(Note: This happens on 3.2.0 only) Create a new Mobile Module project. Select the iOS option, hit 'Next' and 'Finish'. The wizard dialog hangs, and an error appears in the log. {code} java.lang.NullPointerException com.appcelerator.titanium.core.TitaniumProject.getGUID(TitaniumProject.java:201) com.appcelerator.titanium.usage.TitaniumFeatureEvent.generatePayload(TitaniumFeatureEvent.java:53) com.appcelerator.titanium.usage.TitaniumFeatureEvent.<init>(TitaniumFeatureEvent.java:29) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.sendProjectCreateEvent(BasicNewTitaniumProjectWizard.java:186) com.aptana.projects.wizards.AbstractNewProjectWizard.performFinish(AbstractNewProjectWizard.java:399) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.performFinish(BasicNewTitaniumProjectWizard.java:239) com.appcelerator.titanium.mobile.ui.module.wizard.NewMobileModuleProjectWizard.performFinish(NewMobileModuleProjectWizard.java:171) org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:98) org.eclipse.jface.action.Action.runWithEvent(Action.java:498) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code}
| 3 |
train
|
TISTUD-4464
|
Install Eclipse 4.3 M7 on build agents
|
We should download and install eclipse 4.3 M7 to all the build agents (as we have for our other eclipse targets). This involves SSHing into master and the 5 ubuntu agents, then performing something like: Please note that the URLS won't be these exactly. You'll need to grab them from the eclipse.org download site: http://download.eclipse.org/eclipse/downloads/ {code} wget http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M7-201303141330/download.php?dropFile=eclipse-SDK-4.3M7-linux-gtk.tar.gz wget http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M7-201303141330/download.php?dropFile=eclipse-4.3M7-delta-pack.zip tar -xvzf eclipse-SDK-4.3M7-linux-gtk.tar.gz unzip eclipse-4.3M7-delta-pack.zip mv eclipse eclipse_4.3M7 {code}
| 8 |
train
|
TISTUD-4465
|
Update global environment variables to point to new eclipse install and plugins
|
http://hudson-master.hdqt.appcelerator.com/hudson/configure - Edit ECLIPSE_HOME to be /opt/eclipse_4.3M7 - Edit ECLIPSE_LAUNCHER to be the plugin name and version string for the org.eclipse.equinox.launcher_1.2.0.v20110502 plugin jar in /opt/eclipse_4.3M7/plugins (something like org.eclipse.equinox.launcher_1.2.0.v20110502) - Edit ECLIPSE_BUILD to be the plugin name and version string for the org.eclipse.pde.build plugin in /opt/eclipse_4.3M7/plugins (something like org.eclipse.pde.build_3.7.0.v20111116-2009)
| 3 |
train
|
TISTUD-4466
|
Update 3.6 compatibility jobs to point to 3.7.2
|
Now that the default values for eclipse point at 4.3 M7, we should update the compat jobs to override and point at 3.7.2. Configure any job with name ending in "-3.6". - Change name to end with "-3.7". - In the launch ant section, click Advanced and modify the properties we pass to have: {code} vanilla.eclipse=/opt/eclipse_3.7.2 launcher.plugin=org.eclipse.equinox.launcher_1.2.0.v20110502 builder.plugin=org.eclipse.pde.build_3.7.0.v20111116-2009 {code}
| 5 |
train
|
TISTUD-4471
|
Alloy Project: Windows: adb process prevents project from being deleted
|
Alloy Project: Windows: adb process prevents project from being deleted. Test Steps (intermittent?): 1. Create Alloy Project. 2. Run on Android Emulator. 3. Restart Studio. 4. Delete project from disk. Result: Project fails to delete, the project directory remains. Must call adb kill-server manually first.
| 5 |
train
|
TISTUD-4473
|
Titanium Updates: cli version not available on clean install fix NPEs
|
Titanium Updates: cli version not available on clean install. See screenshot. Test Steps: 1. Clean Install Titanium Studio. 2. Open Titanium Studio. Actual Result: Titanium CLI version is N/A. Expected Result: Titanium CLI version is 3.1.0.
| 5 |
train
|
TISTUD-4474
|
BlackBerry: Run Configuration: new configuration should auto-select current project
|
When a new run configuration is created, it would be helpful if the project were auto-selected based on the project currently in focus (either from the project explorer, or app explorer). This has been fixed for all platforms except BlackBerry. Steps to Test: 1. Select a Titanium Mobile project in the project explorer. 2. Go to Run Configurations... 3. Create a new Android Emulator run configuration. Expected Result: The project selected in the project explorer should be the default project in the new configuration. Currently there is no project selected in the new run config, it must be manually selected.
| 5 |
train
|
TISTUD-4475
|
Move Run > Android Device action to Android plugin(s)
|
This involves moving the launch shortcut and related classes for contributing the Run > Android Device action to Android's own plugins.
| 8 |
train
|
TISTUD-4476
|
Move Run > iOS Device action to ios plugin(s)
|
This involves moving the launch shortcut and related classes for contributing the Run > iPad Simulator action to ios' own plugins.
| 8 |
train
|
TISTUD-4477
|
Diagnostics: Windows: npm hierarchy characters display as rectangles
|
Diagnostics: Windows: npm hierarchy characters display as rectangles. See screenshot. Does not occur on Mountain Lion 10.8.3. Test Steps: 1. Run Help > Diagnostic Log...
| 5 |
train
|
TISTUD-4487
|
Resolve Ubuntu 12.04 Clean Install Startup NPEs
|
Resolve Ubuntu 12.04 Clean Install Startup NPEs. When Studio is first installed and run on Ubuntu 12.04, the user is provided a documentation link to configure a valid environment. The user is also flooded with NPEs and errors in the UI. See log. Documentation Link: http://docs.appcelerator.com/titanium/latest/#!/guide/Troubleshooting_a_Studio_Install_on_Linux-section-30083014_TroubleshootingaStudioInstallonLinux-Ubuntu12.04%2FPrecisePangolinStartupIssues Test Steps: 1. Clean install Studio on Ubuntu 12.04. 2. Open Studio. Result: UI flooded with errors, some of which contain documentation links to configure Studio. Expected Result: Controlled error providing work-around. No extra questionable errors.
| 3 |
train
|
TISTUD-4488
|
Titanium Updates: menu is called Titanium Update instead of Titanium Updates
|
Titanium Updates: menu is called Titanium Update instead of Titanium Updates. See screenshot. Test Steps: 1. Invoke Help > Check for Appcelerator Updates. Result: Menu is called Appcelerator Update. This does not look intentional. Expected Results: Appcelerator Updates.
| 1 |
train
|
TISTUD-4490
|
Download Eclipse 4.3 M7, set as local build target and fix any compilation errors in plugins
|
There may have been breaking API changes that require us to modify our codebase to work with 4.3. We need to download Eclipse 4.3 M7, set it as our local build target and then fix the compilation issues.
| 8 |
train
|
TISTUD-4492
|
Liveview: Fastdev prevents liveview from working on android emulator
|
h5. Description: While testing liveview, I attempted to run on Android emulator and on Android device. Both failed. My first emulator run failed with a red runtime error screen complaining of a timeout. This is similar to the attached image from device. The second run and subsequent runs of the emulator launched and ran, but changes did not show in the emulator. The console reported the changed files however: {code} [32m [INFO][39m Reload Triggered [90m -REASON:[39m File Changed [90m -FILE:[39m /Users/emerriman/Documents/workspace/mayworkspace/basicNoServ/Resources/app.js {code} attempting to install on works, but when the app is auto-launched, it fails with the error shown in the attachment h5. Steps to reproduce: 1) Navigate to the studio install location for liveview and run "./liveview-server stop" 2) Launch a project without crittercism for Android emulator liveview enabled 3) Change the app.js code part two: Launch liveview session on android device h5. Result: Emulator will not show any changes although the console shows the file listener is functioning part two: error as shown in attachment h5. Expected Result: Code changes appear in the emulator Device build runs and shows code changes
| 5 |
train
|
TISTUD-4493
|
BlackBerry: device run config password and token field edits do not Revert if config invalid
|
BlackBerry: device run config password and token field edits do not Revert. See screenshot. Test Steps: 1. Run Configurations... BlackBerry Device. 2. Edit Password and Token fields. 3. Press Revert. Actual Result: Nothing happens.
| 3 |
train
|
TISTUD-4494
|
BlackBerry: Packager run configuration Revert not activated by project name field edit if config invalid
|
BlackBerry: run configuration Revert not activated by project name field edit. Test Steps: 1. Run Configurations... BlackBerry Packager. 2. Edit Run Config project name. Expected Result: Revert button becomes activated, clicking Revert reverts changes to project name. Actual Result: Revert button does not become activated. Revert does not work.
| 3 |
train
|
TISTUD-5749
|
Android: Error if app name contains an umlaut
|
If the app name contains special character like ä,ö,ü - the android build script fails creating a release for the play store. Example name: "Bäckerei Höchste" (Bakery Hoechste) I've already created a pull request a while ago to fix this issue: https://github.com/appcelerator/titanium_mobile/pull/3930
| 5 |
train
|
TISTUD-4525
|
Alloy .tss parser doesn't validate colors property
|
*Problem description* The following code shows an error in the .tss viewer in titanium studio next to the line after "colors" below, even though it's correct syntax. *Error* {code}Syntax Error: Unexpected Token "{"{code} *Test case* {code:css} "#viewPricingTier": { width: Ti.UI.FILL, height: Ti.UI.SIZE, backgroundGradient: { type: 'linear', startPoint: { x: '0%', y: '50%' }, endPoint: { x: '100%', y: '50%' }, colors: [ { color: 'red', offset: 0.0 }, // Error here { color: 'blue', offset: 0.25 }, { color: 'red', offset: 1.0 } ], }, borderWidth: '2dp', borderColor: '#ffffff', borderRadius: '4dp' } {code}
| 8 |
train
|
TISTUD-4510
|
Titanium Updates: when no updates available, appears as an error instead of a success
|
Titanium Update: when no updates installed, appears as an error instead of a success. See screenshots. Test Steps: 1. Install Titanium Updates. 2. Check for Titanium Updates. Result: An error pop-up appears. The icon is misleading. Most programs would consider it a success to have the proper dependencies already installed. Expected Result: A success pop-up appears. One example of a success icon is a green check mark.
| 2 |
train
|
TISTUD-4517
|
Investigate to improve the performance of loading TiApp editor
|
Investigate the areas to improve the load time of opening TiApp files in editor. Areas to investigate : * If there are any network calls that degrades performance, need to investigate whether they can be run in the background while showing the loading the status. * Split the 360 section into a separate tab to defer hitting 360 calls until the 360 tab is opened. The performance unit tests for measuring the load time of TiApp in the editor should be available through TISTUD-4516.
| 8 |
train
|
TISTUD-4518
|
Modify Studio Dashboard to invoke the new platform config wizard for configuring platforms
|
We currently have links in each platform section under Get Started tab to direct user to individual site for downloading the natvie SDKs. We should modify them to invoke the new platform config wizard with the specific platform selected.
| 5 |
train
|
TISTUD-4524
|
Investigate to generate reports from the performance tests
|
A few performance tests for studio3-core are already available and have been have been running now. However, if there's a regression, I think that's just silently logged in the DB right now. We need to generate reports from that data by comparing against the baseline (3.0.0 performance) similar to : http://archive.eclipse.org/eclipse/downloads/drops/R-3.1.1-200509290840/performance/performance.php We need to investigate the required infrastructure or framework to generate the similar reports for the Studio tests.
| 8 |
train
|
TISTUD-4529
|
TiApp: grayed-out deployment targets still have active deployment UI
|
TiApp: grayed-out deployment targets still have active deployment UI. Test Steps: 1. Edit TiApp to contain a deployment target that has no sdk support. Result: Target is greyed-out in TiApp Editor, but the deployment UI is still active (i.e., run, debug, etc.).
| 8 |
train
|
TISTUD-4543
|
Code Processor: output opens multiple result views when repeating the same analysis
|
h5. Description: When running the same analysis (the same project with the same target) multiple times, studio will present a new report each time. This may result in confusion if changes are made between each analysis. h5. Steps to reproduce: 1) Right-click an existing project and choose a target {for example: "iphone") 2) Click the resulting toast that offers to show the result 3) Run the same analysis on the same project 4) Click the resulting toast h5. Result: Multiple reports for the same target are shown h5. Expected Result: Any existing result is replaced by the new result
| 3 |
train
|
TISTUD-4554
|
Error opening the Tiapp.xml after manually adding and removing SDKs
|
I stumble into this issue after removing some previously installed Titanium SDKs, and then adding a new SDK version. After that, I tried to open a tiapp.xml for a project that used an SDK that is no longer available. The TiApp editor failed to load with this exception: {code} java.lang.NullPointerException com.appcelerator.titanium.core.internal.mobile.MobilePlatformsRegistry$LazyMobilePlatform.isSDKSupporting(MobilePlatformsRegistry.java:113) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.updateControlsEnablement(TiAppDeployTargetsSection.java:533) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.initialize(AbstractTiAppSection.java:72) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.initialize(TiAppDeployTargetsSection.java:166) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.<init>(AbstractTiAppSection.java:55) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.<init>(TiAppDeployTargetsSection.java:129) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppFormPage.createFormContent(TiAppFormPage.java:100) org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:471) org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1067) org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:603) org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:352) org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245) org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198) org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597) org.eclipse.ui.internal.PartStack.add(PartStack.java:493) org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) org.eclipse.ui.internal.PartStack.add(PartStack.java:479) org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225) org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213) org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:808) org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:707) org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:666) org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2942) org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850) org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842) org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2756) org.eclipse.ui.ide.IDE.openEditor(IDE.java:683) org.python.pydev.navigator.actions.PyOpenResourceAction.openFiles(PyOpenResourceAction.java:101) org.python.pydev.navigator.actions.PyOpenPythonFileAction.run(PyOpenPythonFileAction.java:86) org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221) org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:185) org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:866) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:864) org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1152) org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462) org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1256) org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275) org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:269) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:309) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code}
| 3 |
train
|
TISTUD-4559
|
Studio: Grammatical error on a dialog window
|
I noticed a grammatical error, when trying to launch the project as Android Emulator (2.2). Test steps: Run the project as Android emulator 2.2. Notice the word "require" on the dialod window. Expected result: the word should be "requires" (see the screenshot)
| 2 |
train
|
TISTUD-4577
|
Embed Git check and install into Studio Windows installer
|
We currently include portablegit and prompt user to install at Studio start if no git is detected. Portablegit is for not just git support, but we also use it as our shell environment for Windows (terminal, getting shell env, etc). For the new installer, we should embed the git check and installation of portablegit in it.
| 13 |
train
|
TISTUD-4581
|
BlackBerry: device deployment wizard validation does not allow user to continue
|
BlackBerry: device deployment wizard validation does not allow user to continue. See screenshots. Test Steps: 1. Delete BlackBerry device run configs. 2. Delete ip fields from BlackBerry preferences. 3. Run on BlackBerry device. Result: Device deployment wizard appears, asks user to provide ips. User enters ips, but cannot continue. Expected Result: Device deployment wizard appears, asks user to provide ips. User enters ips, they are validated, and the user can continue.
| 3 |
train
|
TISTUD-4584
|
Console: Windows: blackberry run on device console displays backspace characters
|
Console: Windows: blackberry run on device console displays backspace characters. See screenshot. Test Steps: 1. Launch on BlackBerry device. Result: Console displays backspace characters.
| 3 |
train
|
TISTUD-4595
|
Dashboard: Templates and Samples don't work on Appcelerator Studio 3.2.0
|
I clicked on the default project template, nothing happens, there is an error in the log: {code} !ENTRY com.aptana.portal.ui 4 0 2013-05-09 17:03:21.321 !MESSAGE (Build 3.2.0.201305092404) [ERROR] org.eclipse.core.commands.ExecutionException: unknown wizard: null !STACK 0 org.eclipse.e4.core.di.InjectionException: org.eclipse.core.commands.ExecutionException: unknown wizard: null org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231) org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212) org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) com.aptana.portal.ui.dispatch.actionControllers.CommandHandlerActionController.execute(CommandHandlerActionController.java:89) sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:103) com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:142) com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:126) com.aptana.portal.ui.internal.BrowserWrapper$2.function(BrowserWrapper.java:51) org.eclipse.swt.browser.WebKit.callJava(WebKit.java:1778) org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:406) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) org.eclipse.swt.widgets.Display.windowProc(Display.java:5616) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5055) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5204) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3646) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: org.eclipse.core.commands.ExecutionException: unknown wizard: null com.aptana.portal.ui.internal.command.NewProjectFromTemplateCommandHandler.execute(NewProjectFromTemplateCommandHandler.java:52) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85) sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ... 47 more {code}
| 8 |
train
|
TISTUD-4603
|
Design the UI for the Mac OSX installer
|
Added an image of Xamarin installer and a screenshot from OSX Installer wiki page for a couple of examples of installer look-and-feel on Mac. The bullet points for us would include something similar: license, prerequisites (Node/SDK/NPM-package), destination, installation, and summary.
| 5 |
train
|
TISTUD-4616
|
BlackBerry and Tizen: not recognized as installed in Appcelerator Studio 3.2.0
|
Description: 1. Download Titanium studio from the BB preview page: http://ec2-50-16-19-245.compute-1.amazonaws.com/studio/bb/ (I can reproduce it on studio 3.2.0.201305081937) 2. Install the studio & setup the BB platform info in the preferences 3. Now create a mobile application app for blackberry Actual result: 1. We can't create an app as the BB platform is greyed out in deployment targets NOTE: When we create a BB module the BB target is not disabled its only when we create an app be it classic or alloy Expected results: 2. The BB target should not be greyed out.
| 5 |
train
|
TISTUD-4618
|
Studio prompts already installed updates
|
We encountered the issue when were checking Studio for updates. The new build was installed as well, as prompted updates. Clicking on "Check for Appcelerator Updates" prompted to install already updated items. It is a *regression*, not occurs in 3.1.0.GA Test steps: 1. Launch Appcelerator Studio 2. Help> Check for Updates and install the build 3. Restart Studio and update available for updates items 4. Help> Check for Appcelerator Updates Actual result: 2. The new Studio build should be offered and installed. 3. Studio should prompt available updates and install them 4. Studio prompts already updated item (see the attachment)
| 8 |
train
|
TISTUD-4619
|
Implement SDKLocator for Windows Phone
|
We need to implement an SDKLocator subclass for windows. The class typically just looks up the SDK given the preference value and does some minor validation on the file/folder structure, and then generates "SDKEntity" instances for each version of the SDK contained therein (which may just be one version here).
| 8 |
train
|
TISTUD-4620
|
Dashboard: Studio 3.2.0 Getting Started switch to advanced perspective generates extra menu
|
Dashboard: Studio 3.2.0 Getting Started switch to advanced perspective generates extra menu. See screenshot. Test Steps: 1. Open Dashboard. 2. Get Started. 3. Switch Perspective. Result: Extra menu appears.
| 5 |
train
|
TISTUD-4621
|
Add Dashboard Configure for Windows Phone
|
Windows: Add Dashboard Configure. See Screenshot.
| 5 |
train
|
TISTUD-4623
|
Update the Dashboard to check for Windows Phone SDK and display corresponding message
|
Update the Dashboard side to call the SDK-Info command with a "windows" key. Then, parse the result and display any info (like we do with the rest of the platforms). The Windows section in Dashboard will look similar to what BlackBerry one shows.
| 5 |
train
|
TISTUD-4631
|
Preferences for Set-up/Configure SDKs link doesn't expand correctly
|
Steps to reproduce: 1. Create a New Titanium Module Project 2. Click on the Set-up/Configure SDKs link 3. A preference dialog pops up, but the user can't edit the android ndk setting (the option is a subset of platforms and it's not expandable) Expected result: User should be able to edit the android ndk Actual result: Android ndk is not editable (NOTE you can still edit this if you go to preferences directly)
| 3 |
train
|
TISTUD-4639
|
Create Alloy Project: Widget Disposed error
|
Studio throws an Internal Error message as Widget Exposed when tried to create an Alloy project. Please refer the attached screen shot and log file for more clarification.
| 3 |
train
|
TISTUD-4640
|
Null Pointer Exception when opening tiapp.xml file (ThreeSixtyProject.java:626)
|
h5. Problem description Could not open tiapp.xml in the editor. After double clicking to open it, an exception is thrown. This is currently happening only in one of my Alloy projects I was working on. Currently not happening on other projects. Attaching Studio log, Error details and Diagnostic Test output. After restarting Studio, tiapp.xml is being opened correctly
| 2 |
train
|
TISTUD-4642
|
NPE when launching a mobile web preview
|
Create a mobile-web project. Right click the project and select to run a preview on a browser. The launch fails with this exception: {code} java.lang.NullPointerException com.appcelerator.titanium.usage.MobileUsageUtil.sendLaunchEvent(MobileUsageUtil.java:45) com.appcelerator.titanium.mobile.cli.nodejs.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:597) com.appcelerator.titanium.mobileweb.ui.launch.MobileWebLaunchConfigurationDelegate.launch(MobileWebLaunchConfigurationDelegate.java:80) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 3 |
train
|
TISTUD-4643
|
Perform shallow clone and remove .git directory when importing samples from git repo
|
I'm assuming if a user imports a sample app like the Field Service one we don't want to retain the commit history, or hook it up to a local git repo. Grabbing a shallow clone will remove the history and make for a faster download. We also will likely want to wipe the .git directory after we clone it so it isn't automatically hooked up to a git repo?
| 5 |
train
|
TISTUD-4646
|
Provide default value/check for BlackBerry NDK path
|
The BlackBerry NDK uses an installer and defaults to specific locations on various OSes. On Mac this is /Applications/bbndk. We should provide a default value or check the default location to try and configure the preference location for the user silently if they use the default location from the installer. We'd likely have to hook a job on plugin startup that checked the location and set the pref (or just use the standard preferences extension to provide a default?)
| 5 |
train
|
TISTUD-4647
|
Use a more visible icon for blackberry platform in userAgent extension
|
The icon used for blackberry platform is very difficult to see on dark themes in the content assist popup.
| 5 |
train
|
TISTUD-4663
|
Android Platform Preferences: unable to remove Android SDK path and Apply changes
|
Android Platform Preferences: unable to remove Android SDK path and Apply changes. This is a regression. This works in Titanium Studio 3.1.0. Test Steps: 1. Open Android Platform Preferences. 2. Delete Android SDK path and Apply. Result: Cannot apply changes. Apply is grayed-out.
| 3 |
train
|
TISTUD-4668
|
Node.ACS Debugger: First debug session results in no variables in stack view
|
Node.ACS Debugger: first debug session results in no variables in stack view. See screenshot. Test Steps: 1. Create Node.ACS Project. 2. Insert breakpoint on line 3 in app.js. 3. Debug. Result: 'No variables' error in stack view.
| 8 |
train
|
TISTUD-4669
|
Node.ACS Debugger: new debug sessions don't hit correct breakpoint
|
Node.ACS Debugger: new debug sessions don't hit correct breakpoint. See screenshot. 1. Create Node.ACS Project. 2. Insert breakpoint on line 3 in app.js. 3. Debug then terminate, kill, and clear the debug session. 4. Debug again. Result: Line 7 is hit instead of line 3. Further debug attempts do not fix the problem. I am not aware of a work-around. Only the first debug session seemed to work.
| 8 |
train
|
TISTUD-4670
|
Node.ACS: Publishing Node.ACS Service does not complete if app removed from acs
|
Node.ACS: Publishing Node.ACS Service does not complete if app removed from acs. Test Steps: 1. Create Node.ACS Project. 2. Package > Deploy App. 3. Package > Remove App. 4. Package > Deploy App. Result: Process never completes, will not cancel. Expected Result: A finite resolution.
| 5 |
train
|
TISTUD-4675
|
Incorrect syntax error notification for a Node.js model's use of the keyword 'default'
|
Incorrect syntax error notification for a Node.js model's use of the keyword 'default' I installed an npm mode mysql (https://npmjs.org/package/mysql) which installed nicely but Titanium Studio (3.1.0.201304151600) is throwing exception errors related to an object property named 'default'. Code snippet is below: {code:javascript} module.exports = FieldPacket; function FieldPacket(options) { options = options || {}; this.catalog = options.catalog; this.db = options.db; this.table = options.table; this.orgTable = options.orgTable; this.name = options.name; this.orgName = options.orgName; this.filler1 = undefined; this.charsetNr = options.charsetNr; this.length = options.length; this.type = options.type; this.flags = options.flags; this.decimals = options.decimals; this.filler2 = undefined; this.default = options.default; //<==== THIS IS WHERE THE SYNTAX ERROR IS this.zeroFill = options.zeroFill; this.protocol41 = options.protocol41 } . . . {code} Screen shot is attached
| 8 |
train
|
TISTUD-4676
|
Node.ACS: disable OK button and add a message on the reason when the input matches the current cname
|
Node.ACS: set cname does not appear to get called. Test Steps: 1. Create Node.ACS Project. 2. Package > Deploy App. 3. Right Click > Node.ACS > Set CName 4. Click OK to use default argument. 5. View log file. Result: Nothing there. No evidence of a shell call.
| 3 |
train
|
TISTUD-4678
|
Node.ACS Debugger: Classic project with acs service asks for filename when breakpoint is hit
|
Node.ACS Debugger: Classic project with acs service asks for filename when breakpoint is hit. See screenshot. Test Steps: 1. Create Classic Project. 2. Add New Node.ACS Service. 3. Insert breakpoint in acs app.js line 3, or appropriate line. 4. Run as Node.ACS Debugger. Result: Ever time a breakpoint is hit, a filename prompt appears. Canceling the prompt appears to be a good workaround. This does not occur with regular Node.ACS Projects.
| 5 |
train
|
TISTUD-4688
|
Android Emulator: new process launched every time emulator is run
|
Android Emulator: new process launched every time emulator is run. Note: LiveView is disabled. Test Steps: 1. Create Classic Project. 2. Run on Android Emulator and let app run. 3. Run on Android Emulator again (Run > Android Emulator). Result: Everytime the run command is run, a new process is launched. See screenshot.
| 8 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.