issuekey stringlengths 8 11 | title stringlengths 16 187 | description stringlengths 10 20k ⌀ | storypoint int64 1 40 | split_mark stringclasses 1
value |
|---|---|---|---|---|
TISTUD-4689 | Projects: non-default project location in workspace generates existing project error | Projects: non-default project location in workspace generates existing project error. See screenshot. This does not happen in Titanium Studio 3.1.0. This appears to be a regression. Test Steps: 1. Open new project wizard. 2. Enter project name and app id. 3. Deselect 'use default location'. Result: ... | 8 | train |
TISTUD-4696 | Node.ACS Binding: disable OK button in import binding dialog if nothing selected | Node.ACS Binding: import binding dialog allow user to continue if nothing selected. See screenshot. Test Steps: 1. Create Mobile Project. 2. Right click and import Node.ACS Binding. Result: Menu appears and user can press 'OK' though nothing is selected and the action will have no result whatsoever. | 3 | train |
TISTUD-4698 | Alloy Editor: new model wizard allows multiple columns with same name | Alloy Editor: new model wizard allow multiple entries with same name, only last one is used. This ticket requests additional validation to the sql model wizard. See screenshots. Test Steps: 1. Open Alloy Project. 2. Add New > Model (sql) to invoke model wizard. 3. Add two entries with the same name. Re... | 3 | train |
TISTUD-4700 | Exception while debugging Node.ACS app | 1) Create a new Node.ACS app 2) Debug Local Node.ACS server The debug session failed on first launch with NullPointerException. The exception stack trace is captured in the attached log. | 5 | train |
TISTUD-4703 | NPE when creating an iOS packaging configuration from the configuration dialog | # Select a BlackBerry project (one that does not have an iOS target defined). # Open the packaging launch configuration dialog. # Double click to manually create a new "Apple iTunes Distribution" A Null Pointer Exception is thrown and surfaced to the UI. {code} java.lang.NullPointerException com.appcelerator.... | 3 | train |
TISTUD-4762 | Node.ACS: Windows: installation failure with bson error | *Problem* I'm using Windows 7 32bit and run Titanium as Administrator, when I check for titanium updates, and install Node.ACS ver1.0.2, an error message appears like this: {code}Error encountered during update Failed to install acs. Please see the Studio log for more information.{code} *Log* {code} !ENTRY co... | 8 | train |
TISTUD-4705 | Failure attaching Alloy templates while installing alloy 1.1.2 | I received an error dialog during installation of alloy 1.1.2 on Appcelerator Studio 3.1.1 RC. I did not have alloy already installed. After the install, it looks like alloy 1.1.2 installed fine, but the template hooks failed? Here's the log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-05-20 13:10:09.376 !MESSAG... | 5 | train |
TISTUD-4712 | Studio samples: check out the tagged version instead of master | Currently we always pull from the master branch when importing samples in Samples view. This creates a problem since the latest source in master may not be compatible with an earlier version of Studio. The suggestion is to tag the source in the sample repo, and we will checkout by the tagged version. We should fall bac... | 8 | train |
TISTUD-4714 | Run > BlackBerry Device: the name of the created launch config does not contain project name | After running Run > BlackBerry Device on a project, a launch config is created and appears in the recent history group under the Run menu; however, it does not contain " - <project_name>" as other created launch configs do. | 5 | train |
TISTUD-4715 | BlackBerry packaging wizard: the description just shows "OK" when the distribution location is selected | 1. Create a BlackBerry project; 2. Publish > Distribute BlackBerry; 3. In the ensuing wizard, select a valid directory. Now the description message shows "OK". I would expect it either to be empty or revert back the default description message when there is no error. | 3 | train |
TISTUD-4718 | BlackBerry: cannot run the created package or device launch configuration from configurations dialog | 1. Create a BlackBerry project; 2. Run Publish > Distribute - BlackBerry; 3. Open Publish > Configurations... dialog; 4. Select the created Titanium BlackBerry Packager launch configuration if it isn't selected. Expected result: "Run" button should be enabled to run the launch config without any change since ther... | 5 | train |
TISTUD-4727 | CodeProcessor: paths.commands and paths.hooks not set during 1.0.1-alpha install | h5. Description: While setting up for testing, I noticed that the code processor mention it has edited my ti config. Here is the output: {code} /usr/local/bin/titanium-code-processor -> /usr/local/lib/node_modules/titanium-code-processor/bin/codeprocessor > titanium-code-processor@1.0.1-alpha install /usr/local... | 5 | train |
TISTUD-4728 | Node.ACS: improve error message when login fails | Node.ACS Project: create fails with Internal error: ERROR object Object. {code} !ENTRY com.appcelerator.titanium.acs.ui 4 0 2013-05-21 15:03:20.891 !MESSAGE Internal error: [ERROR] [object Object] !STACK 1 org.eclipse.core.runtime.CoreException: [ERROR] [object Object] com.appcelerator.titanium.acs.internal... | 3 | train |
TISTUD-4734 | NPE loading rubles | I'm just seeing this in my installed copy of Eclipse with studio plugins from nightly on development branch. On startup I get an error dialog about an NPE. Here's what's in the log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-05-22 11:26:26.854 !MESSAGE An internal error occurred during: "Start Ruble bundle mana... | 3 | train |
TISTUD-4736 | Project Wizard: unsupported targets not automatically deselected | Project Wizard: unsupported targets not automatically deselected. See screenshot. Test Steps: 1. Invoke new Mobile Project Wizard. 2. Select an SDK that supports new targets (such as blackberry) and select that target. 3. Select an SDK that does not support new targets (such as 3.1.0). Result: BlackBer... | 5 | train |
TISTUD-4744 | Saving changes in tiapp.xml results in error message java.lang.NullPointerException | When making changes in tiapp.xml and saving it, the tiapp.xml is being updated. However, the error message is showing "save failed". I have not seen this issue before. | 3 | train |
TISTUD-4745 | Terminate a Node.ACS launch when terminating its thread | When manually terminating a Node.ACS debug session by clicking on the debug-stack threads (the ones that say "Remote node v0.8.22..." and "JavaScript Thread"), the launch state is not terminated. This forces the user to manually click the launch, and hit terminate again, before allowing the launch to be removed from t... | 3 | train |
TISTUD-4748 | Node.ACS Debugger: A problem while evaluating a stack-frame scope Failed to dispatch response to callback | Node.ACS Debugger: A problem while evaluating a stack-frame scope Failed to dispatch response to callback. {code} !ENTRY com.aptana.core 1 0 2013-05-22 14:32:18.899 !MESSAGE (Build 3.1.1.201305212055) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs-debug" "run" "-d" "/Applications... | 5 | train |
TISTUD-4751 | Linux: BlackBerry missing from the tiapp editor | Linux: BlackBerry missing from the tiapp editor. BlackBerry exists in the new project wizard, and the supported platforms list in ti info. See screenshot. Test Steps (Linux): 1. Create Alloy Project without BlackBerry selected as a target. 2. View TiApp Editor Overview after project is created. Result: ... | 3 | train |
TISTUD-4755 | Log: [ERROR] Unknown SDK tizen Unknown SDK mobileweb | Every time studio is loaded, these errors appear in the log: {code} !ENTRY com.appcelerator.titanium.mobile 4 0 2013-05-23 11:42:43.130 !MESSAGE (Build 3.1.1.201305222018) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK tizen !ENTRY com.appcelerator.titanium.mobile 4 0 2013-05-23 11:42:43.1... | 3 | train |
TISTUD-4756 | Alloy: clean install without restart Failed to add Alloy project templates | Clean install Studio with no node.js or alloy. Log: {code} !ENTRY com.appcelerator.titanium.alloy.ui 4 0 2013-05-23 12:06:10.353 !MESSAGE (Build 3.1.1.201305222018) [ERROR] Failed to add Alloy project templates !STACK 1 org.eclipse.core.runtime.CoreException: 'node' is not recognized as an internal or extern... | 5 | train |
TISTUD-4757 | Dashboard: Windows: samples import wizard cutoff at bottom | Dashboard: Windows: samples import wizard cutoff at bottom. See screenshots. Test Steps: 1. Dashboard > Samples > Import. Result: Window does not display cloud section. | 5 | train |
TISTUD-4759 | Node.ACS: Publish fails with database connection error App NodeACSProject already exists | Node.ACS: database connection error App NodeACSProject already exists. This does not affect Mountain Lion 10.8.3. Test Steps: 1. Create Node.ACS Project. 2. Publish > Deploy App. Result: Menu appears, see screenshot, fails to recreate app. Expected Result: No menu appears, app gets published. | 5 | train |
TISTUD-4780 | Node.ACS: should not allow create a method with space in the name | Test Steps: 1. Create or open existing Node.ACS Project. 2. Select New > Node.ACS Method. See results. Actual REsult: A new method appears using the correct name.The method (function) appears in services.js and it has error indication in it. The same thing is observed while adding Node ACS binding to any ty... | 5 | train |
TISTUD-4783 | The message for when the workspace is in use at Studio launch contains "{0}" instead of the actual path | This happens only in Studio 3.2.0. Attached the two screenshots to show the difference between 3.1.1 and 3.2.0 when the workspace is in use. | 5 | train |
TISTUD-4793 | 'Failed to save the signed in user error' is coming on Ubuntu 12.04 machine | Login to Titanium Studio. File > Restart. Actual Result:Credentials are not getting saved.logs attached. {code} !ENTRY com.appcelerator.titanium.core 4 0 2013-05-28 16:22:10.213 !MESSAGE (Build 3.1.1.1364101697) [ERROR] Failed to save the signed-in user !STACK 0 org.eclipse.equinox.security.storage.Stora... | 5 | train |
TISTUD-4796 | Node.ACS Debugger: Node.ACS JavaScript Exception Breakpoint does not work | ENVIRONMENT: Appcelerator Studio, build: 3.1.1.201305271814 ACS v1.0.2 OS X 10.7.5 REPRODUCTION: 1. Create a new Node.ACS project. 2. Replace the controllers/application.js with the following: {code} function index(req, res) { var err = new Error('Danger, Will Robinson!'); throw err; res.render('index... | 8 | train |
TISTUD-4799 | BlackBerry: Allow BB project creation with spaces in the app name | Right now Studio does not allow us to create an app with space or certain characters in the app name. This issue has been fixed from the sdk side & we can create apps with spaces & dot(.) in the app name using the CLI. | 3 | train |
TISTUD-4802 | LiveView: Clean project when unchecking LiveView in run configuration | If you first run an app with LiveView enabled, and then disable LiveView in the run configuration, the application may well be confused, since it's been modified to run with LiveView. Whenever a user unchecks the LiveView checkbox, we should clean the project before rebuilding. | 5 | train |
TISTUD-4803 | Node.ACS debugger stops at breakpoints that were defined on other Node projects | # Create two Node.ACS projects. # Set a breakpoint at line 3 on the app.js of project *A*. # Set a breakpoint at line 2 on the controllers/application.js of project *B*. # Launch a Node.ACS debug session on project *B*. Expected result: No breakpoint should hit. Actual: The application stops on the app.js. ... | 5 | train |
TISTUD-4816 | Tizen: 2.1 support: certificate location | In Tizen 2.1, there are some changes that may require additional Titanium Studio support. In 2.1, there is a new requirement to generate and use a security certificate, before one can build and deploy web apps. Previously, a default developer certificate was used automatically. In order to reference the certificate... | 8 | train |
TISTUD-4806 | Android Preferences: Default Google API and Screen not set when Android SDK Path selected | When I set the Android SDK path in the preferences, the default API and Screen types are not automatically set, but they are available. See screenshot. Logs void of content. Test Steps: 1. Install Android SDK r22.0.1 with Google APIs 2.3.3 only. 2. Switch to Staging network (where android 2.3.3 is the new ... | 3 | train |
TISTUD-4814 | Users upgrading to Studio 3.1.1 can't run new Android projects due to the 2.3.3 sdk requirement | Steps: 1. Run 3.0.0 Studio. Install the default Titanium SDK (3.1.0.GA) 2. Upgrade to 3.1.1 Studio. Install the default Titanium SDK (3.1.1) 3. Create a new Android project 4. Run in the Android emulator 5. An error message appears stating the minimum android sdk is 2.3 6. Go to the preferences and change the def... | 5 | train |
TISTUD-4819 | Node.ACS debugger debug view flickers when starting a session with an existing exception breakpoint | # Create a Node.ACS project # Add a Node.ACS JavaScript exception breakpoint from the 'Run' menu # Open the Breakpoints view and right click the breakpoint # Click the 'Breakpoint Properties' and check the 'Caught Exceptions' option. # Launch the debug session by right-clicking the project and selecting Debug As ->... | 8 | train |
TISTUD-4824 | SDKLocator intermittent failure on Linux when getting the latest version | This one came out of a failed unitest on Linux. The SDKLocator#getLatestVersion does not always return the correct latest version on Linux. | 5 | train |
TISTUD-4831 | Missing progress icon in the device launches dialog | This is a regression. The progress dialog we display when doing a debug on device, and test on device, had a moving animation of a progress image. This image is now missing (see attached screenshot). | 3 | train |
TISTUD-4832 | Windows: Studio Console: Node not recognized on clean install, must restart studio | Windows: Studio Console: Node not recognized on clean install, must restart studio. Test Steps: 1. Clean install Node.js. 2. Open Terminal view in Studio. 3. Type: node -v Result: {code} $ node -v sh: node: command not found {code} | 8 | train |
TISTUD-4841 | Node.ACS: app not removed when project deleted | Node.ACS: app not removed when project deleted. When a Node.ACS project is deleted, it needs to be removed from the acs service list. Note: The only case where an app is correctly prompted for removal is when the app has been deployed. Test Steps: 1. Create Node.ACS Project. 2. Delete Node.ACS Project. ... | 3 | train |
TISTUD-4846 | Android Emulator Run Configuration: preferences hyperlink is mislabeled and non-functional | Android Emulator Run Configuration: preferences hyperlink is mislabeled and non-functional. The preferences hyperlinks for android packaging and run on device are correctly labelled and functional. See screenshots. Test Steps: 1. Create a new android emulator run config. Result: Preferences hyperlink ... | 5 | train |
TISTUD-4847 | Android SDK 2.2: launching invalid config fails to launch android sdk installer | Android SDK 2.2: launching invalid config fails to launch android sdk installer. This occurs when the new minimum android sdk is not installed. Test Steps: 1. Launch Android Emulator Google APIs 2.2 using Studio 3.1.1+. 2. Agree to update to current supported android sdk minimum version. Result: Operati... | 5 | train |
TISTUD-4850 | Dashboard: Configure: Android: update default android sdk to 22.0.1 | Update default dashboard config android sdk to Android SDK: r22.0.1 Test Steps: 1. Dashboard > Configure > Android. Expected Result: Android SDK: r22.0.1 is downloaded. | 3 | train |
TISTUD-4853 | Android: App log messages aren't getting filtered | Steps: 1. Enable all logging in the Console 2. Launch a project in the Android emulator Expected: App output should display messages that are formatted and can be filtered Actual: messages are displayed as follows: {code} D/AppLoads( 385): this.me is null D/CrittercismAPI( 385): POSTING JSON DATA: url = ... | 5 | train |
TISTUD-4854 | iOS Simulator: console ignores log level during build | iOS Simulator: console ignores log level during build. Test Steps: 1. Create Alloy project. 2. Run in iPhone Simulator with log level set to info. Result: Trace and Debug log to console. See screenshot and log. Sample Code: {code} var win = Ti.UI.createWindow({ backgroundColor : 'blue' }); ... | 5 | train |
TISTUD-4858 | iOS Packaging Run Config: 'Upload debug symbol' checkbox deactivates 'Run' option | This does not occur 3.1.1. Test Steps: 1. Package iOS App (Ad-Hoc or iTunes). 2. Goto Configuration >> New Configuration and select the 'Upload debug symbol option' Actual Result: 1. 'Run' option is active before selecting the 'Uploading debug symbols' checkbox. 2. 'Run' option is disabled after selecting... | 5 | train |
TISTUD-4861 | Liveview: No license information presented during plugin install | h5. Description: When installing the plugin for liveview via the RC instructions, no license text is presented. h5. Steps to reproduce: 1) Navigate to http://preview.appcelerator.com/appc-studio/ 2) Install the RC plugin via the help > install new software option 3) Click the "more" link in the lower right on th... | 3 | train |
TISTUD-4864 | App launched using manually created launch configuration does not reflect logging level | 1. Create launch configuration from Launch configuration wizard for iOS/Android. 2. Modify the logging level to Warn. 3. Launch the app on simulator/emulator and the console still logs the output for Trace level. However, if the app is run using launch shortcut, then the logging level is correctly reflected in Con... | 8 | train |
TISTUD-4882 | Debug and Profile on Device: Android and iOS: log level changes not respected in console | Debug on Device: Android and iOS: log level not respected. This does not appear to be a regression. The builds are launched with log level 'TRACE': {code} "/usr/local/bin/titanium" "--no-colors" "--no-prompt" "build" "--platform" "ios" "--sdk" "3.1.1.v20130604110432" "--log-level" "trace" "--target" "device" ... | 8 | train |
TISTUD-4886 | Make user friendly alert for cancelling SDK installation process | Test Steps: 1.Launch Studio. 2.Help > Install Titanium SDK > Install from URL > add the URL . 3. Wait til installation process begins. 4. Cancel the process before completion. Expected Result: Error should be user friendly. Screenshot attached.Logs attached. | 3 | train |
TISTUD-4890 | Node.ACS Debugger: intermittent fail to connect with Premature end of file | Node.ACS Debugger: intermittent fail to connect with Premature end of file. Occurs 1/6 times, could be related to TISTUD-4747, as they seem intertwined. Test Steps: 1. Create default Node.ACS Project. 2. Debug multiple times in a row with a breakpoint in app.js line 3. Result: Error in UI and log. {c... | 8 | train |
TISTUD-4896 | "Remove Node.ACS App" message when terminating a Node.ACS debug session | Does not affect 3.1.1. Change introduced by TISTUD-4841. This looks like a regression that was introduced after we implemented this dialog. The Node.ACS debugger is creating a temporary Node.ACS project when launched in debug mode. When the session is terminated, that project is being deleted, and that's when we ge... | 5 | train |
TISTUD-4897 | Profiler: upload debug symbols exists in the run config, serves no purpose | Profiler: upload debug symbols exists in the run config, serves no purpose. See screenshot. Test Steps: 1. Profile on iOS Device. Results: Note the upload debug symbols option. | 3 | train |
TISTUD-4903 | Node ACS project contains Syntax error: unexpected token in the run.js.chromium file | Test Steps: 1. Create Node ACS project 2. Launch debugger session for the respective project Actual Result: 1. 'Label Jobs' error message pop up is displayed. 2. Syntax error: unexpected token in the run.js.chromium file Please refer the attached screen shot and log file for more details. | 5 | train |
TISTUD-4906 | Code Analyzer: Warning or Error icons are not displayed in code gutter | h5. Problem description After running the Code Processor, results Warnings or Errors are not correctly displayed as Icons next to the code in the Project Files, as described here: https://wiki.appcelerator.org/display/tis/Code+Analyzer#CodeAnalyzer-InterpretingtheResultsintheProjectFiles h5. Steps to reproduce ... | 5 | train |
TISTUD-4917 | Code Analyzer: Alloy: When a Warning or Error is found for an Alloy project, code gutter icons are added to the Resources project files, not to App folder | h5. Problem description When a Warning or Error is found by the Code Analyzer for an Alloy project, Warning or Error icons are placed in the code gutter in the Resources file projects instead than in the App file projects. The result is that the Project is now marked with the red/white error icon and the 'Errors in Wo... | 8 | train |
TISTUD-4918 | Tizen: Tizen target greyed out | Description: 1. First make sure you have the tizen 2.1 sdk installed & have configured tizen sdk in the studio 2. Go to create new app in titanium or appcelerator studio 3. Select the appropriate type of app e.g classic or alloy 4. Notice the tizen deployment target Actual result: 1. The tizen target is greyed ... | 5 | train |
TISTUD-4919 | Update Dashboard with the Tizen mininum SDK version as 2.1 | As the minimum version of Tizen SDK supported by Studio is 2.1, Studio's dashboard should be updated to refer to the minimum version of Tizen SDK as 2.1 instead of 2.0 | 3 | train |
TISTUD-4923 | Samples: Folder context menu has single non-functional import item that fails silently | In the sample pane within studio, it's possible to right-click on the folder for either "Field Service" or "Appcelerator" sample folders and get a contextual menu with a single option "Import sample as project ". Choosing this fail to do anything, and does not notify the user of any failure or success. Test steps: ... | 5 | train |
TISTUD-4926 | Can't terminate iOS Simulator process from the console | Can not terminate iOS Simulator process Step 1: In Studio debug any app as iOS Simulator, it starts the iOS Simulator as it should. Step 2: Click terminate (red square button). Step 3: notice the process will look like it has been terminated in Studio but the Simulator will not terminate. Looks like only switch... | 5 | train |
TISTUD-4932 | Node.ACS Debugger: breakpoint not hit from app.js start method | Test Steps: 1. Create or use existing Node.ACS Project. 2. Insert a breakpoint in app.js at line no. 3. 3. Debug project. See results. Actual Result: Neither Debug perspective is not launched nor is the breakpoint hit. Please refer the attached console and log file for more details. | 5 | train |
TISTUD-4934 | Debug and Profile on Device: Android and iOS: log level intermittently not respected in console on launch | This is a clone of TISTUD-4882 to address possible related problematic behavior. Debug on Device: Android and iOS: log level not respected. Sometimes the old console log level is used instead of trace. Note this ticket might be invalid, as we might actually want to use the existing console level. Also note ... | 5 | train |
TISTUD-4950 | Configuration: Add the Alloy assets paths as part of the Studio search for an App image | After importing the Field Service project from the studio sample pane, the 'TI.FieldService'Configuration error was detected, which explains that image cannot be located. Appcelerator Studio, build: 3.1.1.201306112353 Titanium SDK, buld: 3.1.1.v20130611153550 Mac osx 10.8.4 Mountain Lion | 5 | train |
TISTUD-4951 | Switching Android SDK path results in an NPE | Steps to Reproduce: 1. Go to Preferences > Studio > Platforms > Android 2. Switch the Android SDK path Expected Result: Should switch without any errors Actual Result: The SDK switches fine, but I get a pop up saying there is an NPE. | 3 | train |
TISTUD-4956 | Studio contributions to Customize View should have consistent names | We have two contributions: one for hiding the build folder and one for hiding the Resources folder for Alloy projects. Their names are inconsistent in Appcelerator Studio, one "Appcelerator Build Folders" and one "Titanium Resources Folder". The latter should be "Appcelerator Resources Folders" to keep the branding and... | 2 | train |
TISTUD-4964 | Module creation wizard UI is messed up | This is probably as a result of the latest refactoring. See screenshot. There are two iOS radio options, and the MobileWeb option is not at the right place. | 5 | train |
TISTUD-4965 | Missing string translation in the iOS Module creation wizard | See attached screenshot. This one is probably related to the latest refactoring, and to TISTUD-4964. When clicking the first iOS option, the status error indicates that a string translation is missing. | 3 | train |
TISTUD-4967 | NPE while launching app on iPad simulator | Launch/Profile Field Service app on iPad simulator and the launch throws an NPE error dialog : java.lang.NullPointerException org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:125) org.eclipse.core.internal.runtime.InternalPlatform.getStateLocation(InternalPlatform.java:546) org.ecli... | 3 | train |
TISTUD-4970 | Blackberry SDK not recognized in Dashboard | * Set a valid path for Blackberry SDK (version 10.0.0.9) in Preferences. * Refresh/open the dashboard - it does not recognize the valid blackberry SDK path in the preferences. | 5 | train |
TISTUD-4971 | No provisioning profiles shown in run-on-iOS-device launch configuration | When manually creating a launch configuration for profiling on iOS device, I saw the provisioning profiles combo box is empty, and the same applies to running on iOS device as well. The iOS preference page does show the list correctly. | 5 | train |
TISTUD-4974 | MobileWeb Packaging: recent launch fails to appear in list after run | MobileWeb Packaging: recent launch fails to appear in list after run. However, the mobileweb packaging run config is created properly. All other deployment options/run configs for every other platform and runtype work correctly. See screenshots. Test Steps: 1. Package for MobileWeb using Deployment UI (Pack... | 5 | train |
TISTUD-4978 | Submit Ticket: Windows: some characters produce error illegal unquoted character code 13 | h3. Steps to Reproduce Submit Ticket option shows error when we add numbered steps in "steps to reproduce" section. But it works fine on other cases.See screen shot 1.select help option 2.Select Submit ticket option 3.edit numbered steps in "steps to reproduce section" 4.submit h3. Actual Result "Failed ... | 5 | train |
TISTUD-4977 | Add os platform filter to ios plugins/fragments | We used to guard for Mac OS only in code throughout our codebase for showing/validating iOS platform support. What we should really be doing is limiting the installation of the plugins/fragments for iOS to only get packaged and used on Mac. This will reduce the IDE size on non-Mac OSes (both download and on-disk). | 5 | train |
TISTUD-4994 | Node.ACS exception breakpoint debugging: Enable "Caught Exception" by default | Currently user needs to enable the setting manually after adding Node.ACS exception breakpoint via Run > Add Node.ACS JavaScript Exception Breakpoint; otherwise they would not see the exception getting hit. We should enable it by default. | 3 | train |
TISTUD-4997 | ResourceException when a project is closed | # Create a project (for example, a Node.ACS project) # Close the project (right click -> Close) These error were found in the log: {code} !ENTRY com.aptana.editor.common 4 0 2013-06-18 16:47:02.980 !MESSAGE (Build 3.1.2.201306171542) [ERROR] Resource '/Node-4670' is not open. !STACK 1 org.eclipse.core.inter... | 3 | train |
TISTUD-4998 | Closed Node.ACS project error when updating client's server URLs | # Create a Node.ACS project # Close the project (right-click -> Close) After a while, an error dialog appears (see screenshot). Nothing much in the log, but the error dialog indicates a problem while updating the client's server URLs. | 3 | train |
TISTUD-5003 | NPE in the log when getting the latest SDK release while Studio is shutting down | Spotted this one on my log: {code} !ENTRY org.eclipse.core.jobs 4 2 2013-06-19 12:11:54.458 !MESSAGE An internal error occurred during: "Checking for new Appcelerator Updates...". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.update.TitaniumSDKUpdater.getLatestSDKRelease(TitaniumSDKUpdater... | 3 | train |
TISTUD-5004 | Sort the Android SDK versions in the Android installer and App Store distribution launch configuration pages | This is a regression introduced by TISTUD-1534. The "Android SDK Version" drop-down in the Application installer and the App Store distribution launch configuration tabs is displaying the Android SDK version in an un-sorted way (unlike the sorted display under the "Emulator" configuration page). We should sort th... | 3 | train |
TISTUD-5007 | OAuth key and OAuth secret for Dev and Prod need to be listed in Studio->TiApp.xml | OAuth key and OAuth secret for Dev and Prod need to be listed in Dashboard->ACS and in Studio->TiApp.xml In Studio tiapp.xml we have a link to show cloud keys and it displays one key for dev and one key for prod (see screen shot). When developing Node services that connect to ACS you need OAuth key and OAuth secr... | 5 | train |
TISTUD-5012 | BlackBerry: update platform strings to current format | Currently they are spelled 'Blackberry' and 'Mobile Web'. The convention is to spell them 'BlackBerry' and 'MobileWeb'. Test Steps: 1. Invoke Code Processor context menu (or invoke the project run-menu drop-down). Result: Spelling errors. See screenshots. | 3 | train |
TISTUD-5016 | Dashboard: 3.2.0 dashboard missing ios | Dashboard: 3.2.0 dashboard missing ios. Seems to only affect 3.2.0. Test Steps: 1. Open dashboard Get Started. Result: iOS absent. See screenshot. No logs. | 5 | train |
TISTUD-5020 | Diagnostic Log: reset log focus to the top when run | Diagnostic Log: reset log focus to the top when run. When diagnostic log is run, the focus is at the bottom of the log, making it inconvenient to view, the user must manually scroll to the top. See screenshots. Test Steps: 1. Run diagnostic log. Result: Results appear at the bottom of the log. Expe... | 3 | train |
TISTUD-5029 | Support CoffeeScript syntax coloring | h2. Problem After updating to Titanium Studio build: 3.1.1.201306112235, none of my .coffee files has syntax highlighting anymore. Syntax highlighting for .js files is unaffected. This seems to be a regression. h2. Test case Open any .coffee file. | 3 | train |
TISTUD-5032 | Project Wizard: wizard resizes when alloy loads | Project Wizard: wizard resizes when alloy loads. See video. Test Steps: 1. Create new alloy project. Result: Notice wizard resizes when first invoked. Expected Result: Excellent user experience. | 5 | train |
TISTUD-5035 | NPE: TiAppEditor.java:143 | I created a project, deleted it, then created another project and got an npe somewhere inbetween. {code} !ENTRY org.eclipse.ui 4 0 2013-06-26 12:00:14.634 !MESSAGE Unable to create editor ID com.appcelerator.titanium.ui.ide.tiappEditor: An unexpected exception was thrown. !STACK 0 java.lang.NullPointerException ... | 3 | train |
TISTUD-5039 | The error mark next to deployment target in mobile project wizard could be improved | It's nice that we are now providing additional info on why a platform is disabled in new mobile project wizard. However, the position of the error mark is misleading. For example, in the screenshot attached, it's easy to think Android and Mobile Web are having configuration errors, not BlackBerry and Tizen. The error m... | 5 | train |
TISTUD-5040 | Run/Debug/Profile/Test menu actions are all disabled when the view is not in focus | 1. Create a new mobile project; 2. In Project or App Explorer, select Run > iPad Simulator from the local toolbar; 3. The console view should now take focus since it's outputting logs; if not, click on the Console view to make sure it has the focus; 4. Click on Run again in Project Explorer. Actual result: the me... | 5 | train |
TISTUD-5045 | Run Configuration dialog: new iOS device and publishing launch configurations take some time to load and freeze UI | 1. Open Run > Run Configurations... dialog; 2. Double click on Appcelerator iOS iTunes Distribution. Expected behavior: the launch configuration is created right away and its UI appears. Actual behavior: it takes a few seconds or longer, depending on how many certificates and provisioning profiles you have, for ... | 5 | train |
TISTUD-5046 | New Mobile Module Project wizard: The text when hovering over the warning icon is not very user friendly | It's nice that in the new module project wizard, a warning icon is now displayed for disabled platform. However, when hovering over the one for Android, the text contains "<a href=..." instead of displaying a friendly text that links to the url. | 2 | train |
TISTUD-5047 | Update Eclipse base to 4.3 | Eclipse 4.3 is officially released. We should update the Eclipse base on hudson from 4.3 M7 to 4.3 and update the builds to point to it and use the appropriate launcher jar. | 5 | train |
TISTUD-5049 | Cannot package iOS AdHoc app | # Create a new app with an iOS deploy target # Click to deploy (package) it as AdHoc Result: {code} Titanium Command-Line Interface, CLI version 3.1.1, Titanium SDK version 3.2.0.v20130628134044 Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/... | 3 | train |
TISTUD-5052 | When "missing semicolons" option is set to Ignore, no related marker should appear in the editor | This appears to be an edge case failure with the implementation of TISTUD-3601. When Preferences > Studio > Validation > JavaScript Syntax Validator > Options > Missing semicolons is set to "Ignore", we are still displaying a marker, when the expected result is to not show a marker at all. | 3 | train |
TISTUD-5055 | Provisioning profile not recognized in iOS device launch configuration | Steps to reproduce : 1) Open Launch configuration wizard 2) Create a launch configuration for Run -> iOS Application Installer or iTunes Distribution The provisioning profile is not available though it is already configured on the machine. The same launch configurations on 3.1.2 are displaying provisioning profi... | 3 | train |
TISTUD-5058 | Add git fetch support | Add support for git fetch. {{git fetch <remote>}} Treat like push to remote in terms of UI/handling: show popup menu/children for remotes, if only one just fetch from it without prompting. | 5 | train |
TISTUD-5059 | Support "advanced" git pull specifying remote and/or branch(es) | Add support for git pull with additional arguments. {{git pull <remote> <branch>}} May want to ignore branch argument and assume current branch. Pop a menu with list of remotes to pull from? git pull effectively does fetch + merge (or fetch + rebase depending on config). | 8 | train |
TISTUD-5060 | Add support to create github pull requests for current branch | Currently a user has to break their workflow by going into the browser to generate a pull request. It'd be nice if we could add a command to do that for the user. If the current branch doesn't exist on origin, push to origin. Executes API call to request pull against upstream http://developer.github.com/v3/pulls... | 13 | train |
TISTUD-5061 | Add support to create github forks | We don't easily support a common github workflow of creating a fork of a repo and then cloning it (we just support clone). We may want to add a command or import wizard that allows a user to specify a repository to fork, then we call the Github API to fork to their account (or org? May need to prompt for where to fo... | 13 | train |
TISTUD-5063 | Node.js: update to Node.js 0.10.13 | Node.js: update to Node.js 0.10.12 | 3 | train |
TISTUD-5064 | No menu items appear under Run/Debug/etc when an invalid Android SDK path is set in preferences | 1. Open Preferences > Studio > Platforms > Android; 2. In the Android SDK home, enter a path that exists but doesn't contain any Android SDK; Another way to get into this state is to remove the path completely, go to Dashboard to install from Android install manager, and then quit before installing a valid SDK. 3. Se... | 3 | train |
TISTUD-5067 | Re-use Android "device" launch config type for "profile" mode | Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be usi... | 5 | train |
TISTUD-5068 | Re-use Android "device" launch config type for "test" mode | Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be usi... | 5 | train |
TISTUD-5069 | Re-use Android "device" launch config type for "debug" mode | Every time we added a new mode for a platform, we generated new launch config types. We shouldn't need to do this, and should instead be able to simply add a new launch delegate, shortcut, config tab for the new mode. We typically have a "device" and "simulator" launch config type for each platform. We should be usi... | 5 | train |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.