id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
1,411 |
TISTUD-4696
|
05/18/2013 00:14:48
|
Node.ACS Binding: disable OK button in import binding dialog if nothing selected
|
Node.ACS Binding: import binding dialog allow user to continue if nothing selected. See screenshot. Test Steps: 1. Create Mobile Project. 2. Right click and import Node.ACS Binding. Result: Menu appears and user can press 'OK' though nothing is selected and the action will have no result whatsoever.
| 3 |
1,412 |
TISTUD-4698
|
05/18/2013 01:29:07
|
Alloy Editor: new model wizard allows multiple columns with same name
|
Alloy Editor: new model wizard allow multiple entries with same name, only last one is used. This ticket requests additional validation to the sql model wizard. See screenshots. Test Steps: 1. Open Alloy Project. 2. Add New > Model (sql) to invoke model wizard. 3. Add two entries with the same name. Result: No error message appears. The last entry is the one that will be injected into the generated model code. Expected Result: An error message should appear at the top indicating two columns have the same name. There is already existing validation for a pre-existing model.
| 3 |
1,413 |
TISTUD-4700
|
05/18/2013 03:10:01
|
Exception while debugging Node.ACS app
|
1) Create a new Node.ACS app 2) Debug Local Node.ACS server The debug session failed on first launch with NullPointerException. The exception stack trace is captured in the attached log.
| 5 |
1,414 |
TISTUD-4703
|
05/19/2013 18:08:20
|
NPE when creating an iOS packaging configuration from the configuration dialog
|
# Select a BlackBerry project (one that does not have an iOS target defined). # Open the packaging launch configuration dialog. # Double click to manually create a new "Apple iTunes Distribution" A Null Pointer Exception is thrown and surfaced to the UI. {code} java.lang.NullPointerException at com.appcelerator.titanium.mobile.iphone.IOSConfiguration.getIOSAttributeValue(IOSConfiguration.java:345) at com.appcelerator.titanium.mobile.ui.iphone.wizard.SimpleiPhonePackagingComponent.refreshSettings(SimpleiPhonePackagingComponent.java:584) at com.appcelerator.titanium.mobile.ui.iphone.wizard.SimpleiPhonePackagingComponent.refreshContents(SimpleiPhonePackagingComponent.java:374) at com.appcelerator.titanium.mobile.ui.launching.BaseTitaniumMobileLaunchConfigurationTab.selectedProjectChanged(BaseTitaniumMobileLaunchConfigurationTab.java:97) at com.appcelerator.titanium.ui.launching.BaseTitaniumLaunchConfigurationTab$2.modifyText(BaseTitaniumLaunchConfigurationTab.java:149) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) 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:1461) at org.eclipse.swt.widgets.Text.setText(Text.java:1995) at com.appcelerator.titanium.ui.launching.BaseTitaniumLaunchConfigurationTab.initializeFrom(BaseTitaniumLaunchConfigurationTab.java:318) at com.appcelerator.titanium.mobile.ui.iphone.launch.BaseIOSLaunchConfigurationTab.initializeFrom(BaseIOSLaunchConfigurationTab.java:101) at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:86) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:194) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:751) 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 com.appcelerator.titanium.mobile.ui.handlers.OpenDeployLaunchConfigurationDialogHandler.execute(OpenDeployLaunchConfigurationDialogHandler.java:34) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code}
| 3 |
1,415 |
TISTUD-4762
|
05/20/2013 03:51:58
|
Node.ACS: Windows: installation failure with bson error
|
*Problem* I'm using Windows 7 32bit and run Titanium as Administrator, when I check for titanium updates, and install Node.ACS ver1.0.2, an error message appears like this: {code}Error encountered during update Failed to install acs. Please see the Studio log for more information.{code} *Log* {code} !ENTRY com.aptana.js.core 4 0 2013-05-20 09:16:40.195 !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to install acs. npm http GET https://registry.npmjs.org/acs npm http 304 https://registry.npmjs.org/acs npm http GET https://registry.npmjs.org/colors/0.6.0-1 npm http GET https://registry.npmjs.org/commander/0.6.1 npm http GET https://registry.npmjs.org/connect/2.3.5 npm http GET https://registry.npmjs.org/connect-mongo/0.1.9 npm http GET https://registry.npmjs.org/express/3.0.0 npm http GET https://registry.npmjs.org/ejs/0.8.0 npm http GET https://registry.npmjs.org/fstream/0.1.18 npm http GET https://registry.npmjs.org/longjohn/0.0.3 npm http GET https://registry.npmjs.org/mkdirp/0.3.3 npm http GET https://registry.npmjs.org/node-uuid/1.3.3 npm http GET https://registry.npmjs.org/pkginfo/0.2.2 npm http GET https://registry.npmjs.org/socket.io/0.9.10 npm http GET https://registry.npmjs.org/tar/0.1.13 npm http GET https://registry.npmjs.org/uglify-js/1.3.2 npm http GET https://registry.npmjs.org/temp/0.4.0 npm http GET https://registry.npmjs.org/underscore/1.3.3 npm http GET https://registry.npmjs.org/log4js/0.5.1 npm http GET https://registry.npmjs.org/esprima/0.9.9 npm http GET https://registry.npmjs.org/jade/0.28.1 npm http GET https://registry.npmjs.org/string/1.1.0 npm http GET https://registry.npmjs.org/request/2.14.0 npm http GET https://registry.npmjs.org/wrench/1.3.9 npm http GET https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.6 npm http GET https://registry.npmjs.org/npm/1.2.1 npm http 304 https://registry.npmjs.org/connect-mongo/0.1.9 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/express/3.0.0 npm http 304 https://registry.npmjs.org/colors/0.6.0-1 npm http 304 https://registry.npmjs.org/connect/2.3.5 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/commander/0.6.1 npm http 304 https://registry.npmjs.org/ejs/0.8.0 npm http 304 https://registry.npmjs.org/fstream/0.1.18 npm http 304 https://registry.npmjs.org/longjohn/0.0.3 npm http 304 https://registry.npmjs.org/node-uuid/1.3.3 npm http 304 https://registry.npmjs.org/mkdirp/0.3.3 npm http 304 https://registry.npmjs.org/pkginfo/0.2.2 npm http 304 https://registry.npmjs.org/socket.io/0.9.10 npm http 304 https://registry.npmjs.org/tar/0.1.13 npm http 304 https://registry.npmjs.org/uglify-js/1.3.2 npm http 304 https://registry.npmjs.org/temp/0.4.0 npm http 304 https://registry.npmjs.org/underscore/1.3.3 npm http 304 https://registry.npmjs.org/log4js/0.5.1 npm http 304 https://registry.npmjs.org/esprima/0.9.9 npm http 304 https://registry.npmjs.org/jade/0.28.1 npm http 304 https://registry.npmjs.org/string/1.1.0 npm http 304 https://registry.npmjs.org/request/2.14.0 npm http 304 https://registry.npmjs.org/wrench/1.3.9 npm http 304 https://registry.npmjs.org/npm/1.2.1 npm http 200 https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.6 npm http GET https://registry.npmjs.org/mongodb npm http GET https://registry.npmjs.org/graceful-fs npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/rimraf npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/block-stream npm http GET https://registry.npmjs.org/connect/2.6.0 npm http GET https://registry.npmjs.org/range-parser/0.0.4 npm http GET https://registry.npmjs.org/cookie/0.0.4 npm http GET https://registry.npmjs.org/fresh/0.1.0 npm http GET https://registry.npmjs.org/crc/0.2.0 npm http GET https://registry.npmjs.org/methods/0.0.1 npm http GET https://registry.npmjs.org/send/0.1.0 npm http GET https://registry.npmjs.org/debug npm http GET https://registry.npmjs.org/socket.io-client/0.9.10 npm http GET https://registry.npmjs.org/policyfile/0.0.4 npm http GET https://registry.npmjs.org/redis/0.7.2 npm http GET https://registry.npmjs.org/async/0.1.15 npm http GET https://registry.npmjs.org/coffee-script npm http GET https://registry.npmjs.org/qs/0.4.2 npm http GET https://registry.npmjs.org/mime/1.2.4 npm http GET https://registry.npmjs.org/formidable/1.0.11 npm http GET https://registry.npmjs.org/fresh/0.0.1 npm http GET https://registry.npmjs.org/bytes/0.0.1 npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/graceful-fs npm http 304 https://registry.npmjs.org/rimraf npm http 304 https://registry.npmjs.org/mongodb npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/block-stream npm http 304 https://registry.npmjs.org/connect/2.6.0 npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/range-parser/0.0.4 npm http 304 https://registry.npmjs.org/cookie/0.0.4 npm http 304 https://registry.npmjs.org/fresh/0.1.0 npm http 304 https://registry.npmjs.org/crc/0.2.0 npm http 304 https://registry.npmjs.org/methods/0.0.1 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/send/0.1.0 npm http 304 https://registry.npmjs.org/debug npm http 304 https://registry.npmjs.org/socket.io-client/0.9.10 npm http 304 https://registry.npmjs.org/policyfile/0.0.4 npm http 304 https://registry.npmjs.org/redis/0.7.2 npm http 304 https://registry.npmjs.org/async/0.1.15 npm http 304 https://registry.npmjs.org/coffee-script npm http 304 https://registry.npmjs.org/qs/0.4.2 npm http 304 https://registry.npmjs.org/formidable/1.0.11 npm http 304 https://registry.npmjs.org/mime/1.2.4 npm http GET https://registry.npmjs.org/mime/1.2.6 npm http 304 https://registry.npmjs.org/fresh/0.0.1 npm http 304 https://registry.npmjs.org/bytes/0.0.1 npm http GET https://registry.npmjs.org/hiredis npm http 304 https://registry.npmjs.org/mime/1.2.6 npm http GET https://registry.npmjs.org/qs/0.5.1 npm http GET https://registry.npmjs.org/bytes/0.1.0 npm http GET https://registry.npmjs.org/send/0.0.4 npm http GET https://registry.npmjs.org/pause/0.0.1 npm http GET https://registry.npmjs.org/bson/0.0.4 npm http 304 https://registry.npmjs.org/hiredis npm http 304 https://registry.npmjs.org/bson/0.0.4 npm WARN package.json [email protected] No README.md file found! npm http GET https://registry.npmjs.org/bindings npm http GET https://registry.npmjs.org/uglify-js/1.2.5 npm http GET https://registry.npmjs.org/ws npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2 npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1 > [email protected] install C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\connect-mongo\node_modules\mongodb\node_modules\bson > node install.js 'node' is not recognized as an internal or external command, operable program or batch file. npm http 304 https://registry.npmjs.org/bytes/0.1.0 npm http 304 https://registry.npmjs.org/qs/0.5.1 npm http 304 https://registry.npmjs.org/send/0.0.4 npm http 304 https://registry.npmjs.org/uglify-js/1.2.5 npm ERR! Error: ENOENT, lstat 'C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\npm\node_modules\ini\ini.js' npm ERR! If you need help, you may report this log at: npm ERR! <http://github.com/isaacs/npm/issues> npm ERR! or email it to: npm ERR! <[email protected]> npm ERR! System Windows_NT 6.1.7600 npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "acs" "--color" "false" npm ERR! cwd C:\Users\MRiz\AppData\Local\Titanium Studio npm ERR! node -v v0.8.22 npm ERR! npm -v 1.2.14 npm ERR! path C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\npm\node_modules\ini\ini.js npm ERR! fstream_path C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\npm\node_modules\ini\ini.js npm ERR! fstream_type File npm ERR! fstream_class FileWriter npm ERR! code ENOENT npm ERR! errno 34 npm ERR! fstream_stack C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26 npm ERR! fstream_stack Object.oncomplete (fs.js:297:15) npm http 304 https://registry.npmjs.org/ws npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2 npm http 304 https://registry.npmjs.org/pause/0.0.1 npm ERR! error rolling back Error: ENOTEMPTY, rmdir 'C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\express\node_modules\connect' npm ERR! error rolling back [email protected] { [Error: ENOTEMPTY, rmdir 'C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\express\node_modules\connect'] npm ERR! error rolling back errno: 53, npm ERR! error rolling back code: 'ENOTEMPTY', npm ERR! error rolling back path: 'C:\\Users\\MRiz\\AppData\\Roaming\\npm\\node_modules\\acs\\node_modules\\express\\node_modules\\connect' } npm ERR! [email protected] install: `node install.js` npm ERR! `cmd "/c" "node install.js"` failed with 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is most likely a problem with the bson package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node install.js npm ERR! You can get their info via: npm ERR! npm owner ls bson npm ERR! There is likely additional logging output above. npm ERR! System Windows_NT 6.1.7600 npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "acs" "--color" "false" npm ERR! cwd C:\Users\MRiz\AppData\Local\Titanium Studio npm ERR! node -v v0.8.22 npm ERR! npm -v 1.2.14 npm ERR! code ELIFECYCLE npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1 npm http GET https://registry.npmjs.org/zeparser/0.0.5 npm http 304 https://registry.npmjs.org/bindings > [email protected] install C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\socket.io\node_modules\redis\node_modules\hiredis > node-gyp rebuild 'node-gyp' is not recognized as an internal or external command, operable program or batch file. npm WARN optional dep failed, continuing [email protected] npm http GET https://registry.npmjs.org/tinycolor npm http GET https://registry.npmjs.org/options npm http 304 https://registry.npmjs.org/zeparser/0.0.5 npm http 304 https://registry.npmjs.org/tinycolor npm http 304 https://registry.npmjs.org/options > [email protected] install C:\Users\MRiz\AppData\Roaming\npm\node_modules\acs\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws > (node-gyp rebuild 2> builderror.log) || (exit 0) npm !ENTRY com.appcelerator.titanium.update 4 4 2013-05-20 09:16:40.227 !MESSAGE Error encountered during update !SUBENTRY 1 com.aptana.js.core 4 0 2013-05-20 09:16:40.227 !MESSAGE Failed to install acs. Please see the Studio log for more information. {code}
| 8 |
1,416 |
TISTUD-4705
|
05/20/2013 18:13:38
|
Failure attaching Alloy templates while installing alloy 1.1.2
|
I received an error dialog during installation of alloy 1.1.2 on Appcelerator Studio 3.1.1 RC. I did not have alloy already installed. After the install, it looks like alloy 1.1.2 installed fine, but the template hooks failed? Here's the log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-05-20 13:10:09.376 !MESSAGE An internal error occurred during: "Checking if alloy is installed...". !STACK 0 java.lang.NoSuchMethodError: com.aptana.js.core.node.INodePackageManager.getInstalledVersion(Ljava/lang/String;)Lorg/osgi/framework/Version; at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$3.run(AlloyTemplateInstaller.java:246) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Trying to create a new mobile project, I do see the standard and two tabbed alloy templates listed - so the error looks pretty benign.
| 5 |
1,417 |
TISTUD-4712
|
05/20/2013 23:44:17
|
Studio samples: check out the tagged version instead of master
|
Currently we always pull from the master branch when importing samples in Samples view. This creates a problem since the latest source in master may not be compatible with an earlier version of Studio. The suggestion is to tag the source in the sample repo, and we will checkout by the tagged version. We should fall back to master if the version (x.y.z) does not exist as a tag for the repo.
| 8 |
1,418 |
TISTUD-4714
|
05/21/2013 02:20:55
|
Run > BlackBerry Device: the name of the created launch config does not contain project name
|
After running Run > BlackBerry Device on a project, a launch config is created and appears in the recent history group under the Run menu; however, it does not contain " - <project_name>" as other created launch configs do.
| 5 |
1,419 |
TISTUD-4715
|
05/21/2013 02:30:10
|
BlackBerry packaging wizard: the description just shows "OK" when the distribution location is selected
|
1. Create a BlackBerry project; 2. Publish > Distribute BlackBerry; 3. In the ensuing wizard, select a valid directory. Now the description message shows "OK". I would expect it either to be empty or revert back the default description message when there is no error.
| 3 |
1,420 |
TISTUD-4718
|
05/21/2013 05:36:57
|
BlackBerry: cannot run the created package or device launch configuration from configurations dialog
|
1. Create a BlackBerry project; 2. Run Publish > Distribute - BlackBerry; 3. Open Publish > Configurations... dialog; 4. Select the created Titanium BlackBerry Packager launch configuration if it isn't selected. Expected result: "Run" button should be enabled to run the launch config without any change since there is no error. Actual result: "Run" button is disabled. The same behavior is observed on device launch configuration as well.
| 5 |
1,421 |
TISTUD-4727
|
05/21/2013 23:09:37
|
CodeProcessor: paths.commands and paths.hooks not set during 1.0.1-alpha install
|
h5. Description: While setting up for testing, I noticed that the code processor mention it has edited my ti config. Here is the output: {code} /usr/local/bin/titanium-code-processor -> /usr/local/lib/node_modules/titanium-code-processor/bin/codeprocessor > [email protected] install /usr/local/lib/node_modules/titanium-code-processor > bin/install Notice: Modifying your Titanium Mobile configuration to include commands and hooks for the Titanium Code Processor. Run "titanium config" for more information [email protected] /usr/local/lib/node_modules/titanium-code-processor {code} Although it seemed to work, my "ti config" had no paths.command entry, and no paths.hooks entry for code processor. We tried this on Olga's system (without an updated CLI) and she got: {code} /usr/local/bin/titanium-code-processor -> /usr/local/lib/node_modules/titanium-code-processor/bin/codeprocessor > [email protected] install /usr/local/lib/node_modules/titanium-code-processor > bin/install Warning: Could not query the Titanium paths: fs.js:338 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); ^ Error: EACCES, permission denied '/Users/oromero/.titanium/analytics.json' at Object.fs.openSync (fs.js:338:18) at Object.fs.writeFileSync (fs.js:756:15) at save (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/analytics.js:163:7) at /usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/analytics.js:206:4 at async.parallel (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:476:17) at async.forEach (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:94:25) at async.parallel (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:473:21) at process.on.async.parallel.osinfo (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/analytics.js:56:5) at module.exports.getOSInfo (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/environ.js:215:4) at ChildProcess.exithandler (child_process.js:538:7) The Titanium Code Processor will not be available in the CLI or during builds [email protected] /usr/local/lib/node_modules/titanium-code-processor ├── [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} h5. Steps to reproduce: 1) Check your config with "ti config" and evaluate the paths.hooks and paths.commands. 2) Attempt to install titanium-code-processor with the following: "sudo npm install -g [email protected]" 3) Recheck with "ti config" h5. Result: No changes made to the ti config, so code-processor may not function. h5. Expected Result: Either error with failure to update paths.x or success in editing ti config.
| 5 |
1,422 |
TISTUD-4734
|
05/22/2013 16:28:38
|
NPE loading rubles
|
I'm just seeing this in my installed copy of Eclipse with studio plugins from nightly on development branch. On startup I get an error dialog about an NPE. Here's what's in the log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-05-22 11:26:26.854 !MESSAGE An internal error occurred during: "Start Ruble bundle manager". !STACK 0 java.lang.NullPointerException at java.io.File.<init>(File.java:251) at com.aptana.scripting.model.BundleMonitor.beginMonitoring(BundleMonitor.java:107) at com.aptana.scripting.ScriptingActivator$1.run(ScriptingActivator.java:111) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}
| 3 |
1,423 |
TISTUD-4736
|
05/22/2013 18:17:21
|
Project Wizard: unsupported targets not automatically deselected
|
Project Wizard: unsupported targets not automatically deselected. See screenshot. Test Steps: 1. Invoke new Mobile Project Wizard. 2. Select an SDK that supports new targets (such as blackberry) and select that target. 3. Select an SDK that does not support new targets (such as 3.1.0). Result: BlackBerry target is greyed-out correctly, but it is still selected. Expected Result: BlackBerry target should become deselected when an unsupported SDK is selected, as with Appcelerator Services.
| 5 |
1,424 |
TISTUD-4744
|
05/22/2013 21:18:28
|
Saving changes in tiapp.xml results in error message java.lang.NullPointerException
|
When making changes in tiapp.xml and saving it, the tiapp.xml is being updated. However, the error message is showing "save failed". I have not seen this issue before.
| 3 |
1,425 |
TISTUD-4745
|
05/22/2013 22:08:55
|
Terminate a Node.ACS launch when terminating its thread
|
When manually terminating a Node.ACS debug session by clicking on the debug-stack threads (the ones that say "Remote node v0.8.22..." and "JavaScript Thread"), the launch state is not terminated. This forces the user to manually click the launch, and hit terminate again, before allowing the launch to be removed from the view. We need to terminate the launch when terminating the thread.
| 3 |
1,426 |
TISTUD-4748
|
05/22/2013 22:37:46
|
Node.ACS Debugger: A problem while evaluating a stack-frame scope Failed to dispatch response to callback
|
Node.ACS Debugger: A problem while evaluating a stack-frame scope Failed to dispatch response to callback. {code} !ENTRY com.aptana.core 1 0 2013-05-22 14:32:18.899 !MESSAGE (Build 3.1.1.201305212055) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs-debug" "run" "-d" "/Applications/Appcelerator/Appcelerator_Studio_3.1.1/workspace/NodeACSProject" "-p" "60819" "--no-banner" "--no-colors" Working directory: /Applications/Appcelerator/Appcelerator_Studio_3.1.1/workspace/NodeACSProject Environment: {ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8e, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk, APTANA_VERSION=3.1.1.1364101697, Apple_PubSub_Socket_Render=/tmp/launch-w6ncJN/Render, Apple_Ubiquity_Message=/tmp/launch-VUaqhu/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/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=/Applications/Appcelerator/Appcelerator_Studio_3.1.1/workspace/NodeACSProject, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-IM2pSN/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY org.chromium.debug.core 2 0 2013-05-22 14:32:21.501 !MESSAGE (Build 3.1.1.201305212055) [WARNING] A problem while evaluating a stack-frame scope !STACK 0 org.chromium.sdk.internal.v8native.V8Helper$CallbackException: java.lang.RuntimeException: Exception occured in callback at org.chromium.sdk.internal.v8native.V8Helper.callV8Sync(V8Helper.java:176) at org.chromium.sdk.internal.v8native.V8Helper.callV8Sync(V8Helper.java:147) at org.chromium.sdk.internal.v8native.value.ValueLoaderImpl.loadScopeFields(ValueLoaderImpl.java:199) at org.chromium.sdk.internal.v8native.value.JsScopeImpl.loadScopeObject(JsScopeImpl.java:127) at org.chromium.sdk.internal.v8native.value.JsScopeImpl$ObjectBasedImpl.load(JsScopeImpl.java:242) at org.chromium.sdk.internal.v8native.value.JsScopeImpl$ObjectBasedImpl.access$0(JsScopeImpl.java:240) at org.chromium.sdk.internal.v8native.value.JsScopeImpl$ObjectBasedImpl$1.runSync(JsScopeImpl.java:235) at org.chromium.sdk.internal.v8native.value.JsScopeImpl$ObjectBasedImpl$1.runSync(JsScopeImpl.java:1) at org.chromium.sdk.util.AsyncFuture$SyncOperation.execute(AsyncFuture.java:169) at org.chromium.sdk.internal.v8native.value.JsScopeImpl.getDeferredData(JsScopeImpl.java:117) at org.chromium.sdk.internal.v8native.value.JsScopeImpl$ObjectBasedImpl.getScopeObject(JsScopeImpl.java:249) at org.chromium.debug.core.model.Variable.forObjectScope(Variable.java:109) at org.chromium.debug.core.model.StackFrame$2.visitObject(StackFrame.java:132) at org.chromium.debug.core.model.StackFrame$2.visitObject(StackFrame.java:1) at org.chromium.sdk.internal.v8native.value.JsScopeImpl$ObjectBasedImpl.accept(JsScopeImpl.java:226) at org.chromium.debug.core.model.StackFrame.wrapScopes(StackFrame.java:150) at org.chromium.debug.core.model.StackFrame.getVariables(StackFrame.java:67) at org.eclipse.debug.internal.ui.model.elements.StackFrameContentProvider.getAllChildren(StackFrameContentProvider.java:51) at org.eclipse.debug.internal.ui.model.elements.StackFrameContentProvider.getChildCount(StackFrameContentProvider.java:28) at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildCount(ElementContentProvider.java:114) at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$2.run(ElementContentProvider.java:63) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.RuntimeException: Exception occured in callback at org.chromium.sdk.CallbackSemaphore.tryAcquire(CallbackSemaphore.java:68) at org.chromium.sdk.internal.v8native.V8Helper.callV8Sync(V8Helper.java:174) ... 21 more Caused by: java.lang.Exception: Exception saved from callback at org.chromium.sdk.CallbackSemaphore.callbackDone(CallbackSemaphore.java:79) at org.chromium.sdk.internal.BaseCommandProcessor.callThemBack(BaseCommandProcessor.java:141) at org.chromium.sdk.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:104) at org.chromium.sdk.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:112) at org.chromium.sdk.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:114) at org.chromium.sdk.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:120) at org.chromium.sdk.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:209) Caused by: java.lang.RuntimeException: Unsuccessful command Internal error: illegal access at org.chromium.sdk.internal.v8native.V8BlockingCallback.messageReceived(V8BlockingCallback.java:22) at org.chromium.sdk.internal.v8native.V8Helper$2.messageReceived(V8Helper.java:166) at org.chromium.sdk.internal.v8native.V8Helper$2.messageReceived(V8Helper.java:1) at org.chromium.sdk.internal.BaseCommandProcessor$3.call(BaseCommandProcessor.java:100) at org.chromium.sdk.internal.BaseCommandProcessor$3.call(BaseCommandProcessor.java:1) at org.chromium.sdk.internal.BaseCommandProcessor.callThemBack(BaseCommandProcessor.java:134) ... 5 more !ENTRY org.chromium.debug.core 4 0 2013-05-22 14:32:21.502 !MESSAGE SDK:org.chromium.sdk.internal.BaseCommandProcessor: Failed to dispatch response to callback !STACK 0 java.lang.RuntimeException: Unsuccessful command Internal error: illegal access at org.chromium.sdk.internal.v8native.V8BlockingCallback.messageReceived(V8BlockingCallback.java:22) at org.chromium.sdk.internal.v8native.V8Helper$2.messageReceived(V8Helper.java:166) at org.chromium.sdk.internal.v8native.V8Helper$2.messageReceived(V8Helper.java:1) at org.chromium.sdk.internal.BaseCommandProcessor$3.call(BaseCommandProcessor.java:100) at org.chromium.sdk.internal.BaseCommandProcessor$3.call(BaseCommandProcessor.java:1) at org.chromium.sdk.internal.BaseCommandProcessor.callThemBack(BaseCommandProcessor.java:134) at org.chromium.sdk.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:104) at org.chromium.sdk.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:112) at org.chromium.sdk.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:114) at org.chromium.sdk.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:120) at org.chromium.sdk.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:209) {code} Test Steps: 1. Debug default Node.ACS Project, app.js, line 3 (known). 2. Check log. Result: Stack frame warnings and errors.
| 5 |
1,427 |
TISTUD-4751
|
05/23/2013 01:27:59
|
Linux: BlackBerry missing from the tiapp editor
|
Linux: BlackBerry missing from the tiapp editor. BlackBerry exists in the new project wizard, and the supported platforms list in ti info. See screenshot. Test Steps (Linux): 1. Create Alloy Project without BlackBerry selected as a target. 2. View TiApp Editor Overview after project is created. Result: BlackBerry is absent from the target list.
| 3 |
1,428 |
TISTUD-4755
|
05/23/2013 19:46:05
|
Log: [ERROR] Unknown SDK tizen Unknown SDK mobileweb
|
Every time studio is loaded, these errors appear in the log: {code} !ENTRY com.appcelerator.titanium.mobile 4 0 2013-05-23 11:42:43.130 !MESSAGE (Build 3.1.1.201305222018) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK tizen !ENTRY com.appcelerator.titanium.mobile 4 0 2013-05-23 11:42:43.134 !MESSAGE (Build 3.1.1.201305222018) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK mobileweb {code}
| 3 |
1,429 |
TISTUD-4756
|
05/23/2013 20:19:05
|
Alloy: clean install without restart Failed to add Alloy project templates
|
Clean install Studio with no node.js or alloy. Log: {code} !ENTRY com.appcelerator.titanium.alloy.ui 4 0 2013-05-23 12:06:10.353 !MESSAGE (Build 3.1.1.201305222018) [ERROR] Failed to add Alloy project templates !STACK 1 org.eclipse.core.runtime.CoreException: 'node' is not recognized as an internal or external command, operable program or batch file. at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplatesWithNewCommand(AlloyTemplateInstaller.java:292) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplates(AlloyTemplateInstaller.java:269) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.access$0(AlloyTemplateInstaller.java:267) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:161) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.core 4 1 2013-05-23 12:06:10.354 !MESSAGE 'node' is not recognized as an internal or external command, operable program or batch file. {code} Must restart Studio.
| 5 |
1,430 |
TISTUD-4757
|
05/23/2013 22:21:52
|
Dashboard: Windows: samples import wizard cutoff at bottom
|
Dashboard: Windows: samples import wizard cutoff at bottom. See screenshots. Test Steps: 1. Dashboard > Samples > Import. Result: Window does not display cloud section.
| 5 |
1,431 |
TISTUD-4759
|
05/23/2013 22:43:23
|
Node.ACS: Publish fails with database connection error App NodeACSProject already exists
|
Node.ACS: database connection error App NodeACSProject already exists. This does not affect Mountain Lion 10.8.3. Test Steps: 1. Create Node.ACS Project. 2. Publish > Deploy App. Result: Menu appears, see screenshot, fails to recreate app. Expected Result: No menu appears, app gets published.
| 5 |
1,432 |
TISTUD-4780
|
05/25/2013 07:03:09
|
Node.ACS: should not allow create a method with space in the name
|
Test Steps: 1. Create or open existing Node.ACS Project. 2. Select New > Node.ACS Method. See results. Actual REsult: A new method appears using the correct name.The method (function) appears in services.js and it has error indication in it. The same thing is observed while adding Node ACS binding to any type of project an specific error message pop up is displayed Please refer the attached screen shot Log file for more clarification.
| 5 |
1,433 |
TISTUD-4783
|
05/27/2013 23:30:33
|
The message for when the workspace is in use at Studio launch contains "{0}" instead of the actual path
|
This happens only in Studio 3.2.0. Attached the two screenshots to show the difference between 3.1.1 and 3.2.0 when the workspace is in use.
| 5 |
1,434 |
TISTUD-4793
|
05/28/2013 13:35:54
|
'Failed to save the signed in user error' is coming on Ubuntu 12.04 machine
|
Login to Titanium Studio. File > Restart. Actual Result:Credentials are not getting saved.logs attached. {code} !ENTRY com.appcelerator.titanium.core 4 0 2013-05-28 16:22:10.213 !MESSAGE (Build 3.1.1.1364101697) [ERROR] Failed to save the signed-in user !STACK 0 org.eclipse.equinox.security.storage.StorageException: No password provided. at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304) at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224) at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224) at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110) at com.appcelerator.titanium.core.TitaniumUserManager.saveSignedInUser(TitaniumUserManager.java:474) at com.appcelerator.titanium.rcp.IDEWorkbenchWindowAdvisor.postWindowOpen(IDEWorkbenchWindowAdvisor.java:376) at org.eclipse.ui.internal.WorkbenchWindow.fireWindowOpened(WorkbenchWindow.java:1365) at org.eclipse.ui.internal.WorkbenchWindow.open(WorkbenchWindow.java:826) at org.eclipse.ui.internal.Workbench$70.runWithException(Workbench.java:3724) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code}
| 5 |
1,435 |
TISTUD-4796
|
05/28/2013 22:18:59
|
Node.ACS Debugger: Node.ACS JavaScript Exception Breakpoint does not work
|
ENVIRONMENT: Appcelerator Studio, build: 3.1.1.201305271814 ACS v1.0.2 OS X 10.7.5 REPRODUCTION: 1. Create a new Node.ACS project. 2. Replace the controllers/application.js with the following: {code} function index(req, res) { var err = new Error('Danger, Will Robinson!'); throw err; res.render('index', { title: 'Welcome to Node.ACS!' }); } {code} 3. Add the Node.ACS JavaScript exception breakpoint (under the Run menu bar option). 4. Run in debug mode. 5. Once the server is running, run `curl http://localhost:<ip_address>` RESULTS: Program execution does not stop. EXPECTED RESULTS: Program execution should stop. This works in a classic mobile project with a regular JavaScript exception breakpoint.
| 8 |
1,436 |
TISTUD-4799
|
05/28/2013 23:31:59
|
BlackBerry: Allow BB project creation with spaces in the app name
|
Right now Studio does not allow us to create an app with space or certain characters in the app name. This issue has been fixed from the sdk side & we can create apps with spaces & dot(.) in the app name using the CLI.
| 3 |
1,437 |
TISTUD-4802
|
05/29/2013 00:48:51
|
LiveView: Clean project when unchecking LiveView in run configuration
|
If you first run an app with LiveView enabled, and then disable LiveView in the run configuration, the application may well be confused, since it's been modified to run with LiveView. Whenever a user unchecks the LiveView checkbox, we should clean the project before rebuilding.
| 5 |
1,438 |
TISTUD-4803
|
05/29/2013 01:42:52
|
Node.ACS debugger stops at breakpoints that were defined on other Node projects
|
# Create two Node.ACS projects. # Set a breakpoint at line 3 on the app.js of project *A*. # Set a breakpoint at line 2 on the controllers/application.js of project *B*. # Launch a Node.ACS debug session on project *B*. Expected result: No breakpoint should hit. Actual: The application stops on the app.js. We need to make sure we only send out the relevant project breakpoints and not everything. If that's not possible, we can hook to the same area we hacked for TISTUD-4669 and skip breaks that we cannot associate with the actively debugged project.
| 5 |
1,439 |
TISTUD-4816
|
05/29/2013 18:08:15
|
Tizen: 2.1 support: certificate location
|
In Tizen 2.1, there are some changes that may require additional Titanium Studio support. In 2.1, there is a new requirement to generate and use a security certificate, before one can build and deploy web apps. Previously, a default developer certificate was used automatically. In order to reference the certificate, new CLI flags were added in Tizen 2.1 build script (example below, new flags are keystore, password and keystoreca). {code}titanium build --platform=tizen --device=emulator-26100 --keystore=/home/aod/tizen-sdk/tools/certificate-generator/testme.p12 --password=1234 --keystoreca=/home/aod/tizen-sdk/tools/certificate-generator/certificates/developer/tizen-developer-ca.cer{code} These paths have to be configurable in Titanium Studio, where Tizen SDK properties are set up, and used when invoking build commands for Tizen.
| 8 |
1,440 |
TISTUD-4806
|
05/29/2013 18:50:19
|
Android Preferences: Default Google API and Screen not set when Android SDK Path selected
|
When I set the Android SDK path in the preferences, the default API and Screen types are not automatically set, but they are available. See screenshot. Logs void of content. Test Steps: 1. Install Android SDK r22.0.1 with Google APIs 2.3.3 only. 2. Switch to Staging network (where android 2.3.3 is the new minimum). 3. Open Studio, Open Android Preferences. 4. Set Android SDK. Result: Path is set, but default API and screen type are not.
| 3 |
1,441 |
TISTUD-4814
|
05/30/2013 18:59:30
|
Users upgrading to Studio 3.1.1 can't run new Android projects due to the 2.3.3 sdk requirement
|
Steps: 1. Run 3.0.0 Studio. Install the default Titanium SDK (3.1.0.GA) 2. Upgrade to 3.1.1 Studio. Install the default Titanium SDK (3.1.1) 3. Create a new Android project 4. Run in the Android emulator 5. An error message appears stating the minimum android sdk is 2.3 6. Go to the preferences and change the default Android sdk to 2.3.3 (as suggested by the error message) 7. Re-launch the Android emulator Expected: The launch works Actual: The same error message in step 5 is displayed Studio needs to indicate a better error message, or even set the default to 2.3.3 before the launch configuration is created. The way to fix this problem is to change the launch configuration created, which the user won't know to do since the error message doesn't indicate it. There needs to be a better flow here
| 5 |
1,442 |
TISTUD-4817
|
05/30/2013 20:34:56
|
LiveView: Improve visibility in Studio
|
Here is the proposed flow for engaging with Liveview in Studio: * User opens Studio and creates a mobile app * User clicks Run on Simulator or Device for iOS/Android * Gets a prompt that contains: ** text about what is Liveview: ** prompt if he would like to enable Liveview (Enabling LiveView enables it globally) ** a check to never show this again ** info on where he can change this setting Run Configurations> Enable Liveview When the user goes to Run Configuration, he can turn Liveview on/off per platform (iOS/Android) Text for the Run use case: "Appcelerator Studio contains Liveview. Liveview powers you to make changes to your source code and preview them directly on your simulator or device without rebuilding the app. Would you like to enable it?" Enable Liveview globally (checkbox) [default=YES] You can change your selection from Run > Configurations YES / NO
| 0 |
1,443 |
TISTUD-4819
|
05/30/2013 23:30:05
|
Node.ACS debugger debug view flickers when starting a session with an existing exception breakpoint
|
# Create a Node.ACS project # Add a Node.ACS JavaScript exception breakpoint from the 'Run' menu # Open the Breakpoints view and right click the breakpoint # Click the 'Breakpoint Properties' and check the 'Caught Exceptions' option. # Launch the debug session by right-clicking the project and selecting Debug As -> Local Node.ACS The problem manifests itself after the launch. Switch to the Debug perspective and you will notice a lot of flickering in the Debug view for about 30 seconds. What actually happens is that the Node.ACS loading has a lot of caught JS exceptions that we skip by resuming the session. This is an implementation artifact after the fix for TISTUD-4796, and we need to find a way to avoid that flickering.
| 8 |
1,444 |
TISTUD-4824
|
05/31/2013 22:18:49
|
SDKLocator intermittent failure on Linux when getting the latest version
|
This one came out of a failed unitest on Linux. The SDKLocator#getLatestVersion does not always return the correct latest version on Linux.
| 5 |
1,445 |
TISTUD-4832
|
06/01/2013 01:22:37
|
Windows: Studio Console: Node not recognized on clean install, must restart studio
|
Windows: Studio Console: Node not recognized on clean install, must restart studio. Test Steps: 1. Clean install Node.js. 2. Open Terminal view in Studio. 3. Type: node -v Result: {code} $ node -v sh: node: command not found {code}
| 8 |
1,446 |
TISTUD-4841
|
06/03/2013 19:23:46
|
Node.ACS: app not removed when project deleted
|
Node.ACS: app not removed when project deleted. When a Node.ACS project is deleted, it needs to be removed from the acs service list. Note: The only case where an app is correctly prompted for removal is when the app has been deployed. Test Steps: 1. Create Node.ACS Project. 2. Delete Node.ACS Project. Result: No prompt to remove app from acs service list. Expected Result: Prompt to remove app from acs service list. See screenshot 'prompt.png'. Log excerpt: {code} !ENTRY com.aptana.core 1 0 2013-06-03 11:15:16.633 !MESSAGE (Build 3.1.0.201304151600) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "remove" "NodeACSProject" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/Ttianium-Studio-Workspace-3.1.0/NodeACSProject Environment: {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-w6ncJN/Render, Apple_Ubiquity_Message=/tmp/launch-VUaqhu/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/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/Ttianium-Studio-Workspace-3.1.0/NodeACSProject, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-IM2pSN/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}
| 3 |
1,447 |
TISTUD-4846
|
06/03/2013 23:05:39
|
Android Emulator Run Configuration: preferences hyperlink is mislabeled and non-functional
|
Android Emulator Run Configuration: preferences hyperlink is mislabeled and non-functional. The preferences hyperlinks for android packaging and run on device are correctly labelled and functional. See screenshots. Test Steps: 1. Create a new android emulator run config. Result: Preferences hyperlink is mislabeled and non-functional. Expected Result: Preferences hyperlink is labelled "Android SDK Version" and links to Android Preferences.
| 5 |
1,448 |
TISTUD-4847
|
06/03/2013 23:50:59
|
Android SDK 2.2: launching invalid config fails to launch android sdk installer
|
Android SDK 2.2: launching invalid config fails to launch android sdk installer. This occurs when the new minimum android sdk is not installed. Test Steps: 1. Launch Android Emulator Google APIs 2.2 using Studio 3.1.1+. 2. Agree to update to current supported android sdk minimum version. Result: Operation fails with launch error. Expected Result: Android installation utility is run.
| 5 |
1,449 |
TISTUD-4853
|
06/04/2013 01:36:49
|
Android: App log messages aren't getting filtered
|
Steps: 1. Enable all logging in the Console 2. Launch a project in the Android emulator Expected: App output should display messages that are formatted and can be filtered Actual: messages are displayed as follows: {code} D/AppLoads( 385): this.me is null D/CrittercismAPI( 385): POSTING JSON DATA: url = https://api.crittercism.com/android_v2/handle_app_loads data = {"hashed_device_id":"d8d57426-3713-334c-af57-6d29e73ceb80","app_id":"51ad317a702d3139f7000027","device_name":"android","library_version":"3.0.11","app_loads":[{"type":"appload","app_state":{"orientation":1,"low_memory":0,"memory_usage":14074880,"model":"google_sdk","ts":"2013-06-04T00:35:55.55+0000","app_version_code":1,"arch":"armv5tejl","xdpi":240,"locale":"en","sd_space_free":"65965568","battery_level":0.5,"app_version":"1","wifi":{"connecting":false,"failover":false,"connected":false,"available":false},"system":"android","disk_space_total":"134217728","name":"","ydpi":240,"sd_space_total":"66052096","carrier":"Android","dpi":1.5,"mobile_network":{"roaming":false,"failover":false,"connected":true,"available":true},"activity":"gg.g.g.g.gg.GggggghhhhActivity","disk_space_free":"64585728","system_version":"2.3.4"}}]} D/CrittercismAPI( 385): POSTING JSON DATA: response = {"app_settings":{"crittercism_uuid":"d8d57426-3713-334c-af57-6d29e73ceb80","settings":{"rate_after_load_num":5,"receive_forum_post_email":1,"receive_daily_digest":0,"show_close_button":1,"is_rate_after_load":0,"remind_after_load_num":5,"timezone_offset":-7,"feedback_autovote":0,"rate_title":"Rate My App","include_stacktrace_email":1,"need_pkg":1,"receive_first_error_email":1,"throttle_votes_earned":1,"alert_submitter_only":0,"daily_max_votes":10,"rate_message":"Would you mind taking a second to rate my app? I would really appreciate it!","actions":{},"moderate_feedback":0,"default_votes":3}},"success":1,"app_id":"51ad317a702d3139f7000027","me":{"username":null}} W/TiVerify( 385): (Timer-0) [5002,5002] Verifying module licenses... D/dalvikvm( 385): GC_CONCURRENT freed 1029K, 50% free 3465K/6919K, external 1657K/3150K, paused 4ms+3ms I/TiVerify( 385): (Timer-0) [423,5425] Succesfully verified module licenses I/TiAnalyticsSvc( 385): (Thread-26) [22752,28177] Analytics Service Started D/dalvikvm( 385): GC_CONCURRENT freed 603K, 49% free 3561K/6919K, external 1657K/3150K, paused 4ms+3ms D/dalvikvm( 385): GC_CONCURRENT freed 932K, 52% free 3360K/6919K, external 1657K/3150K, paused 3ms+3ms I/TiAnalyticsSvc( 385): (Thread-26) [1655,29832] Stopping Analytics Service {code} Sample Code: {code} var win = Ti.UI.createWindow({ backgroundColor : 'blue' }); var button = Ti.UI.createButton({ title : 'click', top : '40%', bottom : '40%', left : '30%', right : '30%' }); button.addEventListener('click', function() { console.log('console.log()'); console.log(['arg0', 'arg1', 'arg2']); console.debug('console.debug()'); console.debug(['arg0', 'arg1', 'arg2']); console.info('console.info()'); console.info(['arg0', 'arg1', 'arg2']); console.warn('console.warn()'); console.warn(['arg0', 'arg1', 'arg2']); console.error('console.error()'); console.error(['arg0', 'arg1', 'arg2']); Ti.API.trace('Ti.API.trace()'); Ti.API.trace(['arg0', 'arg1', 'arg2']); Ti.API.debug('Ti.API.debug()'); Ti.API.debug(['arg0', 'arg1', 'arg2']); Ti.API.info('Ti.API.info()'); Ti.API.info(['arg0', 'arg1', 'arg2']); Ti.API.warn('Ti.API.warn()'); Ti.API.warn(['arg0', 'arg1', 'arg2']); Ti.API.error('Ti.API.error()'); Ti.API.error(['arg0', 'arg1', 'arg2']); Ti.API.log('TRACE', 'Ti.API.log(TRACE)'); Ti.API.log('TRACE', ['arg0', 'arg1', 'arg2']); Ti.API.log('DEBUG', 'Ti.API.log(DEBUG)'); Ti.API.log('DEBUG', ['arg0', 'arg1', 'arg2']); Ti.API.log('INFO', 'Ti.API.log(INFO)'); Ti.API.log('INFO', ['arg0', 'arg1', 'arg2']); Ti.API.log('WARN', 'Ti.API.log(WARN)'); Ti.API.log('WARN', ['arg0', 'arg1', 'arg2']); Ti.API.log('ERROR', 'Ti.API.log(ERROR)'); Ti.API.log('ERROR', ['arg0', 'arg1', 'arg2']); Ti.API.log('LOG', 'Ti.API.log(LOG)'); Ti.API.log('LOG', ['arg0', 'arg1', 'arg2']); switch(Ti.Platform.osname) { case 'ipad': case 'iphone': { Ti.API.timestamp('Ti.API.timestamp()'); Ti.API.timestamp(['arg0', 'arg1', 'arg2']); } } }); win.add(button); win.open(); {code}
| 5 |
1,450 |
TISTUD-4854
|
06/04/2013 01:37:05
|
iOS Simulator: console ignores log level during build
|
iOS Simulator: console ignores log level during build. Test Steps: 1. Create Alloy project. 2. Run in iPhone Simulator with log level set to info. Result: Trace and Debug log to console. See screenshot and log. Sample Code: {code} var win = Ti.UI.createWindow({ backgroundColor : 'blue' }); var button = Ti.UI.createButton({ title : 'click', top : '40%', bottom : '40%', left : '30%', right : '30%' }); button.addEventListener('click', function() { console.log('console.log()'); console.log(['arg0', 'arg1', 'arg2']); console.debug('console.debug()'); console.debug(['arg0', 'arg1', 'arg2']); console.info('console.info()'); console.info(['arg0', 'arg1', 'arg2']); console.warn('console.warn()'); console.warn(['arg0', 'arg1', 'arg2']); console.error('console.error()'); console.error(['arg0', 'arg1', 'arg2']); Ti.API.trace('Ti.API.trace()'); Ti.API.trace(['arg0', 'arg1', 'arg2']); Ti.API.debug('Ti.API.debug()'); Ti.API.debug(['arg0', 'arg1', 'arg2']); Ti.API.info('Ti.API.info()'); Ti.API.info(['arg0', 'arg1', 'arg2']); Ti.API.warn('Ti.API.warn()'); Ti.API.warn(['arg0', 'arg1', 'arg2']); Ti.API.error('Ti.API.error()'); Ti.API.error(['arg0', 'arg1', 'arg2']); Ti.API.log('TRACE', 'Ti.API.log(TRACE)'); Ti.API.log('TRACE', ['arg0', 'arg1', 'arg2']); Ti.API.log('DEBUG', 'Ti.API.log(DEBUG)'); Ti.API.log('DEBUG', ['arg0', 'arg1', 'arg2']); Ti.API.log('INFO', 'Ti.API.log(INFO)'); Ti.API.log('INFO', ['arg0', 'arg1', 'arg2']); Ti.API.log('WARN', 'Ti.API.log(WARN)'); Ti.API.log('WARN', ['arg0', 'arg1', 'arg2']); Ti.API.log('ERROR', 'Ti.API.log(ERROR)'); Ti.API.log('ERROR', ['arg0', 'arg1', 'arg2']); Ti.API.log('LOG', 'Ti.API.log(LOG)'); Ti.API.log('LOG', ['arg0', 'arg1', 'arg2']); switch(Ti.Platform.osname) { case 'ipad': case 'iphone': { Ti.API.timestamp('Ti.API.timestamp()'); Ti.API.timestamp(['arg0', 'arg1', 'arg2']); } } }); win.add(button); win.open(); {code}
| 5 |
1,451 |
TISTUD-4858
|
06/04/2013 12:19:28
|
iOS Packaging Run Config: 'Upload debug symbol' checkbox deactivates 'Run' option
|
This does not occur 3.1.1. Test Steps: 1. Package iOS App (Ad-Hoc or iTunes). 2. Goto Configuration >> New Configuration and select the 'Upload debug symbol option' Actual Result: 1. 'Run' option is active before selecting the 'Uploading debug symbols' checkbox. 2. 'Run' option is disabled after selecting the 'Uploading debug symbols' checkbox. Please refer the attached screen shot for further clarification.
| 5 |
1,452 |
TISTUD-4861
|
06/04/2013 19:14:22
|
Liveview: No license information presented during plugin install
|
h5. Description: When installing the plugin for liveview via the RC instructions, no license text is presented. h5. Steps to reproduce: 1) Navigate to http://preview.appcelerator.com/appc-studio/ 2) Install the RC plugin via the help > install new software option 3) Click the "more" link in the lower right on the second install screen 4) Navigate to the license section h5. Result: No license text h5. Expected Result: License text
| 3 |
1,453 |
TISTUD-4864
|
06/04/2013 23:49:05
|
App launched using manually created launch configuration does not reflect logging level
|
1. Create launch configuration from Launch configuration wizard for iOS/Android. 2. Modify the logging level to Warn. 3. Launch the app on simulator/emulator and the console still logs the output for Trace level. However, if the app is run using launch shortcut, then the logging level is correctly reflected in Console as specified in the launch configuration.
| 8 |
1,454 |
TISTUD-4882
|
06/05/2013 22:08:09
|
Debug and Profile on Device: Android and iOS: log level changes not respected in console
|
Debug on Device: Android and iOS: log level not respected. This does not appear to be a regression. The builds are launched with log level 'TRACE': {code} "/usr/local/bin/titanium" "--no-colors" "--no-prompt" "build" "--platform" "ios" "--sdk" "3.1.1.v20130604110432" "--log-level" "trace" "--target" "device" "--ios-version" "6.1" "--developer-name" "Dustin Hyde (R766MCANNQ)" "--distribution-name" "Dustin Hyde (R766MCANNQ)" "--pp-uuid" "AEDDA127-DC85-4B6E-93C9-F5498C570E0B" "--deploy-type" "development" "--debug-host" "::1370463608993:192.168.0.166" "--skip-js-minify" "/usr/local/bin/titanium" "--no-colors" "--no-prompt" "build" "--platform" "android" "--sdk" "3.1.1.v20130604110432" "--log-level" "trace" "--target" "device" "--android-sdk" "/Users/dhyde/Desktop/android/android-sdk" "--avd-id" "4" "--debug-host" "adb:9419" "--skip-js-minify" {code} When the log level is changed in the console during runtime, the changes do not take effect. Test Steps: 1. Launch app in Device Debug mode. 2. Change log level in console view. Result: No effect. Sample Code (insert breakpoints as needed): {code} var win = Ti.UI.createWindow({ backgroundColor : 'blue' }); var button = Ti.UI.createButton({ title : 'click', top : '40%', bottom : '40%', left : '30%', right : '30%' }); button.addEventListener('click', function() { console.log('console.log()'); console.log(['arg0', 'arg1', 'arg2']); console.debug('console.debug()'); console.debug(['arg0', 'arg1', 'arg2']); console.info('console.info()'); console.info(['arg0', 'arg1', 'arg2']); console.warn('console.warn()'); console.warn(['arg0', 'arg1', 'arg2']); console.error('console.error()'); console.error(['arg0', 'arg1', 'arg2']); Ti.API.trace('Ti.API.trace()'); Ti.API.trace(['arg0', 'arg1', 'arg2']); Ti.API.debug('Ti.API.debug()'); Ti.API.debug(['arg0', 'arg1', 'arg2']); Ti.API.info('Ti.API.info()'); Ti.API.info(['arg0', 'arg1', 'arg2']); Ti.API.warn('Ti.API.warn()'); Ti.API.warn(['arg0', 'arg1', 'arg2']); Ti.API.error('Ti.API.error()'); Ti.API.error(['arg0', 'arg1', 'arg2']); Ti.API.log('TRACE', 'Ti.API.log(TRACE)'); Ti.API.log('TRACE', ['arg0', 'arg1', 'arg2']); Ti.API.log('DEBUG', 'Ti.API.log(DEBUG)'); Ti.API.log('DEBUG', ['arg0', 'arg1', 'arg2']); Ti.API.log('INFO', 'Ti.API.log(INFO)'); Ti.API.log('INFO', ['arg0', 'arg1', 'arg2']); Ti.API.log('WARN', 'Ti.API.log(WARN)'); Ti.API.log('WARN', ['arg0', 'arg1', 'arg2']); Ti.API.log('ERROR', 'Ti.API.log(ERROR)'); Ti.API.log('ERROR', ['arg0', 'arg1', 'arg2']); Ti.API.log('LOG', 'Ti.API.log(LOG)'); Ti.API.log('LOG', ['arg0', 'arg1', 'arg2']); switch(Ti.Platform.osname) { case 'ipad': case 'iphone': { Ti.API.timestamp('Ti.API.timestamp()'); Ti.API.timestamp(['arg0', 'arg1', 'arg2']); } } }); win.add(button); win.open(); {code}
| 8 |
1,455 |
TISTUD-4886
|
06/06/2013 11:48:58
|
Make user friendly alert for cancelling SDK installation process
|
Test Steps: 1.Launch Studio. 2.Help > Install Titanium SDK > Install from URL > add the URL . 3. Wait til installation process begins. 4. Cancel the process before completion. Expected Result: Error should be user friendly. Screenshot attached.Logs attached.
| 3 |
1,456 |
TISTUD-4890
|
06/06/2013 19:56:19
|
Node.ACS Debugger: intermittent fail to connect with Premature end of file
|
Node.ACS Debugger: intermittent fail to connect with Premature end of file. Occurs 1/6 times, could be related to TISTUD-4747, as they seem intertwined. Test Steps: 1. Create default Node.ACS Project. 2. Debug multiple times in a row with a breakpoint in app.js line 3. Result: Error in UI and log. {code} !ENTRY org.eclipse.debug.core 4 5012 2013-06-06 11:45:49.869 !MESSAGE org.xml.sax.SAXParseException: Premature end of file. occurred while reading launch configuration file: /Applications/Appcelerator/Appcelerator_Studio_3.1.1/workspace/.metadata/.plugins/org.eclipse.debug.core/.launches/Local Node.ACS server - NodeACSProject.launch. !STACK 0 org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1427) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1056) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:232) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284) at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:918) at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1322) at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:614) at org.eclipse.debug.internal.core.LaunchManager.getLaunchConfigurations(LaunchManager.java:1388) at com.appcelerator.titanium.acs.core.ACSCorePlugin$ServerChangeListener$1.run(ACSCorePlugin.java:257) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 8 |
1,457 |
TISTUD-4896
|
06/07/2013 21:56:59
|
"Remove Node.ACS App" message when terminating a Node.ACS debug session
|
Does not affect 3.1.1. Change introduced by TISTUD-4841. This looks like a regression that was introduced after we implemented this dialog. The Node.ACS debugger is creating a temporary Node.ACS project when launched in debug mode. When the session is terminated, that project is being deleted, and that's when we get this dialog. Expected: We should only show this dialog for the Node.ACS projects that the user created.
| 5 |
1,458 |
TISTUD-4897
|
06/07/2013 23:03:21
|
Profiler: upload debug symbols exists in the run config, serves no purpose
|
Profiler: upload debug symbols exists in the run config, serves no purpose. See screenshot. Test Steps: 1. Profile on iOS Device. Results: Note the upload debug symbols option.
| 3 |
1,459 |
TISTUD-4903
|
06/10/2013 11:23:01
|
Node ACS project contains Syntax error: unexpected token in the run.js.chromium file
|
Test Steps: 1. Create Node ACS project 2. Launch debugger session for the respective project Actual Result: 1. 'Label Jobs' error message pop up is displayed. 2. Syntax error: unexpected token in the run.js.chromium file Please refer the attached screen shot and log file for more details.
| 5 |
1,460 |
TISTUD-4906
|
06/10/2013 20:35:14
|
Code Analyzer: Warning or Error icons are not displayed in code gutter
|
h5. Problem description After running the Code Processor, results Warnings or Errors are not correctly displayed as Icons next to the code in the Project Files, as described here: https://wiki.appcelerator.org/display/tis/Code+Analyzer#CodeAnalyzer-InterpretingtheResultsintheProjectFiles h5. Steps to reproduce - Create a project using a code that should generate errors or warnings (see the sample app here - in this case I'm using an iPad specific API) {code} var win = Ti.UI.createWindow({ backgroundColor:'gray', title:'test' }); var label = Ti.UI.createLabel({ text:'test', font:{ fontSize:'24dp' } }); var ipadPopover = Ti.UI.iPad.createPopover(); win.add(label); win.add(ipadPopover); win.open(); {code} - Run the Code Analyzer; in our case run the Code Analyzer for Android, since the sample is using a specific platform API and it should fail if run on Android. Results: in the html Results report, Warnings are correctly displayed. However, there should be displayed too a Warning icon and hovering on the warning icon, a message saying why this code is not supported should be displayed.
| 5 |
1,461 |
TISTUD-4917
|
06/11/2013 20:14:40
|
Code Analyzer: Alloy: When a Warning or Error is found for an Alloy project, code gutter icons are added to the Resources project files, not to App folder
|
h5. Problem description When a Warning or Error is found by the Code Analyzer for an Alloy project, Warning or Error icons are placed in the code gutter in the Resources file projects instead than in the App file projects. The result is that the Project is now marked with the red/white error icon and the 'Errors in Workspace' alert is displayed every time the project is being build. 'Resources' folder is by default not visible for Alloy projects on Studio, so the default result is also that the project is marked with an error icon, but the user can't see any other red error icon next to any visible Project file. Also, having an error or a warning reported for the Alloy compiled code in the Resources folder is not adding much value for the user as the intended behavior is not to manually modify the compiled code files in the Resources (user should only handle Alloy files, all included into the App folder). h5. Steps to reproduce Paste the sample code. Note the code error in the controller.js , where foobar is actually not a function. The error is correctly reported by the Code Analyzer (see the screenshot), also getting the correct position in the Alloy project. However, in Studio the Error icon is placed in 'Resources/alloy/controllers/index.js' , which is hidden by default and should in any case manually modified by the user. h6. controller/index.js {code} $.mainwin.foobar({ backgroundColor : 'blue' }); $.index.open(); {code} h6. index.xml {code} <Alloy> <Window title="Win 1" id='mainwin'> <Label>I am Window 1</Label> <Button>Click</Button> </Window> </Alloy> {code} h5. Note Alloy projects could also be displaying errors or warning relative to compiled code, generated by Alloy, not necessarily linked to "App" alloy files created by the user but only present in "Resources" folder.
| 8 |
1,462 |
TISTUD-4918
|
06/11/2013 22:34:57
|
Tizen: Tizen target greyed out
|
Description: 1. First make sure you have the tizen 2.1 sdk installed & have configured tizen sdk in the studio 2. Go to create new app in titanium or appcelerator studio 3. Select the appropriate type of app e.g classic or alloy 4. Notice the tizen deployment target Actual result: 1. The tizen target is greyed out Expected Results: 1. The tizen target should be enabled after its configured in studio prefs
| 5 |
1,463 |
TISTUD-4919
|
06/11/2013 23:27:09
|
Update Dashboard with the Tizen mininum SDK version as 2.1
|
As the minimum version of Tizen SDK supported by Studio is 2.1, Studio's dashboard should be updated to refer to the minimum version of Tizen SDK as 2.1 instead of 2.0
| 3 |
1,464 |
TISTUD-4923
|
06/12/2013 18:41:36
|
Samples: Folder context menu has single non-functional import item that fails silently
|
In the sample pane within studio, it's possible to right-click on the folder for either "Field Service" or "Appcelerator" sample folders and get a contextual menu with a single option "Import sample as project ". Choosing this fail to do anything, and does not notify the user of any failure or success. Test steps: 1. In the Samples Explorer right click on the folder (Appcelerator or Field Services)- you should see "Import sample as project" 2.Click "Import sample as project" Actual result: 2. Nothing happens Expected: 2.Notification of success or failure
| 5 |
1,465 |
TISTUD-4926
|
06/12/2013 20:21:58
|
Can't terminate iOS Simulator process from the console
|
Can not terminate iOS Simulator process Step 1: In Studio debug any app as iOS Simulator, it starts the iOS Simulator as it should. Step 2: Click terminate (red square button). Step 3: notice the process will look like it has been terminated in Studio but the Simulator will not terminate. Looks like only switching consoles and terminating the process will work. Note: it is happening with Android Emulator as well.
| 5 |
1,466 |
TISTUD-4932
|
06/13/2013 09:15:31
|
Node.ACS Debugger: breakpoint not hit from app.js start method
|
Test Steps: 1. Create or use existing Node.ACS Project. 2. Insert a breakpoint in app.js at line no. 3. 3. Debug project. See results. Actual Result: Neither Debug perspective is not launched nor is the breakpoint hit. Please refer the attached console and log file for more details.
| 5 |
1,467 |
TISTUD-4934
|
06/13/2013 18:39:19
|
Debug and Profile on Device: Android and iOS: log level intermittently not respected in console on launch
|
This is a clone of TISTUD-4882 to address possible related problematic behavior. Debug on Device: Android and iOS: log level not respected. Sometimes the old console log level is used instead of trace. Note this ticket might be invalid, as we might actually want to use the existing console level. Also note the device run config does not allow the user to select a preferred default log level. This does not appear to be a regression. The builds are launched with log level 'TRACE': {code} "/usr/local/bin/titanium" "--no-colors" "--no-prompt" "build" "--platform" "ios" "--sdk" "3.1.1.v20130604110432" "--log-level" "trace" "--target" "device" "--ios-version" "6.1" "--developer-name" "Dustin Hyde (R766MCANNQ)" "--distribution-name" "Dustin Hyde (R766MCANNQ)" "--pp-uuid" "AEDDA127-DC85-4B6E-93C9-F5498C570E0B" "--deploy-type" "development" "--debug-host" "::1370463608993:192.168.0.166" "--skip-js-minify" "/usr/local/bin/titanium" "--no-colors" "--no-prompt" "build" "--platform" "android" "--sdk" "3.1.1.v20130604110432" "--log-level" "trace" "--target" "device" "--android-sdk" "/Users/dhyde/Desktop/android/android-sdk" "--avd-id" "4" "--debug-host" "adb:9419" "--skip-js-minify" {code} When the log level is changed in the console during runtime, the changes do not take effect (TISTUD-4882), so the initial launch level cannot be changed. If TISTUD-4882 is fixed, this ticket may no longer have the same severity. Test Steps: 1. Launch app in Device Debug mode. 2. Change log level in console view. Result: No effect. Intermittently the default log level is not trace, but the previous log level from the existing console. Sample Code (insert breakpoints as needed): {code} var win = Ti.UI.createWindow({ backgroundColor : 'blue' }); var button = Ti.UI.createButton({ title : 'click', top : '40%', bottom : '40%', left : '30%', right : '30%' }); button.addEventListener('click', function() { console.log('console.log()'); console.log(['arg0', 'arg1', 'arg2']); console.debug('console.debug()'); console.debug(['arg0', 'arg1', 'arg2']); console.info('console.info()'); console.info(['arg0', 'arg1', 'arg2']); console.warn('console.warn()'); console.warn(['arg0', 'arg1', 'arg2']); console.error('console.error()'); console.error(['arg0', 'arg1', 'arg2']); Ti.API.trace('Ti.API.trace()'); Ti.API.trace(['arg0', 'arg1', 'arg2']); Ti.API.debug('Ti.API.debug()'); Ti.API.debug(['arg0', 'arg1', 'arg2']); Ti.API.info('Ti.API.info()'); Ti.API.info(['arg0', 'arg1', 'arg2']); Ti.API.warn('Ti.API.warn()'); Ti.API.warn(['arg0', 'arg1', 'arg2']); Ti.API.error('Ti.API.error()'); Ti.API.error(['arg0', 'arg1', 'arg2']); Ti.API.log('TRACE', 'Ti.API.log(TRACE)'); Ti.API.log('TRACE', ['arg0', 'arg1', 'arg2']); Ti.API.log('DEBUG', 'Ti.API.log(DEBUG)'); Ti.API.log('DEBUG', ['arg0', 'arg1', 'arg2']); Ti.API.log('INFO', 'Ti.API.log(INFO)'); Ti.API.log('INFO', ['arg0', 'arg1', 'arg2']); Ti.API.log('WARN', 'Ti.API.log(WARN)'); Ti.API.log('WARN', ['arg0', 'arg1', 'arg2']); Ti.API.log('ERROR', 'Ti.API.log(ERROR)'); Ti.API.log('ERROR', ['arg0', 'arg1', 'arg2']); Ti.API.log('LOG', 'Ti.API.log(LOG)'); Ti.API.log('LOG', ['arg0', 'arg1', 'arg2']); switch(Ti.Platform.osname) { case 'ipad': case 'iphone': { Ti.API.timestamp('Ti.API.timestamp()'); Ti.API.timestamp(['arg0', 'arg1', 'arg2']); } } }); win.add(button); win.open(); {code}
| 5 |
1,468 |
TISTUD-4950
|
06/13/2013 21:31:15
|
Configuration: Add the Alloy assets paths as part of the Studio search for an App image
|
After importing the Field Service project from the studio sample pane, the 'TI.FieldService'Configuration error was detected, which explains that image cannot be located. Appcelerator Studio, build: 3.1.1.201306112353 Titanium SDK, buld: 3.1.1.v20130611153550 Mac osx 10.8.4 Mountain Lion
| 5 |
1,469 |
TISTUD-4951
|
06/14/2013 01:43:43
|
Switching Android SDK path results in an NPE
|
Steps to Reproduce: 1. Go to Preferences > Studio > Platforms > Android 2. Switch the Android SDK path Expected Result: Should switch without any errors Actual Result: The SDK switches fine, but I get a pop up saying there is an NPE.
| 3 |
1,470 |
TISTUD-4956
|
06/14/2013 21:57:11
|
Studio contributions to Customize View should have consistent names
|
We have two contributions: one for hiding the build folder and one for hiding the Resources folder for Alloy projects. Their names are inconsistent in Appcelerator Studio, one "Appcelerator Build Folders" and one "Titanium Resources Folder". The latter should be "Appcelerator Resources Folders" to keep the branding and plural consistent.
| 2 |
1,471 |
TISTUD-4964
|
06/14/2013 23:41:01
|
Module creation wizard UI is messed up
|
This is probably as a result of the latest refactoring. See screenshot. There are two iOS radio options, and the MobileWeb option is not at the right place.
| 5 |
1,472 |
TISTUD-4965
|
06/14/2013 23:43:07
|
Missing string translation in the iOS Module creation wizard
|
See attached screenshot. This one is probably related to the latest refactoring, and to TISTUD-4964. When clicking the first iOS option, the status error indicates that a string translation is missing.
| 3 |
1,473 |
TISTUD-4967
|
06/15/2013 00:53:39
|
NPE while launching app on iPad simulator
|
Launch/Profile Field Service app on iPad simulator and the launch throws an NPE error dialog : java.lang.NullPointerException at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:125) at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:546) at org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:541) at org.eclipse.core.runtime.Platform.getStateLocation(Platform.java:975) at com.aptana.js.debug.core.internal.ProtocolLogger.<init>(ProtocolLogger.java:38) at com.appcelerator.titanium.ios.internal.core.IOSNodeJSCommandsHelper.runOnSimulator(IOSNodeJSCommandsHelper.java:442) at com.appcelerator.titanium.ios.internal.core.IOSCommandsHelper.run(IOSCommandsHelper.java:461) at com.appcelerator.titanium.ios.internal.core.IOSNodeJSCommandsHelper.run(IOSNodeJSCommandsHelper.java:1) at com.appcelerator.titanium.core.internal.cli.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:399) at com.appcelerator.titanium.ios.ui.launching.simulator.IOSSimulatorLaunchConfigurationDelegate.launch(IOSSimulatorLaunchConfigurationDelegate.java:66) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:857) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
| 3 |
1,474 |
TISTUD-4970
|
06/15/2013 01:55:43
|
Blackberry SDK not recognized in Dashboard
|
* Set a valid path for Blackberry SDK (version 10.0.0.9) in Preferences. * Refresh/open the dashboard - it does not recognize the valid blackberry SDK path in the preferences.
| 5 |
1,475 |
TISTUD-4971
|
06/15/2013 05:20:28
|
No provisioning profiles shown in run-on-iOS-device launch configuration
|
When manually creating a launch configuration for profiling on iOS device, I saw the provisioning profiles combo box is empty, and the same applies to running on iOS device as well. The iOS preference page does show the list correctly.
| 5 |
1,476 |
TISTUD-4974
|
06/15/2013 23:00:30
|
MobileWeb Packaging: recent launch fails to appear in list after run
|
MobileWeb Packaging: recent launch fails to appear in list after run. However, the mobileweb packaging run config is created properly. All other deployment options/run configs for every other platform and runtype work correctly. See screenshots. Test Steps: 1. Package for MobileWeb using Deployment UI (Package => etc.). 2. Invoke Package => <dropdown>. Results: Recent launch does not appear for mobileweb packaging, but the run config is created correctly.
| 5 |
1,477 |
TISTUD-4978
|
06/17/2013 12:14:05
|
Submit Ticket: Windows: some characters produce error illegal unquoted character code 13
|
h3. Steps to Reproduce Submit Ticket option shows error when we add numbered steps in "steps to reproduce" section. But it works fine on other cases.See screen shot 1.select help option 2.Select Submit ticket option 3.edit numbered steps in "steps to reproduce section" 4.submit h3. Actual Result "Failed to create ticket" h3. Expected Result ticket should be create successfully
| 5 |
1,478 |
TISTUD-4977
|
06/17/2013 17:02:34
|
Add os platform filter to ios plugins/fragments
|
We used to guard for Mac OS only in code throughout our codebase for showing/validating iOS platform support. What we should really be doing is limiting the installation of the plugins/fragments for iOS to only get packaged and used on Mac. This will reduce the IDE size on non-Mac OSes (both download and on-disk).
| 5 |
1,479 |
TISTUD-4994
|
06/18/2013 20:56:43
|
Node.ACS exception breakpoint debugging: Enable "Caught Exception" by default
|
Currently user needs to enable the setting manually after adding Node.ACS exception breakpoint via Run > Add Node.ACS JavaScript Exception Breakpoint; otherwise they would not see the exception getting hit. We should enable it by default.
| 3 |
1,480 |
TISTUD-4997
|
06/19/2013 00:51:36
|
ResourceException when a project is closed
|
# Create a project (for example, a Node.ACS project) # Close the project (right click -> Close) These error were found in the log: {code} !ENTRY com.aptana.editor.common 4 0 2013-06-18 16:47:02.980 !MESSAGE (Build 3.1.2.201306171542) [ERROR] Resource '/Node-4670' is not open. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/Node-4670' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150) at org.eclipse.core.internal.resources.Project.getDescription(Project.java:428) at com.aptana.editor.common.preferences.ContentAssistPreferencePage.createUserAgentGroupContent(ContentAssistPreferencePage.java:316) at com.aptana.editor.common.preferences.ContentAssistPreferencePage.createFieldEditors(ContentAssistPreferencePage.java:91) at org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:227) at com.aptana.ui.preferences.PropertyAndPreferenceFieldEditorPage.createContents(PropertyAndPreferenceFieldEditorPage.java:197) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501) at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258) 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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674) at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704) 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.handlePostSelect(StructuredViewer.java:1226) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1251) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:262) at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433) 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.observerProc(Display.java:3525) 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_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052) at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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) !SUBENTRY 1 org.eclipse.core.resources 4 372 2013-06-18 16:47:02.981 !MESSAGE Resource '/Node-4670' is not open. !ENTRY com.aptana.core 4 0 2013-06-18 16:47:03.615 !MESSAGE (Build 3.1.2.201306171542) [ERROR] Failed to retrieve the setting for the last synchronization connection !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/Node-4670' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150) at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:200) at org.eclipse.core.internal.resources.Resource.getPersistentProperty(Resource.java:1178) at com.aptana.ide.syncing.core.ResourceSynchronizationUtils.getLastSyncConnection(ResourceSynchronizationUtils.java:105) at com.aptana.ide.syncing.ui.properties.SynchronizationPropertyPage.createContents(SynchronizationPropertyPage.java:62) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501) at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258) 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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674) at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704) 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.handlePostSelect(StructuredViewer.java:1226) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1251) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:262) at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433) 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.observerProc(Display.java:3525) 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_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052) at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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) !SUBENTRY 1 org.eclipse.core.resources 4 372 2013-06-18 16:47:03.616 !MESSAGE Resource '/Node-4670' is not open. {code}
| 3 |
1,481 |
TISTUD-4998
|
06/19/2013 00:58:37
|
Closed Node.ACS project error when updating client's server URLs
|
# Create a Node.ACS project # Close the project (right-click -> Close) After a while, an error dialog appears (see screenshot). Nothing much in the log, but the error dialog indicates a problem while updating the client's server URLs.
| 3 |
1,482 |
TISTUD-5003
|
06/19/2013 20:15:38
|
NPE in the log when getting the latest SDK release while Studio is shutting down
|
Spotted this one on my log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-06-19 12:11:54.458 !MESSAGE An internal error occurred during: "Checking for new Appcelerator Updates...". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.update.TitaniumSDKUpdater.getLatestSDKRelease(TitaniumSDKUpdater.java:583) at com.appcelerator.titanium.update.TitaniumSDKUpdater.getAvailableUpdates(TitaniumSDKUpdater.java:304) at com.appcelerator.titanium.update.TitaniumUpdaterUtil.getAvailableUpdates(TitaniumUpdaterUtil.java:243) at com.appcelerator.titanium.update.TitaniumUpdateStartup$1.run(TitaniumUpdateStartup.java:58) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 3 |
1,483 |
TISTUD-5004
|
06/19/2013 22:26:54
|
Sort the Android SDK versions in the Android installer and App Store distribution launch configuration pages
|
This is a regression introduced by TISTUD-1534. The "Android SDK Version" drop-down in the Application installer and the App Store distribution launch configuration tabs is displaying the Android SDK version in an un-sorted way (unlike the sorted display under the "Emulator" configuration page). We should sort those the same as the emulator.
| 3 |
1,484 |
TISTUD-5007
|
06/19/2013 23:00:59
|
OAuth key and OAuth secret for Dev and Prod need to be listed in Studio->TiApp.xml
|
OAuth key and OAuth secret for Dev and Prod need to be listed in Dashboard->ACS and in Studio->TiApp.xml In Studio tiapp.xml we have a link to show cloud keys and it displays one key for dev and one key for prod (see screen shot). When developing Node services that connect to ACS you need OAuth key and OAuth secret for both dev and prod for the ACS.init() method (http://docs.appcelerator.com/cloud/latest/#!/guide/node_acs) You have to go into the XML or go to the dashboard to get this info but it would be nice to have it appear when you press show keys in tiapp.xml (overview mode).
| 5 |
1,485 |
TISTUD-5012
|
06/20/2013 19:38:58
|
BlackBerry: update platform strings to current format
|
Currently they are spelled 'Blackberry' and 'Mobile Web'. The convention is to spell them 'BlackBerry' and 'MobileWeb'. Test Steps: 1. Invoke Code Processor context menu (or invoke the project run-menu drop-down). Result: Spelling errors. See screenshots.
| 3 |
1,486 |
TISTUD-5016
|
06/21/2013 01:25:34
|
Dashboard: 3.2.0 dashboard missing ios
|
Dashboard: 3.2.0 dashboard missing ios. Seems to only affect 3.2.0. Test Steps: 1. Open dashboard Get Started. Result: iOS absent. See screenshot. No logs.
| 5 |
1,487 |
TISTUD-5020
|
06/21/2013 23:00:39
|
Diagnostic Log: reset log focus to the top when run
|
Diagnostic Log: reset log focus to the top when run. When diagnostic log is run, the focus is at the bottom of the log, making it inconvenient to view, the user must manually scroll to the top. See screenshots. Test Steps: 1. Run diagnostic log. Result: Results appear at the bottom of the log. Expected Result: Results appear at the top of the log.
| 3 |
1,488 |
TISTUD-5029
|
06/26/2013 11:07:40
|
Support CoffeeScript syntax coloring
|
h2. Problem After updating to Titanium Studio build: 3.1.1.201306112235, none of my .coffee files has syntax highlighting anymore. Syntax highlighting for .js files is unaffected. This seems to be a regression. h2. Test case Open any .coffee file.
| 3 |
1,489 |
TISTUD-5032
|
06/26/2013 20:21:26
|
Project Wizard: wizard resizes when alloy loads
|
Project Wizard: wizard resizes when alloy loads. See video. Test Steps: 1. Create new alloy project. Result: Notice wizard resizes when first invoked. Expected Result: Excellent user experience.
| 5 |
1,490 |
TISTUD-5035
|
06/26/2013 23:38:17
|
NPE: TiAppEditor.java:143
|
I created a project, deleted it, then created another project and got an npe somewhere inbetween. {code} !ENTRY org.eclipse.ui 4 0 2013-06-26 12:00:14.634 !MESSAGE Unable to create editor ID com.appcelerator.titanium.ui.ide.tiappEditor: An unexpected exception was thrown. !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppEditor.addPages(TiAppEditor.java:143) at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198) at org.eclipse.ui.internal.PartStack.presentationSelectionChanged(PartStack.java:834) at org.eclipse.ui.internal.PartStack.access$1(PartStack.java:823) at org.eclipse.ui.internal.PartStack$1.selectPart(PartStack.java:137) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:133) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:269) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:278) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.access$1(DefaultTabFolder.java:1) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder$2.handleEvent(DefaultTabFolder.java:88) 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.custom.CTabFolder.setSelection(CTabFolder.java:2746) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1433) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:257) 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) {code}
| 3 |
1,491 |
TISTUD-5039
|
06/27/2013 21:38:29
|
The error mark next to deployment target in mobile project wizard could be improved
|
It's nice that we are now providing additional info on why a platform is disabled in new mobile project wizard. However, the position of the error mark is misleading. For example, in the screenshot attached, it's easy to think Android and Mobile Web are having configuration errors, not BlackBerry and Tizen. The error mark probably should be after the platform name, and hovering over the disabled text should also show the reason.
| 5 |
1,492 |
TISTUD-5040
|
06/27/2013 21:57:59
|
Run/Debug/Profile/Test menu actions are all disabled when the view is not in focus
|
1. Create a new mobile project; 2. In Project or App Explorer, select Run > iPad Simulator from the local toolbar; 3. The console view should now take focus since it's outputting logs; if not, click on the Console view to make sure it has the focus; 4. Click on Run again in Project Explorer. Actual result: the menus are all disabled. Expected result: the menus should be enabled. The workaround is to click Run one more time and then the menus will appear enabled again. This appears to be a regression as it works fine in 3.1.1.
| 5 |
1,493 |
TISTUD-5045
|
06/28/2013 21:18:01
|
Run Configuration dialog: new iOS device and publishing launch configurations take some time to load and freeze UI
|
1. Open Run > Run Configurations... dialog; 2. Double click on Appcelerator iOS iTunes Distribution. Expected behavior: the launch configuration is created right away and its UI appears. Actual behavior: it takes a few seconds or longer, depending on how many certificates and provisioning profiles you have, for the launch config UI to appear, and the UI is frozen in the mean time. The same behavior applies to iOS Ad-hoc/Enterprise Distribution and iOS Application Installer. We should improve the behavior by doing something similar to what we did in iOS preference page, i.e. showing "Loading..." in the related combo-box and load the certificates in the background. The Run button should also be disabled until the combo-box is filled with actual values.
| 5 |
1,494 |
TISTUD-5046
|
06/28/2013 21:52:37
|
New Mobile Module Project wizard: The text when hovering over the warning icon is not very user friendly
|
It's nice that in the new module project wizard, a warning icon is now displayed for disabled platform. However, when hovering over the one for Android, the text contains "<a href=..." instead of displaying a friendly text that links to the url.
| 2 |
1,495 |
TISTUD-5047
|
06/28/2013 22:39:59
|
Update Eclipse base to 4.3
|
Eclipse 4.3 is officially released. We should update the Eclipse base on hudson from 4.3 M7 to 4.3 and update the builds to point to it and use the appropriate launcher jar.
| 5 |
1,496 |
TISTUD-5049
|
06/29/2013 00:19:02
|
Cannot package iOS AdHoc app
|
# Create a new app with an iOS deploy target # Click to deploy (package) it as AdHoc Result: {code} Titanium Command-Line Interface, CLI version 3.1.1, Titanium SDK version 3.2.0.v20130628134044 Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ Accepted values: test development [ERROR] Invalid --deploy-type value 'production' {code}
| 3 |
1,497 |
TISTUD-5052
|
07/01/2013 19:47:29
|
When "missing semicolons" option is set to Ignore, no related marker should appear in the editor
|
This appears to be an edge case failure with the implementation of TISTUD-3601. When Preferences > Studio > Validation > JavaScript Syntax Validator > Options > Missing semicolons is set to "Ignore", we are still displaying a marker, when the expected result is to not show a marker at all.
| 3 |
1,498 |
TISTUD-5055
|
07/02/2013 01:11:00
|
Provisioning profile not recognized in iOS device launch configuration
|
Steps to reproduce : 1) Open Launch configuration wizard 2) Create a launch configuration for Run -> iOS Application Installer or iTunes Distribution The provisioning profile is not available though it is already configured on the machine. The same launch configurations on 3.1.2 are displaying provisioning profiles without any errors. The iOS preferences also does not display the provisioning profiles on 3.2.0
| 3 |
1,499 |
TISTUD-5059
|
07/02/2013 14:28:53
|
Support "advanced" git pull specifying remote and/or branch(es)
|
Add support for git pull with additional arguments. {{git pull <remote> <branch>}} May want to ignore branch argument and assume current branch. Pop a menu with list of remotes to pull from? git pull effectively does fetch + merge (or fetch + rebase depending on config).
| 8 |
1,500 |
TISTUD-5060
|
07/02/2013 14:31:20
|
Add support to create github pull requests for current branch
|
Currently a user has to break their workflow by going into the browser to generate a pull request. It'd be nice if we could add a command to do that for the user. If the current branch doesn't exist on origin, push to origin. Executes API call to request pull against upstream http://developer.github.com/v3/pulls/#create-a-pull-request - "head": "<username>:<current_branch_name>" - "base": "<base branch of upstream, usually development>" - "title": "Pull Request" - "body": "some string. Pre-populate with commit messages on branch?"
| 13 |
1,501 |
TISTUD-5061
|
07/02/2013 14:33:56
|
Add support to create github forks
|
We don't easily support a common github workflow of creating a fork of a repo and then cloning it (we just support clone). We may want to add a command or import wizard that allows a user to specify a repository to fork, then we call the Github API to fork to their account (or org? May need to prompt for where to fork to), then clone the fork and automatically add the original as 'upstream' remote.
| 13 |
1,502 |
TISTUD-5063
|
07/02/2013 21:15:18
|
Node.js: update to Node.js 0.10.13
|
Node.js: update to Node.js 0.10.12
| 3 |
1,503 |
TISTUD-5064
|
07/02/2013 22:34:20
|
No menu items appear under Run/Debug/etc when an invalid Android SDK path is set in preferences
|
1. Open Preferences > Studio > Platforms > Android; 2. In the Android SDK home, enter a path that exists but doesn't contain any Android SDK; Another way to get into this state is to remove the path completely, go to Dashboard to install from Android install manager, and then quit before installing a valid SDK. 3. Select an existing project with Android enabled and click on the Run icon in Project Explorer toolbar. Expected result: the proper menu items get populated. Actual result: nothing happens, and the following exception appears in the log. {code} !ENTRY org.eclipse.ui 4 0 2013-07-02 14:24:24.032 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Ljava.lang.String; at com.appcelerator.titanium.core.internal.mobile.MobilePlatformsRegistry$LazyMobilePlatform.configurationStatus(MobilePlatformsRegistry.java:296) at com.appcelerator.titanium.core.TitaniumProjectPropertyTester.test(TitaniumProjectPropertyTester.java:104) at org.eclipse.core.internal.expressions.Property.test(Property.java:58) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) at org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:287) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.getLaunchShortcuts(LaunchConfigurationManager.java:717) at com.appcelerator.titanium.ui.AbstractLaunchActionProvider.fillMenu(AbstractLaunchActionProvider.java:80) at com.aptana.ui.actions.DefaultNavigatorActionProvider.run(DefaultNavigatorActionProvider.java:107) at com.aptana.ui.actions.DefaultNavigatorContributionItem$1.widgetSelected(DefaultNavigatorContributionItem.java:57) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) {code}
| 3 |
1,504 |
TISTUD-5067
|
07/03/2013 15:01:21
|
Re-use Android "device" launch config type for "profile" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the Android "profile on device" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,505 |
TISTUD-5068
|
07/03/2013 15:12:28
|
Re-use Android "device" launch config type for "test" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the Android "test on device" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,506 |
TISTUD-5069
|
07/03/2013 15:12:57
|
Re-use Android "device" launch config type for "debug" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the Android "debug on device" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,507 |
TISTUD-5070
|
07/03/2013 15:14:03
|
Re-use Android "emulator" launch config type for "profile" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the Android "profile on emulator" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 3 |
1,508 |
TISTUD-5071
|
07/03/2013 15:14:13
|
Re-use Android "emulator" launch config type for "test" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the Android "test on emulator" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 3 |
1,509 |
TISTUD-5073
|
07/03/2013 15:15:29
|
Re-use iOS "simulator" launch config type for "debug" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the iOS "debug on simulator" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
1,510 |
TISTUD-5074
|
07/03/2013 15:15:42
|
Re-use iOS "simulator" launch config type for "test" mode
|
Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be using that across all the modes of "run", "debug", "profile" and "test" - rather than defining a new launch config type for each mode. This ticket is to remove the iOS "test on simulator" launch config type, and then update the delegate, shortcut and tab group to point to the standard android device launch config type id (an attribute on the extension and for the classes usually one single reference to the id in code). It will also involve removing the launch config type image registered for the profile launch config type.
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.