issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-2071
|
Replace Geolocation client/server icons with new versions
|
The icons for the RedHat Open Shift client/server are not in keeping with rest of the icon templates. They need to be upgraded.
| 2 |
train
|
TISTUD-2072
|
%wizard.nodejsproject.name in "Create Project' wizard
|
# File > New > Project # Note %wizard.nodejsproject.name near the top. Looks like a missed refactoring. Should be something like "New Node.js Project"
| 2 |
train
|
TISTUD-2073
|
Direct user to Node.JS troubleshooting document if NPM is not installed, or package fails to install
|
When a user attempts to install a NPM package and NPM is not installed, or NPM is installed and the package fails, we should direct the user to a troubleshooting document as part of displaying the error. http://go.aptana.com/Installing+Node.js
| 5 |
train
|
TISTUD-2074
|
Assign key-bindings for the Alloy generation wizards
|
Add keyboard shortcut for opening dialog and generating Alloy resources (so user isn't forced to go through UI to do this action and can do so by keeping hands on keyboard) This includes key-bindings for: # Widget # Migration # Controller # Model
| 5 |
train
|
TISTUD-2077
|
New Project Wizard: Templates: template icons are solid red if offline
|
If offline, template icons in the new project wizard are solid red. This is not a regression. There is no log info. Steps to Reproduce: 1. Turn off the internet. 2. Create a new Titanium Mobile project to bring up the new project wizard. Actual Result: Template icons are solid red. Expected Result: Each template icon should have unique pixel art.
| 5 |
train
|
TISTUD-2078
|
For Mobile project wizard, double-click on a template should proceed to next page
|
Steps: 1. Right click in Project explorer > New Titanium Mobile Project 2. On the Template page, double-click on the Single Tab Template Expected result: The next page is shown and the template is selected Actual result: The template is selected
| 5 |
train
|
TISTUD-2079
|
Android Packaging Wizard: allow user to manually enter new directory in distribution path
|
When packaging an android project, the user must select an existing directory. If the user manually enters a previously non-existent directory, there is an error. The directory should be created based on the entered path if it did not exist before. Test Steps: 1. Create an android project. 2. Package to bring up package wizard. 3. Enter an otherwise valid directory that does not exist (e.g., Downloads/newdirectory). Expected Result: Manually entered valid directory should not generate error and should be created when packaging is run.
| 5 |
train
|
TISTUD-2083
|
Investigate if the CTRL-SHIFT-W is related to the browser wrapper
| null | 8 |
train
|
TISTUD-2084
|
Investigate if the CTRL+SHIFT+W is related to the CEF implementation
| null | 8 |
train
|
TISTUD-2086
|
"Right click > Open in New window" in Dashboard should honor Eclipse browser settings
|
This was found in the course of testing TISTUD-1527. Steps: 1. Open dashboard 2. Right click (on a link) > Open in new window Expected Link is opened in a browser based on the Eclipse/Studio settings Actual Link is opened in a new external generic browser with no navigation controls This is currently only occurring on Windows, but an implementation change will affect osx/linux as well
| 8 |
train
|
TISTUD-2088
|
Review Debug on Device platform code contributions
|
Ensure code fits our conventions and standards.
| 8 |
train
|
TISTUD-2089
|
Restrict debugging on device to SDK 2.2+
|
The menu options for debugging should be disabled in < SDK 2.2. There may be other locations we need to check as well, like validating the launch configuration.
| 5 |
train
|
TISTUD-2090
|
Display a set of instructions when launching iOS "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 * Sync to device (iTunes) * Launch app on device (waiting for connection) * Connected 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.
| 13 |
train
|
TISTUD-2091
|
Prompt user to choose a device for debugging when multiple devices with the same application are discovered on a local network
|
If multiple devices all present themselves with the same launched app and same security key, we need to allow the user to select between them * Pop a dialog with the names of all the devices in question * Add a small 16px icon next to the device to identify it (iOS/Android, but could eventually be something like iPhone/iPad) * Okay/Cancel to select a device. Double-clicking on the device also performs an "OK"
| 8 |
train
|
TISTUD-2092
|
Modify code to auto-generate a security key on app packaging
|
See RunOnDeviceIOSConfigurator.java for more information
| 8 |
train
|
TISTUD-2093
|
Templates: Error Enabling Cloud Services during HTML project creation.
|
Description: Creating a new HTML template from Titanium Studio causes an Error Enabling Cloud Services. ACS can be enabled from tiapp overview. See an attached screenshot. Steps to reproduce: 1. Click on HTML-based Application from Titanium Studio Dashboard > Develop Actual result: ACS Error Expected result: No Error
| 8 |
train
|
TISTUD-2105
|
Templates: Error unzipping HTML project creation.
|
Description: Creating a new HTML template from Titanium Studio causes an unzipping error. Steps to reproduce: 1. Click on HTML-based Application from Titanium Studio Dashboard > Develop Actual result: Error Expected result: No Error
| 5 |
train
|
TISTUD-2109
|
"Installed Node.js is an unsupported version"
|
The error message in the issue title pops up when I open TiStudio 2.1.2.201208141459 (attached as image). Clicking "OK" takes me to an [empty document on our wiki|https://wiki.appcelerator.org/display/tis/Upgrading+Node.js] for updating Node.js. As per a conversation with Ingo, this should not be happening in this version of TiStudio.
| 5 |
train
|
TISTUD-2111
|
Reduce required supported node version to 0.6.0
|
Currently, we require node.js to be version 0.8.0 or higher. This can be reduced to 0.6.0.
| 2 |
train
|
TISTUD-2112
|
Python not on the list in commands menu
|
Python is not on the list in Commands menu. This is not regression. h3. Step to reproduce: # Open a Python file: File > New From Template > Python > Blank File # Run a command from the Python Commands Menu (Commands>Python>*) h3. Actual result: Python is not on the list in Commands Menu. h3. Expected result Should exist Python commands in Commands Menu.
| 8 |
train
|
TISTUD-2118
|
If Node.js version is out of date, offer to re-run installer for new version
|
If you have an older version of node.js, you can just install a newer version over the top. Currently we direct the user to a troubleshooting page, but we can improve that process. If the version of node.js is out of date: # Pop up a dialog (currently implemented) letting the user know the version is out of date # Offer to install a newer version for the user (mac and windows). Follow the same steps as the normal installation # If that fails, or on Linux, direct the user to the previous troubleshooting page.
| 5 |
train
|
TISTUD-2127
|
Give descriptive name to Titanium Studio inside VisualVM app
|
For debugging, it's nice to give our app a better name than "Unknown Process". This is relatively straightforward as detailed here: http://stackoverflow.com/questions/4433979/how-do-i-give-a-name-to-a-visualvm-unknown-application {code} -Dvisualvm.display.name=FooBar {code}
| 3 |
train
|
TISTUD-2133
|
A new launch configurations is added on every iOS debug-on-device launch
|
When launching an iOS debug on device (via the Project Explorer debug dropdown), a couple of two new launch configurations is added to the dropdown list. The list is growing on every launch, and there is no way to remove those items, even from the launch configuration dialog (those launches are probably defined as private). Expected behavior: A previous launch should be added to the list, only if it's a new one for the project. Also, only one item should be added, and be named as 'iOS Device - xxx'. Clicking that item should just launch the debug on device, just like clicking the project-explorer "iOS Device" debug action.
| 13 |
train
|
TISTUD-2134
|
Validate project name for Node.ACS projects
|
When creating projects with Node.ACS enabled, we need to validate the name. So far, I know that "." are not valid for Node.ACS projects. So for Titanium Mobile, we need to check the "." only if Node.ACS is enabled. For a standalone Node.ACS project, we need to add a check for valid strings. An alternative would be to format the project name so it's valid for an nettle "new" command. I'm not sure what the implications are. Note: There may be other strings that are not valid h3. Suggestions * For new projects, validate that "." does not appear in the name * For existing projects, if a "." appears in the name, prompt the user to pick a new name
| 13 |
train
|
TISTUD-2136
|
Unable to distribute iPhone app due to NPE in loading local provisioning profile
|
When trying to build for distribution, the distribute window never opens and the user cannot distribute their app. An error ops up with a NullPointer Exception. Here is the provisioning profile info: {"wwdr": true, "iphone_dist_name": ["*****"], "sdks": [], "iphone_dev_name": [*****], "iphone_dist_message": null, "wwdr_message": null, "itunes_message": null, "itunes": true, "iphone_dev_message": null, "iphone_dev": true, "iphone_dist": true, "ipad": false, "itunes_version": "10.0"} The error log is below: !ENTRY org.eclipse.jface 4 2 2012-08-23 14:35:53.615 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfile(IOSConfigurationHelper.java:276) at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfiles(IOSConfigurationHelper.java:179) at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.loadLocalProvisioningProfiles(IOSConfiguration.java:507) at com.appcelerator.titanium.mobile.ui.iphone.wizard.SimpleiPhonePackagingComponent.refreshProfiles(SimpleiPhonePackagingComponent.java:511) at com.appcelerator.titanium.mobile.ui.iphone.wizard.SimpleiPhonePackagingComponent.createPageContents(SimpleiPhonePackagingComponent.java:99) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingComponent.createContents(AbstractiPhonePackagingComponent.java:61) at com.appcelerator.titanium.mobile.ui.iphone.launch.BaseIOSLaunchConfigurationTab.createPlatformControl(BaseIOSLaunchConfigurationTab.java:70) at com.appcelerator.titanium.ui.launching.BaseTitaniumLaunchConfigurationTab.createControl(BaseTitaniumLaunchConfigurationTab.java:74) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:803) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:735) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:623) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:640) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:602) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:578) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:941) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:560) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1726) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:283) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.access$1(LaunchConfigurationView.java:272) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView$2.run(LaunchConfigurationView.java:261) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1132) at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:579) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:587) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:521) at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:81) at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.runWithEvent(OpenLaunchDialogAction.java:89) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241) at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !SESSION 2012-08-23 14:38:05.046 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/mark_allen/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/mark_allen/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.net 1 0 2012-08-23 14:38:19.204 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.ui 4 0 2012-08-23 14:39:29.166 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfile(IOSConfigurationHelper.java:276) at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfiles(IOSConfigurationHelper.java:179) at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.loadLocalProvisioningProfiles(IOSConfiguration.java:507) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningComponent.createPageContents(IOSProvisioningComponent.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingComponent.createContents(AbstractiPhonePackagingComponent.java:61) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingPage.createControl(AbstractiPhonePackagingPage.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningPage.createControl(IOSProvisioningPage.java:38) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.appcelerator.titanium.mobile.ui.iphone.wizard.PackageHandler.execute(PackageHandler.java:43) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.ui 4 0 2012-08-23 14:39:55.355 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfile(IOSConfigurationHelper.java:276) at com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.loadLocalProvisioningProfiles(IOSConfigurationHelper.java:179) at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.loadLocalProvisioningProfiles(IOSConfiguration.java:507) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningComponent.createPageContents(IOSProvisioningComponent.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingComponent.createContents(AbstractiPhonePackagingComponent.java:61) at com.appcelerator.titanium.mobile.ui.iphone.wizard.AbstractiPhonePackagingPage.createControl(AbstractiPhonePackagingPage.java:62) at com.appcelerator.titanium.mobile.ui.iphone.wizard.IOSProvisioningPage.createControl(IOSProvisioningPage.java:38) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.appcelerator.titanium.mobile.ui.iphone.wizard.PackageHandler.execute(PackageHandler.java:43) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
| 5 |
train
|
TISTUD-2138
|
Dashboard: Update Android SDK to 20.0.3 on Staging
|
Dashboard: Update Android SDK to 20.0.3 on Staging
| 3 |
train
|
TISTUD-2139
|
Exception in the log during acs.core plugin loading
|
{code} !ENTRY org.eclipse.osgi 2 0 2012-08-23 14:46:05.930 !MESSAGE While loading class "com.appcelerator.titanium.acs.core.ACSCorePlugin$TiAppChangeListener", thread "Thread[Worker-15,5,main]" timed out waiting (5044ms) for thread "Thread[Worker-8,5,main]" to finish starting bundle "com.appcelerator.titanium.acs.core_1.0.0.qualifier [4]". To avoid deadlock, thread "Thread[Worker-15,5,main]" is proceeding but "com.appcelerator.titanium.acs.core.ACSCorePlugin$TiAppChangeListener" may not be fully initialized. !STACK 0 org.osgi.framework.BundleException: State change in progress for bundle "reference:file:/Users/mxia/git-workspaces/master/titanium_studio/plugins/com.appcelerator.titanium.acs.core/" by thread "Worker-8". 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.BundleLoader.findClassInternal(BundleLoader.java:476) 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$1.run(ACSCorePlugin.java:199) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException ... 15 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.BundleLoader.findClassInternal(BundleLoader.java:476) 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$1.run(ACSCorePlugin.java:199) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 8 |
train
|
TISTUD-2140
|
Create a wiki page on how to debug on iOS device from Studio
|
We should create a wiki page that lists out the requirements needed as well as the detailed steps to successfully debug on iOS device. We should also add a link that points to the wiki page to the wizard when it is launched in debug mode.
| 8 |
train
|
TISTUD-2142
|
Make the progress monitor for the debug process display more detailed message
|
Debuggin on iOS device is a multi-step process (listed in TISTUD-2090), and before we implement the wizard idea, we should improve the message we show to the user after we started step 2 and are waiting for user to complete step 3 once iTunes finishes syncing. The suggest message is "Waiting for device... (the app is being installed to iTunes; when iTunes finishes syncing, please launch the app on device for the debugger to connect)."
| 5 |
train
|
TISTUD-2143
|
Macbook Pro Retina: display text needs adjustment
|
The tab header text needs to be adjusted to appear more desirable.
| 8 |
train
|
TISTUD-2150
|
Create Module: New > Titanium Mobile Module project > Install JDT link should point to latest docs
|
New > Titanium Mobile Module project > Install JDT link should point to latest docs Steps to Reproduce: 1. On a system on which JDT is not installed, choose to create a new titanium mobile module through titanium studio. A wizard to create New Titanium Mobile Module project is shown 2. Click on the Install JDT link, below the Deployment Target field. Actual: Links to 2.0 documentation Expected: Should point to latest and get redirected to 2.1.1 docs.
| 3 |
train
|
TISTUD-2151
|
Tweak new device and packaging icons
|
Related to TISTUD-1351, we request a few small changes to the icons: # The Android device debugging icon looks odd next to the iOS one. The phones should probably be at least similar in width # The shadows around the boxes for distribution are too dark. Perhaps just reduce the opacity a bit.
| 5 |
train
|
TISTUD-2156
|
Download the latest Android SDK directly
|
Download the latest SDK unless the user has a compatible SDK already installed. See https://wiki.appcelerator.org/display/tools/Android+SDK+Installation for reference.
| 8 |
train
|
TISTUD-2157
|
Download and install the base required packages
|
The packages include: 1. Platform tools 2. Google Maps v8 3. Base Platform v8 See https://wiki.appcelerator.org/display/tools/Android+SDK+Installation for reference.
| 13 |
train
|
TISTUD-2158
|
"Enable Cloud Services" button is enabled for external tiapp.xml files
|
When opening an external tiapp.xml in the TiApp editor, the 'Cloud Services' button should be disabled just like the other controls that require a project context.
| 2 |
train
|
TISTUD-2159
|
Notify the dashboard when a module installation is completed
|
Fire a dashboard notification at the end of the Module installation.
| 5 |
train
|
TISTUD-2160
|
Refresh the 'My Modules' listing in the Dashboard when it's being notified that a module was installed
|
The Studio will notify with an event that a Module was installed. Once this notification is captured, refresh the 'My Modules' list (probably by calling again the 'getMobileModules' action on the 'portal.titanium.modules' controller)
| 8 |
train
|
TISTUD-2163
|
Rename the configure tab to "Get Started"
|
# Rename the first tab in the Dashboard to "Get Started" # Update the wiki documentation to reference the new tab name (https://wiki.appcelerator.org/display/guides2/Setting+up+Titanium+Studio)
| 5 |
train
|
TISTUD-2164
|
Run the browser configuration check to make sure Mobile Web can be used
|
# If on Mac and Windows, the check described in TISTUD-2187 will be run on dashboard open with the other platform configuration options # If there are compatible browsers, indicate the user is good to go # If there are no compatible browsers, or you are on Linux, indicate the set of required browsers. # Add a button to refresh the check (if it failed)
| 13 |
train
|
TISTUD-2165
|
Add button to create a new Mobile Web project from the dashboard
|
See https://wiki.appcelerator.org/display/prd/Studio+Dashboard for more information.
| 5 |
train
|
TISTUD-2166
|
Add button to dashboard to run previously created projects
|
# Add button to call new action to run project created in above step (APSTUD-4801), greyed out until a project is created, or there is at least one project in the workspace. # If the user happened to close and reopen the dashboard, the "just created" project might be lost. So, we always run the most recent project based on timestamp.
| 8 |
train
|
TISTUD-2169
|
Add user-friendly labels for template types
|
We have a way of defining groups or categories of templates, but there is no user-friendly name for them such that it could be displayed to the user. Add something that would allow us to group templates as shown in the mockup.
| 5 |
train
|
TISTUD-2170
|
Rework template selection UI to new version
|
By default, the first item in the first group is selected, and the corresponding description is shown. This should be the "Alloy blank" template for Titanium Mobile projects, assuming they have alloy installed
| 13 |
train
|
TISTUD-2172
|
Create build participant to auto-compile embedded ACCS service when changes occur
|
For an integrated project, where the client and server are the same thing, we need to update the bindings for the embedded service when the service changes # Watch for changes in the service.js file # If a change happens, re-run the compilation step to update the bindings.
| 8 |
train
|
TISTUD-2174
|
Dashboard: Develop: Create New Project template is duplicated and deprecated
|
The 'Create New Project' template on the dashboard is duplicated and deprecated by 'Default Project'. 'Default Project' is the option that exists in the New Project Wizard. This occurs on the Dashboard and Dashboard Preview. Steps to Reproduce: 1. Open the Dashboard. 2. View Develop. Actual Result: 'Create New Project' and 'Default Project' both exist though they are the same. 'Create New Project' is deprecated. Expected Result: Only 'Default Project' should exist because it is the option available in the New Project Wizard.
| 5 |
train
|
TISTUD-2178
|
Add version information to Mac browser configuration names and refresh version info on demand
|
Related to TISTUD-1414. As discussed, we need to include the version of the browser in question as part of the browser name (see image for example) Ideally, this value would be dynamic, but that appears to be impossible given the current UI. In the case where the user upgrades the browser later, the suggestion is that when the user re-runs the configuration step to auto-search, we replace the version #s of the existing browsers with the newer version. *Chrome* /Applications/Google\ Chrome.app/Contents/Info.plist *Safari:* /Applications/Safari.app/Contents/version.plist *Firefox:* firefox -v
| 8 |
train
|
TISTUD-2180
|
Add tags column to project template selections screen
|
Once APSTUD-7352 is implemented, add a column to the left displaying a list of all the tags assigned to templates. A template might appear in one or more tagged areas: Left column is separated by template tag. For Titanium Mobile projects, we might see: * Alloy * Titanium Mobile Other project types might just see (assuming there is no tags) * Ruby * Mobile Web * etc Suggest having an "All" tag at the bottom that shows all templates if you'd like to browse the complete list
| 8 |
train
|
TISTUD-2186
|
Publishing: Distribute > Apple iTunes Store: success dialog does not appear
|
When Distribute > Apple iTunes Store is complete, there is no success dialog, but the process appears to have been completed successfully. This is not a regression. Steps to Reproduce: 1. Create a new project. 2. Distribute > Apple iTunes Store. Actual Result: Process completes successfully and the Xcode Organizer is brought up. Expected Result: Process completes successfully, Xcode Organizer is brought up, success dialog appears.
| 5 |
train
|
TISTUD-2188
|
Add Mobile Web requirements to sdk_info.json file
|
Mobile Web has minimum supported browser requirements. Add an element to sdk_info.json for the dashboard that encapsulates this information (the values below are correct): {code} "mobileweb":{ "win32":{"Firefox":["10.0"],"InternetExplorer":["9.0"],"Chrome":["10.0"],"Safari":["5.0"]}, "macosx":{"Firefox":["10.0"],"Chrome":["10.0"],"Safari":["5.0"]}, "linux":{"Firefox":["10.0"],"Chrome":["10.0"]} } {code} Note that a single number is actually an OSGI version range, i.e. "4.0" == >= 4.0. The above values should accept version ranges
| 5 |
train
|
TISTUD-2189
|
Run browser configuration check on Mac and Windows if necessary
|
If on Mac or Windows, run the configuration in TISTUD-1414 and TISTUD-1738 if there are no browsers configured (if not, you would notice no browser names have version #s attached)
| 5 |
train
|
TISTUD-2190
|
Check version strings from the browser settings vs the versions in sdk_info and return results
|
# Check the version strings in the name vs the versions in sdk_info. The version string is appended to the end of the browser name. # Return a similar success value to iosSdk with installedBrowsers and installedBrowsers
| 5 |
train
|
TISTUD-2200
|
Dashboard: Update Android SDK to 20.0.3 on Production
|
Android SDK 20.0.3 has been tested on all platforms, there are no issues, it can be pushed to the live dashboard.
| 3 |
train
|
TISTUD-2201
|
New user on Appcelerator if directly logins to Titanium Studio, their Login Splash Screen text boxes dislocates upwards and covers Appcelerator logo.
|
This bug affects Titanium Studio 2.1.2; 2.1.1; 2.1.0 Steps : 1.Log out from titanium studio. 2.Launch Titanium Studio . 3.Select second option on Titanium Splash screen : "I don't have an account with Appcelerator".( Screenshot- Titanium Studio_004.png attached) 4. Press "Next" button. 5.Observe the splash screen which asks for login credentials (Screenshot Titanium Studio _001.png attached ) [Expected Result] No UI related error should happen . [Actual Result] Login Screen text boxes are dislocated upwards and covering Appcelerator logo. Note: This issue is specific to Ubuntu 12.04 and Ubuntu 10.04; unable to recreate it on Mac OS X and Windows OS
| 5 |
train
|
TISTUD-2210
|
Allow developer to specify custom domain name for Node.ACS service when publishing
|
When publishing a Node.ACS service, the user can choose the custom domain name for which to associate the service. Pop up a dialog during the the _initial_ publish process, allowing the user to enter a domain name instead of the default.
| 5 |
train
|
TISTUD-2211
|
Support "define" method for defining RequireJS/AMD modules
|
Looking at http://usejsdoc.org/howto-commonjs-modules.html http://requirejs.org/docs/api.html#define and https://github.com/amdjs/amdjs-api/wiki/AMD There's a "define" method that takes in up to 3 arguments. The last argument is a function or object that is the object assigned to the module's module.exports property. The first optional argument is a string defining the module id. The second optional argument is an array of strings representing dependencies (ids of modules this one depends upon).
| 8 |
train
|
TISTUD-2212
|
Auto-update ACCS local port numbers if related projects change
|
When we bind a ACCS service to a Titanium Mobile project, the local port number for the ACCS service might change. We need to listen for these port event changes, and update the references in the local project.
| 8 |
train
|
TISTUD-2213
|
Add Alloy Widget menu item to select/import widgets that are available locally
|
Add a right-click menu "Alloy > Add Widget > (dynamic list of widgets)". Place a separator between the dialog item (from TISTUD-2280) and the actual list. Selecting an item adds it to the app right away, as a quick way to do so when you already know the widget you want. The list of available widgets and metadata will come from the "alloy list widgets" command. When user selects a widget put the id that is listed in the returned json metadata for the widget into the Alloy app/config.json in the dependencies object. For example if the user selected the "Search For Books" widget then the config should look like the following. { "global": {}, "env:development": {}, "env:test": {}, "env:production": {}, "os:ios": {}, "os:android": {}, "dependencies": { "com.appcelerator.searchForBooks":"1.0" } }
| 13 |
train
|
TISTUD-2214
|
Titanium Studio: License Agreement is not provided.
|
Installer copyright information is not available in Installer copyright option. Step to Reproduce: 1. Click on 'Help Menu' 2. Click 'Install New Software' 3. Click on 'Already Install' Link 4. Select Installed 'Titanium Studio' 5. Click on 'Property' Option 6. Select 'License Agreement' Actual Result: No License Agreement is present. Expected Result: Present License Agreement available for user.
| 3 |
train
|
TISTUD-2216
|
Titanium Studio: New Installation Copyright information is missing.
|
Installer copyright information is not available. Step to Reproduce: 1. Click on 'Help Menu' 2. Click 'Install New Software' 3. Click on 'Already Install' Link 4. Select Installed 'Titanium Studio' 5. Click on 'Property' Option 6. Select 'Copyright' Actual Result: No Copyright Information is present. Expected Result: Present copyright Information available for user.
| 5 |
train
|
TISTUD-2217
|
Update ACCS unpublish/list/logcat/loglist commands to pass an appid or app name rather than a directory
|
Based on the related ticket, we need to pass in appids or app names rather than the directory when calling: * unpublish * list * logcat * loglist
| 8 |
train
|
TISTUD-2218
|
User has to constantly re-enter usernames and passwords. Error is "Secure storage was unable to retrieve the master password from the OS keyring"
|
{code} !ENTRY org.eclipse.equinox.security 4 0 2012-08-30 10:44:01.037 !MESSAGE Secure storage was unable to retrieve the master password from the OS keyring. Make sure that this application has access to the OS keyring. If the error persists, the password recovery feature could be used, or secure storage can be deleted and re-created. !STACK 0 java.lang.SecurityException: Could not obtain password. Result: -67061 at org.eclipse.equinox.internal.security.osx.OSXProvider.getPassword(Native Method) at org.eclipse.equinox.internal.security.osx.OSXProvider.getPassword(OSXProvider.java:45) at org.eclipse.equinox.internal.security.storage.PasswordProviderModuleExt.getPassword(PasswordProviderModuleExt.java:35) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:259) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224) at org.eclipse.equinox.internal.security.storage.SecurePreferences.get(SecurePreferences.java:262) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.get(SecurePreferencesWrapper.java:106) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:83) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:63) at org.eclipse.equinox.internal.security.ui.storage.TabPassword.changePassword(TabPassword.java:318) at org.eclipse.equinox.internal.security.ui.storage.TabPassword$3.widgetSelected(TabPassword.java:136) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.equinox.security 4 0 2012-08-30 10:44:01.038 !MESSAGE Unable to decrypt value associated with the key "org.eclipse.equinox.security.osxkeystoreintegration" on the node "/org.eclipse.equinox.secure.storage/verification". !STACK 0 org.eclipse.equinox.security.storage.StorageException: No password provided. at org.eclipse.equinox.internal.security.storage.SecurePreferences.get(SecurePreferences.java:264) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.get(SecurePreferencesWrapper.java:106) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:83) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:63) at org.eclipse.equinox.internal.security.ui.storage.TabPassword.changePassword(TabPassword.java:318) at org.eclipse.equinox.internal.security.ui.storage.TabPassword$3.widgetSelected(TabPassword.java:136) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.equinox.security 4 0 2012-08-30 10:44:01.040 !MESSAGE Secure storage was unable to retrieve the master password from the OS keyring. Make sure that this application has access to the OS keyring. If the error persists, the password recovery feature could be used, or secure storage can be deleted and re-created. !STACK 0 java.lang.SecurityException: Could not obtain password. Result: -67061 at org.eclipse.equinox.internal.security.osx.OSXProvider.getPassword(Native Method) at org.eclipse.equinox.internal.security.osx.OSXProvider.getPassword(OSXProvider.java:45) at org.eclipse.equinox.internal.security.storage.PasswordProviderModuleExt.getPassword(PasswordProviderModuleExt.java:35) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:259) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224) at org.eclipse.equinox.internal.security.storage.SecurePreferences.get(SecurePreferences.java:262) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.get(SecurePreferencesWrapper.java:106) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:83) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:63) at org.eclipse.equinox.internal.security.ui.storage.TabPassword.changePassword(TabPassword.java:318) at org.eclipse.equinox.internal.security.ui.storage.TabPassword$3.widgetSelected(TabPassword.java:136) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.equinox.security 4 0 2012-08-30 10:44:01.041 !MESSAGE Unable to decrypt value associated with the key "com.appcelerator.titanium.core.ACCOUNT_TIMESTAMP/file:/Applications/Titanium Studio/" on the node "/com/appcelerator/titanium/core". !STACK 0 org.eclipse.equinox.security.storage.StorageException: No password provided. at org.eclipse.equinox.internal.security.storage.SecurePreferences.get(SecurePreferences.java:264) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.get(SecurePreferencesWrapper.java:106) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:83) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:96) at org.eclipse.equinox.internal.security.storage.friends.ReEncrypter.decrypt(ReEncrypter.java:63) at org.eclipse.equinox.internal.security.ui.storage.TabPassword.changePassword(TabPassword.java:318) at org.eclipse.equinox.internal.security.ui.storage.TabPassword$3.widgetSelected(TabPassword.java:136) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclip...
| 13 |
train
|
TISTUD-2221
|
Dashboard: Dashboard displays old version for build numbers higher then 2.X
|
After updating to the nightly 3.3.0.201209032204 build of Titanium Studio, I now only get the generic old dashboard rather then the new dashboard. Loading in any 2.X build of Titanium Studio loads the correct dashboard. This is a regression as this works in the 2.x builds. Steps to reproduce: 1. Install any Titanium Studio build in the 2.x range. 2. Upgrade from the nightly build to 3.3.0.201209032204. 3. Open Titanium Studio. Expected results: The dashboard should correctly load with the new dashboard content. Actual results: The dashboard loads with the default older dashboard (see screenshot).
| 5 |
train
|
TISTUD-2224
|
Add CLI command support for building an iOS project
|
This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command. We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build [--platform=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]] [--package] [--device] [--simulator|--emulator] [--production] [--development] [--verbose [0-5]] [project-dir] {code}
| 5 |
train
|
TISTUD-2225
|
Add CLI command support for building an Android project
|
This one is only for V2 (Node.js). The Python implementation in V1 does not support a building command. We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build [--platform=[iphone,ipad,ios,android,blackberry,mobileweb,etc.]] [--package] [--device] [--simulator|--emulator] [--production] [--development] [--verbose [0-5]] [project-dir] {code}
| 5 |
train
|
TISTUD-2226
|
Prevent users from using a capital letter in module name or module ID
|
While creating a new android or mobile web module,if the 'Project name' field contains any capital letter, then it is giving error message.Screenshot of the message and studio logs are attached with the bug. Steps to reproduce 1. Create a new titanium mobile module project and select android as deployment target. 2. Give project name - 'MyAndroidModule' and module id - 'ti.mymodule' .Click next and then finish Expected result 2. Android module should get created. Actual result 2. It creates module with many files missing. Gives an error message for the same. Snapshot attached.
| 5 |
train
|
TISTUD-2228
|
Commands: HTML: Validate Syntax (W3C) does not respect browser settings
|
When Commands > HTML > Validate Syntax (W3C) is run on an html file, the resulting webpage loads in the internal browser opposed to the browser in the settings (i.e., Chrome). Here is the local URL that was opened when command is run: {code} file:///var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/com.aptana.editor.common1730299112518326424.html {code} Steps to Reproduce: 1. Create a new project. 2. Add an HTML file. 3. Open the HTML file in editor. 4. Run Commands > HTML > Validate Syntax (W3C) Actual Result: Local syntax validation webpage opens in internal browser. Expected Result: Local syntax validation webpage should open in browser based on Preferences (i.e., Chrome, Firefox). Note: The internal browser is known to crash studio.
| 5 |
train
|
TISTUD-2231
|
Update Alloy branding
|
Update the project and wizard icons with the updated imagery.
| 3 |
train
|
TISTUD-2236
|
Update sdk_info.json file in dashboard to support iOS 6
|
See http://preview.appcelerator.com/dashboard/sdk_info.json for the current content. We need to update the versions for iOS to include 6.0.
| 5 |
train
|
TISTUD-2237
|
Opening tiapp.xml for already present apps after updating to studio 2.1.3.201209051727 beta gives us error 'Could not open the editor: An unexpected exception was thrown.'
|
This is a regression.It was fixed in Titanium Studio 1.0.But now we can see the issue again. Description: 1.Update the studio to 2.1.3.201209051727 Beta. 2.open any tiapp.xml for the app already present. 3.You will see that you will get an error "could not open the editor:An exception was thrown." NOTE : If I create a new project I am not seeing this issue.I am seeing it only for the projects already present. Actual result: 1.Opening tiapp.xml in studio 2.1.3.201209051727 beta gives us error 'Could not open the editor: An unexpected exception was thrown.' Expected result: 1.Opening tiapp.xml in studio 2.1.3.201209051727 beta should not give us error 'Could not open the editor: An unexpected exception was thrown.'
| 5 |
train
|
TISTUD-2239
|
Update SDK version checks from 2.2 to 3.0
|
The SDK changed its versioning from 2.2 to 3.0. We need to review any checks inside the code to see if they need to be updated.
| 5 |
train
|
TISTUD-2241
|
Modules in the tiapp section shows as not supported by sdk
|
Steps: 1. Open a tiapp.xml 2. Add a module that has both a name and id (look at the module manifest file) Expected Results: Module should appear as valid and enabled Actual Results: Module is displayed as not supported by sdk Looking at the code, it looks like the issue is with mismatch between id and name. It is also causing junit failures
| 8 |
train
|
TISTUD-2243
|
Build: running titanium project causes No enum const class error
|
Launching Android Emulator in debug, or iPhone Simulator w/o debug mode prompts error message. Android Error Message: "An internal error occurred during: "Launching Titanium Android Emulator - Default_Project". No enum const class com.appcelerator.titanium.core.launching.LogLevel.info" iOS Error Message: "An internal error occurred during: "Launching Titanium iPhone Simulator - Default_Project". No enum const class com.appcelerator.titanium.core.launching.LogLevel.info" Steps to Reproduce: 1. Create Default Mobile Project 2. Run Project Debug as "Android Emulator" OR run in iOS Simulator. Actual Result: Error Message, but app otherwise runs successfully. Expected Result: Debug/run is successful.
| 3 |
train
|
TISTUD-2244
|
NPE in the log when opening Titanium preferences page on Linux
|
When the Titanium Studio > Titanium preference page is opened on Linux, the following exception is generated in the log: {code} !ENTRY com.appcelerator.titanium.ui.ide 4 0 2012-09-04 13:01:14.789 !MESSAGE (Build 2.1.2.201208301612) [ERROR] Failed to load BlackBerry device password !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.ui.preferences.TitaniumPreferencePage.initialize(TitaniumPreferencePage.java:153) org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233) org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501) org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258) 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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252) org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674) org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704) org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888) 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.firePostSelectionChanged(StructuredViewer.java:886) org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1726) org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139) org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1054) org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:729) org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:375) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:371) org.eclipse.jface.window.Window.create(Window.java:431) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.createDialogOn(WorkbenchPreferenceDialog.java:102) org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:192) org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:116) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection$2.linkActivated(TiAppDeployTargetsSection.java:278) org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:616) 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) {code} This is because we are only creating BlackBerry fields on Mac and Windows. Think we should instead always create the fields but then hide them using GridData.exclude according to the OS; that way we don't have to check if a field is null all over the place.
| 5 |
train
|
TISTUD-2245
|
iOS Device Debug and deployment ends up in Error " java.lang.NullPointerException..."
|
An error occurred while running debug on iOS device Error: "java.lang.NullPointerException..." Steps to Reproduce: 1. Create default mobile application 2. Debug on iOS device Actual Result: Error Expected Result: App installed on the device and run in debug perspective.
| 5 |
train
|
TISTUD-2246
|
Android Device Debugger pointer is not pointing to the current lines
|
The debugger Arrow pointer does not indicate any breakpoints in app.js. Steps to Reproduce: 1. Create default project 2. Run debug on the device 3. Press "Step Over" in debug window Actual Result: No Arrow pointer hits the breakpoints in app.js Expected result: Arrow pointer hits the breakpoints.
| 8 |
train
|
TISTUD-2251
|
Support Node/NPM module loadpaths
|
We currently assume that a project root is the module root path. We need to query node/npm for the list of module load paths ($NODE_PATH) and try to resolve/search against those, as well as handle searching up the hierarchy for node_modules directories, and handle loading "core" modules from node itself. The following pseudo-code gives the algorithm: http://nodejs.org/api/modules.html#modules_all_together See: http://www.bennadel.com/blog/2169-Where-Does-Node-js-And-Require-Look-For-Modules-.htm http://nodejs.org/api/modules.html#modules_core_modules Additionally, it may make sense to index the paths specified in NODE_PATH on startup.
| 13 |
train
|
TISTUD-2253
|
Add Update All Modules Functionality
|
Currently the my modules "Update All" button is disabled, since we don't currently support installing multiple modules. The action controller is in place to support multiple module updates, the dashboard needs to use it. It will also need to properly refresh the status of the installed modules
| 8 |
train
|
TISTUD-2255
|
Users should be able to add modules to specific projects using the my modules section in the dashboard
|
We need to add an additional use case to allow users to add modules to projects. The my modules section should support the following use cases: -If a module is already installed globally, we should have an "Add to Project" action. This will display a prompt to select multiple projects to add the module reference to. -If the module is not installed globally, after installation, we prompt the user to select multiple projects to add the module reference to
| 8 |
train
|
TISTUD-2256
|
Update all modules using the dashboard to allow users to add modules to projects
|
If update all is used, the user should be prompted to add the modules to a set of projects. So for each module, the user can select a list of projects to add the module to. The current proposed UI is to use a check tree of modules, and the child nodes of each tree is a project. Enabling the check for the top-level module node would automatically add module to all the projects. Users can select which specific modules to add to which projects.
| 13 |
train
|
TISTUD-2263
|
Add ability to pass a list of platforms to be initially selected in Titanium Mobile project wizard
|
The Titanium mobile project wizard page currently will select all deployment targets that are enabled. For creating new mobile web project from dashboard, we need the ability to pass in the list of platforms to be selected by default.
| 13 |
train
|
TISTUD-2264
|
HTML Files get !DOCTYPE declarations marked as warnings for unclosed tags
|
This is not a regression bug.This happens on Titanium Studio, build: 2.1.0 as well. Tested and found this bug on : Ubuntu 10.04 and Mac Mountain Lion 10.8.1. Steps to reproduce: 1. Open File > New -> Web Project > and choose "Next" 2. Select the HTML Boilerplate (cached) version and select "Finish" 3. Observe the 'red color' error mark on created new web project. 4. Expand created new web project. Actual result: The "New web project" is throwing error on style.css file. Expected result: Default Project should be error free. Screenshots attached.
| 8 |
train
|
TISTUD-2265
|
Remove extraneous templates as part of Custom Cloud project wizard
|
When creating a new ACCS/Node.ACS project, the project wizard shows Web templates. This is confusing, as those templates don't apply. They should be removed. It's likely we need a project type of nodeacs (since that is different than a straight node.js project might be)
| 2 |
train
|
TISTUD-2267
|
Add deprecated flag to JSCA spec for functions, events and properties
|
Currently only types can be marked as deprecated. We need to extend this to functions, properties, events, and event properties
| 8 |
train
|
TISTUD-2268
|
Add validation build participant to highlight deprecated Titanium Mobile code
|
Once we have the deprecated flag for more JSCA members, we need to validate and warn about deprecated usage on both build and reconcile. This would leave the typical yellow "squiggly" underlining of the reference, as well as an entry in the Problems view.
| 13 |
train
|
TISTUD-2269
|
Preferences: Add ability to display full Xcode path if truncated
|
In the Titanium preferences, if the Xcode path is too long, there is no way to view the full path because the text field is locked. There is no way of knowing which Xcode is being used. This blocks testing. See Screenshot. Steps to Reproduce: 1. Open Preferences > Titanium Studio > Titanium > Xcode Path. Actual Result: If the path is too long, it will be visually truncated, without the ability to reveal the full path. Expected Result: Some mechanism to view the full path.
| 3 |
train
|
TISTUD-2729
|
Update Titanium Mobile HTML template with new iPhone 5 splash image
|
Based on the new image attached to TIMOB-10886, update the default image for samples and templates. Marking this for 3.0.0, as we'll need a new Studio build to get this into user's hands.
| 3 |
train
|
TISTUD-2275
|
Make the left and right arrow keys traverse the list of project templates
|
Left and right arrow keys fail to select project templates. Steps to reproduce. 1. Select 'New' Menu bar 2. Select 'Titanium Mobile Project' 3. Try to select project templates with 'Arrow Keys' ex: Left and Right Keys. Actual Result: Fail to select project templates. Expected Result: Project templates get selected with arrow keys.
| 5 |
train
|
TISTUD-2276
|
Support adding modules with no version specified
|
Titanium SDK added a feature that will default to the latest module version if none is specified int he tiapp.xml (TIMOB-7973). When specifying a module, we should default to no version (use latest). This will enable users to more easily update modules without having to modify the tiapp.xml
| 13 |
train
|
TISTUD-2277
|
Add vertical scrolling to project template description area
|
Unable to scroll down to view project template's detailed description. Steps to Reproduce: 1. Select 'Titanium Mobile Project' from the menu bar 2. Select 'Master Detail Application' 3. Observe the detail description area. Actual Result: 1. The text is hidden and unable to scroll down. Expected Result: 1. All text should be visible and if scroll able in case if text are more descriptive or long.
| 5 |
train
|
TISTUD-2280
|
Present user with Alloy Widget selection dialog to select widgets that are available locally
|
Add a right-click "Alloy > Add Widget > Browse..." menu item/command that opens a dialog/wizard similar to our Project template selection. This is a means of users being able to browse and explore the available widgets when they're not sure the specific one they want. The list of available widgets and metadata will come from the "alloy list widgets" command. When user selects a widget put the id that is listed in the returned json metadata for the widget into the Alloy app/config.json in the dependencies object. For example if the user selected the "Search For Books" widget then the config should look like the following. { "global": {}, "env:development": {}, "env:test": {}, "env:production": {}, "os:ios": {}, "os:android": {}, "dependencies": { "com.appcelerator.searchForBooks":"1.0" } }
| 13 |
train
|
TISTUD-2285
|
Android Preferences: configure button fails to launch android installer
|
When Preferences > Titanium > iOS Configure button is pressed, nothing appears to happen. In reality, the dashboard is opening in the background to the configure page. I would recommend using the Configure button for the same action it would perform if launched from dashboard. h3. Steps to Reproduce: # Go to Preferences > Titanium > iOS and click the Configure button. h3. Actual Result: Dashboard configure opens in the background. From a usability perspective it appears as though nothing happens. h3. Expected Result: Either the button isn't there at all because it doesn't appear to do anything, or it opens a wizard that would normally be opened using the dashboard (if possible).
| 5 |
train
|
TISTUD-2286
|
Each Platform should have separate pages for their settings, not enough space to adjust all the platform settings on one page.
|
A) Preferences>Titanium Studio>Titanium The 'Titanium' drop node should have the subclasses for: 1. iOS Platform 2. Android Platform 3. BlackBerry Platform 4. Windows Platform a) Each Platform should have different pages for their settings. There is not enough space for all of the platform to be on one page. b) Currently there is only iOS platform for x-code certification settings. It should include all the 'iOS Certification' settings and 'iOS SDK Home' path settings'.
| 13 |
train
|
TISTUD-2287
|
TiApp Editor: prompt to save when focus leaves tiapp editor
|
Android Device Debugger: debug drop-down menu fails to list device option if tiapp.xml is dirty yet has a valid SDK. For instance, if a project has SDK 2.1.2 selected in the tiapp.xml and the xml is saved, then the tiapp.xml sdk version is changed to 3.0.0 but not saved, the debug to device option is not available under Debug > Android Device until the tiapp.xml is saved. There are probably many edge cases surrounding this issue. We are reading the tiapp.xml that is saved, not the one in memory (OR we should just list all run options by default because there is already an invalid config error, see screenshot 'Correct Error'). This is a usability issue. Steps to Reproduce: 1. Create a new project with the SDK set to a version such as 2.1.2.GA or lower (pre-device debugging support). 2. In the project tiapp.xml, change the sdk without saving to a version such as 3.0.0.X or higher (sdk w/device debugging support). 3. Go to Debug > Android Device. Actual Result: Android Device is not there because the tiapp.xml is not saved. See Screenshot 'Usability'. Expected Result: The Android Device entry should exist, and the tiapp.xml should be prompted for save before deployment. Note: There is currently an error pop-up if device debugging is attempted on an sdk below 2.2, so the current implementation already has a safeguard. See screenshot 'Correct Error'.
| 5 |
train
|
TISTUD-2288
|
iOS Device Debugger: Failed to debug on Device and install on Device after relaunch Studio.
|
Description: Debug as iOS device is not working after relaunch TiStud. Log is attached. Debug_test.zip is attached. Steps to reproduce: Import debug_test (debug_test is attached) > Relaunch studio > Debug as iOS. Actual result: Debug is failed. Expected result. Debugger should work
| 5 |
train
|
TISTUD-2289
|
'Preference' view from Debug Configurations is not same as 'Preference' view from the menu bar.
|
Preference looks are different if they get open from different links. (Please compare the images to see the difference) First Location: (Preference view from menu bar) 1. Click Preference from menu bar. 2. Select Titanium Studio 3. Select Titanium 4. Click on 'Titanium' node to see the sub classes. 5. See Actual Result. Second Location: (Preference view from Debug Configuration) 1. Create a default project 2. Right click on the project and select 'Debug As' 3. Select 'Debug Configuration...' 4. Double click on 'Titanium iOS Application Installer' 5. Select 'New Configuration' 6. Click on Select 'SDK Version' link 7. Click on 'Titanium' Node to see the sub classes. 8. See Actual Result. Actual Result: View of dropped node 'Titanium' is not same. (Missing iOS subclass in Prefered(Filtered) window)
| 5 |
train
|
TISTUD-2290
|
iOS Device Debugging: no console output from device
|
Titanium Studio Console output fail to display output results. Steps to Reproduce: 1. Create default project, add sample code: {code} Ti.API.info('INFO LOGGED'); {code} 2. Run 'debug' on iOS Device. Port forward message should appear on console. 3. Launch app from device. Actual Result: Titanium Studio console log fail to display the console output Expected Result: Titanium Studio console log display the console output.
| 13 |
train
|
TISTUD-2291
|
Update CLI --dir to --project-dir and --workspace-dir
|
We have renamed the --dir CLI option to --project-dir for the following commands: * build * clean * project and --workspace-dir for: * create Note: there is no longer a run or install command.
| 3 |
train
|
TISTUD-2292
|
Add ability to edit app icon as part of tiapp.xml
|
The app icon is an important identifier for a 360 app. Users should be able to update hte app icon via the tiapp.xml editor * Add a field showing the current icon (scaled for size) * Add a browse button allowing the user to pick a new icon * Restrict the icon to standard app store guidelines.
| 8 |
train
|
TISTUD-2295
|
Dashboard: Linux: dashboard is not open as expected, pop up error msg "Internal error ..."
|
Dashboard Fail to Open. Steps to Reproduce: 1. Open Ti.Studio Actual Result: Fail to load Dashboard. Error#1: {Failed to install alloy. Please see http://go.aptana.com/installing+Node.js for additional information} Error#2: {An internal error has occurred. org.eclipse.ui.internal.ErrorEditorPart cannot be cast to com.aptana.portal.ui.browser.AbstractPortalBrowserEditor} Expected Result: Display Dashboard.
| 8 |
train
|
TISTUD-2298
|
iOS Device Debugging: debugger silently fails to connect
|
Description: After installing app on device unable to connect to debugger, progress bar stops at 57%"Waiting for device". Opening app on device is not open debugger. Debug_test is attached screenshot is attached xcode log is attached (log.txt) jstack.log is attached Steps to Reproduce: Import debug_test (debug_test is attached) 1. From TiStudio go to Debug perspective 2. In the Breakpoints view, Remove All existing breakpoints and right-click to "Import Breakpoints..." 3. Browse to breakpoint-basic.bkpt in Test File Location 4. Run in debug as iOS device. 5. After installing app on device. Launch app from device. Actual Result: Open app on device Debugger mode is not running. Expected Result: Debugger mode should run on Studio.
| 13 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.