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
|
|---|---|---|---|---|---|
911 |
TISTUD-2919
|
11/30/2012 19:29:54
|
Console/build log needs to indicate which Titanium CLI is being called
|
Steps To Reproduce: 1. Build an application with CLI enabled Actual: Can't tell whether CLI was used Expected: To be able to log whether CLI is enable or disabled
| 5 |
912 |
TISTUD-2920
|
11/30/2012 21:56:32
|
TiApp Editor with invalid sdk value opens in dirty state with no notification
|
Steps: 1. Open a tiapp.xml with invalid sdk value (open tiapp.xml in text editor and change version to an invalid one. Open in tiapp.xml editor) Expected results: 1. The editor should have error/warning about the invalid sdk version, or update to the latest sdk value and open a message dialog stating the sdk version was changed to a valid version Actual results: There are warnings displayed for a split second, then the warnings disappears and the editor is in dirty state
| 5 |
913 |
TISTUD-2922
|
11/30/2012 23:51:56
|
MobileWeb Run Configuration: displayed selected browser does not refresh immediately after installed browser search
|
When a MobileWeb run config is opened, and the browser list is updated after searching for installed browsers, 'Default Browser' is always displayed as selected in the run config browser list. Selecting another browser does not change the display. The issue goes away if the run config is reopened. Steps to Reproduce: 1. Open MobileWeb Run Config. 2. Browser Drop-Down List > Search Installed Browsers, and select/recognize all browsers. 3. Select a browser in the run config drop-down list. Actual Result: After a browser is selected, 'Default Browser' always appears as the selected item. Reopening the run config fixes the issue. Expected Result: Browser list refreshes correctly after search for installed browsers is first run.
| 5 |
914 |
TISTUD-2925
|
12/01/2012 13:18:52
|
Alloy: alloy.js plugin hook showing "read-only" JavaScript error
|
When creating a new alloy project, I'm seeing an error about a variable being "read-only" This is important as we warn people before running an application if it has errors in it. # Create a new Alloy project # Note the error on alloy.js I appear to only have our JS Syntax Validator turned on
| 5 |
915 |
TISTUD-2926
|
12/01/2012 17:57:15
|
On a very large jsca file, Studio crashes with out-of-memory and 'Java heap space' error
|
This is a regression bug as it doesn't happen in 2.1.2 Steps to Reproduce: 1.Launch latest studio. 2.Create a project . Package ios ,android and web modules in that project. 3.Debug that project in emulator. Launch debugger multiple times for multiple projects. Also a I have added a long file onehundredsixtythousand.jsca (found on Barcelona: Appcelerator/QE/TestApplications/Content Assit/onehundredsixtythousand.jsca)in that project and debugged it. Actual Result: Studio becomes very slow and then freezes and crashes.Error prompt and logs have been attached. Also the logs have become vanished when I relaunched Studio and also update for Node.acs plugin feature again appear ( it was already installed but after studio crashes , it got removed )
| 8 |
916 |
TISTUD-2929
|
12/03/2012 05:46:40
|
'Unhandled event loop exception' error is shown in logs when package a mobile web project and select third option 'create a new project for a mobile web app'
|
This is not a regression bug.It happens in Studio 2.1.2 with sdk 2.1.2 GA Test Steps: 1.Install latest studio. 2.Create a Titanium mobile two tabbed project only for mobile web. 3.From project explorer, package the mobile web project created in 2nd step. 4.Select the third option 'create a new project for a mobile web app'. 5.Give any name to the new project eg test234. 6.Pakage the project. Actual Error: Unhandled event loop exception error is coming.Logs attached. !ENTRY org.eclipse.ui 4 0 2012-12-03 10:51:31.374 !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:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:774) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:568) at org.eclipse.swt.widgets.Label.setText(Label.java:518) at org.eclipse.jface.wizard.ProgressMonitorPart.updateLabel(ProgressMonitorPart.java:367) at org.eclipse.jface.wizard.ProgressMonitorPart.subTask(ProgressMonitorPart.java:358) at org.eclipse.jface.wizard.WizardDialog$4.subTask(WizardDialog.java:707) at org.eclipse.jface.operation.AccumulatingProgressMonitor$Collector.run(AccumulatingProgressMonitor.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 22 more
| 5 |
917 |
TISTUD-2930
|
12/03/2012 06:07:43
|
'Finish' tab should be disabled when first opened Titanium Studio > Help > 'Install specific Titanium SDK from URL'
|
This is not a regression bug . I have recreated this bug with Titanium 2.1.2. Steps to reproduce: 1)Open Titanium Studio. 2)Help >'Install specific titanium SDK ' > 'install from URL'. 3)Without entering anything in the text-box, press 'finish tab. 4)Observe that if you check the radio button "install from update stream" then finish tab for Install specific titanium SDK ' > 'install from URL' will be disabled. Actual result: 'Your Titanium SDKs have been updated' pop up window is appearing.Also logs shws [ERROR] NULL. Logs and screenshot attached. Expected Result: Finish tab should be disabled if URL textbox is empty.
| 3 |
918 |
TISTUD-2933
|
12/03/2012 06:33:37
|
Node.ACS: adopt to the change in "acs list" command
|
The command to call "acs list" under a project dir to show an app info has been deprecated; instead, we should run "acs list <appname>". The acs change is in the latest git. We should verify the syntax we call to "acs list" in Studio and make appropriate changes.
| 3 |
919 |
TISTUD-2934
|
12/03/2012 06:57:48
|
Not to show the error message when first opening package Mobile Web wizard
|
This is not a regression bug.It happens in Studio 2.1.2 . Test Steps: 1.Install latest studio. 2.Create a Titanium project which must support mobile web . 3.Project explorer > Package - Mobile web > observe the window. Actual Result: A red cross with a message 'Project Directory must be specified' is displayed though I haven't chosen any of the three actions mentioned on that window. Expected Result: By default first action would be selected with the launch of the package -mobile web window but before choosing any action red cross error shouldn't appear. The error message behavior should be same as Help > 'Install specific titanium SDK from URL'
| 3 |
920 |
TISTUD-2936
|
12/03/2012 08:56:51
|
Titanium Studio: 'Module packaging successful' prompt should display correct directory location path for packaged module zipped file.
|
This is a regression. Test Steps: 1.Install latest studio. 2.Create a New Titanium module project for mobile web. 3.From project explorer, package mobile web module created in 2nd step. 4.Select the third option ' package mobile web module to a directory'. 5.Give any location on the local machine. Actual Result: 'Module packaging successful' prompt displays wrong directory location where zip file is stored. It doesn't show the directory path given in the third option where actual packaged mobile web zipped file is stored. Expected Result: 'Module packaging successful' prompt should read and display correct directory location for packaged mobile web module zipped file. P.S. This erroneous behavior is found for all three ios , android and mobile web modules respectively.
| 5 |
921 |
TISTUD-2949
|
12/03/2012 11:29:58
|
CLI: ERROR Invalid ios version value
|
This appears to be a regression issue. Since it works fine in 2.1.2 Studio. iOS Simulator 5.0/5.1 runs in Studio 2.1.2 build. Steps To Reproduce: 1. Install Xcode and Studio 3.0 2. Create a default project. 3. Try running app in iOS simulator. Actual: Error appears in console. [ERROR] Invalid --ios-version value '5.0' Accepted values: 6.0 5.1 Expected: iOS simulator 5.0/5.1 must run for default project.
| 13 |
922 |
TISTUD-2940
|
12/03/2012 18:48:46
|
Unable to finish Android SDK installation with Titanium Studio open.
|
While installing the Android SDK via the dashboard I get a warning from the android tools that TitaniumStudio.exe is locking the tools directory and I can not continue the install with Studio open (see screenshot). This may be caused by trying to install the new Android SDK Tools, v21. Steps to reproduce: 1. Launch studio. 2. Install the Android SDK via the Configure Native SDKs in the dashboard. 3. Start the default install Expected result: Android should be able to correctly install without closing Titanium Studio. Actual results: Above warning error. Note this only happens on Windows.
| 8 |
923 |
TISTUD-2941
|
12/03/2012 19:20:31
|
Alloy view element content assist not respecting ns attribute value
|
{code} <| ns="Titanium.Map"> {code} Given that code, we should only be suggesting "Annotation" and "View" (as per http://docs.appcelerator.com/titanium/latest/#!/api/Titanium.Map) We're not filtering properly and are showing all elements.
| 5 |
924 |
TISTUD-2942
|
12/03/2012 19:22:45
|
XML Editor isn't auto-closing <> pairs
|
When typing a '<', I don't get a '>' character to close the pair. Maybe we're not including the XML ruble? Maybe the pairs aren't defined properly?
| 5 |
925 |
TISTUD-2944
|
12/03/2012 19:24:45
|
Use same stylesheet for Alloy release notes as Titanium SDK
|
When we show the Alloy release notes int he update dialog, it doesn't look the same as the Titanium SDK notes. It'd be nice to make sure they look similar and are easily readable.
| 5 |
926 |
TISTUD-2947
|
12/03/2012 21:18:15
|
XML Editor doesn't open CA proposals after typing '<'
|
In HTML, if you type ',", we auto-pop CA. That isn't the case for XML. We should make it do so (mainly for alloy, because normal XML doesn't actually have any proposals).
| 5 |
927 |
TISTUD-2948
|
12/03/2012 21:34:37
|
Add Alloy samples to Samples view
|
After we have alloy samples from ALOY-412, we should integrate them in Samples view, with Alloy as a top level category and individual samples underneath.
| 8 |
928 |
TISTUD-2950
|
12/03/2012 23:58:15
|
iOS Simulator: intermittent error cleaning the build before launching
|
Error cleaning when deploying Titanium Project to iOS Simulator. Steps to Reproduce: 1. Deploy app to iPad Simulator. 2. Using same run config, run app in iPhone Simulator. Actual Result: Clean error. Could be causing related ticket. Expected Result: No error.
| 8 |
929 |
TISTUD-2953
|
12/04/2012 00:09:21
|
Port HTML content assist unit tests to XML
|
Porting the large amount of HTML unit tests should help us identify the area in content assist where functionality exists in HTML but not XML.
| 8 |
930 |
TISTUD-2955
|
12/04/2012 00:18:39
|
Unable to find Titanium SDK when tiapp.xml is opened on startup
|
When tiapp.xml is opened on startup, Studio is unable find Titanium Mobile SDK and report errors about unable to locate the SDK. However, closing and re-opening tiapp.xml file fixes this issue. At this time, the problem is reproducible only in dev environment.
| 5 |
931 |
TISTUD-2958
|
12/04/2012 01:04:15
|
Studio display two update dialogs if user initiates "Check for Titanium Updates"
|
Steps: 1. Start a titanium studio that will prompt for updates to the sdk/node/acs/etc 2. While studio is loading, right away click Help->Check for Titanium Updates Expected results: One update dialog is displayed Actual: Two dialogs are displayed. If a dialog is requested manually, the check that runs during startup should not be displayed
| 5 |
932 |
TISTUD-2960
|
12/04/2012 02:35:31
|
Dashboard: Change the button to Launch Recent project after creating a project
|
In the new workspace, the dashboard show 'Create a new mobile web project' button and once the user creates a new project using this button, it does not update the button to 'launch recently created project'. The user has to explicitly refresh the dashboard to get the option.
| 5 |
933 |
TISTUD-2965
|
12/04/2012 16:33:32
|
NPE: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources"
|
Following NPE on shutdown: {code} !ENTRY org.eclipse.core.resources 4 2 2012-12-04 08:30:57.294 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.NullPointerException at com.aptana.core.build.UnifiedBuilder.getBuildParticipantManager(UnifiedBuilder.java:282) at com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:433) at com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:414) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:307) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Steps to reproduce: 1. Close Titanium Studio 2. Reopen Titanium Studio 3. View the Log file Expected result: Titanium Studio should close without error. Actual result: The above NPE shows in the log.
| 3 |
934 |
TISTUD-2966
|
12/04/2012 16:55:44
|
Disparity in CLI reports from Windows and Ubuntu to Mac OS
|
When checking the diagnostic print out, Titanium Studio, build: 3.1.0.201212031735 now shows if the new CLI is being used. I see "Titanium CLI Enabled: true" for Windows and Ubuntu, and "Titanium CLI Enabled: false" for Mac with default flag settings. This functionality does not exist in Titanium Studio 3.0.0 or 3.0.1. Steps to reproduce: 1. On Mac OS start Titanium Studio. 2. Run the Diagnostic test (Help > Titanium Studio > Run Diagnostic Test...) 3. On Windows start Titanium Studio. 4. Run the Diagnostic test (Help > Titanium Studio > Run Diagnostic Test...) 5. Compare the results. Expected Result: Results for CLI usage with default flag settings should match. Actual Result: Windows (and Ubuntu) reads "Titanium CLI Enabled: true" Mac OS reads "Titanium CLI Enabled: false"
| 3 |
935 |
TISTUD-2969
|
12/04/2012 23:18:22
|
iOS: Developer name passed to CLI is trimming ID
|
QE discovered a problem where the developer identity is not correctly set. In this case, it was determined that the developer name which should read something like "Eric Merriman (9JU76422)" is being trimmed by studio and passed as "Eric Merriman". The problem with this technique is that we were trying to use Developer name "Eric Merriman (W6xxxxx)" and were getting a certificate mismatch. To prevent this, the full developer name should be passed, including the "(9JU76422)" Steps to reproduce: 1) Using a configured system that includes multiple identities, attempt to build for device using one of the multiple identities (the one appearing second in "Titanium info") Result: Studio reports that the identity (the one you didn't select) doesn't match the provision, and fails Expected: The identity selected in the build dialog is the one used for the build
| 5 |
936 |
TISTUD-2970
|
12/04/2012 23:27:10
|
Studio: Distribution name seems to be using developer name, which is incorrect
|
After discovering an identity bug, the investigation also uncovered that Studio is using the developer name (plus ID) in place of the distribution name. The correct value shows in the build dialog, but according to Chris, the developer name is being passed in place of the distribution name. Steps to reproduce: 1) Create a project in studio 2) Package for distribution Result: Studio passes the developer name e.g. "Eric Merriman (9JUJ8DJW9G)" instead of the distribution name, eg "Eric Merriman" Expected: Studio passes the distribution name as part of a packaging attempt.
| 5 |
937 |
TISTUD-2971
|
12/04/2012 23:43:16
|
XML Editor suggests attribute name proposals after '='
|
In XML, if you invoke CA after a '=' we suggest attribute names, not values.
| 5 |
938 |
TISTUD-2972
|
12/04/2012 23:47:35
|
Run Diagnostic Test: add Titanium CLI Enabled: true/false
|
Add Titanium CLI Enabled: True/False to diagnostic log. Suggested Fields: {code} Titanium CLI Version: 3.0.11 Titanium CLI Enabled: True/False {code}
| 3 |
939 |
TISTUD-2973
|
12/05/2012 01:15:32
|
iOS build to device freezes studio if git locks up
|
Steps to reproduce: 1.Create a default app in studio. 2.Run on iOS device. Actual result: 1.Studio Freezes. Expected Results: 1.Studio should build app & not freeze.
| 8 |
940 |
TISTUD-2976
|
12/05/2012 11:44:35
|
Titanium Project: terminating new project creation process is throwing error
|
This is not a regression bug.It happened in 2.1.2 Studio. Test Steps: 1.File > New >Create a Titanium Project. 2.Enter project name and app id . 3.This project can support to any of the platform ie iOS or Android or Mobile web 4.Press Finish. 5.Before the creation of project folder , cancel it by click on the red square at the bottom. Observe the error .Screenshots and logs attached.
| 5 |
941 |
TISTUD-2977
|
12/05/2012 16:55:42
|
Adopt CLI "titanium info" for determine iOS certificates and provisioning profiles
|
Studio needs to adopt the CLI command to replace prereq.py and provisioner.py (provisioning profiles). The command is: titanium info -o json -t ios It returns certficates and provisioning profiles, as well as information used by prereq.py (keychains, wwdr, etc) Only data missing is the itunes version, see referenced ticket
| 8 |
942 |
TISTUD-2978
|
12/05/2012 17:08:31
|
Support outputting adhoc/enterprise ios builds as archives
|
In the iOS adhoc/enterprise distribution, Studio needs to support an output type of archive. That enables users to archive an app and perform additional utilities in Xcode. An additional entry should be added to the "Select format:" combo, named "archive". When the operation finishes, we should state in the toast popup that the archive is in xcode
| 8 |
943 |
TISTUD-2979
|
12/05/2012 17:27:38
|
Remove CLI logic that calls titanium select prior to running operations
|
Studio added logic that runs titanium select before any CLI operation that specifies an SDK, to work around an issue with the CLI. That issue has now been resolved in TIMOB-11883
| 2 |
944 |
TISTUD-2981
|
12/05/2012 21:15:19
|
Node.ACS: add node.acs preview stream to previews page
|
http://preview.appcelerator.com/studio/ needs node.acs stream info for testing.
| 5 |
945 |
TISTUD-2984
|
12/05/2012 21:53:22
|
MobileWeb Browsers: safari can be added to the list multiple times
|
In a MobileWeb run config, if you 'check for browsers', Safari continues to be recognized every time the command is run. This results in a long list of Safari installs, all the same version. Steps to Reproduce: 1. Open MobileWeb run config. 2. Select browser as 'check for installed browsers' and install all browers. 3. Run the command again. Actual Result: Safari appears as unrecognized. Can install multiple identical Safari versions if you repeat the 'search for browsers'/install action. Expected Result: There should be no duplicates in the recognized browsers list.
| 5 |
946 |
TISTUD-2985
|
12/06/2012 00:17:40
|
Remove Run Web Deployment Wizard option from the Titanium Module Project
|
Steps to Reproduce: 1. Create Titanium Module Project. 2. Select Publish > ... Actual Result: There is the "Run Web Deployment Wizard..." option. Expected Result: The web deployment wizard option does not apply to Titanium Module project and should be filtered out.
| 3 |
947 |
TISTUD-2988
|
12/06/2012 17:50:08
|
NPE: An internal error occurred during: "Launching Titanium iOS on Device - [project name]"
|
When trying to debug on device for IOS I get the following error when testing in Titanium Studio, build: 3.0.1.201212051858: {code} !ENTRY org.eclipse.core.jobs 4 2 2012-12-06 09:12:44.737 !MESSAGE An internal error occurred during: "Launching Titanium iOS on Device - Test_Mac". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.build(IOSNodeJSCommandsHelper.java:143) at com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.installOnDevice(IOSNodeJSCommandsHelper.java:113) at com.appcelerator.titanium.mobile.cli.IOSCommandsHelper.runOnDevice(IOSCommandsHelper.java:135) at com.appcelerator.titanium.mobile.cli.nodejs.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:442) at com.appcelerator.titanium.mobile.ui.iphone.launch.IOSDebugOnDeviceLaunchConfigurationDelegate.launch(IOSDebugOnDeviceLaunchConfigurationDelegate.java:47) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} This is a regression as it does not happen in 3.0.0. Steps to reproduce: 1. Create a standard Titanium project. 2. Debug on device. 3. Click finish. Expected result: Debugging begins to build for device and steps the user through the process. Actual result: Above NPE is thrown. Error detection fails to close the Debug on Device session.
| 5 |
948 |
TISTUD-2990
|
12/06/2012 22:52:33
|
Disable the "Android Runtime" combo-box in tiapp.xml for 3.0.0+ SDK
|
We would like to deprecate rhino and discourage people from using it, and the suggestion is to disable the "Android Runtime" combo-box in tiapp.xml when the selected SDK is 3.0.0+. User could still go into the source and change it manually, and we won't prevent them from doing that.
| 3 |
949 |
TISTUD-3022
|
12/07/2012 06:37:12
|
Android Emulator: can't launch two separate projects in a row on Windows
|
Test Steps: 1.Install Latest Studio. 2.Create two Titanium Mobile projects for android platform. 3.Run first project on Android emulator. 4.Once emulator has been launched , try to run second project on android emulator. Actual Result: Emulator hangs on 'not responding' screen. Expected Result: The second project application should be launched in emulator.
| 8 |
950 |
TISTUD-2997
|
12/07/2012 19:03:33
|
Remove iTunes version check from iOS publish wizard
|
The itunes version check is no longer necessary, since the requirement of v10 is standard, and the platform no longer requires the itunes version check. Studio needs to remove the version check from the Publish iOS simple and full wizards
| 5 |
951 |
TISTUD-2999
|
12/07/2012 23:27:49
|
Run Configurations: Project Text Field is Read Only for most configs
|
Some run configurations have a read-only Project text field if the user wants to manually type in the project name. The browse button works correctly. This is not a regression. List of Project Text Field Read-Only Run Configs: Titanium Android App Store Distribution Titanium Android Application Installer Titanium Android Module Packager Titanium Apple Ad Hoc/Enterprise Distribution Titanium Apple iTunes Distribution Titanium iOS Application Installer Titanium iOS Module Packager Titanium Mobile Web Module Packager List of Correctly-Behaving Run Configs: Titanium Android Emulator Titanium iOS Simulator Titanium Mobile Web Distribution Titanium Mobile Web Preview on Emulator Titanium Mobile Web Previewer Steps to Reproduce: 1. Open run configs menu. 2. Click in the Project text field for a run config from the failure list above. Actual Result: Field is readonly, user can't manually edit the field. Expected Result: User should be able to manually edit the field, as they can in some run configs from the above 'correctly behaving' list.
| 5 |
952 |
TISTUD-3000
|
12/08/2012 01:29:05
|
TiApp Editor: sdk intermittently fails to save based on sdk value in overview
|
TiApp Editor: sdk intermittently fails to save in the xml tag based on sdk value in overview. Steps to Reproduce: 1. Open TiApp Editor. 2. Open tiapp.xml and edit titanium sdk to invalid value and save. 3. Open TiApp Editor Overview and save. 4. Open tiapp.xml and view titanium sdk tag. Actual Result: The sdk value is the same invalid it was before the save. This happens intermittently.
| 5 |
953 |
TISTUD-3002
|
12/08/2012 15:34:41
|
Debug on Device: prompting 3.0 as minimum SDK would be user-friendly
|
Test Steps: 1.Install Latest studio. 2.Connect an android device. 3.Create a Titanium Mobile android project with 2.1.4 GA SDK . 4.Right click on the project and select debug > debug configuration >create a new configuration for android device > run. Actual Result: SDK 2.2 is prompted as the minimum sdk. 2.2 is the old name for 3.0. Expected Result: SDK Error is an expected behavior but it should display SDK 3.0 version or above.
| 1 |
954 |
TISTUD-3003
|
12/10/2012 11:44:29
|
NPM intermittently fails to install on first try
|
Test Steps: 1.Download and install latest Titanium Studio installer on a clean Windows 7 / Windows 8 machine. 2.After launching Studio , accept Titanium Updates >Next >Install. 3.Configure GIT support. 4.After that Windows Installer prompt will appear in order to install Nodejs exe. Accept all the steps so that Nodejs configuration should successfully finish. 5.After closing Nodejs wizard 'finish' tab , an error window "Problem Occurred - Installing Titanium Updated has encountered a problem -NPM is not installed " has appeared. 6.After restarting window multiple times same error "Problem Occurred - Installing Titanium Updated has encountered a problem -NPM is not installed " has appeared. Screenshot and logs attached.
| 8 |
955 |
TISTUD-3004
|
12/10/2012 21:12:40
|
Use same stylesheet for module update content
|
Similar to TISTUD-2944, where we updated the alloy update style sheet, we need to do the same for the modules update style sheet. Right now the text in the module details is large and not consistent. [EDIT] The module JSON file should be updated to direct a release-notes page. This page should later be read by the release notes system and be applied with the same stylesheet we use for the rest.
| 5 |
956 |
TISTUD-3064
|
12/10/2012 23:20:11
|
iOS: Unable to select mobile provisioning profile
|
Summary: Unable to select mobile provisioning profile Steps to reproduce: 1. Run 2. iOS Device 3. Next 4. Next 5. Browse 6. Select .mobileprovisioning file Actual result: Invalid Provisioning Profile "Specified Provisioning Profile is invalid or is the wrong type." Expected result: Ability to click "Finish" Log: !ENTRY com.appcelerator.titanium.mobile 4 0 2012-12-10 18:11:49.885 !MESSAGE (Build 3.0.1.201212082232) [ERROR] Unable to parse the output generated from running the script '/Library/Application Support/Titanium/mobilesdk/osx/3.1.0/iphone/provisioner.py' with file path '/Users/*****/Documents/Provisioning/****_Development.mobileprovision': /usr/bin/python: can't open file '/Library/Application Support/Titanium/mobilesdk/osx/3.1.0/iphone/provisioner.py': [Errno 2] No such file or directory
| 8 |
957 |
TISTUD-3010
|
12/11/2012 00:16:52
|
Titanium Updates: add NodeJS version to success toast
|
Titanium Updates: add NodeJS version to success toast. Screenshot attached. Steps to Reproduce: 1. Install NodeJS using Titanium Updates. Actual Result: Success toast lists NodeJS version as N/A. Expected Result: Success toast lists NodeJS version as <nodejs version>.
| 3 |
958 |
TISTUD-3012
|
12/11/2012 16:16:31
|
Preferences: Xcode path does not refresh until restart
|
The refresh button in Properties > Titanium Studio > Titanium > iOS SDK Home does not refresh the iOS SDK when you click it after change is via xcode-select. It does pickup the new xcode path after restarting Studio. h4. Steps to repro 1. In Studio go to Properties > Titanium Studio > Titanium > iOS SDK Home and note the location of xcode 2. Use xcode-select to switch to another xcode version in another location 3. Click refresh 4. Notice that the location of xcode does not change in studio 5. Restart Studio 6. In Studio go to Properties > Titanium Studio > Titanium > iOS SDK Home and note the location of xcode 7. Notice that the location of xcode has changed to what it was set to using xcode-select
| 5 |
959 |
TISTUD-3013
|
12/11/2012 17:35:00
|
XML Editor does not list correct suggestions for content assist.
|
When using content assist in Alloy it incorrectly populates the content assist window. It seems to be loading attributes rather then the Alloy elements. This worked before implementing TISTUD-2942. Steps to reproduce: 1. Create an Alloy project. 2. In the app/views/index.xml add the following to the Alloy container element: {code} <Window> <> </Window> {code} 3. Invoke content assist between the two empty brackets. Expected result: Content assist should open with a list of Alloy container names. Actual result: Content assist opens with a list of default container attributes.
| 3 |
960 |
TISTUD-3015
|
12/11/2012 18:42:05
|
Convert JSON scanner(s) to JFlex based
|
JSON uses text rule based scanners for parsing, partitioning and colorization. This is a performance issue for larger files. JSON is very simple to lex/scan and using a JFlex based scanner for parsing at the least should be relatively straightforward.
| 8 |
961 |
TISTUD-3016
|
12/11/2012 18:55:46
|
Preferences: dragging titanium sdk into text field produces error: Value must be an absolute path
|
This is a regression. Does not occur in Studio 2.1.2. Dragging titanium sdk from OS GUI to Studio Preferences results in path error. Clicking on DETAILS makes error go away. Note that manually typing in the path or selecting it in BROWSE work correctly. There is no log info. Steps to Reproduce: 1. Open Preferences > Titanium. 2. Locate Titanium folder in OS filesystem GUI. 3. Drag folder to Titanium path text field. Actual Result: Invalid path. Note the path from dragging vs browser is identical. Expected Result: Valid path.
| 5 |
962 |
TISTUD-3017
|
12/11/2012 19:02:04
|
Splash: improve positioning of login fields
|
Login screen is dead-center, looks odd. Recommend using http://en.wikipedia.org/wiki/Rule_of_thirds login ui elements would be lowered a bit. Also suggest making buttons same width as text fields, and centering links below the group.
| 0 |
963 |
TISTUD-3021
|
12/11/2012 19:26:41
|
Add more logging to provisioning profile loading and caching
|
To provide better troubleshooting for provisioning issues, we need to log more information about the available provisioning profiles and the process of loading the profiles from the filesystem and the cache
| 5 |
964 |
TISTUD-3020
|
12/11/2012 23:07:14
|
Remove duplicate entries in the environment variable PATH
|
I enabled logging for ALL, and I ran through the iOS publishing wizard. I noticed when the environment variable PATH contains numerous entries for the JDK path: Environment: {ANALYTICS_SOURCE=studio, APTANA_VERSION=3.0.1.qualifier, Apple_PubSub_Socket_Render=/tmp/launch-lARzbP/Render, Apple_Ubiquity_Message=/tmp/launch-YOCWjK/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer, HOME=/Users/nle, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=nle, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin, PWD=/Applications/eclipse_42/Eclipse.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-puYPOq/Listeners, TMPDIR=/var/folders/zw/n1jmn7z52yb6x0rfd2cn5bgr0000gq/T/, USER=nle, __CF_USER_TEXT_ENCODING=0x1F7:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI.java}
| 5 |
965 |
TISTUD-3024
|
12/12/2012 00:34:29
|
Titanium Module Packager: can't apply changes to most packaging types
|
Titanium Android, iOS, & MobileWeb Module Packager: can't apply changes to most packaging types. If you select Mobile App, then Titanium SDK, you can't save the changes. If you select Titanium SDK, then Mobile App, you can't save the changes. If you select Directory, you CAN save the changes. No log info. Steps to Reproduce: 1. Open Titanium Project. 2. Open Android/iOS/MobileWeb Module Project. 3. Open Android/iOS/MobileWeb Module Packaging Run Config for that project. 4. Select Mobile Project. Apply. 5. Select Titanium SDK. Actual Result: Apply doesn't work, module will package to wrong type. Expected Result: Each type should work if it selected. Work-around is to create a new run config every time, or click around until you can apply the changes.
| 3 |
966 |
TISTUD-3025
|
12/12/2012 01:08:16
|
Show the error from console in the dialog when running iOS on device
|
When I was trying to run on iOS device, a problem has occurred and there was no information in the dialog. However, the console logs information about the error. The user expects the error diagnostic information to be available in the error dialog. Please refer to screenshot for further details.
| 5 |
967 |
TISTUD-3026
|
12/12/2012 01:31:38
|
Cloud: Plugin - Node.ACS plugin does not download and install Node.ACS cli for you
|
*Details:* Node.ACS plug-in does not download and install the Node.ACS cli for you *Steps to reproduce:* 1. Make sure node.acs is completely removed from your machine 2. Install node.acs plug-in following these instructions: http://preview.appcelerator.com/appcelerator/studio/acs/update/rc/ 3. In the Project Explorer pane, go to New > Node.ACS project 4. Start typing a project name *Actual:* Studio will not be able to find the acs executable/node package (see attachment) *Expected:* Studio should download the node.acs cli after installing the node.acs plugin *Note:* To get around this issue, you will need to install node.acs cli through the terminal: *sudo npm install -g acs*
| 3 |
968 |
TISTUD-3028
|
12/12/2012 08:56:22
|
File > Import > General > Existing Folder as New Project remove error icon
|
Steps To Reproduce: 1. Install Studio. 2. Go to File>Import>General>Existing Folder as NewProject>Next to import a sample project. Actual: observe the error message appears on top stating " Please select a folder" Expected: Error icon should not appear.
| 5 |
969 |
TISTUD-3029
|
12/12/2012 09:39:14
|
Allow user to easily import and run old projects
|
Steps To Reproduce: 1. Go to File>Import>General>Existing Folder as NewProject>Next to import a project (attached zip). 2. Run Project in debug mode using iphone simulator. Actual: "Requested SDK version does not have an assigned commands-handler." error message appears. On opening tiapp.xml and saving same resolves the issue. On windows 8 "Null Pointer" exception appears. refer snapshot Expected: Project must be imported and run without any error.
| 8 |
970 |
TISTUD-3033
|
12/12/2012 21:35:22
|
NullPointerException thrown when trying to find provisioning profiles in Ti Studio 3.0CI
|
One of our customers is reporting an issue related to provisioning profiles in Studio. NullPointerException is thrown when 'Manage Settings' is selected while trying to find provisioning profiles. I have attached the crash log from studio for more information. Screenshot of the error : http://cl.ly/image/2R2E1t3P0c0w Ti Studio Version : 3.0.0.201211131839
| 3 |
971 |
TISTUD-3035
|
12/13/2012 11:13:35
|
Help > 'Install Titanium Module' > 'Install from URL ' with no specified URL should fail
|
This is not a regression bug. It happens in Studio 2.1.2 too. Test Steps: 1.Launch Studio. 2.Help > Install Titanium Module > press 'OK' (don't enter a module) Actual Result: Module is successfully installed. Expected Result: 'OK' tab should be disabled since the input is not valid.
| 3 |
972 |
TISTUD-3037
|
12/13/2012 19:20:41
|
Terminating iOS debug on device session in Studio disables further debug on device sessions
|
If a debug on iOS device session is terminated while in progress, then it seems that it does not completely release the sockets or listener sessions. Due to that, if another debug on iOS device session is launched, Studio fails to connect debugger to the app running on iOS device. The workaround would to re-start Studio to start another debug on iOS device session.
| 8 |
973 |
TISTUD-3044
|
12/14/2012 00:08:16
|
Unable to log into JIRA when using Help > Titanium Studio > Submit a Ticket...
|
This is a regression. Steps to reproduce: 1. Select Help > Titanium Studio > Submit a Ticket...; 2. Enter the JIRA credential to log in; 3. Click on "Log in". Expected result: user will successfully log into JIRA. Actual result: an "Unknown error" error dialog pops up.
| 2 |
974 |
TISTUD-3045
|
12/14/2012 01:33:46
|
Alloy debugging: specify the source map interface requirement in a wiki page
|
After the discussion with Tony, Max, and Shalom, we decided the first action item is to define the source map API contract for connecting the original alloy source with the generated code. In the wiki page, we should spell out the specific calls (with parameters) Studio will make to alloy and the expected return values. There should be code samples for each call, and if the returned value is a JSON string, the expected syntax of the string should be clearly stated. This will allow us to decouple the work on Studio and Alloy sides, and we will return to modify the page if additional contract is needed or existing ones should be amended.
| 8 |
975 |
TISTUD-3050
|
12/14/2012 23:42:56
|
Import Existing project wizard does not close when project is copied into workspace
|
If an existing project is imported into workspace using 'Existing projects into workspace' wizard with 'copy project into workspace' option selected, then the wizard does not close after the import. Manually closing the wizard pops up a dialog indicating about an active operation.
| 8 |
976 |
TISTUD-3051
|
12/15/2012 02:05:48
|
Running blackberry simulator fails with no error when device IP is not specified
|
When a Blackberry project is run on simulator, it creates a default run configuration and launches it. However, if the preferences of blackberry does not already contain the device IP address, then the app launch will fail as the IP address is required value for launching the app. Expected: Either the run configuration or blackberry preferences dialog should be opened to allow user to enter device IP address, or show the corresponding error in the console.
| 8 |
977 |
TISTUD-3806
|
12/15/2012 03:09:11
|
iOS: Spaces in <name> field of tiapp.xml generates error
|
*Problem description* Having a <name> with spaces in tiapp.xml: <name>Laguna Beach</name> generates a red-x pop-up error message in the TiApp Editor: Multiple Markers at this line - 'Laguna Beach' is not a valid value for NCName - The value 'Laguna Beach' of element 'name' is not valid *Build log* {code} [TRACE] : ProcessInfoPlistFile "build/Debug-iphonesimulator/Laguna Beach.app/Info.plist" Info.plist [TRACE] : cd /Users/jrf/Workspace/Laguna/build/iphone [TRACE] : setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Developer/usr/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Users/jrf/.rvm/gems/ruby-1.9.2-p180@dataentry/bin:/Users/jrf/.rvm/gems/ruby-1.9.2-p180@global/bin:/Users/jrf/.rvm/rubies/ruby-1.9.2-p180/bin:/Users/jrf/.rvm/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin" [TRACE] : builtin-infoPlistUtility Info.plist -genpkginfo "/Users/jrf/Workspace/Laguna/build/iphone/build/Debug-iphonesimulator/Laguna Beach.app/PkgInfo" -expandbuildsettings -format binary -platform iphonesimulator -o "/Users/jrf/Workspace/Laguna/build/iphone/build/Debug-iphonesimulator/Laguna Beach.app/Info.plist" [ERROR] : ** BUILD FAILED ** [ERROR] : The following build commands failed: [ERROR] : ProcessInfoPlistFile "build/Debug-iphonesimulator/Laguna Beach.app/Info.plist" Info.plist [ERROR] : (1 failure) {code}
| 3 |
978 |
TISTUD-3052
|
12/16/2012 18:03:50
|
Refactor Mobile Web code from mobile.* plugins into its own mobileweb.core and mobileweb.ui plugins
|
The idea is to have no Mobile Web related code or constant in com.appcelerator.titanium.mobile and com.appcelerator.titanium.mobile.ui plugins. The subtasks will capture the work needed in the various areas to make this happen.
| 0 |
979 |
TISTUD-3053
|
12/16/2012 22:50:47
|
Refactor the Titanium project wizard to have mobileweb plugin contribute its entry
|
Currently the Titanium project wizard defines all the checkboxes for deployment targets. We should have the mobileweb plugin contribute the following attributes through the extension point from TISTUD-3066: 1. A display name ("Mobile Web"); 2. A string for platform type ("mobileweb") that will be used by CLI and other necessary operations; 3. A mean to check if the requirement for platform support is met, i.e. if the Titanium SDK contains the platform, if the platform SDK is installed (not applicable to Mobile Web), and if the OS supports the platform (not applicable here either), so the project wizard could enable/disable the checkbox as appropriate. It should return a status so we could display a warning or error message if needed. 4. Potentially a post-project creation hook to perform any Mobile Web specific task needed (don't think we have any?). 5. An optional "priority" attribute to control the order of the platforms both here and in tiapp.xml. Currently we are sorting them in alphabetical order, but there might be a case in the future where we like to have the flexibility.
| 13 |
980 |
TISTUD-3054
|
12/17/2012 00:33:26
|
Refactor the Deployment Targets section of tiapp.xml to have mobileweb plugin contribute its entry
|
We should be able to re-use the attributes defined from TISTUD-3053 for the "Deployment Targets" section of tiapp.xml, as the idea here is to also have mobileweb plugin contribute the name, platform type, and if it's supported on the current system.
| 8 |
981 |
TISTUD-3055
|
12/17/2012 00:45:43
|
Move Run > Mobile Web Preview in Browser action to mobileweb's own plugins
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Run > Mobile Web Preview in Browser action to mobileweb's own plugins.
| 8 |
982 |
TISTUD-3056
|
12/17/2012 00:51:05
|
Have mobileweb plugin contribute to the preferences page
|
We should have a subnode for each platform under Preferences > Titanium Studio > Titanium and move the respective section from Titanium preference page there. The mobileweb plugin will contribute the Mobile Web preference page and handle its preference settings.
| 8 |
983 |
TISTUD-3062
|
12/17/2012 21:17:42
|
Unable to install modules via Dashboard my modules section
|
When you click the "Install" button for a module in the My modules section, it does not install the module. Nothing happens
| 3 |
984 |
TISTUD-3066
|
12/18/2012 07:22:56
|
Create an extension point for defining individual supported platform
|
For this ticket, we will create the extension point placeholder for defining individual supported platforms (iOS/Android/MobileWeb/etc) and the manager class to process the contributors. The actual elements and their attributes will be added when working on the refactoring of various functionality.
| 5 |
985 |
TISTUD-3067
|
12/18/2012 07:44:48
|
Refactor the modules table section of tiapp.xml to have mobileweb plugin contribute its column
|
The plugin will need to contribute the icon. We also need a mechanism to parse out the module version for Mobile Web to be shown in the table. Is the platform type enough, and the tiapp model could parse the directory structure from there?
| 8 |
986 |
TISTUD-3070
|
12/18/2012 18:24:21
|
Update BB10 preference panel to have 2 ip addresses. (see description)
|
Currently there is a single IP address box that is used for both device install and running in simulator. It is a pain to switch the address between simulator and device. Please have 2 boxes 1 for simulator and a second for device. For device have an initial value of "169.254.0.1"
| 5 |
987 |
TISTUD-3071
|
12/19/2012 01:01:09
|
CLONE - Studio loses connection settings on restart
|
h3. Steps to Reproduce create connections, shut down the program, restart and connections are gone. h3. Actual Result no connection info h3. Expected Result expect to not have to recreate connection info for all sites everytime the program is started
| 13 |
988 |
TISTUD-3072
|
12/19/2012 20:45:28
|
Unable to publish applications using publish provider
|
Found two issues with 3.0.0. The publish wizard does not proceed past the distribution page if the environment only had one provisioning profile. Second, the build for iOS fails. It needs to be adopted to the new CLI
| 8 |
989 |
TISTUD-3074
|
12/20/2012 00:21:21
|
Clicking on "Titanium Mobile Developer Center" in Titanium Mobile Ruble leads to 404
|
# Open up Titanium Studio # Click on Commands > Titanium Mobile > Titanium Mobile Developer Center # Browser pops up with a 404 Looks like a bad search string or bad redirect in the dashboard index.php
| 2 |
990 |
TISTUD-3075
|
12/20/2012 00:39:12
|
Create a BlackBerry packaging launch tab-group
|
The BlackBerry packaging is done via a launch-configuration. However, since it's missing a tab-group implementation, it's not being displayed in the Run configurations, so a user has to go through the packaging wizard every time.
| 8 |
991 |
TISTUD-3080
|
12/20/2012 18:26:38
|
Remove "beta" from Alloy templates
|
The Alloy templates should be displayed as follows (no beta description): Alloy The tag/category and the template title/description should also no longer include the word "beta"
| 2 |
992 |
TISTUD-3084
|
12/21/2012 16:45:03
|
java.lang.IllegalArgumentException: Illegal group reference
|
After updating to last night's nightly build (Titanium Studio, build: 3.1.0.201212201822) I see the following error on start up in Windows 8: {code} !ENTRY com.appcelerator.titanium.nodejs.core 4 0 2012-12-21 08:33:29.804 !MESSAGE (Build 3.1.0.201212201822) [ERROR] Illegal group reference !STACK 0 java.lang.IllegalArgumentException: Illegal group reference at java.util.regex.Matcher.appendReplacement(Unknown Source) at com.aptana.core.util.replace.TextPatternReplacer.searchAndReplace(TextPatternReplacer.java:156) at com.appcelerator.titanium.update.internal.DefaultReleaseNotesProvider.applyTemplate(DefaultReleaseNotesProvider.java:138) at com.appcelerator.titanium.update.GitHubReleaseNotesProvider.getReleaseNotes(GitHubReleaseNotesProvider.java:79) at com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:76) at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:439) at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:503) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66) at com.appcelerator.titanium.update.TitaniumUpdateStartup$1$1.run(TitaniumUpdateStartup.java:64) 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:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} Steps to reproduce: 1. Start Titanium Studio. Expected result: Titanium Studio opens without error. Actual results: Titanium Studio opens with the above error.
| 5 |
993 |
TISTUD-3085
|
12/21/2012 17:15:23
|
Numerous calls to npm config get prefix while indexing js modules
|
I was running my dev environment and noticed that while indexing modules (see screenshot), my log was filled with calls to: !ENTRY com.aptana.core 1 0 2012-12-21 09:14:41.326 !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/npm" "config" "get" "prefix" Working directory: null Environment: {APTANA_VERSION=3.1.0.qualifier, Apple_PubSub_Socket_Render=/tmp/launch-lARzbP/Render, Apple_Ubiquity_Message=/tmp/launch-YOCWjK/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/nle, LANG=en_US.UTF-8, LOGNAME=nle, PATH=/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin, PWD=/Applications/eclipse_42/Eclipse.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-puYPOq/Listeners, TMPDIR=/var/folders/zw/n1jmn7z52yb6x0rfd2cn5bgr0000gq/T/, USER=nle, __CF_USER_TEXT_ENCODING=0x1F7:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI.java} This seems like something we can cache before the indexing job happens and re-use it. Making this call every ~300ms seems overkill
| 5 |
994 |
TISTUD-3086
|
12/21/2012 17:18:01
|
BadLocationException in error log
|
While investigating the iOS provisioning issue customers were seeing in 3.0.0, I kept running into this exception in their logs: !ENTRY com.appcelerator.titanium.ui 1 0 2012-12-18 11:02:01.359 !MESSAGE (Build 3.1.0.201212162216) [INFO] Failed to properly color output. !STACK 0 org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.TreeLineTracker.fail(TreeLineTracker.java:1055) at org.eclipse.jface.text.TreeLineTracker.getLineInformationOfOffset(TreeLineTracker.java:1151) at org.eclipse.jface.text.AbstractLineTracker.getLineInformationOfOffset(AbstractLineTracker.java:145) at org.eclipse.jface.text.AbstractDocument.getLineInformationOfOffset(AbstractDocument.java:936) at org.eclipse.ui.internal.console.ConsoleDocument.getLineInformationOfOffset(ConsoleDocument.java:52) at com.appcelerator.titanium.ui.internal.ConsolePageParticipant$LogLineStyleListener.calculateStyles(ConsolePageParticipant.java:104) at com.appcelerator.titanium.ui.internal.ConsolePageParticipant$LogLineStyleListener.lineGetStyle(ConsolePageParticipant.java:59) at org.eclipse.swt.custom.StyledTextListener.handleEvent(StyledTextListener.java:48) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.custom.StyledText.sendLineEvent(StyledText.java:8023) at org.eclipse.swt.custom.StyledText.getLineStyleData(StyledText.java:4154) at org.eclipse.swt.custom.StyledTextRenderer.getTextLayout(StyledTextRenderer.java:794) at org.eclipse.swt.custom.StyledTextRenderer.getTextLayout(StyledTextRenderer.java:720) at org.eclipse.swt.custom.StyledTextRenderer.calculate(StyledTextRenderer.java:211) at org.eclipse.swt.custom.StyledTextRenderer.calculateClientArea(StyledTextRenderer.java:229) at org.eclipse.swt.custom.StyledText.resetCache(StyledText.java:7791) at org.eclipse.swt.custom.StyledText.handleTextChanged(StyledText.java:6181) at org.eclipse.swt.custom.StyledText$6.textChanged(StyledText.java:5615) at org.eclipse.ui.internal.console.ConsoleDocumentAdapter.documentChanged(ConsoleDocumentAdapter.java:375) at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged2(AbstractDocument.java:769) at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:736) at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:721) at org.eclipse.jface.text.AbstractDocument.fireDocumentChanged(AbstractDocument.java:796) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1191) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) at org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.java:82) at org.eclipse.ui.internal.console.IOConsolePartitioner.processQueue(IOConsolePartitioner.java:572) at org.eclipse.ui.internal.console.IOConsolePartitioner$QueueProcessingJob.runInUIThread(IOConsolePartitioner.java:520) 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:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) Occurred for almost every user that had the provisioning issue. May be coincidence but we should fix it
| 5 |
995 |
TISTUD-3087
|
12/23/2012 20:13:46
|
Hookup standard output (stdout) to Console for BB10 apps (see description)
|
If developers put Ti.API.info("It would be great to get this output in Studio Console"); in their Javascript application (app.js) when running the following command from mac terminal: "PATH_TO_SDK/blackberry/builder.py" run -t simulator -d "PATH_T0_PROJECT" -p /Applications/bbndk --ip_address=192.168.137.151 Everything works fine and will show the info text. Which is expected as the scripts to view simulator logs and output has been directed to stout. See Ti_SDK/blackberry/blackberryndk.py line 351 def _printAppLog(self, deviceIP, package, password = None): If do Run As->Blackberry Simulator from Ti Studio I do not see the info output until I quit the Application. I would expect Studio to behave like Mac terminal in regards to stdout, and as the app runs and calls the info API to see the results in the Console view.
| 8 |
996 |
TISTUD-3088
|
12/26/2012 00:03:41
|
New Titanium project wizard: should not auto-select Cloud enablement when switching SDK
|
1. File > New > Titanium Project; 2. Click Next; 3. Uncheck "Automatically cloud-enable this application"; 4. Switch Titanium SDK version to a different one. Expected result: the "Automatically cloud-enable this application" checkbox remains unchecked. Actual result: the checkbox is rechecked.
| 5 |
997 |
TISTUD-3089
|
12/26/2012 23:12:15
|
Move Run > Mobile Web Preview in Emulator action to mobileweb's own plugins
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Run > Mobile Web Preview in Emulator action to mobileweb's own plugins.
| 5 |
998 |
TISTUD-3090
|
12/26/2012 23:16:26
|
Move Publish > Package - Mobile Web action to mobileweb's own plugins
|
This involves moving the command/handler/menu/launch-config definitions and related classes for contributing the Publish > Package - Mobile Web action to mobileweb's own plugins.
| 5 |
999 |
TISTUD-3094
|
01/02/2013 03:53:43
|
Updating the Studio code to support BlackBerry when checking for the supported platforms
|
Updating the Studio code to support BlackBerry when checking for the supported platforms. This includes the work to update the sdk_info.json file with links to the BlackBerry NDK download and simulator downloads (https://bdsc.webapps.blackberry.com/native/download).
| 8 |
1,000 |
TISTUD-3095
|
01/02/2013 03:57:21
|
Update the Dashboard to check for BlackBerry NDK and display corresponding message
|
Update the Dashboard side to call the SDK-Info command with a "blackberry" key. Then, parse the result and display any info (like we do with the rest of the platforms). The BlackBerry section in Dashboard will look similar to what Android one shows.
| 8 |
1,001 |
TISTUD-3097
|
01/02/2013 17:20:28
|
UnsupportedOperationException when updating the npm packages
|
User reported the following exception is seen in the log when prompted for updating the npm packages, and the installation failed: {code} !ENTRY com.appcelerator.titanium.update 4 4 2013-01-01 16:24:30.649 !MESSAGE Error encountered during update !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2013-01-01 16:24:30.649 !MESSAGE !STACK 0 java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableMap.put(Unknown Source) at com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.install(NodePackageManager.java:174) at com.appcelerator.titanium.update.TitaniumNPMRelease.install(TitaniumNPMRelease.java:43) at com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:591) at com.appcelerator.titanium.update.TitaniumSDKUpdater.access$0(TitaniumSDKUpdater.java:556) at com.appcelerator.titanium.update.TitaniumSDKUpdater$2.run(TitaniumSDKUpdater.java:388) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2013-01-01 16:24:30.649 !MESSAGE !STACK 0 java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableMap.put(Unknown Source) at com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.install(NodePackageManager.java:174) at com.appcelerator.titanium.update.TitaniumNPMRelease.install(TitaniumNPMRelease.java:43) at com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:591) at com.appcelerator.titanium.update.TitaniumSDKUpdater.access$0(TitaniumSDKUpdater.java:556) at com.appcelerator.titanium.update.TitaniumSDKUpdater$2.run(TitaniumSDKUpdater.java:388) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY com.appcelerator.titanium.alloy.ui 4 0 2013-01-01 16:24:30.659 !MESSAGE (Build 3.0.1.201212181159) [ERROR] Failed to add Alloy templates !STACK 1 org.eclipse.core.runtime.CoreException: Unable to find 'alloy' binary. at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplatesWithNewCommand(AlloyTemplateInstaller.java:261) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplates(AlloyTemplateInstaller.java:246) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.access$0(AlloyTemplateInstaller.java:244) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:151) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.appcelerator.titanium.alloy.ui 4 0 2013-01-01 16:24:30.659 !MESSAGE Unable to find 'alloy' binary. {code}
| 5 |
1,002 |
TISTUD-3099
|
01/02/2013 17:55:55
|
Titanium Update wizard pops up at startup even though they are only updates
|
When there are only updates to npm packages or modules or SDK, a toast should appear indicating about the available updates. The Titanium Wizard should be popped up only when any of the required packages are not installed on the machine. Actual Result : The titanium wizard is popped up even though there are only updates.
| 5 |
1,003 |
TISTUD-3106
|
01/03/2013 07:13:26
|
Retain ordering of build path entries
|
Build path entries are returned as a Set from the BuildPathManager, so order is not guaranteed. However, order is important because it determines the order we query the indices for entries. This order should be retained when we persist the entries, load them, iterate through them. This would also involve updating the build path entry UI to use an ordered list, allowing users to move entries up and down in the list.
| 8 |
1,004 |
TISTUD-3108
|
01/03/2013 08:43:31
|
Install specific SDK lists all SDKs installed when they are not
|
When trying to install specific SDKs using the Help > Install Specific Titanium SDK option, all SDKs are listed as installed regardless of the actual installed SDKs. Titanium Update still correctly checks for the newest stable release. This is a regression as this functionality works in Titanium Studio 3.0.2 Steps to reproduce: 1. Open Titanium Studio 2. Click Help > Install Specific Titanium SDK 3. Check Install from Update Stream. 4. Select a SDK from the drop down menu. Expected result: Studio should only grey out installed SDKs. Actual result: All SDKs are marked as installed regardless of what is really installed.
| 5 |
1,005 |
TISTUD-3109
|
01/03/2013 09:00:42
|
Install Titanium SDK: disable Finish button for installed sdks
|
When initially selecting "Intall from Update Stream" in the Install specific Titanium SDK wizard, the most current stable SDK is selected and the finish button lights up regardless of it's installed state. I would suggest that the finish button only light up for the initial selection if it is not installed. Clicking finish now downloads and installs the SDK without issue. This is not a regression as this happens in all current versions of Titanium Studio. Steps to reproduce: 1. Open Titanium Studio 2. Install a specific Titanium SDK (Help > Install specific Titanium SDK) 3. Select Install from Update Stream. Expected result: The initial selection is listed and the Finish button lights up if it is not installed. Actual result: The initial selection is listed and the Finish button lights up even when the SDK is listed as installed.
| 3 |
1,006 |
TISTUD-3115
|
01/03/2013 15:11:58
|
Denso: add checkbox to project creation wizard to enable automotive module
|
In the Denso version of Titanium Studio, add a checkbox "Automatically enabled automotive extension for this project" to the project creation wizard. It should be enabled and auto-selected when IVI platform is selected. When selected, Studio will automatically include the automotive module in project's tiapp.xml.
| 8 |
1,007 |
TISTUD-3117
|
01/03/2013 15:18:24
|
Add launch configuration for running on Denso/IVI emulator
|
Initially, the launch configuration tab could just contain a project field and an option to re-build project on launch. See the screenshot for an example of the Android emulator launch configuration tab.
| 5 |
1,008 |
TISTUD-3118
|
01/03/2013 15:20:03
|
Add launch configuration for running on Denso/IVI device
|
The launch configuration tab will just have a project field unless additional options are needed. See the screenshot for an example of the corresponding launch configuration tab for Android.
| 5 |
1,009 |
TISTUD-3119
|
01/03/2013 15:22:00
|
Add launch configuration for packaging Denso application
|
The launch configuration tab for now could contain just a project field and the distribution location. We will add more if more fields are required. See the screenshot for an example of our Android packaging's main tab.
| 8 |
1,010 |
TISTUD-3120
|
01/03/2013 15:58:23
|
iOS Simulator: console log level filter does not work
|
iOS Simulator console filter does not work, all levels are logged regardless of settings. Does not occur with debugger. This could be CLI-related. Steps to Reproduce: 1. Run code in Simulator (set run config log level to ERROR): {code} alert('SESSION ID: ' + Ti.App.sessionId); Ti.API.error('SESSION ID: ' + Ti.App.sessionId); Ti.API.trace('TRACE'); Ti.API.log('TRACE', 'TRACE'); Ti.API.debug('DEBUG'); Ti.API.log('DEBUG', 'DEBUG'); Ti.API.info('INFO'); Ti.API.log('INFO', 'INFO'); Ti.API.warn('WARN'); Ti.API.log('WARN', 'WARN'); Ti.API.error('ERROR'); Ti.API.log('ERROR', 'ERROR'); Ti.API.log('FREEFORM', 'FREEFORM'); {code} Actual Result: Console level is set to ERROR, but nothing is filtered. Expected Result: Console level is set to ERROR, and only ERROR messages print to console.
| 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.