issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-3162
|
ACS: improve login progress message to have correct spelling and meaning
|
ACS: improve login progress message to have correct spelling and meaning. See screenshot. Ill-formatted message reads: 'Register as apps with ACS'. Should probably read: 'Register app with ACS' or 'Register as app with ACS'. Steps to Reproduce: 1. Create Titanium Project with ACS enabled. 2. If ACS login prompt appears, view progress indicator text. Actual Result: Ill-conceived message. Expected Result: Perfectly spelled message with laser-sharp grammar and meaning.
| 3 |
train
|
TISTUD-3164
|
Wiki Docs: update command line docs to include -D
|
Wiki Docs: update command line docs to include -D. https://wiki.appcelerator.org/display/tools/Available+Command-Line+Options The -D is not currently documented and is required for the arguments to work.
| 1 |
train
|
TISTUD-3165
|
CLI: cannot use cli when offline
|
Cannot use CLI offline. Error: {code} Titanium Command-Line Interface, CLI version 3.0.22, Titanium SDK version 3.0.1.v20130104113203 Copyright (c) 2012, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ [ERROR] Missing required option "--username" [ERROR] Missing required option "--password" {code} Steps to Reproduce: 1. Open Titanium Studio. 2. Go offline. 3. Create Titanium Project. 4. Run Titanium Project. Actual Result: Error. Expected Result: Project creation and deployment without error.
| 5 |
train
|
TISTUD-3166
|
Titanium Updates doesn't show Node.ACS on a clean machine
|
Test Steps: 1. Close Titanium studio if its already opened. 2. On the terminal I have used following commands for testing : sudo npm uninstall acs -g sudo npm uninstall alloy -g sudo npm uninstall titanium -g sudo npm uninstall npm -g Also I have removed Nodejs forcefully . 3. Launch Titanium Studio. 4.Check for titanium updates. Observation: ACS prompt is not available while Node, alloy and cli prompts are available.
| 3 |
train
|
TISTUD-3167
|
Cannot add provisioning profiles to Studio
|
h3. Issue Cannot select or add provisioning profiles in Studio This issue is related to https://jira.appcelerator.org/browse/TISTUD-3064 The customer has the latest stable version but is still having the same issue. We have already tried the following: 1. Revert studio to old version and then upgraded. Also tried the nightly build. 2. Reinstall Studio 3. Downloaded new profile 4. Also, checked for openssl modules as per this blog http://developer.appcelerator.com/blog/2012/12/titanium-studio-3-0-1.html Will attach the log file soon.
| 8 |
train
|
TISTUD-3169
|
Node.JS: update version validation to node.js installer
|
Node.JS: add version validation to node.js installer. If an out-dated version of node.js is installed, studio will not recognize and prompt to re-install node.js in the titanium updates menu. Depending on the out-dated version of node.js installed, alloy and other titanium plugins will fail to install without proper notification. Terminal Diagnostic: {code} DHydeMBP:~ dhyde$ node -v v0.6.1 DHydeMBP:~ dhyde$ npm -bash: npm: command not found {code} Titanium Documentation: https://wiki.appcelerator.org/display/guides2/Titanium+Compatibility+Matrix#TitaniumCompatibilityMatrix-Node.js {code} Node.js To run all Appcelerator components, you must have Node.js 0.8.13 or later. The 0.9 (development) builds are not supported. If you don't have Node installed, install it from: nodejs.org {code} Steps to Reproduce: 1. Uninstall Node.js and node modules (alloy, etc). 2. Install old Node.js (see docs above and http://nodejs.org/dist/). 3. Open Titanium Studio and Check for Titanium Updates. Actual Result: Node.js does not show up. Other titanium plugins fail to install. Expected Result: Node.js should show up and update to latest version.
| 8 |
train
|
TISTUD-3170
|
Node.JS: improve titanium updates release notes documentation
|
Node.JS: improve titanium updates release notes documentation. Currently there is a blank page. It would be helpful to at least have a documentation link to node.js (e.g., http://nodejs.org/). Steps to Reproduce: 1. Uninstall Node.js. 2. Open Titanium Studio. 3. Check for Titanium Updates. Actual Result: Node.js entry has a blank page. Expected Result: Some description of the form or purpose of Node.js (i.e., a documentation link http://nodejs.org/ or simple statement of some kind https://wiki.appcelerator.org/display/tis/Node.js+Development).
| 5 |
train
|
TISTUD-3172
|
Node.js: update to v0.8.17
|
Node.js: update to v0.8.17. Current hosted version is v0.8.14. Minimum supported is: v0.8.13 See story for more information: TISTUD-3171
| 5 |
train
|
TISTUD-3173
|
Android Preferences: Android SDK not recognized due to non-numeric Titanium SDK
|
Though the Android SDK is installed correctly, Studio starts reporting that the Android SDK is not configured correctly. The problem also occurs when Studio is updated to latest 3.0.2 release and it happens on development as well.
| 8 |
train
|
TISTUD-3189
|
GitHub clone repo should support http connections
|
When listing the available git hub repos, they are connected using the ssh method via [email protected] connection. The connection should have an option of using http, which in that case will use the github credentials. The issue here is I don't connect to github using ssh, I use http. So I get an error when I try to clone the repo
| 8 |
train
|
TISTUD-3187
|
Github login shouldn't display success dialog
|
Steps: 1. Use Import->Git Repo as projects 2. Enter the github credentials and click validate Expected result: The login is successful and the UI is displayed as expected Actual results: A login success dialog appears. The user closes the dialog and the UI is displayed as logged in The login message is unnecessary since the UI reflects that the login was successful. If there was an error with the login, it should be displayed as an dialog error
| 5 |
train
|
TISTUD-3193
|
"Screenshots" Field should be renamed as "Attachments" in "Submit a Ticket" screen in studio
|
Steps to Reproduce 1. Choose Help > Titanium Studio > Submit Ticket. 2. Attach css, html, etc any type of file Actual Result All attachments of any type gets attached. Expected Result One is able to attach only jpeg or png type files for "Screenshots" field. Or The field should be renamed as Attachment to provide more options to the users.
| 2 |
train
|
TISTUD-3220
|
Mobile Web: Build for Emulator does not appear in Windows 8
|
While testing TISTUD-3089 on Windows 8 in Titanium Studio, build: 3.1.0.201301151536 I ran into an issue where after running a project in Mobile Web in Browser test the Menu option for Mobile Web in Emulator option disappears from the Run drop down menu in the App Explorer view. Steps to reproduce: 1. Open a Mobile Web project 2. Run the project in a Browser (Run > Mobile Web Preview in a Browser) 3. Open the Run menu from the App Explorer view. Expected result: Both the Mobile Web Preview in Browser and Mobile Web Preview in Emulator are present. Actual result: Only Mobile Web Preview in Browser is present.
| 8 |
train
|
TISTUD-3245
|
Add CLI command support for building an Denso project
|
We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build [--platform=[ivi]] [--package] [--device] [--emulator] [--production] [--development] [--verbose [0-5]] [project-dir] {code}
| 8 |
train
|
TISTUD-3246
|
Add CLI command support for packaging Denso applications
|
Add support for the packaging command via the CLI extension. {code} titanium build --package --platform=[platform] [project.dir] {code}
| 8 |
train
|
TISTUD-3247
|
Add CLI command support to run a Denso project
|
{code:title=V2|borderStyle=solid} titanium build --platform=[platform] --emulator=[emulator.name] [project-dir] titanium run --platform=[platform] --emulator=[emulator.name] [project-dir] {code}
| 8 |
train
|
TISTUD-3248
|
Add Publish > Package - IVI menu action in App and Project Explorer
|
The action will invoke a wizard that contains the same fields the packaging launch configuration tab has (TISTUD-3119) except for the project field.
| 8 |
train
|
TISTUD-3249
|
Add Run > IVI Emulator menu action in App and Project Explorer
|
The action will create the launch shortcut for the corresponding launch config from TISTUD-3117 and directly install the app on IVI emulator without an additional wizard. The menu should only appear when the IVI platform is enabled in project's tiapp.xml.
| 5 |
train
|
TISTUD-3251
|
Add Run > IVI Device menu action in App and Project Explorer
|
The action will create launch shortcut based on the launch configuration defined in TISTUD-3118 and install the app on IVI device. The menu should only appear when the IVI platform is enabled in project's tiapp.xml.
| 5 |
train
|
TISTUD-3254
|
Add Tizen as a deployment target choice in the Titanium project wizard
|
We should show Tizen as a checkbox in the deployment targets section of Titanium project creation wizard. The checkbox should only be enabled if user specified the Tizen SDK location in the preferences page and the selected Titanium SDK version has Tizen support. Please see https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on the Tizen-enabled CLI.
| 8 |
train
|
TISTUD-3255
|
Add Tizen as a deployment target in tiapp.xml
|
The checkbox should only be enabled when user specified the Tizen SDK location in the preferences page and the selected Titanium SDK has Tizen platform support.
| 5 |
train
|
TISTUD-3256
|
Add a preference page for Tizen platform
|
The preference page node will be under Titanium, and the content will contain a field for the Tizen SDK location and a browse button. It should validate the path and generate TizenSDKLocator from it. The Tizen SDK could be downloaded at https://developer.tizen.org/downloads/sdk.
| 13 |
train
|
TISTUD-3257
|
Add launch configuration for running on Tizen 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 |
train
|
TISTUD-3258
|
Add launch configuration for running on Tizen 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 |
train
|
TISTUD-3259
|
Add CLI command support to run a Tizen project
|
{code:title=V2|borderStyle=solid} titanium build --platform=[platform] --emulator=[emulator.name] [project-dir] titanium run --platform=[platform] --emulator=[emulator.name] [project-dir] {code} See https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on downloading and running Tizen-enabled CLI.
| 8 |
train
|
TISTUD-3260
|
Add CLI command support for building an Tizen project
|
We should try call "build" again when we've cleaned all our projects and build automatically is checked. The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed. {code} titanium build [--platform=[tizen]] [--package] [--device] [--emulator] [--production] [--development] [--verbose [0-5]] [project-dir] {code} See https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on installing a version of CLI that supports Tizen.
| 8 |
train
|
TISTUD-3261
|
Add CLI command support for packaging Tizen applications
|
Add support for the packaging command via the CLI extension. {code} titanium build --package --platform=[platform] [project.dir] {code} See https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on downloading and running Tizen-enabled CLI.
| 8 |
train
|
TISTUD-3262
|
Add launch configuration for packaging Tizen 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 |
train
|
TISTUD-3263
|
Add Run > Tizen Emulator menu action in App and Project Explorer
|
The action will create the launch shortcut for the corresponding launch config from TISTUD-3257 and directly install the app on Tizen emulator without an additional wizard. The menu should only appear when the Tizen platform is enabled in project's tiapp.xml.
| 5 |
train
|
TISTUD-3264
|
Add Run > Tizen Device menu action in App and Project Explorer
|
The action will create launch shortcut based on the launch configuration defined in TISTUD-3258 and install the Tizen app on device. The menu should only appear when the Tizen platform is enabled in project's tiapp.xml.
| 5 |
train
|
TISTUD-3265
|
Add Publish > Package - Tizen menu action in App and Project Explorer
|
The action will invoke a wizard that contains the same fields the packaging launch configuration tab has (TISTUD-3262) except for the project field.
| 8 |
train
|
TISTUD-3281
|
Running Mobile Project throws error while running on browser or emulator
|
Works fine with SDK: 3.0.GA or previous versions 3.0.1.v20130115150204 on browser but throws error on 3.0.1.v20130115150204 & 3.0.1.v20130111165328 version when run on emulator. Steps To Reproduce: 1. Create Mobile Web Project. 2. Run the project in Browser or emulator. Actual: Error appears [Refer Screenshots] For Running in Browser refer mobPrjBrowser.png and ConsoleLog file For Emulator error refer error.png and StudioLog file Expected: Project must run without any error
| 5 |
train
|
TISTUD-3272
|
Allow creating iOS project with app id that starts with numbers
|
In 3.0.1/3.0.2, when user creates a project with app id say "test.12", we did not show an error unless Android platform is selected, and that is the correct behavior. But in 3.1.0, we show an error when only iOS or Mobile Web platform is selected, even though such format is valid for them.
| 8 |
train
|
TISTUD-3279
|
FTP: "java.lang.NullPointerException" error is coming when opening a file
|
Precondition: FTP setup should be done. (http://appcelerator.testlodge.com/projects/1313/test_plans/3057) Connection Manager should have a FTP connection. Test Steps: 1.Create a Titanium Project and link the FTP connection from above. 2.In Project Explorer, open the Connections node of the project with the FTP connection. 3.Launch Connection window by doing double click on the FTP connection listed in the project's connections node (Project > connection > connection site) 4.Right click >OPEN on any file available on SOURCE side. Expected Result: File should be opened in the correct Titanium Studio editor. Actual Result: "java.lang.NullPointerException" error is coming when opening a file Screenshot and logs attached.
| 5 |
train
|
TISTUD-3283
|
Prompted to install NodeJS on a clean Titanium Studio startup even though it's already installed
|
I started up Titanium Studio in a dev workspace of eclipse. On startup I was prompted to install a number of things including NodeJS. On the second page I was asked to Install or set the path manually. I already had Node installed in it's standard {{/usr/local/bin/node}} location. My installed version is 0.8.3, the new version is 0.8.17. I'm guessing it's trying to update Node, but if that is the case it shouldn't be prompting "Install/Set path manually" in a second page.
| 5 |
train
|
TISTUD-3285
|
Format TSS files
|
Add formatting support to TSS files after parser is created. We could copy from JSON formatter and extend. Here is an example of formatted TSS file: {code} "Window": { backgroundColor: "#fff" }, "Label": { width: Ti.UI.SIZE, height: Ti.UI.SIZE, color: "#000", font: { fontSize: 20, fontFamily: 'Helvetica Neue' }, textAlign: 'center' } {code}
| 8 |
train
|
TISTUD-3286
|
Prompted to install/update Titanium SDK I already have installed
|
I keep getting prompted to install Titanium SDK 3.0.0GA, but I already have it installed. At first I did not, but had a 3.0.1 build (which is newer). I thought I shouldn't have gotten prompted since what I had was newer, but accepted and let 3.0.0GA get installed. On restart I'm still getting prompted to install 3.0.0GA even though it is installed.
| 5 |
train
|
TISTUD-3288
|
Connection: "java.lang.String cannot be cast to com.aptana.ide.core.io.IConnectionPoint" error is appearing
|
This is not a regression bug.This is existing in 3.0.1 Precondition: No FTP connection should be added. Test Steps: 1.Create a Titanium Project. 2.In Project Explorer, double click on the Connections node of the project. 3.Click on the 'remove' icon (press OK) and then 'add' icon. Expected Result: No error should occur. Actual Result: "java.lang.String cannot be cast to com.aptana.ide.core.io.IConnectionPoint" error is appearing.Logs and screenshot attached.
| 5 |
train
|
TISTUD-3291
|
TiApp Editor: surface xml errors in overview UI
|
Errors in tiapp.xml should be surfaced to TiApp Editor Overview UI. See screenshots. Steps to Reproduce: 1. Open Titanium Project. 2. Enter invalid value in tiapp.xml. 3. Open TiApp Editor Overview. Actual Result: No indication of xml errors. Expected Result: TiApp Overview should indicate if the xml contains errors or warnings. The details of the errors or warnings are irrelevant.
| 8 |
train
|
TISTUD-3292
|
Investigate using Eclipse as Node Applications debugger
|
Before starting to work on debugging local Node.ACS projects (TISTUD-2814), we would like to first investigate if we could get debugging a regular node.js app to work using the steps described in https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger. Once we determine it is a feasible approach, we could then break down the tickets for implementing the feature.
| 8 |
train
|
TISTUD-3310
|
Restore Defaults button on the Project Build Path Properties page does nothing
|
While testing TISTUD-3106 in Titanium Studio, build: 3.1.0.201301242001 I encountered the following issue: The Restore Defaults button on the Project Build Path Properties page does not restore the defaults and clicking the button does not seem to do anything. Steps to reproduce: 1. Open a project in Titanium Studio. 2. View the Project's Properties (Project > Properties) 3. Click Project Build Path. 4. Change options on the preference page. 5. Click the Restore Defaults button. Expected Result: Preference page returns the the default settings. Actual Result: Nothing happens.
| 3 |
train
|
TISTUD-3315
|
Investigate the "Advanced Installers" product for Windows
|
We want to replace NSIS installer with a better one that would allow us to package different components easier. One candidate is http://www.advancedinstaller.com/. This ticket is to try it out to find the pros and cons. It will also be good to understand the steps to build the installer with our source. We should have a wiki page on the findings.
| 13 |
train
|
TISTUD-3321
|
Builds should always use --log-level of trace
|
For builds (ie, debug on device) that utilizes parsing the build output to determine the state of the build, the log-level should always be set to trace. The console view is responsible for filtering the output and display messages appropriate to the set level. This applies to: Steps: 1. In the console, set the log-level to Error 2. Launch Debug on iOS device Expected results: Logging is filtered for errors, and debug proceeds as normal Actual results: Logging is filtered properly, but the debug progress does not proceed past "Building Application" Applies to: Run/Debug/Test ios/android
| 5 |
train
|
TISTUD-3323
|
TSS validation should not generate an error when there's no commas between
|
In the sprint demo on 1/28/2013 the TSS validation was creating a validation error when there was no commas between top-level styles elements. For example, this was valid: {code:javascript} "#someId": {}, "#someOtherId": {} {code} but this was not: {code:javascript} "#someId": {} "#someOtherId": {} {code} According to the [Alloy grammar|https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs], both should be valid.
| 3 |
train
|
TISTUD-3332
|
Add extension point to override behavior of LaunchConfiguration Tab group
|
The extension point should declare an implementation of -ILaunchConfigurationOverride -priority -String representing the ILaunchConfigurationType The ILaunchConfigurationOverride is defined as {code} // Sets the launch configuration with the expected values, also returns a status that contains status is valid. Responsible for updating the UI created by createControls() public IStatus validate(IProject, ILaunchConfiguration) // creates the UI for the override public void createControls(Composite) {code} Utility methods should be added to retrieve and store the extension points
| 8 |
train
|
TISTUD-3333
|
Incorporate LaunchConfigurationTabGroup extension into default implementation of launch configuration tab groups
|
Update BaseTitaniumLaunchConfigurationTab to: -utilize the extension point to determine to create additional UI for the main page -If the extension returns an error or warning, show the appropriate message -Verify all subclasses ~10-15
| 13 |
train
|
TISTUD-3334
|
Take into account the minify attribute for builds
|
The Node command handler for CLI needs to take into account the "minify" attribute. The attribute is set in the launch configuration, if it is not present should default to "true"
| 8 |
train
|
TISTUD-3335
|
Dashboard: Xcode 4.6 not recognized as installed
|
Dashboard: Xcode 4.6 not recognized as installed. Xcode is correctly recognized by the CLI, and the Studio Preferences. No log. Steps to Reproduce: 1. Install Xcode 4.6. 2. Open Titanium Studio. 3. Open Dashboard. 4. Get Started > Configure > iOS. Actual Result: Xcode not recognized as installed. User prompted to download Xcode. Expected Result: Xcode recognized as installed.
| 3 |
train
|
TISTUD-3345
|
Dashboard: update ios installation info to include current os support
|
Dashboard: update ios installation info to include current os support. See attached 'if not installed info'. We need to remove Snow Leopard (deprecated), and add Mountain Lion or a generic instruction for Lion+. Steps to Reproduce: 1. Move Xcode in filesystem (without changing xcode-select path). 2. Open Titanium Studio. 3. Open Dashboard. 4. Get Started > Configure > iOS. 5. Hover over 'Install or Update iOS SDK' button. Actual Result: Snow Leopard (deprecated) and Lion appear. Expected Result: No Snow Leopard. Yes Mountain Lion, Lion, and/or Lion+.
| 5 |
train
|
TISTUD-3351
|
Add extensions to contribute "minify" checkbox to Titanium launch configurations
|
Add an extension that contributes the "minify" checkbox. The checkbox is associated with an attribute that the build will utilize to determine whether minification will happen. Checkbox enablement should only occur if the SDK is > 3.0.2
| 8 |
train
|
TISTUD-3357
|
Improve the Node.ACS icons
|
*Details:* The node.acs logo in the context menu and in the Project Explorer (and probably other places) could use some improvement. *Steps to reproduce:* 1. In the Project Explorer pane, right-click > New *Actual:* Node.ACS logo is not centered properly and doesn't fit with other icons we have. *Expected:* Node.ACS logo should be improved.
| 5 |
train
|
TISTUD-3358
|
"Configure SDKs" link from project wizard should include all the platform preference pages
|
This applies to Studio 3.1.0 only. After we moved the platform SDK preferences into their own preference pages, we should include all those pages to show when clicking on the "Set-up/Configure SDKs" link in project creation wizard. Otherwise, user has to exit out of the wizard, go to the preferences page, and then come back.
| 5 |
train
|
TISTUD-3359
|
ACS: duplicate guid does not generate accurate error
|
ACS: duplicate guid does not generate accurate error. Current UI Error (& see screenshot): {code} java.io.IOException: Server returned HTTP response code: 400 for URL: https://api.cloud.appcelerator.com/v1/apps/create.json?key=7fI2AZHmrSvAHNKsSQKzrSXz5NWjo2tt Server returned HTTP response code: 400 for URL: https://api.cloud.appcelerator.com/v1/apps/create.json?key=7fI2AZHmrSvAHNKsSQKzrSXz5NWjo2tt {code} Studio Log Error: {code} !ENTRY com.appcelerator.titanium.core 1 0 2013-01-29 22:22:11.235 !MESSAGE (Build 3.0.2.201301281948) [INFO] com.appcelerator.titanium.core/debug/api ACS Register App API Request: https://api.cloud.appcelerator.com/v1/apps/create.json?key=7fI2AZHmrSvAHNKsSQKzrSXz5NWjo2tt, parameters description=not+specified&name=p2&ti_guid=8a582c80-a1b3-4816-a616-e3cf55ab2fe8&suffix=development%2Cproduction&ti=true !ENTRY com.appcelerator.titanium.ui.ide 4 0 2013-01-29 22:22:11.277 !MESSAGE (Build 3.0.2.201301281948) [ERROR] Failed to register app for ACS !STACK 0 java.io.IOException: Server returned HTTP response code: 400 for URL: https://api.cloud.appcelerator.com/v1/apps/create.json?key=7fI2AZHmrSvAHNKsSQKzrSXz5NWjo2tt sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436) sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) com.appcelerator.titanium.core.acs.ACSManager.registerApp(ACSManager.java:410) com.appcelerator.titanium.core.acs.ACSManager.registerApp(ACSManager.java:362) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection$2$1.run(TiAppCloudSection.java:243) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Steps to Reproduce: 1. Create TiProject1 with ACS enabled. 2. Copy GUID from TiProject1 tiapp.xml. 3. Create TiProject2 w/o ACS enabled. 4. Paste GUID into TiProject2 tiapp.xml. 5. Enable TiProject2 ACS via TiApp Editor Overview. Actual Result: Meaningless error. Expected Result: Duplicate GUID error.
| 5 |
train
|
TISTUD-3372
|
Make URL list for RC 3.0.2 release, and RC 3.0.2 dashboard for testing
|
Make URL list for RC 3.0.2 release, and RC 3.0.2 dashboard for testing. All urls that titanium studio uses are needed for quick validation and update.
| 5 |
train
|
TISTUD-3374
|
Content Assist: Global.console and console do not appear
|
Content Assist: Global.console and console do not appear. However, the methods within console correctly appear. See TIDOC-860 for ongoing issue. Steps to Reproduce: 1. Open app.js. 2. Type 'con' or 'Global.con' and activate content assist. Actual Result: 'console' does not appear, but if you manually type it in, the methods will appear. Expected Result: 'console' appears, 'console'.methods appear as well.
| 5 |
train
|
TISTUD-3377
|
Alloy: Project > New Model generates unclear error
|
Alloy: Project > New Model generates unclear error. Error: {code} [34m .__ .__ _____ | | | | ____ ___.__. \__ \ | | | | / _ < | | / __ \| |_| |_( <_> )___ | (____ /____/____/\____// ____| \/ \/[39m [37mAlloy by Appcelerator. The MVC app framework for Titanium. [39m {code} Steps to Reproduce: 1. Create Alloy Project. 2. Project Context Click > New Alloy Model. 3. Enter name, press OK. Actual Result: Strange error. Expected Result: Model is created without error, or a meaningful error that can spawn user action.
| 5 |
train
|
TISTUD-3379
|
iOS Console: log level filter does not update in realtime, or respect run config
|
iOS Console: log level filter does not update in realtime. Steps to Reproduce: 1. Create Titanium Project. 2. Edit app.js: {code} var win = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title : 'click', top : '40%', bottom : '40%', left : '30%', right : '30%' }); button.addEventListener('click', function() { Ti.API.error('ERROR => Ti.API.error'); Ti.API.log('ERROR', 'ERROR => Ti.API.log'); Ti.API.warn('WARN => Ti.API.warn'); Ti.API.log('WARN', 'WARN => Ti.API.log'); Ti.API.info('INFO => Ti.API.info'); Ti.API.log('INFO', 'INFO => Ti.API.log'); Ti.API.debug('DEBUG => Ti.API.debug'); Ti.API.log('DEBUG', 'DEBUG => Ti.API.log'); Ti.API.trace('TRACE => Ti.API.trace'); Ti.API.log('TRACE', 'TRACE => Ti.API.log'); Ti.API.log('FREEFORM', 'FREEFORM => Ti.API.log'); }); win.add(button); win.open(); {code} 3. Run project in iPhone Simulator. 4. Click button in app. 5. Change log level in console UI using drop-down list. 6. Click button in app. Actual Result: Same log filter as before, not updated in real-time. Expected Result: Different log filter, updated in real-time. Works for Android Emulator.
| 5 |
train
|
TISTUD-3421
|
Studio: tiapp.xml Overview detects an error if creating a new project and importing in Studio
|
h5. Problem tiapp.xml Overview detects an error for 'Publisher URL' if creating a new project using CLI and then importing it in Studio. h5. Steps to reproduce 1. Create a new project with CLI ($ ti create) 2. Once created, import it in Studio 3. Open tiapp.xml Overview Result: an error is detected, referring to 'Publisher URL', set to 'not specified' in this case. 4. Build/run Result: project build/run as expected. No issues related to the tiapp.xml reported errror. 5. Fill in just 'http://' or Result: no error is then detected.
| 5 |
train
|
TISTUD-3380
|
Simulator and emulator launch configurations are missing from the Run > Run Configurations... dialog
|
When running the nightly 3.1.0 build, I noticed all the simulator and emulator related launch configuration types for iOS/Android/MobileWeb/BlackBerry are missing from the run configuration dialog. Checked their declarations in plugin.xml, and they are declared public. This doesn't happen in 3.0.2; attached screenshots for comparison between the two versions.
| 8 |
train
|
TISTUD-3381
|
Do more validation in create keystore dialog
|
I was attempting to test the keystore creation and when I finished the dialog I received an error dialog with a stacktrace saying something like "Incorrect AVA format". After some Googling it turns out that you can't use commas in the company name. I think we should validate for invalid values/characters in some of the fields, or provide a more meaningful error message in a case like this. See http://gyurigrell.com/2012/2/14/incorrect-ava-format-when-creating-signing-key http://stackoverflow.com/questions/11808391/keytool-error-java-io-ioexceptionincorrect-ava-format http://www.docjar.com/html/api/sun/security/x509/AVA.java.html
| 8 |
train
|
TISTUD-3382
|
Provide drop-down for country codes in create keystore dialog
|
We currently use a text field for the country code. We may want to provide a writable combo box with the 2-letter country codes already in it (and default to US?). See {{Locale.getISOCountries()}} http://modemsite.com/56k/_ccodes.asp
| 5 |
train
|
TISTUD-3383
|
Investigate adding support for BlackBerry development on Linux
|
You can now install the BlackBerry SDK on Linux: http://developer.blackberry.com/native/download/?os=linux We should investigate the difficulty in allowing Linux users to build for BlackBerry with Titanium Studio.
| 5 |
train
|
TISTUD-3386
|
Alloy: disable the OK button in Project > New Model dialog when no columns are entered
|
Steps to Reproduce: 1. Create Alloy Project. 2. Project Context Click > New Alloy Model. 3. Enter name, press OK. Actual Result: Strange error. Expected Result: The OK button should be disabled when no column entries are entered yet.
| 3 |
train
|
TISTUD-3393
|
JS Content Assist: no instance methods listed in for statement with no code block
|
JS Content Assist: console API methods not listed in for statement with no code block. Steps to Reproduce: 1. Enter code in app.js: {code} console. for(i in []) console.; for(i in []) { console. } {code} 2. Activate content assist after each dot (.) method access operator. Actual Result: console methods not listed in for loop without code block Expected Result: console methods are listed everywhere
| 8 |
train
|
TISTUD-3396
|
Unable to select enterprise provisioning profile in iOS publish wizards
|
Enterprise provisioning profiles are now longer showing up for publishing to Ad hoc/Enterprise as well as the publish provider wizard (ie TestFlight, due to the same issue). The problem is the CLI does not detect Enterprise distribution profiles properly, but categorizes them as "Distribution". Not sure if this is a change in the recent CLI or what, but it appeared to be working in a previous 3.0.2 version Studio. Investigation needs to be done to determine if it's a CLI issue and if it will be fixed in the timeframe, otherwise Studio needs to allow all "Distribution" profile types for Ad hoc/Enterprise distribution
| 5 |
train
|
TISTUD-3397
|
Node : 'Node is not an internal or external command' error when creating a Titanium Project due to path
|
This is a regression bug. It happened on both 3.0.1 and 3.0.2 Test Steps: 1.On a clean machine , download titanium studio installer for 3.0.1 and install Titanium Studio. 2.Accept all the titanium updates ( it includes NodeJs, Alloy , Titanium) I haven't added Node.ACS plugin deliberately . -> Observe that NodeJs exe should be installed successfully. 4.Exit from Studio using 'Exit' option. 5.Again launch Titanium Studio. 6.File > new > Titanium project. 7.Observe the behaviour. Note: This behaviour is specific to only one machine. Actual Result: The following error is coming :" 'node' is not recognized as an internal or external command, operable program or batch file. " Screenshot and logs attached. Expected Result: No error should come.
| 8 |
train
|
TISTUD-3398
|
Add git commit SHA and/or jenkins build id to about box text
|
We should provide the git commit SHA that makes up each feature/repo in some form (about box/diagnostic log). I was trying to determine if a particular commit had landed in a built version of Studio and the dates matched but time of day was different and I wasn't sure if both were in GMT/UTC. It'd be useful to try and insert the commit SHA into the version/about/log text to get an idea what we've built. Possibly we could even insert Jenkins build #/id like Eclipse does. I think the sha would need to get inserted on a feature/product basis. We currently provide a copyright message that can be drilled into in the about box (drilling into the feature level) on the branding plugins.
| 8 |
train
|
TISTUD-3401
|
iOS Console: log level filter does not update in real time for Debug
|
From testing in TISTUD-3379: Log console does not update based on user selection from the drop down for Debug on iOS simulator. Steps to Reproduce: 1. Create Titanium Project. 2. Edit app.js: {code} var win = Ti.UI.createWindow(); var button = Ti.UI.createButton({ title : 'click', top : '40%', bottom : '40%', left : '30%', right : '30%' }); button.addEventListener('click', function() { Ti.API.error('ERROR => Ti.API.error'); Ti.API.log('ERROR', 'ERROR => Ti.API.log'); Ti.API.warn('WARN => Ti.API.warn'); Ti.API.log('WARN', 'WARN => Ti.API.log'); Ti.API.info('INFO => Ti.API.info'); Ti.API.log('INFO', 'INFO => Ti.API.log'); Ti.API.debug('DEBUG => Ti.API.debug'); Ti.API.log('DEBUG', 'DEBUG => Ti.API.log'); Ti.API.trace('TRACE => Ti.API.trace'); Ti.API.log('TRACE', 'TRACE => Ti.API.log'); Ti.API.log('FREEFORM', 'FREEFORM => Ti.API.log'); }); win.add(button); win.open(); {code} 3. Debug project in iPhone Simulator. 4. Click button in app. 5. Change log level in console UI using drop-down list. 6. Click button in app. Actual Result: Log filtering is locked at run time. Expected Result: log filter updates based on user controls in real-time.
| 8 |
train
|
TISTUD-3404
|
Include Eclipse node debugger plugins and make them JRE 1.5 compatible
|
Checkout the source code (using "svn checkout http://chromedevtools.googlecode.com/svn/trunk/ chromedevtools-read-only") and fix the syntax for the following plugins so it compiles against JRE 1.5: org.chromium.debug org.chromium.debug.core org.chromium.debug.core.tests org.chromium.debug.ui org.chromium.sdk org.chromium.sdk.tests org.chromium.sdk.wip.eclipse
| 13 |
train
|
TISTUD-3405
|
Replace the JS editor in Eclipse node debugger plugins with our existing JS editor
|
Currently the Eclipse node debugger plugins contribute their own JS editor that opens the generated .js.chromium files. We should remove it and make our existing JS editor the default one so it doesn't cause confusion. It will also make theming consistent.
| 8 |
train
|
TISTUD-3893
|
BlackBerry: support project creation with multiple deployment targets
|
Description: 1.Create a default app with templates in the studio & select other deploy targets along with blackberry 2.Now open the resources folder of the created app in studio Actual Result: 1.The 'blackberry' folder does not get created in the resources folder as 'android','iphone','mobileweb' 2.due to this running the app gives errors: {code} [INFO] Running retCode = builder.run(ipAddress, devicePassword, debugToken, storePass, outputDir) File "/Users/lokeshchoudhary/Desktop/bb-mobilesdk-osx/mobilesdk/osx/3.1.0.v20130204182020/blackberry/builder.py", line 78, in run resources = os.listdir(self.blackberryResources) OSError: [Errno 2] No such file or directory: '/Users/lokeshchoudhary/Desktop/Titanium BB Workspace/default_123/Resources/blackberry'[INFO] Running retCode = builder.run(ipAddress, devicePassword, debugToken, storePass, outputDir) File "/Users/lokeshchoudhary/Desktop/bb-mobilesdk-osx/mobilesdk/osx/3.1.0.v20130204182020/blackberry/builder.py", line 78, in run resources = os.listdir(self.blackberryResources) OSError: [Errno 2] No such file or directory: '/Users/lokeshchoudhary/Desktop/Titanium BB Workspace/default_123/Resources/blackberry' {code} NOTE : If we create a default app with only blackberry as target then the 'blackberry' folder is getting created Expected Result: 1.The 'blackberry' folder gets created along with other targets
| 5 |
train
|
TISTUD-3410
|
SDK Module Packaging: allow user to package to path that does not exist
|
SDK Module Packaging: allow user to package to path that does not exist. See screenshot. Steps to Reproduce: 1. Open Titanium Module. 2. Package module to directory (manually type in an extra sub-directory to selected path). Actual Result: Error, cannot package to path that does not exist. Expected Result: Either limited to a warning, or no UI notifications, packaging operation creates directory as needed.
| 5 |
train
|
TISTUD-3411
|
JS Editor: improve default for-statement new line indentation
|
JS Editor: improve default for-statement new line indentation. If the cursor is at the end of the same line as a for or if statement, and at the beginning of the code block, pressing enter should position the cursor one line down and indented. Currently the line does not indent as would be expected. The lines are correctly indented, however, if there is an explicit code block ({}). See screenshots. Steps to Reproduce: 1. Enter code to app.js: {code} for(i in []); for(i in []){}; {code} 2. Place cursor here: for(i in [])<cursor>; and press enter. Actual Result: Cursor appears one line down and NOT indented. Expected Result: Cursor appears one line down AND indented. for(i in []){<cursor>}; => Note the expected behavior with an explicit code block.
| 5 |
train
|
TISTUD-3412
|
Titanium Preferences: Android SDK path always has focus when menu first invoked
|
When Titanium Preferences menu is invoked, the Android SDK path always has focus, breaking the menu navigation flow using the up and down arrow keys. This is a regression. Worked in 1.0.9. Steps to Reproduce: 1. Open Preferences > Titanium Studio. 2. Select the menu item just above Titanium (such as Themes). 3. Press down. Actual Result: Titanium menu invoked, Android SDK path has focus. Cannot press up to go back, or down to continue. Expected Result: Titanium menu invoked, nothing has focus. User can continue to navigate.
| 5 |
train
|
TISTUD-3413
|
SDK Module Project Explorer Deployment UI contains Active Run Icon (Invalid)
|
SDK Module Project Explorer Deployment UI contains Active Run Icon (Invalid). It is not possible to run a module. Not a regression. Steps to Reproduce: 1. Open Titanium Module. 2. Open Project Explorer. Actual Result: Deployment Run command icon is active. Expected Result: Deployment Run command icon is inactive. Only Publish icon should be active, as it is the only supported action.
| 5 |
train
|
TISTUD-3414
|
Make Eclipse node debugger plugin work with breakpoints set in our JS editor
|
We need to connect the code so that the debug launch configuration in the node debugger plugin understand the breakpoints set in our JS editor.
| 8 |
train
|
TISTUD-3422
|
Add Blackberry Applications Installer to the run configurations
|
Description: 1.Open studio 2.Go to preferences 3.Click 'Run As' 4.Clicked 'Run Configurations' Actual Results: 1.Notice that there is no blackberry application installer Expected results: 1.We should have a blackberry application installer NOTE: This will be particularly useful with the 10.1 beta out which is mainly targeted for the Q10 device & is different than the Z10 simulator
| 8 |
train
|
TISTUD-3423
|
Improve Module Packaging Run Config wording
|
Improve Module Packaging Run Config wording. See screenshot. Suggest using: "A mobile app" => "Mobile Project" "A directory" => "Location" (seems consistent with other run config menus) Applies to all module packagers (Android, iOS, etc.). Steps to Reproduce: 1. Create Titanium Module. 2. Package Titanium Module and view run config menu. Actual Result: Odd strings. Expected Result: Consistent and meaningful UI.
| 2 |
train
|
TISTUD-3432
|
Studio: Proxy settings do not retain username or password
|
When logging into studio through a proxy, every call back to the Appcelerator prompts for username and password for the proxy even when username and password are stored in the options. Steps to reproduce: 1. Launch and sign into Studio without any proxy setup. 2. Open Preferences > General > Network Connections. 3. Change Active Provider to Manual and edit the HTTPS entry with proxy information and proxy log in information. 4. Click OK and sign out of the Studio. 5. Launch and sign into Studio again. Expected results: User is able to login without issue using the stored username password for the proxy. Actual result: The user is prompted for proxy login information for each call to appcelerator's servers.
| 8 |
train
|
TISTUD-3433
|
Studio: Unable to use proxy settings from login screen
|
While trying to use the proxy setting for testing I ran into the following issue: I am currently unable to sign into studio via the proxy setup by Appcelerator's IT. Tested using the following: Titanium Studio, build: 3.0.2.201302011646 Connection type: HTTP and HTTPS tried IP: 50.17.15.139 Port:8080 Username: qetester Password: I get a generic error back when trying to log into Studio while using the above information (see screenshot) Steps to reproduce: 1. Start Titanium Studio after a logout. 2. Click "I have an account" and click next. 3. Click the "use proxy link". 4. Enter the proxy information into the form. 5. Click OK. 6. Login using correct credentials. Expected result: User is logged in through the proxy. Actual result: The error shown in the screen shot.
| 8 |
train
|
TISTUD-3434
|
Debugger: Debug process hangs at itunes initialization with cli -cr
|
Test steps: 1. Open Titanium project. 2. Insert the following code with break points {code} // this sets the background color of the master UIView (when there are no windows/tab groups on it) Titanium.UI.setBackgroundColor('#000'); // create tab group var tabGroup = Titanium.UI.createTabGroup(); // breakpoint // // create base UI tab and root window // var win1 = Titanium.UI.createWindow({ title:'Tab 1', backgroundColor:'#fff' }); var tab1 = Titanium.UI.createTab({ icon:'KS_nav_views.png', title:'Tab 1', window:win1 }); var label1 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 1', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win1.add(label1); // // create controls tab and root window // var win2 = Titanium.UI.createWindow({ title:'Tab 2', backgroundColor:'#fff' }); var tab2 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Tab 2', window:win2 }); var label2 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 2', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win2.add(label2); // // add tabs // tabGroup.addTab(tab1); tabGroup.addTab(tab2); // open tab group tabGroup.open(); alert('SESSION ID: ' + Ti.App.sessionId); // breakpoint Ti.API.error('SESSION ID: ' + Ti.App.sessionId); Ti.API.error('ERROR => Ti.API.error'); Ti.API.log('ERROR', 'ERROR => Ti.API.log'); Ti.API.warn('WARN => Ti.API.warn'); Ti.API.log('WARN', 'WARN => Ti.API.log'); Ti.API.info('INFO => Ti.API.info'); Ti.API.log('INFO', 'INFO => Ti.API.log'); Ti.API.debug('DEBUG => Ti.API.debug'); Ti.API.log('DEBUG', 'DEBUG => Ti.API.log'); Ti.API.trace('TRACE => Ti.API.trace'); Ti.API.log('TRACE', 'TRACE => Ti.API.log'); Ti.API.log('FREEFORM', 'FREEFORM => Ti.API.log'); var x = 0; // breakpoint var y = 0; // breakpoint {code} 3. Run iOS Debugger Actual result: Debug process hangs at Installing in iTunes. Note: Debugger section connected after the project started on device manually, and it completed successfully.
| 8 |
train
|
TISTUD-3436
|
Import NodeACS project disables publish option
|
Steps to reproduce: 1. Create a Node Service 2. Deploy the node service. 3. Import the node service to a new workspace using the option "existing folder as project" option. Here select NodeACS as primary and then Web for project natures. 4. Try to publish imported project. You receive no option to deploy app.
| 8 |
train
|
TISTUD-3437
|
Importing an Alloy project created using CLI, 'Resources' folder is shown
|
h6. Problem Studio is showing the 'Resources' folder of an Alloy project if the project has been created using CLI and then imported h6. Steps to reproduce 1. From Terminal, create a new project using CLI $ ti create 2. cd to the newly created project and convert it to an Alloy project $ alloy new 3. Import the project in Studio Expected result: project is displayed just like an Alloy project created from Studio (so, Resources folder shouldn't be visible) Result: 'Resources' folder is shown
| 8 |
train
|
TISTUD-3439
|
Error when changing module version in tiapp.xml
|
Getting this message when changing module version (full error log below): An error has occurred. See error log for more details. Index: 1, Size: 0 I have not been able to repo this consistently, but here the steps that usually cause it to happen. h4. Steps to repro: 1. Create an app 2. Add a module to the app via the tiapp.xml overview tab 3. while you have this view of studio open, extract a module with the same name but a newer version number to your modules folder. 4. Back in the tiapp.xml overview tab, edit the module and select the new version 5. click ok 6. You should see the error above in an alert dialog and the error log is below. 7. Notice that the module version number did not change. 8. Look at the actual tiapp.xml and change the module version number 9. Go back to the overview and it will work correctly. {code} !ENTRY org.eclipse.jface 4 2 2013-02-07 14:30:12.900 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 java.util.ArrayList.addAll(ArrayList.java:497) com.appcelerator.titanium.ui.ide.tiappEditor.ModulesTable.editModule(ModulesTable.java:550) com.appcelerator.titanium.ui.ide.tiappEditor.ModulesTable$2.doubleClick(ModulesTable.java:189) org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:845) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:843) org.eclipse.jface.viewers.StructuredViewer.handleDoubleSelect(StructuredViewer.java:1134) org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1246) org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249) org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:246) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:307) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 3 |
train
|
TISTUD-3441
|
Ignore the SDK version that starts with a non-numeric character
|
Studio currently doesn't handle a version string that doesn't start with a number (e.g. test-3.0.0 instead of 3.0.0.GA), and CLI doesn't handle such SDK either, so we should just ignore it in our SDKLocator class.
| 5 |
train
|
TISTUD-3443
|
Change default path of Workspace in Windows to avoid space in path of "My Documents"
|
Steps To Reproduce: 1. Install studio on Win machine. 2. Notice the default path of workspace contains "My Documents" Actual: The default path containing space in path creates problem in android. Expected: There must be no issues cause of default settings, hence path needs to be changed. One important thing to consider while doing the same is to Maintain Consistency with all OS's default path.
| 3 |
train
|
TISTUD-3447
|
The string '24-cr' in version '3.0.24-cr' for CLI throws error when we run diagnostic test from studio
|
Description: 1.Update the cli to 3.0.24-cr 2.Start up studio 3.Goto help -> titanium studio -> run diagnostic test Actual Result: 1.We get an error 'An internal error occurred during: "Getting Diagnostic Logs". For input string: "24-cr"' Expected Result: 1.we should see the diagnostic report Screenshot attached
| 3 |
train
|
TISTUD-3454
|
TiStudio: Cloud - When creating a new Titanium Project, the "Automatically cloud-enable this application" should be unchecked by default
|
Currently when a developer creates a new Titanium project, "Automatically cloud-enable this application" is checked by default. The problem is that this skews our "ACS" results because this shows almost every application is using ACS, when we know it is a significantly smaller group that is actually using ACS. So this should be changed to unchecked by default. Also the word "Automatically" should be removed because it will not automatically be cloud-enabled. The user/developer will have to check the "Cloud-enable this application" check box.
| 3 |
train
|
TISTUD-3456
|
Android distribution wizard : The keystore locations combo is not reflected immediately with browsed locations
|
In the Android distribution wizard, if couple of new certificates are added, then the latest one is only available in the list and the previous added certificates are not available in the list of keychain locations. However, reopening the wizard shows all the locations in the combo list. The case is similar to Browse button as well.
| 5 |
train
|
TISTUD-3468
|
Advertisement on the header of dashboard should be missing
|
Steps To Reproduce: 1. Open Studio>Dashboard Actual: Notice header above "Welcome back, <Username>". Studio Advertisements are not appearing Expected: Studio Ads must appear.
| 5 |
train
|
TISTUD-3474
|
Not to use legacy scripts if CLI is not installed and SDK is 3.0.0+
|
Remove Legacy Scripts if CLI is not installed and SDK is 3.0.0+. One example of the consequences of supporting legacy scripts on SDK 3.0.0+ is TISTUD-3452.
| 8 |
train
|
TISTUD-3476
|
Titanium Project: Terminating new Node.ACS project creation process is throwing error
|
This is a regression. It did not happen in Studio 3.0.1. Test Steps: 1.File > New > Node.ACS Project. 2.Enter project name. 3.Press Finish. 4.Before the creation of the project folder, cancel it by clicking on the red square at the bottom. Observe the error. Screenshots and logs attached.
| 8 |
train
|
TISTUD-3480
|
Windows: Android SDKs not recognized without moving them
|
This is a regression. Works correctly in TISTUD 2.1.2. Windows: Android SDKs not recognized in Preferences. Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium Studio > Titanium. 3. Clear Android SDK Path and Apply. 4. Browse to Android SDK to select path. Actual Result: Android SDKs not recognized. Expected Result: Android SDKs recognized.
| 8 |
train
|
TISTUD-3484
|
Add an option to publish to the Oracle Mobile Server
|
Reference https://wiki.appcelerator.org/display/guides2/Adding+a+new+Publish+Provider#AddinganewPublishProvider-ContributetoPublishMenus for contributing to the Publish menu. The action should be visible only if the project has Android as a deploy target. When invoked, it will launch the publishing wizard (see TISTUD-3485). See https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server for the Oracle integration document.
| 5 |
train
|
TISTUD-3485
|
Contribute a publish provider for publishing to Oracle mobile server
|
Reference https://wiki.appcelerator.org/display/guides2/Adding+a+new+Publish+Provider#AddinganewPublishProvider-PublishProviderExtensionPoint for using the publish provider extension. 1. The supported platform is Android; 2. The publish target is the Oracle Mobile Server. We have a test server as specified in https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server.
| 8 |
train
|
TISTUD-3486
|
Implement publishing to the Oracle Mobile Server using their APIs
|
The publishing should happen through Oracle APIs(check the Resource Manager APIs). See http://docs.oracle.com/cd/E22663_01/doc.11100/e22677/sync.htm#i1007512. Use the Resource Manager APIs to create the publication, package it with an application, and publish it to the mobile server. See the oracle.mobile.admin.MobileResourceManager in the Oracle Database Mobile Server JavaDoc, which is located off the ORACLE_HOME/Mobile/doc/index.htm page. Reference the doc at https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server.
| 13 |
train
|
TISTUD-3487
|
Warn user it will overwrite when re-publishing the project to Oracle server
|
When re-publishing an Oracle module integrated app, the developer should be alerted that an overwrite of a previously published application is going to occur. Reference the doc at https://wiki.appcelerator.org/display/tools/Publish+Apps+to+Oracle+Mobile+Server.
| 5 |
train
|
TISTUD-3488
|
Create a feature for the Oracle server integration
|
We want to ship the integration for enterprise users only but separate from the 360 release, so we will need to create separate feature and builder. This ticket covers the feature part.
| 5 |
train
|
TISTUD-3490
|
Create a builder for the Oracle integration feature
|
Create a builder and corresponding Jenkins build to generate an update site.
| 8 |
train
|
TISTUD-3493
|
Tizen: Create icons for Tizen platform integration
|
As we are you integrating Tizen platform into Studio, it requires Tizen based images/icons to represent Tizen SDK platform in the menus, toolbars and module tables. The icon/image might be similar to the icon referred to Tizen at https://developer.tizen.org/ It need images for elcl12, elcl16 and obj16 formats.
| 8 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.