issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-3980
|
Run Configurations: ios run configs are artificially separated
|
Run Configurations: ios run configs are artificially separated. See screenshot. Possible solutions: 1. Group the run configs under nodes. 2. Rename the ios packaging run configs to begin with iOS.
| 2 |
train
|
TISTUD-3981
|
Alloy Debugger: wrong behavior setting breakpoints on functions under Android
|
h5. Problem description Debugger is not correctly handling a breakpoint set for a function in the controller .js file h5. Steps to reproduce Android OS tested: 2.3.6 Nexus One, Android emulator See the sample attached. h6. index.xml {code} <Alloy> <Window class="container"> <Label id="label" onClick="doClick">Hello, World</Label> </Window> </Alloy> {code} h6. index.js {code} function doClick(e) { alert($.label.text); } $.index.open(); {code} 1. Set a BreakPpoint at line 3 for the'alert($.label.text);' 2. Debug the App on Android Result: App starts but the breakpoint is immediately triggered before displaying the Window (so just the splashscreen is displayed) and without having to click on the label. From the Debug tab, it looks the behavior is wrong and that actually the wrong line is highlighted, focusing on the 'doClick() function' instead of the 'alert' function inside. See the two screenshots, one for Android (wrong behavior), one for iOS (correct one, being triggered only when clicking on the sample 'label' for displaying the alert, not when starting the App). 3. Click to go past the breakpoint. Manually click on the app label to trigger the alert again. Result: breakpoint is now ignored. Alert is being displayed. Attaching Debugger log, where there is this line (not present in the iOS debugger log): {code} [57:33.986] Recv: >1364417853985*!unknown option <monitorXHR>< {code} Attaching Android build.log too
| 8 |
train
|
TISTUD-3983
|
TiApp: internal error updating the tiapp section widget is disposed when changing sdk
|
I changed the Titanium SDK in the TiApp Overview from 3.0.2.GA to 3.1.0.v20130327135307, and an error was generated in the UI. Log attached. Test History: 1. Install Titanium Studio 3.0.2 w/JDT 3.7.2 and accept all updates. 2. Create MobileWeb Module, Create Titanium Project, Package Module to Project, Move app.js example to Titanium Project. 4. Update to Titanium Studio 3.1.0.201303261815 (3.1.0.X). 5. Install alpha npm packages (titanium, alloy). 6. Install Titanium SDK 3.1.0.v20130327135307 (3.1.0.X). 7. Open Titanium Project tiapp.xml. 8. Edit Titanium SDK field to 3.1.0.v20130327135307 (3.1.0.X). Test Result: Error. Cannot reproduce. Notice the MobileWeb module version is missing from TiApp Overview (TISTUD-3984), but it correctly and soundly exists in tiapp.xml. Deleting and Adding the module provides identical incorrect behavior. See screenshots. Expected Result: No error.
| 3 |
train
|
TISTUD-3984
|
TiApp: mobileweb module missing version
|
Notice the MobileWeb module version is missing from TiApp Overview, but it correctly and soundly exists in tiapp.xml. Deleting and Adding the module provides identical incorrect behavior. See screenshots. Test History: 1. Install Titanium Studio 3.0.2 w/JDT 3.7.2 and accept all updates. 2. Create MobileWeb Module, Create Titanium Project, Package Module to Project, Move app.js example to Titanium Project. 4. Update to Titanium Studio 3.1.0.201303261815 (3.1.0.X). 5. Install alpha npm packages (titanium, alloy). 6. Install Titanium SDK 3.1.0.v20130327135307 (3.1.0.X). 7. Open Titanium Project tiapp.xml. Test Result: Notice the MobileWeb module version is missing from TiApp Overview, but it correctly and soundly exists in tiapp.xml. Deleting and Adding the module provides identical incorrect behavior. See screenshots. Expected Result: TiApp Overview lists MobileWeb module versions.
| 8 |
train
|
TISTUD-3986
|
Module Packaging Launch: all modules show MobileWeb launch shortcuts
|
Module Packaging Launch: all modules show MobileWeb launch shortcuts. See screenshots. Test Steps: 1. Create Module Projects for every supported platform. 2. Select Package UI. Test Results: All module types show MobileWeb as a Packaging option. Expected Results: MobileWeb Packaging is specific to MobileWeb modules.
| 5 |
train
|
TISTUD-3989
|
"Illegal initial capacity" error when reading the index
|
Saw this on one of the logs: {code} java.lang.IllegalArgumentException: Illegal initial capacity: -1 java.util.HashMap.<init>(HashMap.java:172) java.util.HashMap.<init>(HashMap.java:199) com.aptana.internal.index.core.DiskIndex.readCategoryTable(DiskIndex.java:1101) com.aptana.internal.index.core.DiskIndex.mergeCategory(DiskIndex.java:795) com.aptana.internal.index.core.DiskIndex.mergeCategories(DiskIndex.java:768) com.aptana.internal.index.core.DiskIndex.mergeWith(DiskIndex.java:929) com.aptana.index.core.Index.save(Index.java:698) com.aptana.index.core.Index.save(Index.java:671) com.aptana.core.internal.build.IndexBuildParticipant.buildEnding(IndexBuildParticipant.java:66) com.aptana.core.internal.build.LazyBuildParticipant.buildEnding(LazyBuildParticipant.java:67) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:341) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:277) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:235) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.fullReconcile(CommonReconcilingStrategy.java:477) com.aptana.editor.common.text.reconciler.CompositeReconcilingStrategy.fullReconcile(CompositeReconcilingStrategy.java:125) com.aptana.editor.common.text.reconciler.CommonReconciler.process(CommonReconciler.java:162) org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:206) {code}
| 5 |
train
|
TISTUD-3991
|
Studio First Time Startup: Address iOS NPEs in log
|
When Studio is first installed and configured, BEFORE any Titanium Updates are installed, there exist a few NPM-related NPEs in the log. It would be a more-complete experience to address these. Log: {code} !SESSION 2013-03-28 16:56:38.875 ----------------------------------------------- eclipse.buildId=3.1.0.201303261815 java.version=1.6.0_43 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/dhyde/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/dhyde/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.jface 4 2 2013-03-28 17:30:20.835 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.mobile.iphone.IOSConfigurationHelper.runPackagePrereqCheck(IOSConfigurationHelper.java:256) com.appcelerator.titanium.mobile.ui.preferences.IOSSDKPreferencePage.reloadCertificateTable(IOSSDKPreferencePage.java:746) com.appcelerator.titanium.mobile.ui.preferences.IOSSDKPreferencePage.createCertificatesSection(IOSSDKPreferencePage.java:421) com.appcelerator.titanium.mobile.ui.preferences.IOSSDKPreferencePage.createMobileOptions(IOSSDKPreferencePage.java:129) com.appcelerator.titanium.mobile.ui.preferences.BasePlatformFieldEditorPreferencePage.createFieldEditors(BasePlatformFieldEditorPreferencePage.java:57) org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:227) 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.handlePostSelect(StructuredViewer.java:1226) org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1251) org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:262) org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256) org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.observerProc(Display.java:3525) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007) org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) 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:3610) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) 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) {code} {code} !ENTRY com.appcelerator.titanium.nodejs.core 1 0 2013-03-28 17:33:23.276 !MESSAGE (Build 3.1.0.201303261815) [INFO] Failed to retrieve latest version string for package acs from npm !STACK 1 org.eclipse.core.runtime.CoreException: NPM is not installed. com.aptana.js.internal.core.node.NodePackageManager.getLatestVersionAvailable(NodePackageManager.java:442) com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getLatestVersion(NPMConfigurationComponent.java:116) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.latestVersionString(TitaniumNPMRelease.java:36) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.<init>(TitaniumNPMRelease.java:30) com.appcelerator.titanium.update.TitaniumSDKUpdater$3.map(TitaniumSDKUpdater.java:623) com.appcelerator.titanium.update.TitaniumSDKUpdater$3.map(TitaniumSDKUpdater.java:1) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:408) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:442) com.appcelerator.titanium.update.TitaniumSDKUpdater.getNPMUpdates(TitaniumSDKUpdater.java:619) com.appcelerator.titanium.update.TitaniumSDKUpdater.getAvailableUpdates(TitaniumSDKUpdater.java:309) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasToInstallPackages(TitaniumSDKUpdater.java:847) com.appcelerator.titanium.update.TitaniumUpdateStartup.earlyStartup(TitaniumUpdateStartup.java:128) org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87) org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.Workbench$63.run(Workbench.java:2470) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.js.core 4 0 2013-03-28 17:33:23.277 !MESSAGE NPM is not installed. {code} {code} !ENTRY com.appcelerator.titanium.nodejs.core 1 0 2013-03-28 17:33:25.164 !MESSAGE (Build 3.1.0.201303261815) [INFO] Failed to retrieve latest version string for package alloy from npm !STACK 1 org.eclipse.core.runtime.CoreException: NPM is not installed. com.aptana.js.internal.core.node.NodePackageManager.getLatestVersionAvailable(NodePackageManager.java:442) com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getLatestVersion(NPMConfigurationComponent.java:116) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.latestVersionString(TitaniumNPMRelease.java:36) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.<init>(TitaniumNPMRelease.java:30) com.appcelerator.titanium.update.TitaniumSDKUpdater$3.map(TitaniumSDKUpdater.java:623) com.appcelerator.titanium.update.TitaniumSDKUpdater$3.map(TitaniumSDKUpdater.java:1) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:408) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:442) com.appcelerator.titanium.update.TitaniumSDKUpdater.getNPMUpdates(TitaniumSDKUpdater.java:619) com.appcelerator.titanium.update.TitaniumSDKUpdater.getAvailableUpdates(TitaniumSDKUpdater.java:309) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasToInstallPackages(TitaniumSDKUpdater.java:847) com.appcelerator.titanium.update.TitaniumUpdateStartup.earlyStartup(TitaniumUpdateStartup.java:128) org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87) org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.Workbench$63.run(Workbench.java:2470) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.js.core 4 0 2013-03-28 17:33:25.164 !MESSAGE NPM is not installed. {code} {code} !ENTRY com.appcelerator.titanium.nodejs.core 1 0 2013-03-28 17:33:26.721 !MESSAGE (Build 3.1.0.201303261815) [INFO] Failed to retrieve latest version string for package titanium from npm !STACK 1 org.eclipse.core.runtime.CoreException: NPM is not installed. com.aptana.js.internal.core.node.NodePackageManager.getLatestVersionAvailable(NodePackageManager.java:442) com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getLatestVersion(NPMConfigurationComponent.java:116) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.latestVersionString(TitaniumNPMRelease.java:36) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.<init>(TitaniumNPMRelease.java:30) com.appcelerator.titanium.update.TitaniumSDKUpdater$3.map(TitaniumSDKUpdater.java:623) com.appcelerator.titanium.update.TitaniumSDKUpdater$3.map(TitaniumSDKUpdater.java:1) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:408) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:442) com.appcelerator.titanium.update.TitaniumSDKUpdater.getNPMUpdates(TitaniumSDKUpdater.java:619) com.appcelerator.titanium.update.TitaniumSDKUpdater.getAvailableUpdates(TitaniumSDKUpdater.java:309) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasToInstallPackages(TitaniumSDKUpdater.java:847) com.appcelerator.titanium.update.TitaniumUpdateStartup.earlyStartup(TitaniumUpdateStartup.java:128) org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87) org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.Workbench$63.run(Workbench.java:2470) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.js.core 4 0 2013-03-28 17:33:26.721 !MESSAGE NPM is not installed. {code}
| 3 |
train
|
TISTUD-3993
|
Titanium Updates: could not instantiate a release notes provider error
|
Clicking on Titanium Updates plugins release notes results in error messages in log. No visible affect on the UI or installation process. Log: {code} !ENTRY com.appcelerator.titanium.nodejs.core 4 0 2013-03-28 17:58:22.472 !MESSAGE (Build 3.1.0.201303261815) [ERROR] Could not instantiate a release notes provider !STACK 1 org.eclipse.core.runtime.CoreException: Plug-in "com.appcelerator.titanium.mobile.ui" was unable to instantiate class "com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider". org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186) org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58) com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:430) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.access$0(TitaniumUpdatePage.java:422) com.appcelerator.titanium.update.ui.TitaniumUpdatePage$1.selectionChanged(TitaniumUpdatePage.java:273) org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) 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.Viewer.fireSelectionChanged(Viewer.java:162) org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) org.eclipse.jface.viewers.CheckboxTableViewer.handleSelect(CheckboxTableViewer.java:310) org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) 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.applicationNextEventMatchingMask(Display.java:4875) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) org.eclipse.swt.widgets.Table.mouseDownSuper(Table.java:2004) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) org.eclipse.swt.widgets.Table.mouseDown(Table.java:1966) org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) 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:3610) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:74) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler$1$1.run(TitaniumUpdateHandler.java:67) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) 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) Caused by: java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider with modifiers "" sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) java.lang.Class.newInstance0(Class.java:351) java.lang.Class.newInstance(Class.java:310) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) ... 78 more !SUBENTRY 1 org.eclipse.equinox.registry 4 1 2013-03-28 17:58:22.473 !MESSAGE Plug-in "com.appcelerator.titanium.mobile.ui" was unable to instantiate class "com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider". !STACK 0 java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider with modifiers "" sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) java.lang.Class.newInstance0(Class.java:351) java.lang.Class.newInstance(Class.java:310) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58) com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:430) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.access$0(TitaniumUpdatePage.java:422) com.appcelerator.titanium.update.ui.TitaniumUpdatePage$1.selectionChanged(TitaniumUpdatePage.java:273) org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) 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.Viewer.fireSelectionChanged(Viewer.java:162) org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) org.eclipse.jface.viewers.CheckboxTableViewer.handleSelect(CheckboxTableViewer.java:310) org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) 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.applicationNextEventMatchingMask(Display.java:4875) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) org.eclipse.swt.widgets.Table.mouseDownSuper(Table.java:2004) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) org.eclipse.swt.widgets.Table.mouseDown(Table.java:1966) org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) 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:3610) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:74) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler$1$1.run(TitaniumUpdateHandler.java:67) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) 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) !ENTRY com.appcelerator.titanium.nodejs.core 4 0 2013-03-28 17:58:24.438 !MESSAGE (Build 3.1.0.201303261815) [ERROR] Could not instantiate a release notes provider !STACK 1 org.eclipse.core.runtime.CoreException: Plug-in "com.appcelerator.titanium.alloy.ui" was unable to instantiate class "com.appcelerator.titanium.alloy.internal.ui.releaseNotes.AlloyReleaseNotesProvider". org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186) org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159) com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58) com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:430) com.appcelerator.titanium.update.ui.TitaniumUpdatePage.access$0(TitaniumUpdatePage.java:422) com.appcelerator.titanium.update.ui.TitaniumUpdatePage$1.selectionChanged(TitaniumUpdatePage.java:273) org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) 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.Viewer.fireSelectionChanged(Viewer.java:162) org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) org.eclipse.jface.viewers.CheckboxTableViewer.handleSelect(CheckboxTableViewer.java:310) org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) 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.applicationNextEventMatchingMask(Display.java:4875) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) org.eclipse.swt.widgets.Table.mouseDownSuper(Table.java:2004) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) org.eclipse.swt.widgets.Table.mouseDown(Table.java:1966) org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) 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:3610) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:74) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler$1$1.run(TitaniumUpdateHandler.java:67) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) 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.a...
| 5 |
train
|
TISTUD-3996
|
Studio Update: user must login again after update
|
When updating from 3.0.2 Stable to 3.1.0.X RC, the user is forced to login again if they ever want to use Studio. Test Steps: 1. Install Studio Stable. 2. Update to Studio RC/Beta/Nightly and Restart as Prompted. Actual Result: User must login again. See screenshot. Expected Result: User must login automatically, as if Studio were restarted under File > Restart.
| 5 |
train
|
TISTUD-4002
|
MobileWeb Module: packaging run configuration lists module as an invalid module project
|
MobileWeb Module: packaging run configuration lists module as an invalid module project. See screenshot. Log attached for completeness. Test Steps: 1. Create MobileWeb Module. 2. Create Mobile Project. 3. Package Module to Project. 4. Open MobileWeb Module Packaging Run Configuration. Actual Result: MobileWeb Module is listed as an error in it's own packaging run configuration. Note the module and associated mobile project appear to be valid, produce no errors, and run correctly.
| 5 |
train
|
TISTUD-4003
|
Bad State: Every time I open the run configurations, Studio locks up
|
Bad State: Every time I open the run configurations, Studio locks up. While investigating TISTUD-4002, if the mobileweb packaging run config is selected, and the user opens Run Configurations..., an NPE dialog appears, then the Run Configurations menu appears, and the Studio UI locks up. This happens every time, even if Studio is Force Quit. Test Steps: 1. Reproduce TISTUD-4002. 2. Select the bad run config. 3. Reopen Run Configurations... Behavior: Studio UI locks-up. Happens every time.
| 5 |
train
|
TISTUD-4008
|
New Android Emulator Run Configuration ignores Preferences until preferences menu is loaded
|
New Android Emulator Run Configuration ignores Preferences. See screenshots. There is no way out of this, beyond manually editing the run configuration. Manually creating a Run Configuration results in identical invalid default values. Test Steps: 1. Run Android Emulator. Test Result: Launch fails. Run Configuration is Invalid. Run Configuration not based on Preferences.
| 5 |
train
|
TISTUD-4011
|
Projects: deleting a mobile project with node.acs service results in Updating Client npe
|
Projects: deleting a mobile project with node.acs service results in Updating Client npe. Test Steps: 1. Create Titanium Project. 2. Enable New > Node.ACS Service. 3. Delete project (not from disk). Test Result: Error.
| 3 |
train
|
TISTUD-4012
|
iOS Packaging: development provisioning profiles listed in distribution run configuration
|
iOS Packaging: development provisioning profiles listed in distribution run configuration. The certificates are filtered properly, but the profiles are not. Test Steps: 1. Open iOS Packaging Run Configuration. 2. View Certificates List and Profiles List. Actual Result: Certs are only distribution certs. Profiles are all types. Expected Result: Certs and Profiles are only distribution and ad-hoc, no development profiles or certs.
| 8 |
train
|
TISTUD-4013
|
iOS Packaging: ad hoc and itunes distribution both have TWO success toasts!
|
iOS Packaging: ad hoc and itunes distribution both have TWO success toasts! Test Steps: 1. Package in iTunes or Ad-Hoc. Test Result: Observe the TWO success toasts! Expected Result: There should, in all circumstances, be ONE toast at a time...
| 5 |
train
|
TISTUD-4014
|
iOS Packaging Run Config: no way to edit config without project name set
|
iOS Packaging Run Config: no way to edit config without project name set. This is inconvenient and unnecessary. See screenshot. Test Steps: 1. Create iOS Packaging run config without project name. Test Result: Cannot edit run config.
| 5 |
train
|
TISTUD-4018
|
Dashboard: RC dashboard loads blank with can't find variable mobileWebProblems error
|
Dashboard: RC dashboard loads blank with can't find variable mobileWebProblems error. See screenshots and log. Test Steps: 1. Go on staging. 2. Load dashboard. Failure Result: Dashboard background loads, nothing else. Error appears.
| 8 |
train
|
TISTUD-4019
|
Alloy: new widget fails to save prompt for dirty config.json
|
Alloy: new widget fails to save prompt for dirty config.json. Test Steps: 1. Create Alloy Project. 2. Edit app/config.json without save. 3. Create New > Alloy Widget. Actual Result: Widget saves over config.json with no save prompt.
| 5 |
train
|
TISTUD-4021
|
Node.ACS: intermittent No user account logged in for Appcelerator Node.ACS
|
Node.ACS: No user account logged in for Appcelerator Node.ACS. I am online. This is an intermittent edge case. If I am online, Studio should try to login to acs again, not just fail. Test History: 1. Login to Studio on Staging. 2. Move over to production. 3. Create an Alloy Project. 4. Activate New > Node.ACS Service on the project. Test Result: Error. Expected Result: Studio is online, so studio can login again before resorting to error.
| 5 |
train
|
TISTUD-4022
|
Node.ACS Service: enabling service failed to result in success toast, silent success
|
Node.ACS Service: enabling service failed to result in success toast, silent success. Test Steps: 1. Create Alloy Project. 2. Enable New > Node.ACS Service. Actual Result: Silent success. Expected Result: Toast.
| 3 |
train
|
TISTUD-4023
|
Diagnostics: titanium cli listed three times in run diagnostics
|
Help > Studio > Run Diagnostics... Titanium CLI is listed twice, all npm packages are listed as a whole. In total, CLI is listed three times, and alloy & node.acs are listed twice. Note that Titanium CLI enabled is a mandatory field. {code} Titanium CLI Version: 3.0.25.alpha Titanium CLI Enabled: true Titanium CLI Version: 3.0.25.alpha Alloy Version: 1.1.0.alpha Node.ACS Version: 0.9.34 Node.JS Version: v0.8.22 NPM Path: /usr/local/bin/npm NPM Version: 1.2.14 Packages: /usr/local/lib └─┬ [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├─┬ [email protected] │ ├── [email protected] │ ├── [email protected] │ └── [email protected] ├─┬ [email protected] │ ├── [email protected] │ ├─┬ [email protected] │ │ └── [email protected] │ └─┬ [email protected] │ ├── [email protected] │ ├── [email protected] │ ├── [email protected] │ ├── [email protected] │ └── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├─┬ [email protected] │ ├── [email protected] │ ├── [email protected] │ ├── [email protected] │ └── [email protected] └── [email protected] {code}
| 5 |
train
|
TISTUD-4025
|
Node.ACS: new method save prompt is not standard
|
Node.ACS: new method save prompt is not standard. Test Steps: 1. Create Titanium Project. 2. Add New Node.ACS Service. 3. Add New Node.ACS Method. 4. Edit the services (methods) file that was created, do not save. 5. Add Another New Node.ACS Method. Current Result: Prompt appears 'Would you like to save before proceeding?'. If you select no, the file is saved anyway. The file was literally not saved before overwriting it. This prompt is followed by another prompt to view the overwritten file. Expected Result: Prompt appears. If you select no, the operation is cancelled.
| 5 |
train
|
TISTUD-4026
|
Node.ACS Publish: improve appearance of publish menu list
|
Node.ACS Publish: improve appearance of publish menu list. See screenshot.
| 3 |
train
|
TISTUD-4031
|
Samples: change Titanium to Classic
|
Samples: change Titanium to Classic. See screenshot. Technically these are 'Titanium' samples, but it was chosen to use the same constant string value, and that default is decided to be 'Classic' for now.
| 2 |
train
|
TISTUD-4034
|
Dashboard: Titanium Samples icons should match quality of Templates icons
|
Dashboard: Titanium Samples icons should match quality of Templates icons. When TISTUD-2628 is done, this issue will address the parity issue created.
| 5 |
train
|
TISTUD-4035
|
Dashboard: Create Alloy Samples section
|
Add a new section above Alloy Templates, call it Alloy Samples.
| 8 |
train
|
TISTUD-4051
|
LiveTi: add mechanism to query npm package version
|
Suggest Run Diagnostics... No 'universally accessible' way to verify environment.
| 5 |
train
|
TISTUD-4055
|
Update LCD: An internal error has occurred. java.lang.NullPointerException
|
Update LCD: An internal error has occurred. java.lang.NullPointerException. I updated Studio to latest RC, this error appeared in the UI. Could not Reproduce.
| 3 |
train
|
TISTUD-4066
|
iOS iTunes Packaging: success toast fails to open xcode archive manager
|
iOS iTunes Packaging: success toast links to studio application directory: ~/Desktop/tistud/tistud-rc/titanium-studio/TitaniumStudio.app/Contents/MacOS I would expect it to open Xcode and launch the archive perspective as it does using Titanium Studio 3.0.2 Stable. This is verified as a regression. iOS Ad-Hoc Packaging opens correct directory, as specified in the run configuration.
| 5 |
train
|
TISTUD-4073
|
Surface Full Error: CLI: project create: [ERROR] Invalid platform: blackberry
|
Creating a new blackberry project results in: {code} DHydeMBP:~ dhyde$ "/usr/local/bin/titanium" "create" "--platforms" "ios,android,mobileweb,tizen,blackberry" "--type" "app" "--id" "com. project" "--sdk" "3.1.0.v20130402092426" "--workspace-dir" "/Users/dhyde/Desktop/TitaniumStudio/3.1.0-RC/Workspace" "--name" "project" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" [ERROR] Invalid platform: blackberry Available platforms for SDK version undefined: android ios ipad iphone mobileweb tizen {code} Studio does not surface the full error. See screenshot.
| 5 |
train
|
TISTUD-4074
|
Alloy: Debugger ignore breakpoints and stack frame under Windows
|
h5. Problem description Under Windows, setting a breakpoint on the original controller source did not cause the app to break where expected. Setting a breakpoint on the generated controller source works. h5. Steps to reproduce h6. Sample 'index.js' {code} function doClick(e) { alert($.label.text + a); } var a = 5; $.index.open(); {code} 1) Set a Breakpoint at line 2 ( alert($.label.text + a); ) 2) Debug for Android Result: Breakpoints are ignored See Jira bug: https://jira.appcelerator.org/browse/ALOY-597 for investigation done regarding source map (confirming it's working as expected). Attaching index.js.map file.
| 8 |
train
|
TISTUD-4077
|
iOS iTunes Packaging: clicking success toast opens studio application directory
|
iOS iTunes Packaging: clicking success toast links to studio application directory: ~/Desktop/tistud/tistud-rc/titanium-studio/TitaniumStudio.app/Contents/MacOS I would expect it to open Xcode and launch the archive perspective. Note the archive organizer is correctly automatically opened when success toast appears.
| 3 |
train
|
TISTUD-4079
|
CLI: Setting --retina flag will render 3.0.2.GA projects unable to launch simulator.
|
h5. Description While trying to investigate bugs from the triage meeting, I set the Studio preference to "retina" for the iOS simulator. Attempting to launch in this configuration failed, with an error complaining of a "ridiculous" capacity. This occurs in Studio and in the CLI as well. h5. Console output {code} [DEBUG] Simulator command: "/Users/emerriman/Library/Application Support/Titanium/mobilesdk/osx/3.0.2.GA/iphone/ios-sim" launch "/Users/emerriman/Documents/Appcelerator_Studio_Workspace/Kitchen Sink/build/iphone/build/Debug-iphonesimulator/KitchenSink.app" --sdk 6.1 --family iphone --retina [ERROR] An error occurred running the iOS Simulator [ERROR] 2013-04-02 15:18:49.649 ios-sim[61549:1307] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderArray initWithCapacity:]: capacity (18446744073709551615) is ridiculous' [ERROR] *** First throw call stack: [ERROR] ( [ERROR] 0 CoreFoundation 0x00007fff88a32b06 __exceptionPreprocess + 198 [ERROR] 1 libobjc.A.dylib 0x00007fff9502d3f0 objc_exception_throw + 43 [ERROR] 2 CoreFoundation 0x00007fff889e3035 -[__NSPlaceholderArray initWithCapacity:] + 245 [ERROR] 3 CoreFoundation 0x00007fff88a13719 +[NSMutableArray arrayWithCapacity:] + 41 [ERROR] 4 ios-sim 0x0000000100003463 -[iPhoneSimulator runWithArgc:argv:] + 2771 [ERROR] 5 ios-sim 0x000000010000373b main + 155 [ERROR] 6 ios-sim 0x0000000100001694 start + 52 [ERROR] ) [ERROR] libc++abi.dylib: terminate called throwing an exception [ERROR] [ERROR] Project failed to build after 42s 901ms {code} h5. Steps to reproduce: 1) Create a project and set tiapp.xml to 3.0.2.GA 2) Run from studio with the retina preference set, or use the CLI "ti -p ios -T simulator --retina" h5. Result: Error as listed above. h5. Expected: Retina iphone simulator launches. h5. Notes: Looking at ios-sim.m, there is a line where the number of args goes negative. There may be some legacy code in 3.0.2.GA where "--retina" was implemented but expects "true".
| 5 |
train
|
TISTUD-4084
|
Run Configurations: Re-build on Launch: Error cleaning the build before launching
|
If Android Emulator launched with Run Configuration Preference 'Re-build Project on Launch', there is an error in the logs, there doesn't seem to be an obvious impact in the app runtime. See screenshot for preference. Error (see log for details): {code} !MESSAGE (Build 3.1.0.201304012115) [ERROR] Error cleaning the build before launching !STACK 1 org.eclipse.core.runtime.CoreException: Error while invoking a synchronous builder com.appcelerator.titanium.core.launching.TitaniumSingleProjectLaunchConfigurationDelegate.cleanBuild(TitaniumSingleProjectLaunchConfigurationDelegate.java:77) {code} Test Steps: 1. Run Configurations... Android Emulator : Re-build Project on Launch. 2. App launches without log errors pertaining to CLEAN operation. Test Results: Errors in studio log.
| 3 |
train
|
TISTUD-4087
|
Android Device Run Configuration: add Enable JavaScript Minification preference
|
Android Device Run Configuration has no 'Enable JavaScript Minification' preference. The static default run value is 'Enable JavaScript Minification' = FALSE. All other Android Run Configurations have 'Enable JavaScript Minification' preference. See screenshots. All other Android Run Configurations default to 'Enable JavaScript Minification' = TRUE. Test Steps: 1. Run Configurations... Android Device. Test Results: No 'Enable JavaScript Minification' preference. See screenshot. Scripts build with --skip-js-minify flag as a constant default. {code} !ENTRY com.aptana.core 1 0 2013-04-02 18:54:32.534 !MESSAGE (Build 3.1.0.201304012115) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/titanium" "build" "--platform" "android" "--sdk" "3.1.0.v20130402092426" "--log-level" "trace" "--target" "device" "--android-sdk" "/Users/dhyde/Desktop/android/android-sdk" "--avd-id" "2" "--skip-js-minify" "--no-colors" "--no-prompt" Working directory: /Users/dhyde/Desktop/TitaniumStudio/Appcelerator_Studio/Workspace/MobileProject Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8e, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk, APTANA_VERSION=3.1.0.1358389152, Apple_PubSub_Socket_Render=/tmp/launch-d1P0Kx/Render, Apple_Ubiquity_Message=/tmp/launch-jVEs4h/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/dhyde, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dhyde/Desktop/android/android-sdk/tools:/Users/dhyde/Desktop/android/android-sdk/platform-tools, PWD=/Users/dhyde/Desktop/TitaniumStudio/Appcelerator_Studio/Workspace/MobileProject, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-8TNuXB/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} {code} Expected Results: 1: Android Device Run Configuration has 'Enable JavaScript Minification' preference. 2: 'Enable JavaScript Minification' = TRUE as default value. Note: Android Preferences missing reference to 'Enable JavaScript Minification', new ticket must be logged before this ticket is closed.
| 5 |
train
|
TISTUD-4088
|
Run Configurations: Enable JavaScript Minification defaults to FALSE if no project selected
|
If Android Run Configuration is created with no project selected on run config menu invocation, any new run configurations created will have 'Enable JavaScript Minification' set to FALSE by default. See screenshots. If Android Run Configuration is created WITH a project selecting during invocation, 'Enable JavaScipt Minification' is correctly set to TRUE by default. Test Steps: 1. Deselect project in explorer. 2. Invoke run configurations menu. 3. Create Android Run Configuration. Test Results: Android Run Configurations are created with 'Enable JavaScript Minification' set to FALSE. Expected Result: Android Run Configurations are created with 'Enable JavaScript Minification' set to TRUE.
| 3 |
train
|
TISTUD-4095
|
Android: App kills Android Debugger session on Windows when auto launching the app
|
h5. Problem description Debugger it's not working as expected on Windows OS, exiting just after installing the app on device. h5. Steps to reproduce 1) Create a new default project (either classic one or alloy) 2) Add a breakpoint and debug the App on device Result: 'Debug on Android Device' window appears as expected. The App is built, but just after installing and launching the App, the Debugger exit and disconnect. The App is installed on device, but it's then stuck at the splashscreen if trying to manually launch it. Attaching Studio error log. Not reproducible using Studio GA 3.0.2.201302191606 (regression)
| 8 |
train
|
TISTUD-4133
|
CLI: New Project: non-existing sdk error message not formatted
|
When a non-existing SDK is used to create a project, the studio error message is not formatted. Studio Dialog: {code} [1m[36mTitanium Command-Line Interface[39m[22m, CLI version 3.1.0-beta Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved. Please report bugs to [36mhttp://jira.appcelerator.org/[39m Run [36mtitanium help[39m for available commands. {code} Command Line: {code} DHydeMBP:~ dhyde$ "/usr/local/bin/titanium" "create" "--platforms" "ios,android" "--type" "app" "--id" "com.classic" "--sdk" "3.1.0.v20 130402092426" "--workspace-dir" "/Users/dhyde/Desktop/tistud/appcelerator-studio-rc/workspace" "--name" "Classic" "--verbose" "--force" "--no-colors" "--no-prompt" "--no-banner" Titanium Command-Line Interface, CLI version 3.1.0-beta Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ [ERROR] "create" is an unrecognized command. Run titanium help for available commands. {code} Test Steps: 1. Open New Titanium Project Wizard. 2. Delete selected SDK from filesystem. 3. Finish project creation. Test Result: I'll-formatted error with no specific error content.
| 3 |
train
|
TISTUD-4099
|
Add logging to code analysis when Studio is enabled for troubleshooting
|
Studio does not enable logging in the input configuration file of code processor every time a project is analyzed (to improve performance). However, if the code processor fails to generate output, then a diagnostic file is required to investigate the problem. If the studio is enabled for troubleshooting (may be, for code processor component), the logging section in the input configuration file should be enabled for trace or debug output to analyze the code processor failure or results.
| 5 |
train
|
TISTUD-4101
|
Titanium Updates: Failed to install acs. if PYTHON not in system path
|
On a completely clean installation, if python is not in the system path on windows, node.acs will fail to install. The workaround is to set the PYTHON path to the installation directory located inside Titanium Studio (example): PYTHON system variable. {code} C:\Users\ASUS\AppData\Local\Titanium Studio\plugins\com.appcelerator.titanium.python.win32_1.0.0.1338515509\python {code} Node.acs can be installed from the command line, but there is a PYTHON path warning. Adding PYTHON to the path makes the warning go away. Titanium Studio can only install Node.acs with the PYTHON path set. Titanium Studio has it's own Python installation on Windows, so in theory should use that one.
| 8 |
train
|
TISTUD-4105
|
Denso : Add Device IP address to the preference page
|
Add Device IP address to the preference page of Denso platform. The IP address has to be configured before the app is launched on Denso device. The IP address should be used to set the environment variable IVI_HOST before launching the app on Denso device.
| 8 |
train
|
TISTUD-4108
|
Android Emulator: process launches in new terminal
|
Android Emulator: process launches in new terminal. The emulator output should exist in the Studio console. See screenshots. Test Steps: 1. Run Android Emulator. Test Results: Process launches in new OS terminal, logs appear in external terminal. Stable Results: Process launches and log appear in Studio console.
| 5 |
train
|
TISTUD-4112
|
NumberFormatException with hex numbers in JS Style Validator
|
{code}!ENTRY com.aptana.js.core 1 0 2013-04-03 14:22:02.818 !MESSAGE (Build 3.1.1.201304021936) [INFO] Error trying to parse JS number: '0x7FFFFFFF' !STACK 0 java.lang.NumberFormatException java.math.BigDecimal.<init>(BigDecimal.java:459) java.math.BigDecimal.<init>(BigDecimal.java:728) com.aptana.js.internal.core.build.JSStyleValidator.enterNumber(JSStyleValidator.java:1726) com.aptana.js.internal.core.build.JSStyleValidator.enterNode(JSStyleValidator.java:696) com.aptana.js.internal.core.build.JSStyleValidator.access$1(JSStyleValidator.java:611) com.aptana.js.internal.core.build.JSStyleValidator$1.enterNode(JSStyleValidator.java:496) com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:258) com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:234) com.aptana.js.internal.core.build.JSStyleValidator.buildFile(JSStyleValidator.java:485) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:603) com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:514) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:486) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:332) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:167) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
| 5 |
train
|
TISTUD-4119
|
Improve beta/rc update process
|
Currently when we release a Beta or RC candidate, besides updating to the right version of Studio, user will also need to update their npm packages from command line. See http://developer.appcelerator.com/blog/2013/04/titanium-sdkstudio-3-1-0-beta-now-available.html for an example on the number of steps users need to do. The idea is to improve the process by utilizing the update stream user set in Studio preferences page and installing the beta/rc versions of npm packages when checking for updates. The published versions for npm packages will include "-beta" and "-cr".
| 8 |
train
|
TISTUD-4122
|
NPE while building ACS project
|
The below NPE is thrown when Studio tries to build Node.ACS project during its startup: java.lang.NullPointerException org.eclipse.core.runtime.Path.append(Path.java:261) com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.determineMainFileURI(ACSCompileParticipant.java:173) com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.buildFile(ACSCompileParticipant.java:81) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:603) com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:514) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:486) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:332) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:167) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
| 3 |
train
|
TISTUD-4135
|
Add CLI command support for building a BlackBerry 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-4136
|
Add CLI command support for packaging BlackBerry applications
|
Russ provided the command in TISTUD-4134: ti build --platform blackberry -T distribute --keystore-password "pookiepie" --output-dir /Users/rmcmahon/Desktop/test
| 8 |
train
|
TISTUD-4137
|
Add CLI command support to run a BlackBerry project
|
This applies to run-on-simulator and run-on-device. Russ provided the following commands: ti build --platform blackberry -T simulator -A 192.168.137.159 ti build --platform blackberry -T device -A 192.168.0.157
| 8 |
train
|
TISTUD-4140
|
Android Device Debugger Wizard: update UI to 'App Should Automatically Start'
|
h5. Problem description When launching the Debugger on device, the message given to the user is to eventually manually run the App in order to start debugging (see attached screenshots). Current behavior is that the App should automatically starts once built and installed.
| 8 |
train
|
TISTUD-4151
|
Refactor the Titanium project wizard to have Android plugin contribute its entry
|
Currently the Titanium project wizard defines all the checkboxes for deployment targets. We should have the Android plugin contribute the following attributes through the extension point from TISTUD-3066: 1. A display name ("Android"); 2. A string for platform type ("android") that will be used by CLI and other necessary operations; 3. A mean to check if the requirement for platform support is met, i.e. if the Titanium SDK contains the platform, if the platform SDK is installed (not applicable to Mobile Web), and if the OS supports the platform (not applicable here either), so the project wizard could enable/disable the checkbox as appropriate. It should return a status so we could display a warning or error message if needed. 4. Potentially a post-project creation hook to perform any Android specific task needed (don't think we have any?). 5. An optional "priority" attribute to control the order of the platforms both here and in tiapp.xml. Currently we are sorting them in alphabetical order, but there might be a case in the future where we like to have the flexibility.
| 8 |
train
|
TISTUD-4152
|
Refactor the Deployment Targets section of tiapp.xml to have Android plugin contribute its entry
|
We should be able to re-use the attributes defined from TISTUD-3053 for the "Deployment Targets" section of tiapp.xml, as the idea here is to also have Android plugin contribute the name, platform type, and if it's supported on the current system.
| 3 |
train
|
TISTUD-4153
|
Move Run > Android Emulator action to Android plugin(s)
|
This involves moving the launch shortcut and related classes for contributing the Run > Android Emulator action to Android's own plugins.
| 8 |
train
|
TISTUD-4154
|
Have Android plugin contribute to the preferences page
|
We should have a subnode for each platform under Preferences > Studio > Platforms and move the respective section from Platforms preference page there. The android.ui plugin will contribute the Android preference page and handle its preference settings.
| 5 |
train
|
TISTUD-4155
|
Refactor the modules table section of tiapp.xml to have Android plugin contribute its column
|
The plugin will need to contribute the icon. We also need a mechanism to parse out the module version for Android to be shown in the table. Is the platform type enough, and the tiapp model could parse the directory structure from there?
| 3 |
train
|
TISTUD-4157
|
Move Publish > Distribute Android App Store action to Android plugin
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Publish > Distribute Android App Store action to Android's own plugins.
| 8 |
train
|
TISTUD-4158
|
Move all references of Android from the mobile and core plugins to Android plugins
|
Once all the subtasks of refactoring the mobileweb code into its own plugin is completed, all the references of Android from the mobile and mobile.ui plugins has to be either removed or moved to Android's ui/core plugins. All the constants, resources and utility methods corresponding to Android should only be available in Android plugins.
| 8 |
train
|
TISTUD-4159
|
Refactor the mobile module project wizard to have Android plugin contribute its entry
|
Refactor the Titanium module project wizard to have Android plugin contribute its entry.
| 8 |
train
|
TISTUD-4162
|
Refactor the mobile project wizard to have BlackBerry plugin contribute its entry
|
Currently the mobile project wizard defines all the checkboxes for deployment targets. We should have the BlackBerry plugins contribute the following attributes through the extension point from TISTUD-3066: 1. A display name ("BlackBerry"); 2. A string for platform type ("blackberry") that will be used by CLI and other necessary operations; 3. A mean to check if the requirement for platform support is met, i.e. if the Titanium SDK contains the platform, if the platform SDK is installed (not applicable to Mobile Web), and if the OS supports the platform (not applicable here either), so the project wizard could enable/disable the checkbox as appropriate. It should return a status so we could display a warning or error message if needed. 4. Potentially a post-project creation hook to perform any BlackBerry specific task needed (don't think we have any?). 5. An optional "priority" attribute to control the order of the platforms both here and in tiapp.xml. Currently we are sorting them in alphabetical order, but there might be a case in the future where we like to have the flexibility.
| 8 |
train
|
TISTUD-4163
|
Refactor the Deployment Targets section of tiapp.xml to have BlackBerry plugin contribute its entry
|
We should be able to re-use the attributes defined from TISTUD-3053 for the "Deployment Targets" section of tiapp.xml, as the idea here is to also have BlackBerry plugin contribute the name, platform type, and if it's supported on the current system.
| 3 |
train
|
TISTUD-4164
|
Move Run > BlackBerry Simulator action to BlackBerry plugin(s)
|
This involves moving the launch shortcut and related classes for contributing the Run > BlackBerry Simulator action to BlackBerry's own plugins.
| 8 |
train
|
TISTUD-4165
|
Move BlackBerry preference page to blackberry UI plugin
|
We should have a subnode for each platform under Preferences > Studio > Platforms and move the respective section from Platforms preference page there. The blackberry.ui plugin will contribute the BlackBerry preference page and handle its preference settings.
| 5 |
train
|
TISTUD-4166
|
Refactor the modules table section of tiapp.xml to have BlackBerry plugin contribute its column
|
The plugin will need to contribute the icon. We also need a mechanism to parse out the module version for BlackBerry to be shown in the table. Is the platform type enough, and the tiapp model could parse the directory structure from there?
| 3 |
train
|
TISTUD-4167
|
Move Publish > Distribute BlackBerry action to BlackBerry plugin
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Publish > Distribute BlackBerry action to BlackBerry's own plugins.
| 8 |
train
|
TISTUD-4168
|
Move all references of BlackBerry from the mobile and core plugins to BlackBerry plugins
|
Once all the subtasks of refactoring the BlackBerry code into its own plugin is completed, all the references of BlackBerry from the mobile and mobile.ui plugins has to be either removed or moved to BlackBerry's ui/core plugins. All the constants, resources and utility methods corresponding to BlackBerry should only be available in BlackBerry plugins.
| 8 |
train
|
TISTUD-4173
|
JS Content Assist: access operator closes content assist menu
|
If the content assist suggestion menu is active, and the user enters the member access operatior ('.'), content assist disappears. This is eclipse behavior. This greatly reduces the core purpose of content assist. Test Steps: 1. Open JS File. 2. Activate Content Assist (e.g., Control + Space). 3. Type: Ti 4. Type: . Actual Result: Content Assist disappears. Expected Result: Content Assist populates new list based on scope change.
| 8 |
train
|
TISTUD-4183
|
Simplify the File > New From Template menu
|
We should keep Alloy, CSS, HTML, JavaScript, JSON, Text, and XML while removing others for Titanium Studio.
| 8 |
train
|
TISTUD-4191
|
intermittent Update home control job (Sleeping) process on application launch
|
h3. Steps to Reproduce 1. Open Appcelerator Studio. h3. Actual Result Update home control job (Sleeping) process never self-terminates. h3. Expected Result All self-launching processes self-terminate.
| 3 |
train
|
TISTUD-4198
|
Include Ruby related rubles in the Ruby feature
|
The following rubles should be packaged in the Ruby feature instead of the Studio core feature: Capistrano, Cucumber, EngineYard, HAML, Heroku, Rails, Rspec, Ruby, Sass. We have an extension point com.aptana.scripting.applicationBundlePaths to define a path where bundles are contained. Check com.appcelerator.titanium.core plugin and com.appcelerator.titanium.studio.build for an example.
| 8 |
train
|
TISTUD-4199
|
Include PHP related rubles in the PHP feature
|
The PHP ruble should be packaged in the PHP feature instead of the Studio core feature. We have an extension point com.aptana.scripting.applicationBundlePaths to define a path where bundles are contained. Check com.appcelerator.titanium.core plugin and com.appcelerator.titanium.studio.build for an example.
| 5 |
train
|
TISTUD-4200
|
Clean up non-Ruby/PHP related rubles for Titanium Studio
|
For now, the candidate to remove from Titanium Studio is YAML.ruble. It should be packaged in Aptana Studio only.
| 5 |
train
|
TISTUD-4201
|
Both updates wizard dialog and updates toast appear at startup
|
Steps to reproduce : 1) Backup/Remove the required SDK version (3.0.2GA) of Studio. 2) Also, install any old version of the npm package (NodeJS or alloy or code processor). 3) During the startup of Studio, both the update wizard dialog and update notification toast appear. Expected : The update wizard dialog should appear only if any of the components are not installed on the machine and in that case, notification toast should be suppressed. Otherwise, if there are only updates to the components, then notification toast should only appear.
| 5 |
train
|
TISTUD-4202
|
Debugger: Android Debug Progress window bad behavior on Windows
|
h5. Problem description On Windows, the 'Debug on Android device' progress window it's not showing the progress as expected, eventually not automatically hiding. h5. Steps to reproduce Only reproducible on Windows. 1. Create a new project (classic or alloy) 2. Set a breakpoint and launch the debugger on Android device Result: the 'Debug on Android device' window appears. No progress is shown after the second bullet 'Device connected. Performing pre compilation tasks'. The progress actually goes on and eventually the app is launched and breakpoints works fine, but the window stays on top. 3. Click on the 'Hide' button. Result: the window is placed on the background and the user is able to use the debugger as expected. However, a 'Debug on Android Device' bottom right notification is displayed - clicking on it, the Debug Progress is shown again as stuck at the second bullet. See screenshots.
| 5 |
train
|
TISTUD-4203
|
unexpected characters in the console, building the project on Linux and Windows
|
Building project on device or emulator returns unexpected characters in the console. However App launches successfully. Please see screenshot
| 5 |
train
|
TISTUD-4208
|
Error appears when empty Node.ACS >"Import Node.ACS binding " to a mobile project
|
Test Steps: 1.File > New >Create a Titanium Project. 2.Project Explorer >Context menu > Node.ACS > Import Node.ACS binding. Actual Result: Error appears.Log attached.
| 3 |
train
|
TISTUD-4209
|
Projects: npe deleting project with node.acs service
|
error trying to delete a project with a node.acs service. {code} !ENTRY org.eclipse.core.jobs 4 2 2013-04-09 10:42:56.477 !MESSAGE An internal error occurred during: "Populating Services menu". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getGUID(ThreeSixtyProject.java:162) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getAppData(ThreeSixtyProject.java:361) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.is360(ThreeSixtyProject.java:533) at com.appcelerator.titanium360.internal.ui.action.Titanium360PopupContributionItem$1.run(Titanium360PopupContributionItem.java:91) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 3 |
train
|
TISTUD-4212
|
Debugger: Android SDK default version is not being saved on Windows
|
h5. Problem description When launching the debugger on device, the 'Debug Configuration' popup window always appears and the 'Settings/Android SDK Version' drop down menu is not displaying a default SDK. h5. Steps to reproduce 1. Create a default project (Alloy or classic one) 2. Run the Debugger on Android device Result: the 'Debug Configuration' popup window always appears and the 'Settings/Android SDK Version' drop down menu is not displaying a default SDK. The user can then select an Android SDK version from the menu and start the Debugger. The configuration is saved as a new one and next time the debugger is launched the user is prompted again with the 'Debug Configuration' window and no SDK is selected by default. See screenshots.
| 5 |
train
|
TISTUD-4214
|
Dashboard: when dashboard is loading, some menus are unresponsive and project wizard is not populated
|
Dashboard: when dashboard is loading, some menus are unresponsive and project wizard is not populated. See screenshots. Test Steps: 1. Open Titanium Studio. 2. Invoke About Menu. Invoke Preference Menu. Invoke New Project Wizard. Test Results: About and Preferences Menus do not launch. The New Project Wizard is missing Alloy templates and missing the Default Titanium Project template.
| 8 |
train
|
TISTUD-4215
|
Profiler: auto-launch app on android device
|
Profiler: launch app on android device. Currently the user must manually launch the app. The debugger launches the app automatically. Test Steps: 1. Launch profiler on Android Device. Expected Result: App launches automatically.
| 5 |
train
|
TISTUD-4217
|
Android debug on device wizard should close on error
|
If there is any exception after launching Android app to debug on device, then the DebugOnDevice progress wizard does not close and it opens the launch configuration wizard on top. For any exceptions while in the debug on device progress wizard, the wizard should be closed and then, it should open the launch configuration wizard.
| 8 |
train
|
TISTUD-4233
|
Denso: TiApp: default module id width too small to display module ids
|
Denso: TiApp: default module id width too small to display module ids. See screenshot. Does not occur in Titanium Studio, but the Titanium Studio behavior is only marginally better.
| 5 |
train
|
TISTUD-4237
|
Alloy debugger: add support for .JS files outside 'controller' folder
|
h5. Improvement description Currently the debugger is supporting only .js files included in the 'Controller' folder. Following https://jira.appcelerator.org/browse/ALOY-616 , other .js files outside of the Controller folder and relevant to be supported should be mapped. 'alloy.js' file mapping has already been provided and it's implementation is going to be addressed by this Jira: https://jira.appcelerator.org/browse/TISTUD-4015
| 3 |
train
|
TISTUD-4239
|
Tizen : Add new CLI flag for running on device and simulator
|
The CLI for Tizen contains a new flag --run-dev-id for running on device and simulator. This flag should replace the existing flag in the CLI support of Titanium Studio to enable app to run on device/simulator.
| 3 |
train
|
TISTUD-4244
|
Windows: Titanium SDK Path: use same path as CLI
|
On Windows: Titanium Studio installs the SDK to C:\Users\ASUS\AppData\Roaming\Titanium Titanium CLI install the SDK to C:\ProgramData\Titanium Titanium Studio is not taking advantage of CLI support for installing Titanium SDKs. For instance, if a user runs 'ti sdk install -b 3_1_X', they will not be able to use the SDK from Studio. There are many possible solutions to this problem, but this is the most direct conflict. Please fix. Note: OS X and Linux currently have Studio/CLI parity.
| 5 |
train
|
TISTUD-4247
|
Dashoard - Marketplace: clicking on the link doesn't open the page
|
The links in the Marketplace tab of the Dashboard don't open unless right clicked > open page. They should open in your browser as soon as they are clicked. The first screenshot shows how the browser opens when I right click the links and click open page.
| 5 |
train
|
TISTUD-4251
|
Mobile project shortcuts should be order as "Mobile Project">"Mobile Module Project"
|
In order of importance, the "Mobile Project" wizard should appear before "Mobile Module Project"
| 2 |
train
|
TISTUD-4256
|
Node.ACS: Local Server Console does not populate on first deployment
|
*Details:* If you try to run Node.ACS project locally, the port does not appear in the console view. *Steps to reproduce:* 1. Right-click in Project Explorer 2. Go to New > Node.ACS Project 3. Specify a project name and click finish 4. Next, right-click on the project 5. Go to Run As > Local Node.ACS Server *Actual:* Port number does not appear in the console view (see attachment) *Expected:* Port number should appear in the console view *Note:* 1. If you repeat step 5 again, then the port number will appear again 2. Cannot reproduce just using the Node.ACS cli
| 5 |
train
|
TISTUD-4264
|
Projects: Workspace - When you create a Titanium project from the wizard and change the workspace, the Resources folder will not appear in the Project Explorer
|
*Details:* When you create a Titanium project from the wizard and change the workspace, the Resources folder will not appear in the Project Explorer. *Steps to Reproduce:* 1. Open TiStudio 2. Right-click in Project Explorer 3. Select New > Mobile Project 4. Select Classic > Default Project and click Next 5. Uncheck *Use default location* and choose a different workspace 6. Specify the Project name and App ID and click finish *Actual:* Resources folder does not appear in the Project Explorer (see noResources.png) However, the the project is created one level up from the workspace (see thereItIs.png) *Expected:* The project should'be been created in the specified workspace
| 5 |
train
|
TISTUD-4267
|
Move S/FTP plugins to their own feature and remove from Studio core, add to Aptana Studio umbrella feature
|
We have a handful of FTP and SFTP plugins. I'm not sure if they're advertised or used much by Titanium Studio users. We may want to break out an S/FTP feature (and repo?) to move them to, build them separately and then include them under the Aptana Studio umbrella so they don't get installed in Titanium Studio by default, but only in Aptana Studio (like we did with Ruby/PHP/PyDev). We already have the S/FTP library in it's own feature and build. It would likely be combined with the following: deploy.ftp, filesystem.ftp, filesystem.secureftp, syncing.core, syncing.ui, ui.ftp, ui.secureftp
| 8 |
train
|
TISTUD-4275
|
Module: installing or packaging module to same location does not prompt overwrite warning
|
Module: installing or packaging module to same location does not prompt overwrite warning. This is an obvious bug. This is also a parity issue, as Titanium SDK installation has a prompt for overwriting modules. Test Steps: 1. Install or package a module to a location. 2. Install or package the same module to the same location. Actual Result: No overwrite warning, module installs or packages directly over the existing module. Expected Result: Overwrite warning. This matches the behavior of installing the Titanium SDK.
| 5 |
train
|
TISTUD-4278
|
Android Device: support run on device console output
|
Android Device: support device console output. Currently if you launch an app on android device, the runtime output does not appear in the console. This is basic functionality. However, we do support debug on device output and emulator output, so this is also a parity issue. Test Steps: 1. Launch app on Android Device (Run > Android Device). Actual Result: Build logs appear in console, runtime logs do not. The last line in the console is: [INFO] : App installer shutdown successfully
| 8 |
train
|
TISTUD-4280
|
Samples: double-click sample to invoke sample import menu
|
Samples: double-click sample to invoke sample import menu. Currently the user has to right-click > import. The expected user action it to double-click. Test Steps: 1. Open Samples View. 2. Expand Samples Folder. 3. Double-Click on a Sample. Actual Result: Nothing happens. Must try some other way. Expected Result: Import menu invokes correctly.
| 3 |
train
|
TISTUD-4335
|
Node.ACS studio plugin : Parsing error in extracting published url on windows
|
1. Update the node.ACS cli to 1.0.0 ( either through studio or from command line ) From studio 2. Create a new node.ACs proj 3. Publish the newly created app 4. Error is displayed as shown in the attached image I have also attached the exception thrown in log file from parsing the url.
| 8 |
train
|
TISTUD-4287
|
Expand default width of "module" column in modules table of tiapp.xml editor
|
The column widths all appear to be the same by default. This makes it so that the module id/name is always cut off. The platform widths likely only need to be enough to hold between 1 and 5 characters typically (version or asterisk), while the module column usually will need 8-30 characters. By this measure it looks like the module column should be about 6+x the width of the platform ones.
| 3 |
train
|
TISTUD-4291
|
Create a Node.ACS debug launch configuration
|
Adapt Google's ChromeDevTools "Standalone V8 VM" launch configuration to our needs. # Rename it to debug as 'Local Node.ACS Server'. # Make sure that the launch configuration delegate creates a local Node.ACS server with a debugger flag and runs it. # Inject the server's port into the newly created launch configuration. # Continue with the Google code launch as usual to connect to our local server.
| 8 |
train
|
TISTUD-4292
|
Console: Windows and Linux: android device alloy build console includes backspace characters
|
Console: android alloy build console includes backspace characters. The alloy android build to device console contains backspace characters. The backspace characters are abruptly and correctly ignored just as the build script ends (and the run script begins). See screenshot and log output below. This is an edge-case. {code} [INFO] : Alloy compiler completed successfully [INFO] : Running build process: python "C:\Users\ASUS\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.GA\android\builder.py" "install" "AlloyProject" "C:\Users\ASUS\AppData\Local\Android SDK" "C:\Users\ASUS\Documents\Titanium_Studio_Workspace_RC\AlloyProject" "com.alloyproject" "2" [INFO] logfile = C:\Users\ASUS\Documents\Titanium_Studio_Workspace_RC\AlloyProject\build.log [DEBUG] C:\Users\ASUS\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.GA\android\builder.py install AlloyProject C:\Users\ASUS\AppData\Local\Android SDK C:\Users\ASUS\Documents\Titanium_Studio_Workspace_RC\AlloyProject com.alloyproject 2 [DEBUG] detected module analytics, path = C:\Users\ASUS\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.GA\android\modules\titanium-analytics.jar [DEBUG] detected module android, path = C:\Users\ASUS\AppData\Roaming\Titanium\mobilesdk\win32\3.1.0.GA\android\modules\titanium-android.jar {code} Test Steps: 1. Run Alloy Project on Android Device in Windows. Actual Result: Build console displays backspace characters.
| 8 |
train
|
TISTUD-4293
|
Titanium Updates: GA npm updates do not register if pre-production npm packages installed
|
Titanium Updates: GA npm updates do not register if pre-production npm packages installed. Applies to all npm packages (Titanium CLI, Alloy, etc.). Test Steps (for example): 1. Install [email protected] 2. Check for Titanium Updates. Actual Result: No updates available. Expected Result: [email protected] appears, it is the GA version. User must uninstall to get GA npm packages.
| 5 |
train
|
TISTUD-4295
|
Titanium Updates: cli version not available on clean install
|
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-4298
|
Denso: can't clear the port number in preferences page after it's set
|
1. Open Preferences > Studio > Platforms > Denso; 2. Fill in the port number and hit OK; 3. Re-open the preferences page and notice the port number correct persists; 4. Now clear the port number so the field is empty and hit OK; 5. Re-open the preferences page. Expected result: the port number field is empty. Actual result: the previous port number is shown.
| 5 |
train
|
TISTUD-4299
|
Titanium Updates: Node.ACS release notes is an icon not found
|
Titanium Updates: Node.ACS release notes is an icon not found. See screenshot. Test Steps: 1. Uninstall Node.ACS. 2. Check for Titanium Updates (could be Windows-only). Actual Result: Strange icon instead of release notes.
| 8 |
train
|
TISTUD-4308
|
Change V8 strings to Node.ACS
|
The Node debugger support plugins have a few UI contributions that display the term "V8". We would like to change these and show "Node.ACS" instead. This will most likely involve changing the messages in the Google's chromium plugins. Here are a few locations that needs to be changed (there may be a few more): # JS file right click menu - Change V8 Debugging to Node.ACS debugging, and change the submenus items to say "local server" instead of "VM". # Locate any error messages that can be surfaced to the user and change the "V8" strings to "Node.ACS".
| 5 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.