issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-5070
|
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 |
train
|
TISTUD-5071
|
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 |
train
|
TISTUD-5073
|
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 |
train
|
TISTUD-5074
|
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 |
train
|
TISTUD-5075
|
Re-use iOS "simulator" 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 iOS "profile 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 |
train
|
TISTUD-5076
|
Re-use iOS "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 iOS "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 |
train
|
TISTUD-5077
|
Re-use iOS "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 iOS "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 |
train
|
TISTUD-5078
|
Re-use iOS "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 iOS "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 |
train
|
TISTUD-5079
|
Make JSCA handling forgiving of arbitrary new properties
|
Looks like the platform wants to be able to add additional data to the JSCa file to be used in Ti.Next. Unfortunately our JSCA support currently blows up (throws a runtime exception that effectively breaks our parsing) when we encounter unexpected properties and their values. See https://github.com/appcelerator/titanium_mobile/pull/4429 We need to eat up the new property value (whether its a primitive, array, or object) while ignoring it rather than blowing up because it's a property we don't understand.
| 5 |
train
|
TISTUD-5084
|
XML code completion adds closing tag when fully typing a self-closed tag
|
Start typing {{<Label /}} in the Studio XML editor (e.g. Alloy view). Now if you wait a sec and then type {{>}} everything is OK. You have created a self-closed {{<Label />}} tag with no problem. But the following cases don't: * Type {{<Label />}} without stopping and you'll get {{<Label />></Label>}} * Type {{<Label foo="bar" />}} and you'll get {{<Label foo="bar">></Label>}} This can be very irritating when typing lots of self closed-tags, e.g. Alloy view elements.
| 5 |
train
|
TISTUD-5089
|
Studio: the Plugin zip does not exist on the update site
|
This applies to both Titanium Studio and Appcelerator Studio. Clicking on the "Download Plugin Update Site" link in http://preview.appcelerator.com/appcelerator/studio/standalone/update/stable/ leads to a non-existent URL.
| 5 |
train
|
TISTUD-5101
|
Improve Github PR submission
|
The Github PR submission works OK, but could use some improvement in behavior/UI: - If I have long commit messages the dialog gets very wide. It should have a max width set and just use horizontal scrolling if necessary - The actual PR submission should happen asynchronously, it currently runs in the UI thread. (Schedule as user job, and show error in error dialog, success in toast as we do) - The UI doesn't summarize the two endpoints being proposed for merging (let alone let user modify them). The dialog should show the name of the target repo and branch and the name of the current repo and branch. - The success toast should give more details (like the generated PR number) and allow the user to click the toast to open the PR in a browser.
| 8 |
train
|
TISTUD-5104
|
List open pull requests for git repo attached to github, selecting PR opens in browser
|
Now that we can generate pull requests in Studio, it'd be nice to see the list of open PRs against a given repo and select them to open the PR in a browser (internal?). http://developer.github.com/v3/pulls/#list-pull-requests We already have a very simple pull request model to parse the JSON that describes a PR returned by the Github API. So the work here is to call the new API endpoint, iterate over the array of PRs turning them into objects, and hooking menu extensions to show the listing and open the PR's URL when selected.
| 8 |
train
|
TISTUD-5105
|
Allow user to merge an open pull request for a git repo attached to github
|
Now that we can generate pull requests in Studio, it'd be nice to see the list of open PRs against a given repo and select them to merge the PR. http://developer.github.com/v3/pulls/#merge-a-pull-request-merge-buttontrade We need to hook a menu extension to show the listing of open PRs and merge the PR when selected. (The user could optionally supply a commit message, but I think for a first cut we just send no commit message and they will likely generate a default)
| 8 |
train
|
TISTUD-5106
|
Alloy project: Add right-click menu items to navigate from XML to JS and TSS files
|
When a xml file in Alloy project is selected in the Project Explorer, we should provide right-click menu items to open the corresponding .js and .tss files. The same menu should also be available when right-clicking in the xml editor if it's from an Alloy project.
| 8 |
train
|
TISTUD-5107
|
Alloy project: Add right-click menu items to navigate from JS to XML and TSS files
|
When a js file in Alloy project is selected in the Project Explorer, we should provide right-click menu items to open the corresponding .xml and .tss files. The same menu should also be available when right-clicking in the JS editor if it's from an Alloy project.
| 5 |
train
|
TISTUD-5108
|
Alloy project: Add right-click menu items to navigate from TSS to XML and JS files
|
When a tss file in Alloy project is selected in the Project Explorer, we should provide right-click menu items to open the corresponding .xml and .js files. The same menu should also be available when right-clicking in the TSS editor if it's from an Alloy project.
| 5 |
train
|
TISTUD-5109
|
Silent failure when creating a Git pull request
|
I have a git project that is on "development" branch. It's not forked, and is linked directly to the 'development' origin. Do a right-click on the project and select Team -> Create Pull Request. At this point, nothing happens and we get this error in the log: {code} !ENTRY org.eclipse.ui 4 0 2013-07-15 16:20:08.110 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.e4.core.di.InjectionException: org.eclipse.core.commands.ExecutionException: Unable to get repository details from github API org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: org.eclipse.core.commands.ExecutionException: Unable to get repository details from github API com.aptana.git.ui.internal.actions.CreatePullRequestHandler.doExecute(CreatePullRequestHandler.java:118) com.aptana.git.ui.internal.actions.AbstractGitHandler.execute(AbstractGitHandler.java:108) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ... 40 more Caused by: org.eclipse.core.runtime.CoreException: Not Found com.aptana.git.internal.core.github.GithubAPI.get(GithubAPI.java:99) com.aptana.git.internal.core.github.GithubUser.getRepo(GithubUser.java:55) com.aptana.git.ui.internal.actions.CreatePullRequestHandler.doExecute(CreatePullRequestHandler.java:114) ... 48 more {code}
| 3 |
train
|
TISTUD-5110
|
NPE when launching the Studio after a fresh install
|
Launched an installed Studio for the first time on a Windows 7 VM and got an exception right at the start. {code} !ENTRY org.eclipse.core.jobs 4 2 2013-07-15 18:06:52.401 !MESSAGE An internal error occurred during: "Computing SDK Info...". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.core.internal.mobile.SDKInfoManager.getSDKInfo(SDKInfoManager.java:59) com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationHelper.getVersionInfo(MobileSDKConfigurationHelper.java:93) com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationProcessor.computeStatus(MobileSDKConfigurationProcessor.java:70) com.aptana.configurations.processor.AbstractConfigurationProcessor.getStatus(AbstractConfigurationProcessor.java:154) com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:127) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}
| 3 |
train
|
TISTUD-5112
|
Errors in the TailLog after deleting a deployed Node.ACS project
|
# Create Node.ACS Project named 'np'. # Deploy App. # Activate Tail Logs. # Delete project. The project is deleted. However, the Tail Log console remains open and an error appear every few seconds: {code} [ERROR] Server returned error. No app found {code}
| 5 |
train
|
TISTUD-5116
|
Create a 16x16 LiveView icon
|
In order to implement TISTUD-4817, we need a LiveView icon that will be displayed in the Project and App Explorer toolbar.
| 5 |
train
|
TISTUD-5139
|
Android SDK Path is misinterpreted
|
h3. Steps to Reproduce On OSX 10.6.8 (outdated, yes, but probably applies to more versions) With a fresh install, use the dashboard link to install the Android SDK. When it requests a path, enter ~/.android (or any path beginning with ~) Install as normal h3. Actual Result SDK is installed to /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/~/.android SDK directory is stored as the path entered, so Titanium Studio cannot find the appropriate SDKs without tracking down where the SDK Manager installed it and entering that directory in the preferences. h3. Expected Result SDK is installed to ~/.android (more specifically: /Users/[username]/.android or at least SDK is installed to /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/~/.android and the directory is set to the same so that Titanium Studio recognizes the installed files.
| 5 |
train
|
TISTUD-5121
|
Add a toggle button in App/Project Explorer toolbar to enable/disable LiveView for the next run
|
This will be a global state to control if the next applicable launch (run on iOS/Android and simulator/device at the moment) will be run with LiveView on or off. Initially the button is toggled off, and the workflow is as followed: 1. User toggles the button on and do Run > iOS Simulator, the simulator will be run with liveview; 2. User toggles it off, do Run > Android Emulator, the emulator will be run without liveview; 3. To run the iOS simulator without liveview, user will just do Run > iOS Simulator again since now the setting is off.
| 5 |
train
|
TISTUD-5122
|
LiveView: Remove the launch configuration contribution
|
Remove the contribution to applicable launch configurations for enabling LiveView as we will be using the global toggle to control the setting. For existing launch configs, we should ignore the liveview attribute and also use the global setting.
| 3 |
train
|
TISTUD-5127
|
Support optional comma in tss file
|
When a .tss file contains certain grammars, Titanium Studio cannot parse for display in the Outline View, and the entire Outline View goes blank. Examples: Example 1) {noformat}"#topShadow[platform=android]":{ left: 0, right: 0, top: 0, height: 4, backgroundColor: "yellow", backgroundGradient: { type: 'linear', startPoint: {x:0,y:0}, endPoint:{x:0,y:"100%"}, colors: [{color: "#919191", offset:0},{color: "#919191", offset:0.125},{color:"#f2f2f2",offset:1}] } },{noformat} The {{colors}} line contains an array of objects. This is a legitimate style in a tss file, but its presence causes the whole outline view to go blank. Example 2) {noformat}"#OrderListSection[platform=ios]":{ text:"List Settings", top:10, },{noformat} The {{top:10,}} has an extra comma in it. This isn't necessarily a correct grammar, but a .tss will compile with it in place. However, it breaks the Outline View for the entire page. I use the Outline View quite heavily when working with tss files, it's hard to go without a working tss. Example 2 has an acceptable workaround, but Example 1 does not.
| 2 |
train
|
TISTUD-5131
|
Studio: Web Preview is not compatible with UNC paths
|
*Problem* The Web Server Preview is not compatible with UNC paths. *Log* {code} '\\server\folder\Documents\Dropbox\Titanium_Studio_Workspace\Project' CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. Titanium Command-Line Interface, CLI version 3.1.1, Titanium SDK version 3.1.1.GA [ERROR] : Invalid project directory "." Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved. {code}
| 8 |
train
|
TISTUD-5132
|
Studio: Update out-dated tiapp.xml files in project templates
|
The {{tiapp.xml}} files in the Studio project templates are out-dated. They still contain the deprecated top-level iOS elements and the {{<iphone />}} section instead of the new {{<ios />}}. Since these templates are the starting point for both beginners and advanced devs, I think they should always reflect the latest best practice.
| 5 |
train
|
TISTUD-5151
|
Errors occurred while refreshing git index ( importing KitchenSink from Samples)
|
Test Steps: 1.Launch Appcelerator Studio. 2.Samples > KitchenSink > import . 3. No sepearate GIT activity has been done , still I received 'Errors occurred while refreshing git index' Screenshot and logs attached. {code} !ENTRY com.aptana.git.core 4 1 2013-07-25 15:14:10.168 !MESSAGE Errors occurred while refreshing git index !SUBENTRY 1 com.aptana.git.core 4 0 2013-07-25 15:14:10.169 !MESSAGE Unable to run update-index: fatal: Not a git repository (or any parent up to mount point /Volumes/MacintoshHD) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). !ENTRY com.appcelerator.titanium.360.soasta 1 0 2013-07-25 15:14:38.559 !MESSAGE (Build 3.1.2.201307232148) [INFO] Running MATT for Kitchen Sink. Utility returned Will configure following JS File: /Volumes/MacintoshHD/Users/deepti.pandey/Documents/Appcelerator_Studio_Workspace_beta_1/Kitchen Sink/Resources/app.js Mobile App Object "KitchenSink_9104c364-f669-47ce-93b1-a5a15fa91ee0_iOS" representing your Application "KitchenSink" has been created in CloudTest Repository. Mobile App Object "KitchenSink_9104c364-f669-47ce-93b1-a5a15fa91ee0_Android" representing your Application "KitchenSink" has been created in CloudTest Repository. !ENTRY com.appcelerator.titanium.mobile 1 0 2013-07-25 15:14:38.563 !MESSAGE (Build 3.1.2.201307232148) [INFO] Module check for com.appcelerator.apm: version: true platform: true !ENTRY com.appcelerator.titanium.mobile 1 0 2013-07-25 15:14:38.565 !MESSAGE (Build 3.1.2.201307232148) [INFO] Module check for com.appcelerator.apm: version: true platform: true {code}
| 5 |
train
|
TISTUD-5154
|
SWTException when closing tiapp editor
|
I was closing editors and saw error dialogs popped up. Here is the exception in the log: {code} !ENTRY org.eclipse.ui 4 4 2013-07-25 15:30:20.018 !MESSAGE An internal error has occurred. !STACK 0 org.eclipse.swt.SWTException: Widget is disposed org.eclipse.swt.SWT.error(SWT.java:4397) org.eclipse.swt.SWT.error(SWT.java:4312) org.eclipse.swt.SWT.error(SWT.java:4283) org.eclipse.swt.widgets.Widget.error(Widget.java:783) org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573) org.eclipse.swt.widgets.Control.getBounds(Control.java:1606) org.eclipse.ui.internal.forms.MessageManager.update(MessageManager.java:504) org.eclipse.ui.internal.forms.MessageManager.updateForm(MessageManager.java:499) org.eclipse.ui.internal.forms.MessageManager.removeMessage(MessageManager.java:374) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.validateSection(TiAppDeployTargetsSection.java:529) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.updateDependentSections(TiAppSDKSection.java:300) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.access$0(TiAppSDKSection.java:294) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection$5.runInUIThread(TiAppSDKSection.java:283) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code}
| 3 |
train
|
TISTUD-5157
|
Add Alloy navigation shortcuts to the Project Explorer
|
The implementation of TISTUD-3295 did not include the Alloy navigation support through the Project Explorer. The implementation only added editor menu action to navigate between the Alloy element, and this enhancement is to add a similar menu item to relevant Alloy files in the project explorer. We should be able to navigate between the js, tss and xml files in all directions.
| 5 |
train
|
TISTUD-5158
|
Run Configurations dialog: create new iOS Application Installer config failed with exception
|
Opened Run Configurations dialog and double-click on Appcelerator iOS Application Installer to create a new launch config, but none was created. Checked the log and saw the following exception: {code} !ENTRY org.eclipse.ui 4 0 2013-07-25 17:46:58.544 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)) org.eclipse.swt.SWT.error(SWT.java:4397) org.eclipse.swt.SWT.error(SWT.java:4312) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?) org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1681) com.appcelerator.titanium.ios.ui.launching.packaging.SimpleiPhonePackagingComponent$9.run(SimpleiPhonePackagingComponent.java:550) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 23 more {code}
| 3 |
train
|
TISTUD-5160
|
Appcelerator Studio is asking for updates every single time user opens studio
|
User opens Appcelerator Studio, then studio prompt to install updates, the user click on the update button, studio download all the updates and says that they has been installed, but the log file is showing errors (attached log file), also , the user try to login on acs with his account (cli -> acs login) and throws an error: RangeError: Maximum call stack size exceeded. If we create a new user and enable that user into another dummy organization, and we log in with those credentials on a different machine we can log in with no issues, then if the user with his machine try to login, shows the same error and if we go to the other machine (the one that before has been logged in successfully) shows that error message now.
| 8 |
train
|
TISTUD-5166
|
Appcelerator Studio: stuck on the splash screen when restart
|
h5. Problem description After hard restarting the system (for everything was completely frozen), Appcelerator Studio was not starting anymore. After launching it and choosing an existing workspace, the login screen didn't appear - only the red Studio Splashscreen was being displayed. Here is the console details: {code} fcasaliMBP:MacOS fcasali$ ./AppceleratorStudio !SESSION 2013-07-26 14:38:39.771 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_51 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/fcasali/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/fcasali/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.resources 2 10035 2013-07-26 14:39:27.612 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.core.net 1 0 2013-07-26 14:39:39.868 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences ^CException in thread "Thread-1" org.eclipse.swt.SWTException: Invalid thread access org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.SWT.error(SWT.java:4168) org.eclipse.swt.widgets.Widget.error(Widget.java:774) org.eclipse.swt.widgets.Widget.dispose(Widget.java:661) org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:611) org.eclipse.swt.widgets.Shell.windowWillClose(Shell.java:2262) org.eclipse.swt.widgets.Display.windowProc(Display.java:5445) org.eclipse.equinox.launcher.JNIBridge._takedown_splash(Native Method) org.eclipse.equinox.launcher.JNIBridge.takeDownSplash(JNIBridge.java:167) org.eclipse.equinox.launcher.Main.takeDownSplash(Main.java:2050) org.eclipse.equinox.launcher.Main$SplashHandler.run(Main.java:111) {code} h5. Workaround After deleting the ~/.eclipse folder, Studio would start correctly.
| 8 |
train
|
TISTUD-5168
|
Proxy settings not used when downloading APM module from AWS S3 bucket
|
Customer is behind proxy server, but checking for updates shows APM 1.0.4, when he downloads, errors out. See attached for logs
| 5 |
train
|
TISTUD-5169
|
Proxy settings do not apply when re-launching into AppC Studio with cached login
|
Customer logs into AppC Studio behind proxy (with beta 3.1.3 build that had proxy fix) and it works first time, then on subsequent close/open, reports that Studio is in Offline mode. Have to logout, then launch and login for it to show as online. See attached logs
| 5 |
train
|
TISTUD-5182
|
Need an alert dialog to warn the developers about the new Window Architecture on Android
|
Need some way (eg. alert dialog) to warn the developers about the new window behavior on Android. Starting from 3.2.0, all the windows are heavyweight on Android (TIMOB-13796).
| 5 |
train
|
TISTUD-5195
|
When importing an existing Titanium Mobile project, refer to the tiapp.xml instead of the manifest file
|
Currently, Studio requires a Titanium Mobile project to contain a "manifest" file in order to import the project. This file only exists to facilitate importing projects into Studio. In Titanium SDK 3.2.0, the "manifest" file will be removed (TIMOB-13166). Studio will need to read the tiapp.xml to get whatever info it needs.
| 5 |
train
|
TISTUD-5199
|
BlackBerry project validation: message has incorrect grammar
|
BlackBerry project validation: message has incorrect grammar. See screenshot. Test Steps: 1. Create Titanium BlackBerry project with project name containing invalid character. Result: Error message 'A BlackBerry project cannot any of these characters in its name:'. Expected Result: Error message 'A BlackBerry project cannot contain any of these characters in its name:'
| 2 |
train
|
TISTUD-5200
|
Allow create Alloy Application Templates using Rubles
|
Using rubles, one can create Titanium Mobile templates - however, this doesn't work when trying to create a template for an Alloy based project. Issues as I've noticed them are: * Alloy nature is not properly applied * Alloy plugin is not added to the tiapp.xml as expected * Alloy assets are not generated appropriately (lack of call to CLI 'alloy new') Multiple work arounds have been tried such as including all required files and the .project file so that the nature is preserved, but this doesn't work as those files are apparently overwritten For more details see the email thread attached
| 8 |
train
|
TISTUD-5205
|
Localization properties set in Alloy .tss files are marked as an error
|
h5. Problem description Specifying a String localized in the Styles .tss, Appclerator Studio marks it as an error (unexpected token "L"). 1. Create a new Alloy project 2. Edit views/index.xml {code} <Alloy> <Window> <!-- Localization via XML attribute --> <Label class="header">via XML attribute:</Label> <Label text="L('hello_world')"/> <!-- Localization via TSS --> <Label class="header">via TSS:</Label> <Label id="viaTss"/> <!-- Localization via JS code in controller --> <Label class="header">via controller:</Label> <Label id="viaController"/> </Window> </Alloy> {code} 3. Edit styles/styles.tss {code} 'Label': { top: '5dp', color: '#222', font: { fontSize: '42dp', fontWeight: 'bold' }, height: Ti.UI.SIZE, width: Ti.UI.SIZE, textAlign: 'center' } '.header': { top: '30dp', color: '#a00', font: { fontSize: '24dp', fontWeight: 'normal' } } '#index': { backgroundColor: '#fff', fullscreen: false, exitOnClose: true, layout: 'vertical' } '#viaTss': { text: L('hello_world') } {code} 4. Edit controllers/index.js {code} $.viaController.text = L('hello_world'); $.index.open(); {code} Result: Studio is showing two error markings in the styles/index.tss - the first on the first line ('Cannot recover from the syntax error'), the second on the localization line (unexpected token "L").
| 8 |
train
|
TISTUD-5206
|
Appcelerator Studio Dashboard - Learn >> Developer Reference >> Titanium Studio Guide link navigates to a proper page but the page displays a 'Page not found' message
|
Dashboard: Learn: Documentation Links Test steps: 1. Click the Titanium Studio Guide link for Developer Reference and observe the page that it navigates to. Actual Result: The link navigates to a page which has a 'Page not found' message on it. Please refer the attached screen shot for more clarification.
| 3 |
train
|
TISTUD-5223
|
Field Service: In description of Field Service Sample in Dashboard we should state to read the ReadMe to configure
|
There are users and partners that have not been able to get the Field Service App to work. It turns out many of them is because they didn't look at the ReadMe. I believe that if we state it in the description, then more users will actually look at the readme and this should increase the overall success of the Field Service App. "Please read the ReadMe file in order to complete the configuration of the application." Or something like that.
| 2 |
train
|
TISTUD-5225
|
Liveview: iOS: Second launch of LV enabled project in iOS simulator fails
|
h5. Description: When launching a Liveview enabled simulator session, it works as expected. When you attempt to rebuild the project again, the simulator fails to launch and this error presented: {code} [INFO] : Finished building the application in 1s 97ms [LiveView] Closing file/event server process id: 34204 [INFO] : Running application in iOS Simulator [LiveView] version 0.1.32 [LiveView] File Server Started on Port 8324 [LiveView] Event Server Started on Port 8323 [INFO] : Launching application in iOS Simulator [INFO] : Focusing the iOS Simulator [ERROR] : Failed to focus the iPhone Simulator window [ERROR] : /Users/emerriman/Library/Application Support/Titanium/mobilesdk/osx/3.1.2.v20130807171139/iphone/iphone_sim_activate.scpt: execution error: iPhone Simulator got an error: Connection is invalid. (-609) [INFO] : Application has exited from iOS Simulator [INFO] : Project built successfully in 3s 58ms {code} This occurs with both the iPad and iPhone simulators. The order of the console output may vary slightly. Also note that the behavior prevents the user from turning off LV and then launching on the first attempt. The first launch with LV off after encountering this error will fail with the same console output. The second launch with LV off seems to work fine. This may be a clue as to root cause. h5. Steps to reproduce: 1) Create a default classic project in Studio 2) Enable Liveview and launch in the simulator 3) Make some edits if you wish 4) Relaunch the simulator - leaving liveview enabled h5. Result: Project fails to launch correctly in the simulator. Turning off LV and launching will also fail, but will work on the next and subsequent launches with LV off. h5. Expected Result: Project launches as expected and allows real-time editing h5. Notes I monitored the processes here, and it may be expected but subsequent launches of Liveview were killing the existing node PID and launching a new one. Process list: Normal non-LV launch: {code} 39786 1.6 0.8 3104976 67028 ?? S 3:07PM 0:02.09 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify {code} Normal LV enabled launch {code} 39891 1.5 0.2 3063424 19808 ?? Ss 3:08PM 0:13.73 /usr/local/bin/node /Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.0.0.1375925433/node_modules/liveview/bin/liveview-server start --project-dir /Users/emerriman/Documents/anewworkspace/Yuntastic --platform ios --no-colors 39873 1.8 1.1 3120336 96244 ?? S 3:08PM 0:16.16 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify --liveview --deploy-type development {code} Failed LV enabled launch: {code} 39978 1.6 0.2 3053660 17976 ?? Ss 3:24PM 0:00.29 /usr/local/bin/node /Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.0.0.1375925433/node_modules/liveview/bin/liveview-server start --project-dir /Users/emerriman/Documents/anewworkspace/Yuntastic --platform ios --no-colors 39959 0.0 0.7 3102660 58440 ?? S 3:24PM 0:02.03 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify --liveview --deploy-type development {code} First launch non LV failure: No processes Second launch non LV: {code} 40678 2.5 0.7 3102660 58916 ?? S 3:26PM 0:01.99 node /usr/local/bin/titanium --no-colors --no-prompt build --platform ipad --sdk 3.1.2.v20130807171139 --log-level trace --target simulator --ios-version 6.1 --device-family ipad --skip-js-minify {code}
| 8 |
train
|
TISTUD-5224
|
Studio: Toast says android build succeeded when build failed
|
If a build fails, TiStudio still says it succeeded, console says (correctly) build failed. See screenshot. The problem is if the build callback receives an error, it says there was an error, but doesn't exit with a non-zero exit code.
| 5 |
train
|
TISTUD-5235
|
Node.ACS - tiapp.xml property always points to locally running endpoint of node.ACS web service
|
Repro steps: 1. Create a new node.ACs proj 2. Publish it to Node.ACS cloud 3. Create a new timob project 4. Import Node.ACS bindings 5. Select the project created in step 1 6. Replace the value of following property in your timob project <property name="acs-service-baseurl-<NodeACSWebserviceProjectName>">http://localhost:64075</property> From localhost:64075 to the actual published URL. 7. Save tiapp.xml 8. Build the timob project for iphone simulator 9. Once the iphone simulator comes up 10. Open the tiapp.xml and you will see that the value of the above property is changed back to localhost:64075
| 5 |
train
|
TISTUD-5236
|
Preferences > Studio > Updates: hitting Apply after switching a stream has no effects on the selected update site
|
1. Open Preferences > Studio > Updates page; 2. Switch from "Stable Release" to Release Candidate Build"; 3. Hit Apply; 4. Switch to Preferences > Install/Update > Available Software Sites. Expected result: the new list of update sites are generated, and the RC one is selected. Actual result: no change occurs to the list of update sites. The update sites do get updated correctly after OK is clicked.
| 3 |
train
|
TISTUD-5241
|
Allow user to configure for iOS development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for iOS. It will have an Advanced Settings section to customize the Xcode location. By default, the location should be filled with "/Applications/Xcode.app", and the text next to the checkbox should say "Not Configured". This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if Xcode is already installed in the default location to update the UI state accordingly.
| 8 |
train
|
TISTUD-5242
|
Allow user to configure for Android development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for Android, and it should contain an expandable "Advanced Settings" section where user could customize the following: # Set a path for the root Android SDK location. It will be filled initially by a default path, e.g. ~/Android. # Choose what Android SDK versions to install. The list should contain from the minimum version (currently 2.3.3) we support to the maximum version available. By default, the minimum version and the maximum available version are selected. The text next to the checkbox should say "Not Configured" by default. This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if Android SDK is installed in the default location to update the UI state accordingly.
| 13 |
train
|
TISTUD-5243
|
Allow user to configure for BlackBerry development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for BlackBerry, and it should contain an expandable "Advanced Settings" section where user could set a path for the root BlackBerry NDK location. It will be filled initially by a default path, e.g. ~/BlackBerry. The text next to the platform checkbox should say "Not Configured" by default. This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if BlackBerry is already installed in the default location to update the UI state accordingly.
| 8 |
train
|
TISTUD-5246
|
Allow user to configure for Tizen development in the platform configuration wizard
|
In the platform configuration wizard, there should be an entry for Tizen, and it should contain an expandable "Advanced Settings" section where user could set a path for the root Tizen SDK location. It will be filled initially by a default path, e.g. ~/Tizen. The text next to the checkbox should say "Not Configured" by default. This ticket just covers the UI aspect. There will be separate tickets for dealing with the actual configuration once "Configure" is clicked as well as auto-detecting if Tizen is already installed in the default location to update the UI state accordingly.
| 8 |
train
|
TISTUD-5247
|
Unable to import projects from dashboard
|
- Open Dashboard -> Develop. - Importing any project does not show up import wizard. The error log indicates exception indicating no handler for the import action. !MESSAGE (Build 3.2.0.201308102436) [ERROR] There is no handler to execute for command com.aptana.samples.ui.commands.import !STACK 0 org.eclipse.core.commands.NotHandledException: There is no handler to execute for command com.aptana.samples.ui.commands.import org.eclipse.core.commands.Command.executeWithChecks(Command.java:512) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) com.aptana.portal.ui.dispatch.actionControllers.CommandHandlerActionController.execute(CommandHandlerActionController.java:95) com.aptana.samples.ui.portal.actionController.SamplesActionController.importSample(SamplesActionController.java:141) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:103) com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:142) com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:126) com.aptana.portal.ui.internal.BrowserWrapper$2.function(BrowserWrapper.java:51) org.eclipse.swt.browser.WebKit.callJava(WebKit.java:1778) org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:406) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648)
| 5 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.