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,911 |
TISTUD-6023
|
01/14/2014 21:51:26
|
Support running on Windows device
|
Add support for running on Windows device.
| 0 |
1,912 |
TISTUD-6024
|
01/14/2014 21:52:38
|
Support running on Windows simulator
|
Add support for running on Windows simulator.
| 0 |
1,913 |
TISTUD-6029
|
01/15/2014 19:47:35
|
Automatically set the active SDK for CLI to the latest stable version after update
|
Currently when Studio updates SDK to the latest stable version, running "ti sdk" from command line still shows the previous SDK as selected. This could cause issues since we don't pass in "--sdk <version>" for all the commands, and when it's not, CLI will use the one set as active and could return inaccurate information. So we should call "ti sdk select <version>" after update. For custom SDK installed from a URL, we should not update the selected SDK since it may not be stable and fully tested.
| 3 |
1,914 |
TISTUD-6031
|
01/16/2014 01:31:23
|
Windows: SplashScreen links lead to incorrect URL
|
h5.Description The SplashScreen on Windows shows 3 links. 'Learn More', 'Forgot Password' and 'Proxy Setup' 'Learn More' and 'Forgot Password' will link to the users default search engine and search 'DelegateExecute'. Users cannot use the Forgot Password button as it links to the wrong address. h5.Steps To Reproduce 1. Open Appcelerator Studio 2. Click the links on the SplashScreen h5.Expected Result Links lead to the correct web addresses h5.Actual Result Links lead to default search engine and searches 'DelegateExecute'
| 5 |
1,915 |
TISTUD-6037
|
01/17/2014 00:55:00
|
After SDK update fails, cannot cancel the process
|
After encountering an error during the SDK configuration process (screenshot4.png) I was unable to cancel the studio process "Installing/Updating a Mobile SDK" (screenshot1.png). Even after waiting 5 minutes it did not cancel and needed a Studio restart to resolve. I spoke to [~mxia] about the issue and the reason you need to cancel the studio process is because after the update error in the SDK tool occurs, the only option you have is to "hide". Previously that button would have been "configure". Attached the studio and diagnostic logs. Let me know if I need to clarify. {code} !ENTRY com.appcelerator.titanium.update.core 4 2 2014-01-15 14:30:51.435 !MESSAGE Problems occurred when invoking code from plug-in: "com.appcelerator.titanium.update.core". !STACK 0 java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.remove(LinkedHashMap.java:364) at com.appcelerator.titanium.update.core.TitaniumSDKUpdater.fireUpdateCompletedEvent(TitaniumSDKUpdater.java:795) at com.appcelerator.titanium.update.core.TitaniumSDKUpdater.access$1(TitaniumSDKUpdater.java:787) at com.appcelerator.titanium.update.core.TitaniumSDKUpdater$5.done(TitaniumSDKUpdater.java:875) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) !ENTRY org.eclipse.ui 4 0 2014-01-15 15:07:34.376 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.eclipse.jface.fieldassist.ControlDecoration.addControlListeners(ControlDecoration.java:602) at org.eclipse.jface.fieldassist.ControlDecoration.<init>(ControlDecoration.java:476) at org.eclipse.jface.fieldassist.ControlDecoration.<init>(ControlDecoration.java:428) at com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite.setError(BasePlatformConfigurationComposite.java:949) at com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite.validate(BasePlatformConfigurationComposite.java:924) at com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite$1.widgetSelected(BasePlatformConfigurationComposite.java:228) 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.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:50) at com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:79) at com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationProcessor$1.run(MobileSDKConfigurationProcessor.java:126) {code}
| 5 |
1,916 |
TISTUD-6038
|
01/17/2014 01:00:08
|
Android: Keystore - When creating a new Android keystore, there should be a drop down list to select the different signature algorithm
|
*Details:* Depending on which Java version is being used by the machine, there should be a drop down list as to which signature algorithm should be used when creating an Android keystore. For instance, Java 1.6.X only ships with SHA1withRSA, so there should be a signature drop down list that has only SHA1withRSA selected. Java 1.7.X ships both SHA1withRSA and SHA256withRSA, so there should be a signature drop down list for both signatures. By having this option when creating an Android keystore, a user can: 1. Package their app to a non-KitKat (< 4.4) device using only the SHA1withRSA signature 2. Package their app to a KitKat device with either SHA1withRSA *or* SHA256withRSA.
| 5 |
1,917 |
TISTUD-6077
|
01/22/2014 00:59:35
|
Remove the requirement of Android 2.3.3 when running MobileWeb app on simulator
|
The MobileWeb app fails to run on (Android) simulator, if the Android SDK 2.3.3 is not installed on the machine. Currently when Studio run app on simulator, it still runs using python script 'builder.py' command and that enforces to have Android SDK 2.3.3 installed.
| 5 |
1,918 |
TISTUD-6076
|
01/22/2014 01:55:00
|
Old version liveview path in paths.hooks can cause failure in running mobile apps
|
Steps to reproduce : # Run a mobile app using liveview using 3.2.0 of Studio, SDK and CLI. # Update CLI, SDK and Studio to RC 3.2.1 # Run a mobile app without liveview The paths.hooks in 'titanium config' still references to old version of the liveview (pre-3.2.1.). Since there are breaking changes of CLI in handling hooks, the old version of liveview path can lead to failure of CLI to run mobile apps on simulator or device.
| 3 |
1,919 |
TISTUD-6084
|
01/22/2014 12:35:32
|
Studio: Can't tell keystores apart when path is reasonably long
|
When you have multiple keystores, and they are all a similar path (like, say, a common "dev" folder inside a user directory), you cannot easily tell them apart. See screenshot. Expected: You should see more of the path, or perhaps just the keystore file name Workaround: Select each keystore in your list, and then move the cursor to the end of the string to see which keystore is which. Labor intensive if you work on more than a couple apps.
| 5 |
1,920 |
TISTUD-6086
|
01/23/2014 18:10:29
|
When behind a proxy, Appcelerator Studio would login in offline mode on restart
|
Workaround is to logout, restart and enter proxy settings/login again. If user enters in proxy settings and logs in to splash screen that will work. But when we try to log them in automatically in the background on restart, it will report being offline and the proxy settings don't get applied properly. On the failed login restart we see the following in the logs: {code} !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.141 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.141 !MESSAGE System property http.proxyHost is not set but should be webproxy.wlb2.nam.nsroot.net. !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.150 !MESSAGE System property http.proxyPort is not set but should be 8080. !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.151 !MESSAGE System property https.proxyPort is not set but should be 0. !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.153 !MESSAGE System property https.proxyPort is not set but should be 0. {code} Which shows that preferences contain valid values, but system properties do not.
| 8 |
1,921 |
TISTUD-6094
|
01/27/2014 00:27:14
|
Studio : Cannot switch provision profiles
|
I am on Titanium Studio, build: 3.2.0.201312191547. I have several run profiles setup. However, it does not seem like I can switch provision profiles and have that new provision profiles save to the run configuration. I read a ticket on the Q&A today where somebody posted the same question yesterday. It seems like a possible bug.
| 5 |
1,922 |
TISTUD-6102
|
01/28/2014 21:40:22
|
Links in Node.ACS release notes displayed in Studio update dialog 404
|
Steps: 1. Remove your Node.ACS install from your system 2. Open Studio and check for Studio updates 3. Click on any link in the Node.ACS change log Results The links lead to wrong locations
| 5 |
1,923 |
TISTUD-6101
|
01/28/2014 21:46:55
|
Widget-is-disposed exception in the log when installing Android via platform config wizard
|
Saw the exception below after performing following steps: 1. Clear Android SDK from Studio preference and Titanium CLI; 2. Open Dashboard and click on the link in Get Started > Configure Native SDKs > Android SDK section to open the platform wizard; 3. Specify a directory and install Android SDK; 4. Click Hide to close the wizard; 5. Click Run in Background to close the progress bar; 6. Wait until the job finishes. {code} !ENTRY org.eclipse.ui 4 0 2014-01-28 13:31:57.222 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) 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) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Widget.error(Widget.java:783) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573) at org.eclipse.swt.widgets.ProgressBar.getSelection(ProgressBar.java:183) at org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:139) at com.appcelerator.titanium.ui.wizard.ProgressDistributor$5.run(ProgressDistributor.java:118) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 23 more {code}
| 3 |
1,924 |
TISTUD-6109
|
01/29/2014 02:27:58
|
<cmd>+F find doesn't highlight the search bar when multiple editor windows are open in side-by-side tabs
|
When editing code in Titanium studio 3.2, pressing <cmd>+F is supposed to open the 'find/replace' dialog and highlight the finding search term. This does not work correctly when multiple editor windows are open side-by-side in a studio instance. ie. 1/ Open multiple source files in studio 2/ Drag one of these windows to the side so that you have split window editing 3/ Press <cmd>+F to open the find/replace control 4/ Type your search term = the cursor is not correctly focused in the find/replace control and your search term is incorrectly entered into the source code you are editing instead of in the find/replace control This is really, really annoying if you are editing in split windows. Split windows are pretty much the major reason I choose to use studio instead of sublime.
| 5 |
1,925 |
TISTUD-6105
|
01/29/2014 08:19:30
|
Navigate the event handlers into the controller code from View
|
The View files in Alloy can contain event handlers such as onClick, onFocus events. The functions referenced as the event handlers are 'mostly' defined in the corresponding controller code. Since Studio has knowledge of the controller code, it should allow to navigate the event handler functions to the controller code (similar to the F3 or method definition navigation in JDT Eclipse).
| 8 |
1,926 |
TISTUD-6106
|
01/29/2014 08:21:16
|
Navigate the class types to the Style code from View
|
The View files in Alloy can contain class types for each UI element. The types referenced in the View are definitely defined in the corresponding Style code. Since Studio has knowledge of the Style code, it should allow to navigate the class type to the Style code (similar to the F3 or method definition navigation in JDT Eclipse).
| 8 |
1,927 |
TISTUD-6108
|
01/29/2014 20:57:24
|
Add a debug scope to output the result from "ti info -t <platform>" calls
|
Sometimes in addition to know the exact "ti info" commands Studio calls, we also want to know the output at the time it is executed, since the output may change when running the same command later on. This ticket is to introduce a new scope to show the output in Studio log when enabled.
| 3 |
1,928 |
TISTUD-6113
|
01/30/2014 00:27:11
|
Appcelerator Studio: JS library causes Studio to hang during index
|
h6.Issue description Including the attached file (source here -> https://github.com/mbostock/d3/blob/master/d3.min.js) in an Appcelerator Studio project, causes the "building workspace, indexing" task to hang indefinitely. The task cannot be cancelled and requires studio to be forcibly shut down (top menu bar gets stuck and no possible action can be done) E.G. BuildingWorkspace_Indexing.jpg h6.Actual behaviour Appcelerator Studio to hang and require a force quit if a specific file is added to a project. h6.Steps to reproduce Attach JS library attached and monitor indexing progress (E.G. BuildingWorkspace_Indexing_IDE.jpg). h6.Additional information Once, library is included the workaround is to store this library in a folder that is marked derived in studio, so it does not index. {quote} (1) In Project Explorer view, click on the drop-down arrow on the upper-right corner and select Customize View...; (2) In the Filters tab, uncheck Titanium Resources Folder and click OK; (3) The "Resources" folder should now appear under the alloy project; (4) Right-click on the Resources folder and select Properties; (5) Make the "Derived" attribute checked and click OK. {quote}
| 8 |
1,929 |
TISTUD-6116
|
01/30/2014 02:19:52
|
Alloy: Show description for the content assist types in View file
|
Studio does not show any description (in the tooltip) for the types shown in the content assist in the Alloy View file. Though Studio is able to display description in the tooltip for the types in the controller file, it does not show any tooltip in the View file.
| 8 |
1,930 |
TISTUD-6123
|
02/01/2014 03:44:01
|
Alloy: add New > Alloy View for creating a new view
|
If a user creates a view file, the very next thing would be to create a corresponding style file and controller file. Studio should provide a way those corresponding files through menu items or context menus. So, the corresponding files should be created with the same name of View file, but under styles and controllers folders.
| 5 |
1,931 |
TISTUD-6124
|
02/01/2014 05:47:28
|
Alloy: add New > Alloy Style for creating a new style
|
Alloy provides a command "alloy generate style <name>" to generate a style file. We should surface the capability in Studio with a New > Alloy Style menu. It should prompt user for the style name and run the command.
| 5 |
1,932 |
TISTUD-6125
|
02/03/2014 05:47:37
|
Alloy: add hover info for property names in Alloy .tss file
|
h5. Improvement description Alloy projects .tss files should also present the hover info like for .js files. When passing the mouse over a .tss style, information should be displayed as a popup like for objects in the .js files.
| 8 |
1,933 |
TISTUD-6129
|
02/03/2014 23:34:39
|
Alloy: add hover info for attribute names in Alloy .xml file
|
h5. Improvement description Alloy projects .xml files should also present the hover info like for .js files. When passing the mouse over an .xml element, information should be displayed as a popup like for objects in the .js files.
| 8 |
1,934 |
TISTUD-6137
|
02/05/2014 23:26:38
|
Alloy: when creating 'Alloy Model' from the contextual menu, 'properties' adapter option is missing
|
h5. Problem description As explained here: http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Sync_Adapters_and_Migrations-section-36739597_AlloySyncAdaptersandMigrations-Ready-MadeSyncAdapters when creating a new Alloy Model, also the 'properties' adapter should be supported. Creating it through Studio, only sql and localStorage options are displayed. Not a regression, also present in Studio 3.2.0.GA Running: {code} alloy info adapters {code} from Terminal returns the correct output: {code} { "properties": { "description": "Local persistence adapter that uses Ti.App.Properties storage", "platforms": [ "android", "ios", "mobileweb", "tizen", "blackberry" ] }, "sql": { "description": "Local persistence adapter that uses SQLite storage", "platforms": [ "android", "ios", "blackberry" ] }, "localStorage": { "description": "Local persistence adapter that uses HTML5 localStorage API", "platforms": [ "mobileweb", "tizen" ] } } {code} h5. Additional notes localStorage adapter should probably be deprecated in favor of just properties (and sql). See https://jira.appcelerator.org/browse/ALOY-950
| 5 |
1,935 |
TISTUD-6142
|
02/07/2014 01:26:35
|
Appcelerator Studio: Implement a method for distribution of FSA that avoids pulling from active development repo
|
h5. Description: When changes are made to the FSA in the active development git repo, these changes are immediately available to anyone importing the sample. This does not allow changes to be evaluated prior to release. h5. Steps to reproduce: Please note: it is not recommended you follow these steps. They are provided for completeness 1) Edit the FSA app code and push change to git 2) Open appcelerator studio and import FSA from sample pane 3) Evaluate the area of changed code from step 1 h5. Result: The imported sample contains the code change h5. Expected Result: New versions of FSA are released in a controlled manner
| 3 |
1,936 |
TISTUD-6144
|
02/10/2014 07:01:48
|
TSS syntax error when there is an additional comma at the end
|
If the TSS file contains an additional comma delimiter at the end of the last attribute, then Studio shows error as "cannot recover from syntax error" at the beginning of the TSS file and shows another error at the end "unexpected end-of-file token", though Alloy compiler can successfully compile and run the TSS file. Create a simple tss file with contents such as- "#class":{ }, "#attribute": { }, Studio shows false compilation errors though they might not be the real errors while running the app.
| 5 |
1,937 |
TISTUD-6148
|
02/10/2014 17:39:20
|
Add App Explorer to the Window > Show View menu
|
App Explorer is no longer shown by default. However, I find it to be the better view than Project Explorer: - you're far less likely to launch the wrong project using App Explorer than Project Explorer - The view is simpler, because you don't see a ton of unrelated files/projects (which is important for developers with many projects) - App Explorer includes a "search-whole-project" text field, which is handy My preference is to have App Explorer returned to being the default file tree view. In lieu of that, having it conveniently accessible on the Window > Show View menu will suffice.
| 2 |
1,938 |
TISTUD-6151
|
02/10/2014 21:40:20
|
Release Notes: Studio release notes are missing images
|
*Details:* If you update to the latest Studio builds, then the release notes are missing some images. *Steps to reproduce:* 1. Make sure to have Studio 3.2.0 2. Update to Studio 3.2.1 on stable stream 3. Check release notes *Actual:* Release notes are missing images (see attachment). *Expected:* Release notes should not have missing images.
| 3 |
1,939 |
TISTUD-6153
|
02/10/2014 22:49:26
|
Release Note: Cannot open Jira links in release notes
|
*Details:* If you update to the latest Studio builds and try to click on the Jira links in the release notes, Jira links will not open. *We were able to reproduce this on Mac and Ubuntu. Not on Windows.* To workaround this, you can right-click on the link and copy the link. *Steps to reproduce:* 1. Make sure to have Studio 3.2.0 2. Update to Studio 3.2.1 on stable stream 3. Check release notes 4. Click on Jira links *Actual:* Jira links will not open *Expected:* Should be able to launch links in an external browser or internal browser.
| 5 |
1,940 |
TISTUD-6155
|
02/11/2014 00:31:45
|
AppC Studio 3.2.1 not compatable with Java 1.7
|
During an enterprise on-boarding a customer had a 100% clean environment, IE no pre-requisites installed. We used the AppceleratorStudio.exe to install the Java that Studio recommended (1.7). Studio would not launch and would throw an error. We restarted the computer and the same result happened. [~pinnamuri] joined the call to help fix the problem. We were able to get studio to launch only after uninstalling Java 1.7 and installing Java 1.6 32-bit.
| 5 |
1,941 |
TISTUD-6162
|
02/12/2014 03:20:34
|
Titanium Studio shows psuedoproperty assignments as errors
|
The pseudo property assignment operator 'get' as shown here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/get isn't parsed correctly by Studio, so shows up as an error, even though the script is valid. Running the attached script ('node error.js') returns the following: someResult1 someResult2 operatorResult1 as expected, but as you can see in the screen shot, the line 'get operator1' is flagged as an error. This parse error also cascades, causing Studio to have difficulty parsing the next few lines. Attachments: 1. error.tiff <-- a screen shot of error.js in studio showing the red x for parse error 2. error.js a simple script that demonstrates the issue 3. should.js a more complex script that shows the issue (at line 1210) and the parse issues cascading down the script.
| 8 |
1,942 |
TISTUD-6174
|
02/13/2014 12:00:55
|
Unable to format any TSS file in Titanium Studio
|
When I want to format my TSS file, I've got an error : "Unable to format. See error log for details". I see log and I've : !ENTRY com.appcelerator.titanium.editor.tss 4 0 2014-02-13 12:57:32.822 !MESSAGE (Build 3.2.1.201402041146) [ERROR] Formatter error: startOffset > endOffset !STACK 0 java.lang.IllegalArgumentException: Formatter error: startOffset > endOffset .....
| 3 |
1,943 |
TISTUD-6179
|
02/19/2014 22:18:14
|
AppC Studio title bar says "Titanium Studio Dashboard"
|
Steps: 1. Open Dashboard in Appc Studio and look at title bar. Results: Title bar text is set to "Studio - Titanium Studio Dashboard - Appcelerator Studio". Expected: Not sure, but maybe just "Appcelerator Studio - Dashboard".
| 3 |
1,944 |
TISTUD-6181
|
02/21/2014 01:06:31
|
Studio: Typing "label1" at certain pace causes autofill with "Ti.API.log('info',})"
|
h5. Description: At certain typing rates, typing "label1" results in the text being replaced with "Ti.API.log('info',})". Not only is this not ideal, the text throws an error in the editor which is "Syntax error: Unexpected token "}" h5. Steps to reproduce: 1) Open any js file in studio. 2) Type "label1" h5. Result: If your typing rate was conducive, the text will be replaced. If not, it will work as expected. h5. Expected Result: "label1" Text remains as entered h5. Notes: Typing fast or slow may not produce the issue. Michael mentioned that: This problem happens due to that there is only one proposal for the case of label1 when '1' is typed, and the proposal is a code snippet. To turn the behavior off, there is the option in Preferences > Studio > Content Assist > "Insert single proposals automatically."
| 8 |
1,945 |
TISTUD-6182
|
02/21/2014 18:51:07
|
Allow to open Run configuration dialog directly with Cmd+Click on launch shortcut
|
In Eclipse, we can directly open the run configuration for a shortcut directly with Cmd+Click on that shortcut. It avoids a long effort to open a generic run configurations dialog and search for the specific launch shortcut. After Studio introduced the global launch shortcuts, we loose the capability of directly opening the specific launch configuration.
| 8 |
1,946 |
TISTUD-6183
|
02/22/2014 00:54:32
|
Intermittent NPE while opening TiApp editor
|
At times when the state of the project or services is corrupted, TiApp fails to open and throws NPE : java.lang.NullPointerException at com.appcelerator.titanium360.internal.core.ServiceInstance.getState(ServiceInstance.java:49) at com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.create360ServiceList(Titanium360TiappContributor.java:633) at com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.createSectionContents(Titanium360TiappContributor.java:538) at com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.createControls(Titanium360TiappContributor.java:393) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection.createControls(TiAppCloudSection.java:68) at com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.initialize(AbstractTiAppSection.java:71) at com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.<init>(AbstractTiAppSection.java:55) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection.<init>(TiAppCloudSection.java:47) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppFormPage.createFormContent(TiAppFormPage.java:123) at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:471) at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1083) at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:603)
| 3 |
1,947 |
TISTUD-6187
|
02/24/2014 22:11:27
|
Allow navigation between Alloy files under a hierarchical structure
|
A suggestion from a user in TISTUD-3295: I have one suggestion that can cover one use case that is being missed by this feature. In our app/controller folder, we have a hierarchical structure that organizes our controllers in a logical fashion. For instance, we have the following: app/ app/assets/ app/controllers/ app/controllers/file1.js app/controllers/file2.js app/controllers/file3.js app/controllers/file4.js app/controllers/file5.js app/controllers/templates/another_controller1.js app/controllers/templates/another_controller2.js app/controllers/templates/another_controller3.js app/controllers/templates/another_controller4.js lib/ lib/... ... The same controller structure is mirrored for the styles and the views. Now, when you open a controller, style or view that is not directly sitting in the folders app/controllers/, app/styles/ or app/views/, then you will not be able to use the new simplified navigation to open the other related files. The option will be greyed out. It would be nice to have that use case supported.
| 8 |
1,948 |
TISTUD-6190
|
02/24/2014 23:42:53
|
Alloy debugging does not suspend at expected line numbers with default preferences
|
With the default JavaScript debugging preferences ON especially with Suspend of errors and Suspend on debugger keyword, the debugger does not suspend at the breakpoints. They do suspend at random lines, but never stop the breakpoints. If both of these preferences are set to OFF, then the thread suspends and breakpoints are hit as expected.
| 8 |
1,949 |
TISTUD-6191
|
02/25/2014 07:56:59
|
Linux Ti Studio ask to update on every startup, failing each time
|
After startup, Studio on linux show me a list of updates. I'm forced to install them to close the dialog, type in admin password and then Studio fails saying like Node udpate can be done only on Win/Mac Npm not found Npm not found Npm not found Really annoying.. Regards
| 8 |
1,950 |
TISTUD-6195
|
02/26/2014 18:33:53
|
Syntax Highlight and Autocomplete Fail
|
While I'm working in a project the syntax hightlight and autocompletion stops working. {code} !ENTRY com.aptana.editor.js.formatter 4 0 2014-02-26 15:23:35.838 !MESSAGE (Build 3.2.1.201402041146) [ERROR] com.aptana.formatter.epl/debug Cannot recover from the syntax error !STACK 0 beaver.Parser$Exception: Cannot recover from the syntax error at beaver.Parser.recoverFromError(Parser.java:601) at com.aptana.js.core.parsing.JSParser.recoverFromError(JSParser.java:489) at beaver.Parser.parse(Parser.java:498) at beaver.Parser.parse(Parser.java:439) at com.aptana.js.core.parsing.JSParser.parse(JSParser.java:374) at com.aptana.js.core.parsing.JSParser.parse(JSParser.java:331) at com.aptana.parsing.ParsingEngine.noCacheParse(ParsingEngine.java:424) at com.aptana.parsing.ParsingEngine.parse(ParsingEngine.java:229) at com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:230) at com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:217) at com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:200) at com.aptana.editor.js.formatter.JSFormatter.format(JSFormatter.java:245) at com.aptana.formatter.ScriptFormattingStrategy.doFormat(ScriptFormattingStrategy.java:185) at com.aptana.formatter.ScriptFormattingStrategy$1.run(ScriptFormattingStrategy.java:115) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.aptana.formatter.ScriptFormattingStrategy.format(ScriptFormattingStrategy.java:111) at org.eclipse.jface.text.formatter.MultiPassContentFormatter.formatMaster(MultiPassContentFormatter.java:193) at org.eclipse.jface.text.formatter.MultiPassContentFormatter.format(MultiPassContentFormatter.java:142) at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:979) at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1507) at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:128) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:126) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:285) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:504) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:555) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:376) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:322) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:84) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1080) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4165) 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.sendKeyEvent(Widget.java:1503) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1499) at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:496) at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5648) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:594) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5558) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) 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:3648) 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) {code} Steps to Reproduce: 1. Create a new Mobile Application (Alloy). 2. Create a new Controller. 3. Paste the following code in the controller file. {code} var args = arguments[0] || {}; var requestComments = function(){ var xhr = Ti.Network.createHTTPClient({ onload: function() { Ti.API.info('Comments: '+this.responseText); var comentarios = JSON.parse(this.responseText); for (var idx in comentarios) { var row = Ti.UI.createTableViewRow({ backgroundColor: '#fff', width: Ti.UI.SIZE, height: Ti.UI.SIZE, }); var rowLabel = Ti.UI.createLabel({ text: comentarios[idx].message, font: { fontSize: 10, fontFamily: 'Helvetica Neue', }, color: '#0e0e0e', left: 5, top: 5, }); row.add(rowLabel); $.detailTView.appendRow(row); } var rowMore = Ti.UI.createTableViewRow({ backgroundColor: '#fff', font: { fontSize: 12, }, height: 30, }); var rowMoreTxt = Ti.UI.createLabel({ title: 'Ver Mas', tintColor: '#34aadc', }); $.detailTView.appendRow(rowMore); }, }); xhr.open('POST',Alloy.Globals.serverRequest); xhr.send({ request: 'comments', postId: args.id }); }; function onClickCancel() { $.detailWin.close(); } function sendComment() { alert('Comment Sent.'); } $.detailWin.addEventListener('open', function(){ var secretRow = Ti.UI.createTableViewRow({ width: Ti.UI.SIZE, height: Ti.UI.SIZE, backgroundColor: '#fff', layout: 'vertical', }); var secretText = Ti.UI.createLabel({ text: args.message, top: 10, left: 10, right: 10, font: { fontSize: 12, fontFamily: 'Arial', }, }); var spaceView = Ti.UI.createView({ height: 10, width: Ti.UI.FILL, }); secretRow.add(secretText); secretRow.add(spaceView); secretRow.selectionStyle = Ti.UI.iPhone.TableViewCellSelectionStyle.NONE; $.detailTView.appendRow(secretRow); $.detailTView.appendRow(Ti.UI.createTableViewRow({backgroundColor: '#fff', height: 35, selectionStyle: Ti.UI.iPhone.TableViewCellSelectionStyle.NONE})); $.detailTView.appendRow(Ti.UI.createTableViewRow({height:10, selectionStyle: Ti.UI.iPhone.TableViewCellSelectionStyle.NONE})); requestComments(); }); var backBtn = Ti.UI.createImageView({ width: 14, height: 21, image: 'icon_left_white.png', }); backBtn.addEventListener('click',function(){ $.tabGroupDetail.close(); }); $.detailWin.leftNavButton = backBtn; $.comentario.keyboardToolbar = $.footerComment; /* $.comentario.addEventListener('change', function() { $.autoHeightLabel.text = $.comentario.value; $.comentario.height = $.autoHeightLabel.height; $.footerComment.height = $.autoHeightLabel.height; }); */ {code} Thanks
| 5 |
1,951 |
TISTUD-6194
|
02/26/2014 18:38:57
|
The global launch toolbar should show tooltip if the shortcuts are disabled
|
If the launch global toolbar is disabled for a valid project, then it should show tooltip with the cause (such as no platforms selected in TiApp or fails to list the emulators/devices for the selected platforms). The tooltip should help to fix the problem with the Titanium project in case if there is a version mismatch or any errors with the project configuration.
| 5 |
1,952 |
TISTUD-6196
|
02/27/2014 08:07:10
|
No option to Publish Android application for Appcelerator Studio on Windows
|
When you install the latest version of Appcelerator Studio on Windows with the Android SDK properly installed, there is no option to publish your applications to the Google Play Store. We have done a couple of workshops with customers that are running Studio on Windows and were trying to illustrate the process of publishing android applications. Of course, this option is not available. Let me know if you need more details. I have uploaded the sample project setup for Android and there is no option available.
| 5 |
1,953 |
TISTUD-6199
|
02/28/2014 19:02:17
|
Alloy : Allow to create event handler from View file
|
If a user includes event handlers for the a UI element in the View file, there is no way to directly create the event handler in the controller file. Currently, they have to manually switch back to controller file and then create the event handler. It would be easy if the user is able to Cmd/Ctrl + Click the event handler method referenced in the View file to directly create the method in the controller file.
| 8 |
1,954 |
TISTUD-6200
|
02/28/2014 19:04:00
|
Alloy: Create a style section for 'id' from the View file
|
If a user defines style element such as 'id' for the a UI element in the View file, there is no way to let user define the style element block directly in the style file. Currently, they have to manually switch back to style file and then create the style data block using the Id defined for the UI element. It would be easy for the user for a quick fix kind of mechanism, where they can press something similar to Cmd/Ctrl + 1 on the id value, and then create the style block in the tss file.
| 8 |
1,955 |
TISTUD-6201
|
02/28/2014 19:10:30
|
Alloy: Show warning if the event handler referenced in the View file is not defined
|
If a user includes event handler for the a UI element in the View file, currently there is no indication that the event handler is a valid method. The user will only get to know about undefined handler while launching the app on device/simulator. Since, we already have the indexed methods from the javascript files of the project, we should be able to figure out the referenced method is valid and then, show a warning, if it not defined.
| 8 |
1,956 |
TISTUD-6209
|
03/04/2014 16:52:33
|
Navigate the ID types to the Style code from View
|
The View files in Alloy can contain ID types for each UI element. The types referenced in the View are probably defined in the corresponding Style file. Since Studio has knowledge of the Style code, it should allow to navigate the ID type to the Style code (similar to the F3 or method definition navigation in JDT Eclipse).
| 8 |
1,957 |
TISTUD-6213
|
03/04/2014 21:17:20
|
Dashboard: BlackBerry native SDK is not configured
|
When Studio Installed on a clean machine, Configure Native SDK for BlackBerry fails. h5.To reproduce 1.Studio Dashboard>Get Started>Configure Native SDKs> BlackBerry SDK h5.Actual result Configuration fails (log attached) h5.Work around 1.Download and Install Momentics from the following link: https://developer.blackberry.com/native/downloads/ 2.Close all popups that appear until on the main screen. 3.Help --> Update API Levels... 4.Open the "Gold" Tab and install the latest stable SDK
| 8 |
1,958 |
TISTUD-6217
|
03/05/2014 19:54:59
|
Android: Default emulator is not created on windows after android tools update to rev.22.6
|
h4. NOTE : This issue will affect a user if he is doing a clean install. The studio will not create a default emulator for him. h5.Description: 1. On windows, delete all available avd from the avd manager. 2. Run appcelerator studio. 3. Select an app & click refresh devices. h5. Actual Results: 1. A default avd does not get created by studio. This issue started after updating the android SDk tools & android sdk build tools to rev.22.6 & 19.0.3 respectively. We tested the same scenario on an windows machine which was not updated & everything worked fine as expected. NOTE: We saw that studio runs the command to create an avd in studio logs ,but somehow it fails I guess. If the same command is run manually it creates the emulator fine. h5. Expected Results: 1. Default avd should get created if none exist.
| 5 |
1,959 |
TISTUD-6234
|
03/07/2014 18:44:27
|
Combine the core and unit tests builds for studio3
|
I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build. Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds).
| 5 |
1,960 |
TISTUD-6235
|
03/07/2014 18:44:45
|
Combine the core and unit tests builds for titanium
|
I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build. Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds).
| 5 |
1,961 |
TISTUD-6236
|
03/07/2014 18:44:54
|
Combine the core and unit tests builds for appcelerator
|
I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build. Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds).
| 5 |
1,962 |
TISTUD-6237
|
03/07/2014 19:02:05
|
Error on project creation & Alloy is not an option when creating a new project
|
When the customer tries to create a new project, the Alloy option is missing from the template selection area. If they close the window and try again, they will have the option to select Alloy. When trying to create a project, they are greeted with a creation error. We were unable to repro this in house, but the customer can consistently show it on webEx. Steps to reproduce: 1. Open Studio 2. go to File->New->Mobile App Project 3. Witness that there is no option to select Alloy 4. Close the "Create project" window 5. Again, go to File->New->Mobile App Project 6. Witness that you can now select Alloy 7. Try to create an Alloy project 8. Witness the creation error in the screenshot Additional Notes: The customer was having trouble enabling services. We discovered that they were trying to log into dashboard with the wrong password and thought Studio may have the wrong password. We logged him out and back in with the "new", correct password. He then started getting these problems on project creation.
| 3 |
1,963 |
TISTUD-6239
|
03/07/2014 20:40:35
|
Alloy: Create a style section for 'class' from the View file
|
If a user defines style element such as 'class' for the a UI element in the View file, there is no way to let user define the style element block directly in the style file. Currently, they have to manually switch back to style file and then create the style data block using the 'class' element defined for the UI element. It would be easy for the user for a quick fix kind of mechanism, where they can press something similar to Cmd/Ctrl + 1 on the class element value, and then create the style block in the tss file.
| 8 |
1,964 |
TISTUD-6240
|
03/07/2014 20:50:22
|
Create a Index reader to index all style elements defined in tss file
|
Studio has to index all the style element sections defined in the TSS file. Currently Studio has only knowledge about the list of the id/class(es) referenced from the View file. However, it has to parse and store the information of all the id/class sections for each TSS file in order to show any annotations of unused elements. The indexer should differentiate the Id and class elements, and might need to store the style elements correspondingly.
| 8 |
1,965 |
TISTUD-6241
|
03/07/2014 20:52:30
|
Alloy: Create a Styles validator to validate the undefined style elements in View file
|
After all the style elements are indexed, then the View file need to validate the missing style elements of 'class' and show any annotations if the class definitions are missing the corresponding style file or in the global file.
| 8 |
1,966 |
TISTUD-6246
|
03/10/2014 22:56:17
|
iOS:Faild to import projects from Studio Samples, if iOS SDK Home is not specified in Studio Preferences
|
h5.To reproduce 1. Set Xcode path, using the Terminal {code} sudo xcode-select -switch /Applications/Xcode.app {code} 2. In Finder move Xcode to another location 3. Import Kitchen Sink from Studio Samples h5.Actual result Error, cloning git repo (screenshot) h5. Expected result No error, importing the project
| 5 |
1,967 |
TISTUD-6250
|
03/12/2014 05:35:03
|
Studio 3.2.3 and 3.3.0 does not show new iOS simulators in Run configurations
|
h3. Issue While debugging into the new issues reported by the user (TISTUD-5614), I have run into an issue with Studio, that it incorrectly use the obsolete cache to detect iOS simulators and SDKs. Due to this, Studio always displays simulator version such as 7.0.3, even though 7.1 or 6.1 are available on the machine. h3. Workaround To workaround the issue, delete the files under <titanium_studio_workspace>/.metadata/.plugins/com.appcelerator.titanium.core/* and then, restart Studio. It should refresh the iOS info and show all the valid simulators.
| 5 |
1,968 |
TISTUD-6258
|
03/12/2014 19:26:56
|
Studio: Theme resets with every update
|
h3. Steps to Reproduce update studio h3. Actual Result theme changes back to white background h3. Expected Result remember my theme
| 5 |
1,969 |
TISTUD-6256
|
03/18/2014 06:06:19
|
Android: ti.info not showing Android Ndk version
|
Missing Android Ndk version while setting the path from Studio. Steps to Reproduce: 1. Download Android ndk and Open Appcelerator Studio. 2. Open Prefrences>Studio>Platform>Android. Set the android ndk path and apply and save. 3. Now launch terminal and run "ti.info" Actual Result: Android Ndk version is missing.However it shows the Android Ndk Path Expected Result: Should get correct Android Ndk version. But if we set the android ndk path from Terminal using command ti.config android.ndkPath pathtoandroidndk After this run "ti.info" We get the Ndk Version
| 5 |
1,970 |
TISTUD-6261
|
03/20/2014 20:54:38
|
Fails to launch iOS app after XCode update
|
h3. Issue After upgrading the XCode SDK to 7.1 from 7.0.3, and if the User launches the titanium app on iOS simulator, then the launch fails with the error 'invalid SDK version 7.0.3'. While launch the app, Studio does not validate SDK version stored in the launch configuration and it launches the app with the same old SDK version that is persisted in the launch configuration. h3. Workaround To workaround the issue, open the launch configuration and set the SDK to 7.1 and then relaunch it.
| 5 |
1,971 |
TISTUD-6265
|
03/21/2014 17:36:50
|
NPM executable should not need to coexist with node executable folder on Mac for recognizing npm
|
On Mac, the npm executable should co-exist in the node executable folder for Studio to find npm executable. If they are installed through any other means that would cause node and npm executables under different directories, then Studio fails to recognize npm executable, though it is accessible on terminal.
| 5 |
1,972 |
TISTUD-6279
|
03/24/2014 16:44:56
|
iOS Developer Certificate encoding issue
|
h2. Description of the problem When the Developer Certificate name contains an international character (e.g. ä), Studio is unable to build. The error shown says that the "--developer-name" is invalid, and the character is replaced by ??
| 5 |
1,973 |
TISTUD-6270
|
03/25/2014 01:00:48
|
Create feature, builder, and Jenkins job for publishing AirWatch integration plugin(s)
|
Add the corresponding feature, builder, and Jenkins job to publish AirWatch integration plugin(s) to an external update site so it could be installed on top of Studio 3.2.0. The feature will eventually be folded into Appcelerator Studio.
| 5 |
1,974 |
TISTUD-6271
|
03/25/2014 01:08:12
|
Implement publishing to Airwatch App Store using their API
|
Using the API in https://wiki.appcelerator.org/display/tools/AirWatch+Integration to publish the package to Airwatch app store. The information needed could be retrieved from the project itself and the publishing wizard.
| 8 |
1,975 |
TISTUD-6272
|
03/25/2014 01:09:38
|
Add a publish provider for publishing to AirWatch App Store
|
Using the API in https://wiki.appcelerator.org/display/tools/AirWatch+Integration to add a publish provider for Airwatch. Could reference our Nukona and Testflight implementations.
| 5 |
1,976 |
TISTUD-6273
|
03/25/2014 01:10:08
|
Make AirWatch plugins installable only onto Appcelerator Studio
|
AirWatch integration will be eventually rolled into Appcelerator Studio 3.3.0. In the mean time, it should be installable only to Appcelerator Studio, not Titanium Studio.
| 2 |
1,977 |
TISTUD-6275
|
03/26/2014 22:57:45
|
NPE during startup while initializing iOS config wizard
|
java.lang.NullPointerException at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.<init>(IOSSDKConfigurer.java:45) at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.<init>(IOSSDKConfigurer.java:39) at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer.doCreateComposite(IOSSDKConfigurer.java:141) at com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.createConfigurationContents(BaseMobilePlatformConfigurer.java:122) at com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createConfigurationContents(PlatformsListConfigurationPage.java:181) at com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createControl(PlatformsListConfigurationPage.java:155)
| 3 |
1,978 |
TISTUD-6276
|
03/27/2014 21:00:25
|
Alloy: Debug on Simulator fails to hit break point
|
Debug breakpoint is never reached when using the latest TiStudio. h3.Steps to reproduce * Create a default Alloy using lastest TiSDK (3.2.3.v20140327115429) with all services enabled. * Place a breakpoint inside index.js doclick() function. * Run the app in Debug mode. * Click on "Hello World" h3.Expected Result * BreakPoint should be hit and no alert should be shown. h3. Actual Result * Alert is shown without hitting the breakpoint. h3.This is a regression : h3.Does not happen with Appc Studio :: 3.2.1.201402061120
| 5 |
1,979 |
TISTUD-6280
|
03/31/2014 20:51:06
|
Studio not able to package after the keystore file, alias and password are entered in wizard
|
h3. Issue When customer is trying to package the app trough Studio and after including the keystore file, password and alias they receive an error in console regarding and N reference not being recognized as a command. During a webex call we try using different SDK throwing the same error, when building from CLI the package build process runs without any problems. h3. Console Log {code} 'N' is not recognized as an internal or external command {code} h3. Attached Files We are including the Studio log and the Studio Diagnostics
| 5 |
1,980 |
TISTUD-6283
|
03/31/2014 21:56:05
|
Some properties aren't getting flagged as deprecated properly
|
Look at parent screenshot #1, 'contentURL' property is not flagged as deprecated, but should be.
| 5 |
1,981 |
TISTUD-6290
|
04/01/2014 17:40:40
|
Fix the download button on the new aptana.github.io download page
|
The download button on the new setup is busted. It probably does some form submission to a server to get the download URL, when we should be able to bake that logic into client-side Javascript to get the correct URLs.
| 5 |
1,982 |
TISTUD-6291
|
04/01/2014 21:45:02
|
Windows: Studio installer does not recognize the installed JDK
|
Even though a JDK version is already installed on the Windows machine (could it be 64-bit or IBM Java or Java 8), at times, Studio doesn't recognize the existing Java installation and tries to install it again. Since we are currently looking at the registry for finding Java installation path, if Java is not installed through standard means or a different variant of Java is installed (such as IBM Java, or a different arch), there is a chance that the registry is not updated with the expected values. In that case, Studio will fail to recognize the installed Java version. We need to fall back looking to PATH env variable for java/javac executable (as we are more keen to have JDK installation) if the registry lookup fail to return a valid Java executable.
| 8 |
1,983 |
TISTUD-6293
|
04/02/2014 01:10:51
|
The controller/style file is not opened automatically after applying quick fix
|
After the quick fix is applied to create a event listener, the corresponding Controller file should be opened and set the cursor in the new created event method. Similarly, the styles file should be opened after applying quick fix to create style ruleset for id/class. After recent refactoring changes, the files are not opened and the new methods are not immediately accessible to the user.
| 3 |
1,984 |
TISTUD-6294
|
04/02/2014 01:14:28
|
The problem markers in editor should disappear after applying quick fix
|
After the quick fix is applied either through quick fix context menu or Problems view, the problem markers disappear in the Problems view, but the marker annotations in the editor does not disappear. Currently we need to do a quick edit in the View file for the reconciler to be kicked back and only then the problem annotations disappear in the editor. After the quick fix is applied, either we need to get hold of the editor problem annotations and remove them, or trigger the reconciler on View file.
| 5 |
1,985 |
TISTUD-6295
|
04/02/2014 01:16:48
|
Improve the context menu UI of Alloy View quick fix proposals
|
The quick fix proposals context menu is a simple and pale option available in the context menu. There is no padding to the beginning of the quick fix proposals and also, it might look better if an icon is added to the proposal.
| 5 |
1,986 |
TISTUD-6296
|
04/02/2014 01:18:19
|
Apply multiple quick fixes together from Problems view
|
If there are multiple quick fixes available for the same category (such as creating style id ruleset) for a bunch of UI elements, then the user should be able to select all of the similar problems and apply quick fix by grouping them together.
| 5 |
1,987 |
TISTUD-6297
|
04/02/2014 01:20:40
|
TSS file does not recognize a selector if it is not trimmed
|
If there is a space between the selector (id/class) and colon ("#container' : {...}), then the TSS file does not recognize it as a selector and incorrectly considers it as a String constant. It has trim the space between the selector id and colon and always shows the selector syntax color.
| 3 |
1,988 |
TISTUD-6299
|
04/02/2014 17:54:59
|
Update CLI calls to old module create/build python scripts
|
Chris Barber is planning on rewriting the module create scripts to move away from the legacy python to the new titanium CLI. We'll need to update our code to call this new command to generate module projects now.
| 8 |
1,989 |
TISTUD-6302
|
04/03/2014 15:30:24
|
Breakpoints Never Hit within Appcelerator Studio
|
When using the Appcelerator Studio build 3.2.1 with the 3.2.2 GA SDK, and placing a breakpoint within the code, whenever using Debug mode, breakpoints are never triggered and entered within the studio environment. Prior to upgrading to the Appcelerator Studio platform, we had issues in the past with the Titanium IDE, which were resolved by placing breakpoints in the Resource files. Now, post upgraded to Appcelerator Studio, we can no longer hit any breakpoints within our code.
| 8 |
1,990 |
TISTUD-6304
|
04/04/2014 23:51:56
|
Studio: Preferences - Platforms - iOS: Refresh button does not work
|
h5. To reproduce 1. Open Studio> Preferences>Platforms>iOS 2. Change Xcode path, using CLI command {code} xcode-select --print-path sudo xcode-select -switch /path to a different Xcode version, if you happened to have it {code} 3. Click Refresh button in Studio> Preferences h5. Actual result No changes h5. Expected The user should see a new path, which was updated, using CLI. Run the command {code} ti info {code} to make sure the "new" Xcode is set as a default.
| 5 |
1,991 |
TISTUD-6306
|
04/08/2014 00:18:55
|
Multiple duplicate platform SDK entities are added
|
After the fix for TISTUD-6216, Studio has been repeatedly adding the SDK entities for iOS and Android. In the packaging wizard, choose the 'Select SDK version' and a numerous duplicate entities are shown for both Android and iOS. For Android and iOS, as we are loading the titanium info for every 30 secs, we are constantly adding the entities without resetting them.
| 5 |
1,992 |
TISTUD-6307
|
04/08/2014 01:28:14
|
Add diagnostic information to investigate the debugging issues
|
There are multiple reports that the breakpoints does not hit while debugging the Alloy apps. Currently, we have very limited information available to quickly investigate the underlying root cause of this problem. We might need to add additional diagnostic information such as - # The list of current breakpoints, before the debug session is initiated. # If the breakpoints are added after the debug session is initiated, then we need to log that info. # As the debugger tries to resolve the original source mappings, we need to log whether we were unable to resolve the original sources.
| 5 |
1,993 |
TISTUD-6310
|
04/09/2014 05:51:59
|
Titanium Studio: Commenting shortcut returns # instead of //
|
h3. Steps to Reproduce Command + / h3. Actual Result # ... [2014-04-09 00:49:01] An error occurred while building environment variables for the 'editor' context property in the 'Comment Line / Selection' command (/Applications/Titanium Studio/configuration/org.eclipse.osgi/bundles/2838/1/.cp/bundles/source.ruble/commands/toggle_comment.rb): (NameError) cannot load Java class com.aptana.editor.common.AbstractThemeableEditor h3. Expected Result //
| 5 |
1,994 |
TISTUD-6309
|
04/09/2014 19:17:33
|
Appcelerator studio becomes sluggish & consumes a lot of cpu after update to 3.2.3.201404031900
|
h5.Description: 1. Update your current 3.2.3 studio to the latest 3.2.3 studio i.e 3.2.3.201404031900. 2. Run appcelerator studio. 3. Use it for sometime. h5.Actual Result: 1. Appcelerator studio is sluggish & consumes lot of cpu (more than 100%) & very frustrating to use with lot of freezes & delays. h5.Expected Results: 1. Appcelerator studio should not be sluggish & run smoothly.
| 8 |
1,995 |
TISTUD-6314
|
04/11/2014 00:29:04
|
iOS: Packaging - Cannot package for Adhoc or iTunes store
|
*Details:* Cannot package for Adhoc or iTunes store. Latest AppcStudio Beta build is passing "--deploy-type" "production" when packaging for Adhoc or iTunes Store e.g. {code} "/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "--no-banner" "build" "--platform" "ios" "--sdk" "3.2.3.v20140403105720" "--deploy-type" "production" "--log-level" "trace" "--project-dir" "/Users/tester/Documents/Appcelerator_Studio_Workspace/Xcode511" "--distribution-name" "Michael Asher (WY35J6ST95)" "--ios-version" "7.1" "--keychain" "" "--pp-uuid" "95B8E578-1273-4D3A-93B4-0607CFE8CFEC" "--target" "dist-appstore" {code} However, AppcStudio GA (3.2.1.201402061120) is passing "--build-type" "production" when packaging for Adhoc or iTunes Store e.g. {code} "/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "--no-banner" "build" "--platform" "ios" "--sdk" "3.2.2.GA" "--build-type" "production" "--log-level" "trace" "--project-dir" "/Users/wluu/Documents/Appcelerator_Studio_Workspace/checkingMonkey" "--distribution-name" "Michael Asher (WY35J6ST95)" "--ios-version" "7.1" "--keychain" "" "--pp-uuid" "C2AF8ADC-F3DC-485D-ADAB-CAB2B9B5D2D3" "--target" "dist-adhoc" "--output-dir" "/Users/wluu/Desktop" "--skip-js-minify" {code} *Workaround:* From CLI, use "\-\-build\-type" "production" instead of "\-\-deploy\-type" "production" *Note:* 1. This is a regression from AppcStudio GA (3.2.1.201402061120) 2. This is not a blocker because of the workaround. *However,* this is a *critical* ticket because the workaround is not intuitive. 3. Using the latest AppcStudio build, you can still package an app for the *Android* store, *however*, AppcStudio is passing "--deploy-type" "production" as well: {code} "/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "--no-banner" "build" "--platform" "android" "--sdk" "3.2.3.v20140403105720" "--deploy-type" "production" "--log-level" "trace" "--project-dir" "/Users/tester/Documents/Appcelerator_Studio_Workspace/Xcode511" "--target" "dist-playstore" "--android-sdk" "/Users/tester/Library/android-sdk-macosx" "--output-dir" "/Users/tester/Desktop" "--api-level" "10" "--alias" "wluu" "--keystore" "/Users/tester/Desktop/package.keystore" "--store-password" "**********" "--key-password" "**********r" {code} *Steps to reproduce:* 1. Create a default Classic or Alloy app 2. Package app for Adhoc or iTunes Store *Actual:* The following error appears in the console view: {code} [ERROR] : Invalid "--deploy-type" value "production" Accepted values: test development For help, run: titanium help build {code} *Expected:* You should be able to package your app for Adhoc or iTunes Store without any workarounds.
| 5 |
1,996 |
TISTUD-6315
|
04/11/2014 00:40:02
|
Breakpoints don't work after running profiler
|
h3. Description If you set break points in your app then run in debug mode then switch to Performance Profiler and then back to debugging, the break points are all turned off and cannot be turned back on. h3. Reproduction # Create a simple app # Add breakpoints # Run the app in Debug mode and confirm they work # Run the app in Profile mode # Re-run the app in Debug mode Result: Breakpoints are all disabled and cannot be enabled h3. Workaround # Restart Studio
| 5 |
1,997 |
TISTUD-6316
|
04/11/2014 01:18:49
|
Auto complete doesn't work on new project and workspace until clean all projects
|
h3.Description Auto complete does not work in Appcelerator Studio 3.2.1 with a brand new project and a brand new workspace. h3.Reproduction Download the latest version of Studio (3.2.1.201402061120) and install Create a new workspace Create a new project Open the XML or TSS file and try to get Mobile Code Complete suggestions Result: No suggestions or non-titanium suggestions will be made Workaround: Project > Clean > Clean All Projects
| 8 |
1,998 |
TISTUD-6323
|
04/14/2014 19:55:47
|
Auto detect the genymotion executables path in preferences
|
CLI 3.3.0 now output the information about Genymotion in the 'ti info -t android' or 'ti info -t genymotion' command. As Studio queries for Android emulators/devices information, we might need to cache the genymotion information and the Android preferences can used the cached data to display the Genymotion executables.
| 8 |
1,999 |
TISTUD-6324
|
04/14/2014 21:42:06
|
Load and store new property constant values from JSCA in JS' model for properties
|
We need to be able to parse out the new property values from the JSCA in our parser that handles the file.
| 5 |
2,000 |
TISTUD-6326
|
04/14/2014 21:43:33
|
Add CA proposals for property values in TSS editor
|
Once the model/index stores the possible constant values for a given property we need to suggest CA proposals for those values when invoked in the right area of a TSS file.
| 8 |
2,001 |
TISTUD-6331
|
04/14/2014 23:52:30
|
iOS: Dashboard displays iOS as not installed
|
h5.Description When Studio is first opened, the dashboard displays iOS as not installed. Closing and reopening the dashboard then marks iOS as installed and set up. h5.Steps To Reproduce 1. Install the latest version of Studio 2. Install Xcode 3. Open Studio h5.Expected Result Studio should detect Xcode and display it on the dashboard as installed and set up. h5.Actual Result Dashboard does not detect Xcode on the first launch.
| 8 |
2,002 |
TISTUD-6336
|
04/16/2014 06:41:32
|
NPE after first launch of Studio
|
This is a regression. Test Steps: 1. Uninstall Xcode *or* move Xcode to a directory in which the CLI cannot pick up 2. Launch Studio with a new workspace 3. Wait untill Studio loads. Actual Result: NPE occurs. {code} !ENTRY org.eclipse.e4.ui.css.core 4 0 2014-04-16 10:13:06.457 !MESSAGE CSS property 'maximize-visible' has been deprecated: renamed as swt-maximize-visible !ENTRY org.eclipse.e4.ui.css.core 4 0 2014-04-16 10:13:06.458 !MESSAGE CSS property 'minimize-visible' has been deprecated: renamed as swt-minimize-visible !ENTRY org.eclipse.ui 4 4 2014-04-16 10:13:33.613 !MESSAGE An internal error has occurred. !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.defaultSDKPath(IOSSDKConfigurer.java:51) at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.createAdvancedSettingsComposite(IOSSDKConfigurer.java:59) at com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite.<init>(BasePlatformConfigurationComposite.java:322) at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.<init>(IOSSDKConfigurer.java:41) at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.<init>(IOSSDKConfigurer.java:39) at com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer.doCreateComposite(IOSSDKConfigurer.java:141) at com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.createConfigurationContents(BaseMobilePlatformConfigurer.java:122) at com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createConfigurationContents(PlatformsListConfigurationPage.java:181) at com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createControl(PlatformsListConfigurationPage.java:155) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:432) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) at com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:48) at com.appcelerator.titanium.ui.TitaniumUIPlugin$6.runInUIThread(TitaniumUIPlugin.java:425) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) 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:3976) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) 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:140) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) 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) {code}
| 3 |
2,003 |
TISTUD-6337
|
04/16/2014 11:21:07
|
Windows OS: Incorrect default path is set for Titanium SDK in Studio as well as in CLI
|
Test Steps: On a clean Windows 8 machine: 1. Install Appcelerator Studio 2. Accept and install all the appcelerator components. 3. Observe the default location for Titanium SDK set in Studio preferences. Actual Result: C:\ProgramData\Titanium is set in the default location for Titanium SDK in Studio preferences. But actual installation (appcelerator modules) happens at the location C:\Users\Global\AppData\Roaming\Titanium Expected Result: Default location for Titanium SDK should be: C:\Users\Global\AppData\Roaming\Titanium Note: CLI also shows the same default SDK location path: C:\ProgramData\Titanium
| 5 |
2,004 |
TISTUD-6338
|
04/16/2014 11:32:43
|
Android:Top Project Context shows Android Application Installer option instead of Android Devices when multiple android devices is attached
|
When multiple iOS Devices are attached, Project Context menu has option "iOS Devices" under which list of devices are shown. But for multiple android devices attached it shows "Android Application Installer" option instead of "Android Devices" Refer to screenshot attached.
| 3 |
2,005 |
TISTUD-6343
|
04/17/2014 11:00:47
|
Android Configuration gives error message on Platform Configuration Wizard
|
This is a regression. Configure Android SDK through Platform Configuration Wizard. Let the process complete. Actual Result: After the installation process is completed an error message is displayed on Platform Configuration Wizard. Please observe the attached screen shot for the error message.
| 8 |
2,006 |
TISTUD-6352
|
04/22/2014 00:41:38
|
Titanium SDK 3.3.0 results in application configuration Error
|
When Titanium SDK build 3.3.0 installed altogether with 3.2.3 Library/Application Support/Titanium/mobilesdk/osx it results in the configuration error (no description). h5. To reproduce: 1. Using Studio, create the default project and check tiapp.xml Overview h5. Actual result: No description. However, the project can be installed on device and ran. Note: the app should be started manually {code} [TRACE] : ** BUILD SUCCEEDED ** [DEBUG] : Waiting for device logs to sync [INFO] : Installing app on device: iphone 5s [INFO] : App successfully installed on device: iphone 5s [INFO] : Project built successfully in 18s 135ms Please manually launch the application or press CTRL-C to quit {code} h5. To compare tiapp.xml {code} <sdk-version>3.2.3.v20140418101718</sdk-version> <description>not specified</description> {code} {code} <sdk-version>3.3.0.v20140418162516</sdk-version> <description/> {code}
| 3 |
2,007 |
TISTUD-6358
|
04/23/2014 19:41:08
|
Remove Tizen from the dashboard
|
Although Tizen platform is not indicated as a deployment target, it set to false in tiapp.xml {code} <target device="tizen">false</target> {code} and the Studio log returns {code} !MESSAGE (Build 3.3.0.201404221437) [ERROR] com.appcelerator.titanium.core/debug/dashboard Unknown SDK tizen {code} Note: The command, ran from studio {code} Process: "/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "--no-banner" "create" "--platforms" "android,blackberry,mobileweb,ios" "--type" "app" "--id" "kd.f" "--sdk" "3.3.0.v20140418162516" "--workspace-dir" "/Users/oromero/Documents/Appcelerator_Workspace3" "--name" "jdkf" "--verbose" "--force" Working directory: {code}
| 3 |
2,008 |
TISTUD-6386
|
04/28/2014 21:45:52
|
Set up signing for master/release windows installers, fire off builds to get signed
|
I need to port over the manual signing to happen for master/release windows installer builds (because they're not yet on Advanced Installer). I also need to fire off a build on each, so that the full artifacts are signed properly now that we renewed the certs.
| 5 |
2,009 |
TISTUD-6389
|
04/29/2014 18:58:34
|
Android: Remove Android SDK version drop-down list from Package dialog
|
The Package for Android App Store dialog has a drop-down list from which you select an Android API version. It is labeled to suggest that this will determine the minimum version of Android on which your app will run. However, that is determined in your tiapp.xml with the minSdkVersion tag. Best practices for Android specify that you should use the latest API tools available, setting compatibility targets with your tiapp.xml. For this reason, as of version 3.2, the CLI uses the newest version of the Android SDK installed. I suggest that the SDK version drop down list be removed from the Package dialog.
| 5 |
2,010 |
TISTUD-6395
|
05/01/2014 18:22:52
|
Copy Advanced installer projects and set up for "online" installer
|
We have an Advanced installer project file for each of Aptana Studio, TitaniumStudio and Appcelerator Studio. We need to copy each of those and then modify them in Advanced Installer to set them up to create a "thin" installer that separates the MSI from the EXE. This will also involve modifying the ant build script to add a target to build the thin installer version.
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.