id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
1,711 |
TISTUD-5568
|
10/22/2013 13:46:52
|
Installing Studio update through our own dialog doesn't ask for restart
|
When a user upgrade Studio through our combined update dialog, after it finishes it doesn't ask the user to restart. I'm not sure that the update will get properly applied without doing so. (for example the update contained some UI changes that didn't happen until I chose to restart).
| 3 |
1,712 |
TISTUD-5570
|
10/22/2013 17:58:27
|
Show a list of Android emulators instead of just "Android Emulator" for each launch mode
|
In the output of "ti info -o json" for CLI 3.2.0, it contains a section "android" > "emulators", where it contains info such as id, name, model, and manufacturer. We should display this list in place of Android Emulator, and when one is invoked, pass the id value in the \--device\-id flag to "ti build" command.
| 8 |
1,713 |
TISTUD-5571
|
10/22/2013 17:58:59
|
Show a list of connected Android devices instead of just "Android Device" for each launch mode
|
In the output of "ti info -o json" for CLI 3.2.0, it contains a section "android" > "devices", where it contains info such as id, name, model, and manufacturer. We should display this list in place of Android Device, and when one is invoked, pass the id value in the \--device\-id flag to "ti build" command.
| 8 |
1,714 |
TISTUD-5573
|
10/22/2013 18:21:12
|
Studio:Typo in error message
|
Typo in error message (see the screenshot) h5.Actual result "retreiving" instead of "retrieving"
| 1 |
1,715 |
TISTUD-5575
|
10/22/2013 19:16:25
|
Android SDK is no longer detected
|
h5. Problem description After the upgrade, Titanium Studio is no longer detecting the Android SDK. However, 'ti info -t android' from terminal do returns the android info. Also I was able to build an existing project on Android from CLI.
| 3 |
1,716 |
TISTUD-5576
|
10/22/2013 19:48:22
|
See the password prompt when only selected to update Studio
|
See the attached screenshot. There are two entries in the update dialog, but I only selected Appcelerator Studio, which does not require sudo password, and I still see the prompt after proceeding.
| 3 |
1,717 |
TISTUD-5577
|
10/22/2013 21:30:28
|
Migrate from use of AVDs to device ids
|
Currently we collect AVDs in our AndroidSDKLocator and treat them as SDKEntities (which is wrong in the first place). We then specify the AVD id when we launch an emulator. We need to move to using device ids. So we need to grab the list of devices from CLI on-demand (since they can change any time) when needed (i.e. when we show a combo box to select one), and we need to pass along the device id on the command line when launching. This will also involve updating the launch configs and their UIs to select the device id rather than avd-id.
| 8 |
1,718 |
TISTUD-5578
|
10/23/2013 00:31:56
|
Show EULA when installing Android SDKs from preference page
|
Currently when user installs additional Android SDKs from the "Install SDKs" button in Android preference page, we don't show a EULA dialog. We should make it consistent with installing from platform configuration wizard.
| 3 |
1,719 |
TISTUD-5579
|
10/23/2013 00:37:13
|
Offer to install Android 2.3.3 for user if trying to run project against pre-3.2.0 SDK without it
|
CLI/SDK 3.2.0 no longer requires Android 2.3.3 when doing the build, so we no longer require user to install it in Studio. However, when user tries to run the app against an older version of SDK, the python script would be used, and it would still require Android 2.3.3. In this case, instead of failing in the build console, we should improve the experience by detecting the situation when running and offer to install 2.3.3 for users using our Android installation dialog.
| 5 |
1,720 |
TISTUD-5582
|
10/23/2013 07:42:16
|
Studio: Installing Nightly version results in new version download but the success prompt displays the older version
|
I upgraded my Studio from 3.2.0.201310181700 to 3.2.0.201310220323, the update was successful but the 'Restart' prompt was missing and the success prompt still displayed the previous version. I also observed that the Studio version displayed in the 'Available Updates' window was correct and showing the Appcelerator Studio, build: 3.2.0.201310220323 to be updated. Steps Followed: 1. Update Studio to a new nightly build Actual Result: 1. The update process gets completed and a success prompt is shown in the lower right hand corner which displays the previous version of Studio which was before updating it. 2. The 'Restart' message which is prompted after completion of update was not displayed. Pleaser refer the attached screen shot for further details.
| 3 |
1,721 |
TISTUD-5585
|
10/23/2013 12:23:38
|
Run Configurations >> Appcelerator iOS Simulator deleting the existing configurations causes NPE
|
Steps Followed: 1. Project Context Menu >> Run as >> Run Configurations >> Appcelerator iOS Simulator >> New Configuration. 2. Delete any existing Run Configurations Actual Result: Deleting the existing configurations causes NPE. I also intermittently observed the same when I clicked on any existing configuration. Please observe the attached screen shot and log file for more clarification.
| 3 |
1,722 |
TISTUD-5587
|
10/23/2013 18:57:28
|
Studio: Titanium Studio Updates - wrong software license agreement, accepting Titanium Studio build
|
When trying to update Titanium Studio build for latest nightly, the License text is provided for Appcelerator Studio. h5.To reproduce Launch titanium Studio>Help>Check for Titanium Updates>Next h5.Actual result APPCELERATOR TITANIUM STUDIO SOFTWARE LICENSE AGREEMENT h5.Should be Titanium Software License Agreement
| 2 |
1,723 |
TISTUD-5588
|
10/23/2013 19:15:22
|
Studio: Titanium Studio cannot be updated
|
Accepting license agreement, trying to update Titanium Studio, results in infinite password prompt. h5.To reproduce Titanium Studio>Help>Check for Titanium Updates>Next>Accept License Agreement h5.Actual result Password is prompted, and after entering it and clicking Install, a password is being prompted again. h5.Expected result No password should be prompted and updates should be installed successfully.
| 5 |
1,724 |
TISTUD-5594
|
10/24/2013 11:14:46
|
Windows 8 : Studio installer fails at the git installation step
|
Steps Followed: 1. Downloaded the Windows installer and tried to install it. 2. Followed the steps in the installer 3. The installer includes the Git installations Actual Result: Studio installer fails at the git installation step.The appcelerator log file picked from the Temp folder mentions 'Git Version detection complete - result = No Git Found'. I tried manually installing the Git version 1.8.4 still I was facing the same issue and the appcelerator log file picked from the Temp folder mentions 'Git Version detection complete - result = Old Git found'. Please observe the attached screen shot and 'appcelerator log file 1 & 2' for more clarification.
| 13 |
1,725 |
TISTUD-5598
|
10/25/2013 01:30:31
|
Studio: Email address is shown on status bar instead of display name
|
On the lower right corner, it should have said "Michael Xia" instead of "[email protected]". Believe this is introduced by the change that we are authenticating after Studio starts. We need to save the display name in addition to just username/email.
| 3 |
1,726 |
TISTUD-5603
|
10/25/2013 23:48:26
|
See white-on-white in Project Explorer when re-applying the "Light Studio" theme
|
1. Open Preferences > Studio > Themes; 2. Switch Overall Theme to "Dark Studio" and switch back to "Light Studio". The Project Explorer view will then become unreadable due to white-on-white text. Have to restart Studio to get it display properly.
| 3 |
1,727 |
TISTUD-5605
|
10/26/2013 00:03:09
|
Add "Run Configurations..." to the global toolbar dropdown
|
We should have a "Run Configurations..." option in the global device profile dropdown as we had under Run icon in the local toolbar of Project Explorer. There should be a separator between it and the shortcuts, and it will launch the run configuration dialog instead of select it as an entry.
| 5 |
1,728 |
TISTUD-5610
|
10/28/2013 11:22:28
|
Install SDK button should be disabled if no android updates available in the preferences.
|
Precondition: All updates must be installed for Android SDK. Test Steps: Launch Appcelerator Studio. Preferences > Studio > Platforms > Android > > 'Install SDK' button Expected: Install SDK button should be disabled if no android updates available in the preferences.
| 3 |
1,729 |
TISTUD-5611
|
10/28/2013 11:32:35
|
Android: Unable to build for device with error "Invalid device-id"
|
Unable to build the app for android device using the sdk build:3.2.0.v20131027201356. App is running fine on android emulator. Steps to reproduce: 1. Create a default titanium project. 2. Select the sdk as 3.2.0.v20131027201356 in tiapp.xml Expected: App should build and deployed to the device. Actual: Build error occurs as "[ERROR] : Invalid "--device-id" value "titanium_7_HVGA" [ERROR] Application Installer abnormal process termination. Process exit value was 1"
| 3 |
1,730 |
TISTUD-5614
|
10/28/2013 18:55:08
|
iOS: Xcode 5.0.1 - Nightly Studio build cannot build app for iOS 7.0.3 simulator, device, or packaging using xcode 5.0.1
|
*Details:* Cannot build app for iOS 7.0.3 simulator, device, or packaging using xcode 5.0.1 *Steps to reproduce:* 1. Make sure to have your xcode-select pointing to xcode 5.0.1 2. In Studio, create a default Alloy or classic app 3. Right-click on the project 4. Go to Run As > iPhone or Run As > iOS Device or Publish > Distribute - Ad Hoc/Enterprise *Actual:* Studio console view will return invalid iOS version (see attachments). *Expected:* Should be able to build app for iOS simulator, device, or packaging.
| 5 |
1,731 |
TISTUD-5619
|
10/29/2013 00:21:32
|
Broken link to docs in Titanium/Eclipse Help
|
1. In Studio, select Help > Help Contents 2. Click 'Appcelerator Document Wiki' link. Results: Page not found http://go.aptana.com/Studio+Home redirects to http://docs.appcelerator.com/titanium/latest/#!/guide/Titanium_Studio Expected: Link/redirect goes to http://docs.appcelerator.com/titanium/latest/#!/guide/Studio
| 2 |
1,732 |
TISTUD-5620
|
10/29/2013 05:55:58
|
Unable to publish Android project to the sample publish provider
|
1. Install Titanium Studio + Eclipse JDT + Eclipse PDE; 2. Clone the git project from https://github.com/appcelerator/titanium_studio_sdk/tree/master/samples/publish/plugins/com.appcelerator.titanium.publish.sample. 3. Import the sample provider plugin to Titanium Studio. 4. Run com.appcelerator.titanium.publish.sample as Eclipse application; this will start a new instance of Titanium Studio which has the sample Publish feature. 5. Create a sample Android project in the new Titanium Studio instance. 6. Publish the Android Project to Sample Publish Provider. 7. Fill details and go until Platform Tab. Select Android SDK Version, Distribution Location, Keystore Location, Keystore Password and Key Alias. 8. Click Next and go to Summary page. Notice the Keystore Alias is shortened to just the first letter, and the same for password. 9. Click Publish and it will fail.
| 5 |
1,733 |
TISTUD-5621
|
10/29/2013 07:56:33
|
Ubuntu 12.04 : Encountered NPE while setting the Android SDK path through Studio > Prferences
|
Steps Followed: 1. Window >> Preference >> Studio >> Platforms >> Android 2. Browse the desired path to Android SDK location Actual Result: NPE is thrown when tried to set the Android SDK path. Pleae refer the atached screen shot and log file for further reference.
| 3 |
1,734 |
TISTUD-5622
|
10/29/2013 17:13:38
|
Group dynamic platform emulators/devices launch shortcuts under second level menu in global toolbar drop-down
|
Right now we have a flat menu under the drop-down where all devices/emulators are listed. If we have multiple devices or multiple emulators, we should group them under a second level menu. So you'd choose drop-down > Android Emulator > and see a list of the emulators. If there is only one emulator or device, there's no need to group into a second-level menu.
| 5 |
1,735 |
TISTUD-5624
|
10/29/2013 20:59:47
|
Android: Creating a project in studio with an Ampersand in the name throws errors
|
h5.Description Creating an android project inside Studio with a project name including an ampersand will throw errors and create a blank project folder with a different name. h5.Steps To Reproduce 1. Open Studio 2. Create a new Android Project 3. Give a name including an ampersand (Example, Test1&Test2) h5.Expected Result The project should be created using the given name h5.Actual Result The project throws an error while trying to create itself and instead makes a blank folder. +Extra Information+ This works through CLI, but will not work through Studio
| 5 |
1,736 |
TISTUD-5625
|
10/29/2013 23:58:49
|
No Mobile Web option is available for packaging under the global toolbar
|
The "Package - Mobile Web" option that's available in the local toolbar of Project Explorer is not available for the global toolbar when packaging mode is selected.
| 8 |
1,737 |
TISTUD-5628
|
10/31/2013 16:58:51
|
Tiapp.xml would not detect any platforms (Only occured once)
|
h5.Description I updated to the latest version of studio with the latest SDK and CLI also. I created a project using an older SDK by accident and after using tiapp to update to the latest the platforms became hidden. They were all linked to the correct places and both the studio dashboard and studio preferences proved it. However tiapp would request I reinstall all the platforms. h5.Steps To Reproduce Note, this only occurred once but these are the steps I took before it happened. 1. Update to the latest studio 2. Open studio 3. Create a project 4. Install and set to default the latest SDK through CLI 5. Once installed change the tiapp of the project to use the latest SDK. h5.Expected Result The SDK should have changed to the latest and the platforms should still have been detected. h5.Actual Result The project struggled a bit on the project cleaning process, taking a minute or so to complete. After completing and saving I got the error message "please select at least one platform" despite them all being checked. Then the wrench icon to edit the preferences of the platform became the hint icon.
| 8 |
1,738 |
TISTUD-5629
|
10/31/2013 20:09:42
|
Show a list of connected iOS devices instead of just "iOS Device" for each launch mode
|
In the output of "ti info -o json" for CLI 3.2.0, it will contain a section "ios" > "devices". We should display this list in place of "iOS Device", and when one is invoked, pass the id value in the \--device\-id flag to "ti build" command.
| 8 |
1,739 |
TISTUD-5631
|
10/31/2013 20:48:38
|
Run on iOS Device: add list of devices to the launch config dialog
|
With the new capability of launching directly on iOS device provided by CLI, we will need to update the launch configuration dialog to include the list of devices to select from.
| 5 |
1,740 |
TISTUD-5632
|
10/31/2013 21:14:22
|
Ti Studio (Mac): TestFlight Plugin does not obey iOS SDK setting
|
On the third screen of the Publish to TestFlight wizard, there is a combobox for "Select SDK Version". Mine defaults to 7.0, but I also have the 6.1 SDK on my machine (and it appears in the combobox as a choice). If I select 6.1 and click Next, I get a java.lang.NullPointerException. When I click Publish (even if I didn't click Next previously), the process proceeds but the console shows "Building using iOS SDK: 7.0". I have found no way to get it to use the 6.1 iOS SDK. I have attached the results of Help > Studio > Run Diagnostic Test.
| 5 |
1,741 |
TISTUD-5633
|
10/31/2013 22:26:09
|
STUDIO: Right-click on project results in period of "Studio is not responding"
|
h5. Description: When right-clicking on a project to run it form the project explorer, I got the beach ball. I opened the force-quit dialog (CMD-OPT-ESC) to see if Studio was responding. It was not. Eventually it resumed normal operation, but as soon as I right-clicked again it beach-balled. Right-clicking on the project explorer OFF a project will work as expected. Unable to determine if this is a regression as I am unable to reproduce in 3.1.4 Studio Please see attached jstack for more detail. h5. Steps to reproduce: The steps to get into this state are unknown. I will continue to work on this, but a restart of Studio resolved the problem. If steps are found I will update the ticket. 1) Right-click an existing project h5. Result: Beach ball and after 1-2 minutes, resumption of normal function. Contexual window displays for a split-second h5. Expected Result: Contexual menu display and functional
| 5 |
1,742 |
TISTUD-5634
|
10/31/2013 23:20:27
|
Default Android emulator is launched when using older version of the TiSDK with Studio 3.2.0
|
ENVIRONMENT: Mac OS X 10.8.4 Appcelerator Studio, build: 3.2.0.201310312112 Titanium SDK Version: 3.2.0.v20131030184044 and 3.1.3.GA REPRODUCTION: Launch the default project in an emulator that is not your default emulator using the 3.1.3.GA Ti SDK. EXPECTED RESULTS: Application should launch on the selected emulator. ACTUAL RESULTS: Application launches on the emulator that is selected as the default. This works as expected with the latest 3.2.0 TiSDK. Same results when using the Run Configurations dialog. When selecting an emulator to use the Code Profiler on, it always selects the default one.
| 5 |
1,743 |
TISTUD-5635
|
11/01/2013 21:49:42
|
Code Profiler: Cannot start Profiler for Android emulator or device on 3.2.0 Studio
|
ENVIRONMENT: Mac OS X 10.8.4 Appcelerator Studio, build: 3.2.0.201310312112 TiSDK 3.1.3.GA and 3.2.0.v20131030184044 Android 4.2.2/API Level 17 REPRODUCTION: Start the profiler for a default project on either the Android emulator or Android device. EXPECTED RESULTS: Profiler starts for targeted device. ACTUAL RESULTS: Profiler does not start with the following errors: On Android emulator: {noformat} shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory [INFO] logfile = /Users/bhatfield/Documents/Appcelerator_Studio_Workspace/TestIcon/build.log [INFO] Building TestIcon for Android ... one moment [ERROR] Application Installer abnormal process termination. Process exit value was 1 [ERROR] JDK version detected, but at least 1.6.0 is required {noformat} On Android device: Dialog displays this message: {noformat} An internal error occurred during: "Launching Appcelerator Android Application Installer - TestIcon". java.lang.NullPointerException {noformat} TiSDK version did not matter. Can launch the profiler for an iOS 7 app on simulator.
| 3 |
1,744 |
TISTUD-5636
|
11/01/2013 23:20:25
|
Android application installer is gets stuck at 57% in the progress tab even thought the build process is successfully complete
|
h5.Description: 1.Build an app for an android device or emulator.(could'nt verify on IOS because of some ios 7.0.3 issues, will update the ticket later). 2.Look at the Application install progress in the progress tab. h5.Actual Result: 1.The progress is stuck at 57% even though the build process is successful & the app has been installed on device or emulator. h5.Expected Result: 1.The build progress should not be stuck at 57% & complete to 100%. NOTE : Refer attached screenshot.
| 5 |
1,745 |
TISTUD-5637
|
11/03/2013 05:21:40
|
The launch shortcuts are not populated with list of devices when active SDK in CLI is set to 3.1.3 but the selected one in tiapp is 3.2.0
|
1. Run "ti sdk select 3.1.3.GA" from the command line to ensure 3.1.3.GA is set to be the active SDK; 2. Launch Studio and create a project with 3.2.0 SDK; 3. Click on the global toolbar dropdown for launch shortcuts. Expected behavior: it shows the list of emulators and connected devices since this project has 3.2.0 SDK selected, which supports the new functionality. Actual behavior: it shows the default emulator and device shortcuts as with 3.1.3. The issue here is that when 3.1.3.GA SDK is set to be the active one from CLI, "ti info" will always return the old data. We need to pass in the --sdk flag instead, i.e. "ti info --sdk 3.2.0.v20131101175645 -o json -t ios", to get the new output.
| 0 |
1,746 |
TISTUD-5641
|
11/04/2013 18:18:55
|
Distributing iOS app to Apple store will not open dialog window
|
h5.Description Trying to publish an app to the iTunes store will not open the dialog through Studio, however it works fine through CLI. h5.Steps To Reproduce 1. Create an iOS project in Studio 2. Publish the application to the Apple iTunes Store h5.Expected Result A dialog window should open to request information for the app from the user. h5.Actual Result Nothing happens. +Extra Information+ The log displays error messages, which have been attached to this ticket.
| 3 |
1,747 |
TISTUD-5642
|
11/04/2013 18:42:32
|
iOS build to device fails
|
h5.Description Building an iOS application to device will fail because it passes the developer name in place of the distribution name. h5.Steps To Reproduce 1. Create an iOS project 2. Run the project on device h5.Expected Result The app should build and install on the device h5.Actual Result [ERROR]: Invalid "--distribution-name" value "<Developer Name>" +Extra Information+ Building from CLI works because I used "--developer-name" "<Developer Name>"
| 3 |
1,748 |
TISTUD-5796
|
11/04/2013 20:33:18
|
Alloy Samples: default 'Two-tabbed Alloy Application' sample app is wrong
|
h5. Problem description The default new app 'Two-tabbed Alloy Application' is wrong. Instead, The one relative to a 'Default Alloy Project' is created. To reproduce, just create a new Alloy project from Studio and choose the 'Two-tabbed Alloy Application'. The project created is the 'Default Alloy project' one. Still reproducible with Titanium Studio 3.2.0.201311211626 , TiSDK 3.2.0.v20131125103938 and Alloy 1.3.0-alpha6
| 3 |
1,749 |
TISTUD-5643
|
11/04/2013 21:59:09
|
Studio: Checking for new Titanium Updates results in internal error
|
An internal error occurred during checking for new titanium Updates. h5.To reproduce Titanium Studio>Help>Check for Titanium Updates h5. Actual result An error message
| 3 |
1,750 |
TISTUD-5644
|
11/04/2013 22:51:00
|
the new list of iOS simulators is not available for Profile and Test modes
|
In the global toolbar select Profile or Test mode, then click on the second dropdown and select iOS Simulator. The expected result is to see a list of the new device profiles we introduced in 3.2.0; instead, only the generic shortcuts are displayed.
| 8 |
1,751 |
TISTUD-5648
|
11/05/2013 13:55:43
|
Alloy: Add Alloy namespace Content Assist to alloy project JS files
|
For the controller code, content assist does not suggest any of the elements in the Alloy namespace, such as Alloy.Globals, Alloy.createController, etc. See http://docs.appcelerator.com/titanium/latest/#!/api/Alloy.
| 8 |
1,752 |
TISTUD-5649
|
11/05/2013 17:54:32
|
XCode not detected in studio
|
h5.Description Every time Titanium Studio is opened I get a pop up saying that iOS info could not be found. Checking in preferences shows that XCode hasn't been detected. Strangely enough though I was still able to run iOS project on simulator and device. h5.Steps To Reproduce 1. Update to latest Studio, CLI and SDK 2. Open Studio 3. Check XCode preferences h5.Expected Result Studio should automatically detect XCode. h5.Actual Result {code}!ENTRY com.aptana.core 1 0 2013-11-05 09:42:04.303 !MESSAGE (Build 3.2.0.201311050151) [INFO] com.aptana.core/debug/shell Running process: Process: "xcode-select" "--print-path" Working directory: / Environment: null !ENTRY org.eclipse.core.jobs 4 2 2013-11-05 09:42:04.332 !MESSAGE An internal error occurred during: "Update iOS info". !STACK 0 java.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Collections.java:2976) at com.appcelerator.titanium.ios.core.IOSSDKLocator.initialize(IOSSDKLocator.java:180) at com.appcelerator.titanium.ios.core.IOSSDKLocator$3.run(IOSSDKLocator.java:205) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}
| 2 |
1,753 |
TISTUD-5650
|
11/05/2013 18:25:25
|
Publishing fails for iOS
|
h5.Description Publishing an iOS app will fail due to the output directory not being specified. h5.Steps To Reproduce 1. Create an iOS project in Studio 2. Publish the application to iOS Store h5.Expected Result The application should build and publish to a specific location. h5.Actual Result [ERROR] : Invalid "--output-dir" value "" +Extra Information+ {code}"/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "--no-banner" "build" "--platform" "ios" "--sdk" "3.2.0.v20131104164843" "--build-type" "production" "--log-level" "trace" "--project-dir" "/Users/sdowse/Documents/Titanium_Studio_Test/iOSTest" "--distribution-name" "Michael Asher" "--ios-version" "7.0.3" "--keychain" "" "--output-dir" "" "--pp-uuid" "BD2EC6D0-2C74-4496-82D1-064218BBE1CD" "--target" "dist-appstore"{code}
| 3 |
1,754 |
TISTUD-5651
|
11/05/2013 18:42:17
|
When doing ti info queries for devices/emulators, use --sdks arg to force latest version of SDK (>= 3.2.0)
|
We don't specify the sdk version and versions < 3.2.0 won't give us the info we want with the full listing. So in IOS and Android SDKLocators when we call out to ti info, add a "--sdks" arg and pass along the latest mobile SDk version available.
| 3 |
1,755 |
TISTUD-5652
|
11/05/2013 18:43:40
|
When there is no installed version of titanium SDK >= 3.2, don't do periodic query of devices/emulators
|
Older versions of the CLI/SDK don't give us the info, so there's no need to query periodically. We do need to remember to kick off the querying again if a newer SDK is installed after the fact.
| 5 |
1,756 |
TISTUD-5653
|
11/05/2013 18:45:37
|
Clone the "iOS Device" and "Android Device" launch shortcuts: one for < 3.2.0 and one for >= 3.2.0
|
We should keep around the current "generic" iOS Device and Android Device launch shortcuts and add to the enablement expression that they will only work for mobile SDK < 3.2.0 The cones should have enablement expressions that is for projects with titanium SDK >= 3.2.0.
| 3 |
1,757 |
TISTUD-5654
|
11/05/2013 18:45:54
|
When we dynamically update launch shortcuts, replace the 3.2.0+ version of the launch shortcut with the device-specific copies
|
When we dynamically update launch shortcuts, replace the 3.2.0+ version of the launch shortcut with the device-specific copies
| 5 |
1,758 |
TISTUD-5655
|
11/05/2013 19:22:39
|
Studio: Intermittent - Deployment Targets are not being picked up after Titanium SDK update
|
Updating Titanium SDK build for the latest and saving it in a project's tiapp.xml, is not showing android, blackberry and tizen Deployment Targets as an active, although target's boxes are checked and Studio Preferences has all platforms set. h5. To reproduce Update Titanium SDK build for the latest. Check an existing project and in tiapp.xml change Titanium SDK to the latest one. h5. Actual result Some of the platforms are not active (screenshots)
| 5 |
1,759 |
TISTUD-5657
|
11/05/2013 22:01:24
|
Mode and launch shortcut dropdowns are disabled when a module project is selected
|
Create an iOS module project and make sure it's selected in Project Explorer. Notice both the mode and launch shortcut dropdowns are disabled. Instead, we should allow "Package" mode and show the shortcut to package the module.
| 3 |
1,760 |
TISTUD-5659
|
11/06/2013 19:28:35
|
Android: Debugging does not work for android
|
h5.Descriptiom: 1.Create a breakpoint in your app at an appropriate location in the code & launch the app in debug mode. 2.Observe the results. h5.Actual Result: 1.The app launches & stays at the appcelerator splash screen. 2.The "debug on android device" dialog stays on the screen with the progress indicator spinning next to 'Device connected.Performing precompilation tasks'. NOTE : Refer that attached screen shot for reference. Expected result: 1.The app should launch & halt & the code which has the breakpoint rather than the appc splash. 2. We should be able to step over, step into etc the breakpoint. 2. The "debug on android device" dialog should complete its steps & close.
| 8 |
1,761 |
TISTUD-5660
|
11/06/2013 22:13:16
|
Add "Configurations..." to the global toolbar dropdown when package mode is selected
|
We should have a "Configurations..." option in the global device profile dropdown for when package mode is selected as we had under Publish icon in the local toolbar of Project Explorer. There should be a separator between it and the shortcuts, and it will launch the run configuration dialog instead of select it as an entry.
| 5 |
1,762 |
TISTUD-5661
|
11/06/2013 22:19:15
|
Missing run menu item on Windows
|
h5.Description There is no button to quickly run a project from Studio on Windows. I can right click on the project and select 'Run As', but there is no shortcut button on display.
| 5 |
1,763 |
TISTUD-5662
|
11/06/2013 22:24:51
|
Windows: Font size
|
h5.Decription The font size in Studio on Windows is too large to fit on screen. Only happens on tab buttons.
| 3 |
1,764 |
TISTUD-5663
|
11/06/2013 22:39:04
|
Android: Auto-create default Android emulator if none available
|
In the old version of the CLI, the CLI would auto-create AVDs as necessary. This is not longer the case. Given that a stock Android SDK does not ship with any emulators, we need to create at least one, with the most common settings based on data here: (Maybe create two, one phone, one tablet) http://developer.android.com/about/dashboards/index.html This would likely be created on startup rather than at run time, so they would be exposed in the menu as options.
| 5 |
1,765 |
TISTUD-5664
|
11/06/2013 22:48:33
|
Android: Add button to preference page to open AVD manager
|
We would like it to be relatively easy to add new Android AVDs. As such, we would add a button to the Android preference page to "Add new AVD" which would open the default Android AVD manager.
| 5 |
1,766 |
TISTUD-5665
|
11/06/2013 23:23:50
|
Make the default dark background for editor a little lighter and closer to Sublime's
|
From Ingo: "I notice the sublime default background is not quite as dark. Can we "lighten" the dark theme a bit to make it match? I think it will make the white text a bit easier to read."
| 8 |
1,767 |
TISTUD-5666
|
11/07/2013 00:29:50
|
Global toolbar: Separate out the icon from mode selection to be the action
|
Here is what Studio currently does: # User first selects a mode (run/debug/profile/test/package) by clicking on the dropdown arrow for modes # Then selects a device or emulator/simulator from the devices dropdown # Then click on the actual mode icon to launch the action This could create confusion on the difference in behavior when clicking on the icon comparing to selecting one from the dropdown. Suggest to have a workflow similar to Momentics': # Separate out the mode selection from the action, so we have one icon where clicking on it would invoke the actual action (run/debug/profile/test), and a combo box next to it with the list of modes in text where user would select one. The icon will update accordingly when the selection changes. Attached Momentics' screenshots for reference.
| 13 |
1,768 |
TISTUD-5668
|
11/07/2013 01:42:31
|
NPE when running Android platform updater
|
Using Studio 3.2 . # In Studio click Restore Defaults in Android platform settings. # Quit Studio. # Delete Titanium config file (e.g., /Users/tstatler/.titanium/config.json) # On Titanium Dashboard screen click Install or Update Android SDK to start new platform install wizard. # Select Android and click configure. Result: Error dialog: 'Configuring SDK has encountered a problem'. See attached screenshot and Titanium log file from session.
| 3 |
1,769 |
TISTUD-5671
|
11/07/2013 21:11:05
|
Studio performs platform check when opening a new Eclipse workspace
|
Steps: # Install Studio 3.2.x on "new" system and launch. Platform Configuration dialog should appear on launch. # Run Platform Configuration wizard for desired platforms. # Launch Studio in a new workspace (File > Switch workspace) Results: Platform Configuration wizard appears on launch. Expected: Wizard doesn't run again since the system was configured for development previously.
| 2 |
1,770 |
TISTUD-5672
|
11/07/2013 23:02:25
|
TiApp: Run As - The Run As button will be intermittently greyed out even after a project is selected
|
*Details:* The Run As button will be intermittently greyed out even after a project is selected. To workaround this, re-launch Studio. *Steps to reproduce:* 1. Create a Titanium app 2. Select the app in the App Explorer *Actual:* The Run As button will be intermittently greyed out (see attachments). *Expected:* The Run As button should not be greyed out.
| 3 |
1,771 |
TISTUD-5673
|
11/07/2013 23:21:25
|
Configuration: iOS - "iPad" appears in the iOS simulator configuration when running only to iPhone simulator
|
*Details:* "iPad" appears in the iOS simulator configuration when running only to iPhone simulator. *This seems like a regression as this bug does not occur on the live stack.* *Steps to reproduce:* 1. Create default Titanium app 2. Select the app 3. Debug As OR Run As iOS Simulator > iPhone 4. Once the simulator is launched, go to Debug As > Debug Configurations ... or Run As > Run Configurations ... *Actual:* "iPad" appears in the configuration (see attachment). *Expected:* "iPad" should not appear in the simulator configuration if running to iPhone simulator.
| 5 |
1,772 |
TISTUD-5675
|
11/08/2013 19:03:58
|
iOS Simulator group does not appear when only iPad is selected in tiapp
|
When only iPad is selected in tiapp, clicking on the dropdown for launch shortcuts does not show "iOS Simulator" as an entry. It works fine when only iPhone is selected.
| 3 |
1,773 |
TISTUD-5676
|
11/08/2013 19:19:59
|
Getting decoration calculation errors frequently while using appc studio 3.2.0.201311080232
|
h5.Decsription: 1. Launch appc studio 3.2.0.201311080232 & use it normally. 2. Observe the studio after some time of use like build on device & other operations. h5. Actual Result: 1. The studio becomes sluggish and we get "decoration calculation" errors. h5. Expected Result: 1. The studio should not become sluggish & we should not see any decoration calculation errors. NOTE : Refer the screenshots for reference
| 8 |
1,774 |
TISTUD-5677
|
11/08/2013 22:48:24
|
When iPhone or iPad is not selected in tiapp, the corresponding simulator shortcuts should not appear
|
When iPhone is not selected as a deployment target in tiapp.xml, we should filter out the launch shortcuts related to iPhone simulator from the list when the project is selected.
| 3 |
1,775 |
TISTUD-5679
|
11/09/2013 00:45:30
|
Studio: Run menu setting overrides wizard setting for device builds
|
h5. Description: When using the wizard to specify a target a build for attached device, but with the run menu still set at "iTunes Sync", the build will not target the device as shown in the "run on iOS device" dialog, but will target the iTunes sync. h5. Steps to reproduce: 1) Remove all existing iOS device run configurations (to prompt the dialog) 2) Attach an iOS device and "trust" the connection 3) Set run menu to "run" and "iTunes sync" 4) Click the "run" button 5) In the dialog, in the "Select Device" popup, choose the attached device 6) Finish and build the project h5. Result: Project builds for iTunes sync, not for the selected device h5. Expected Result: Project builds with attached device as target
| 3 |
1,776 |
TISTUD-5680
|
11/09/2013 00:51:55
|
Studio: iOS: Expired certificates should be filtered from the list of certificates
|
h5. Description: My particular config has a variety of expired certificates installed. None of these are visible in the keychain, but the ti info command is returning them. Studio does not filter them, so the entire list of certificates is presented for selection. This may cause confusion if an expired certificate is replaced by a new one. If both are shown, there will be no way to distinguish which is which from the dialog. h5. Steps to reproduce: 1) Remove all existing iOS device run configurations (to prompt the dialog) 2) Ensure you have expired certificates installed 3) Manipulate the popup "Select development Certificate" h5. Result: All certificates are shown, including expired certificates h5. Expected Result: Only valid certificates are shown
| 3 |
1,777 |
TISTUD-5681
|
11/09/2013 00:57:17
|
Studio: Selecting "refresh" resets the device target on the build dialog
|
h5. Description: h5. Steps to reproduce: 1) Remove all existing iOS device run configurations (to prompt the dialog) 2) Attach an iOS device and "trust" the connection 3) Click the "run" button 4) On the build dialog, set the "Select Device" popup to the attached device 5) Click the "refresh" button h5. Result: The selected device resets to "iTunes sync". All other selected items remain as they were set. h5. Expected Result: No selections are reset.
| 3 |
1,778 |
TISTUD-5682
|
11/09/2013 01:04:45
|
Studio: Global toolbar - Debug mode cannot be switched to Run
|
h5.Details Debug mode cannot be changed to Run mode. When Run mode is checked and a "run" carrot is clicked, the project is running in debug mode. In a while a "bug" sign replaces run "carrot" inside a Global toolbar. h5. To reproduce 1. Create a project 2. Change Run mode to Debug 3. Try to change it back 4. Click on a different project in a work space 5. Click on a newly created project h5. Actual result After step 5 no changes to Run mode are made. Debug mode is displayed. h5. Expected result Debug should be changed to Run
| 3 |
1,779 |
TISTUD-5684
|
11/11/2013 10:34:34
|
Appc-Studio: Machine Specific: Selecting and saving Provisioning file does not reflect when configuration window is reopened. App runs using older file when run again
|
Machine Specific issue. 1. Create a default app 2. Right click on app. --> run as -> Run Configuration 3. Select appropriate provisioning file and Save it 4. close the configuration window 5. Reopen the configuration window and observe the provisioning file saved in step 3 Actual: Provisioning file highlighted is the top most one and not the selected and saved one. On running app next time, it will not use the saved file. Expected: The selected and saved provisioning file must appear and the app must use the same provisioning file each time. Also the provisioning file must appear in appropriate order. Or the most relevant file must appear first in drop down.
| 5 |
1,780 |
TISTUD-5779
|
11/11/2013 15:17:56
|
Problem for import provisioning profile
|
h4. Problem Description Can't import new provisioning profiles within Ti Studio h4. Steps to Reproduce 1. Titanium Studio -> Preferences -> Plataforms -> iOS -> Provisioning Profile -> Browse... 2. Add a provisioning profile 3. Refresh h3. Actual Result The imported provisioning profile doesn't appear in the provisioning profile list. h3. Expected Result Properly import and display the new provisioning profile.
| 3 |
1,781 |
TISTUD-5686
|
11/11/2013 18:33:13
|
Android module packaging disappearing menu items
|
h5.Description Right clicking on an Android module project and opening the publish submenu will display three options. Closing the submenu and hovering over another item, delete for example, and reopening the publish submenu will only display one option. Then closing the submenu and opening another submenu like "run as" and reopening the publish submenu again will now display two options. Despite these menu options changing, the submenu dividers still remain for all three options. h5.Steps To Reproduce 1. Create an Android Module project. 2. Right click and hover over publish. 3. Hover over delete. 4. Hover over publish. 5. Hover over run as. 6. Hover over publish again. h5.Actual Result The amount of options to select changes h5.Expected Result The amount of options should remain the same.
| 5 |
1,782 |
TISTUD-5687
|
11/11/2013 19:05:15
|
Studio: Updates - The difference handling the license agreement
|
There is the difference handling the license agreement in Titanium and Appcelerator Studio. h5. To reproduce 1. Appcelerator Studio> Help> Check for Appcelerator Updates h5. Actual result The button "Install" is active, and "Next" is inactive, so a user cannot read and accept the license. 2. Titanium Studio> Help> Check for Studio Updates h5. Actual result The button "Install" is inactive, a user has to click "Next" and Accept the license agreement to be able to click the button "Install" h5. Expected result License agreement should be enforced in both cases
| 5 |
1,783 |
TISTUD-5689
|
11/12/2013 01:30:00
|
Console does not automatically scroll to bottom when building for device
|
Steps to reproduce: 1. Create a titanium app 2. Build the titanium app for device 3. Focus the Console view and observe Expected Result: The logs should scroll down to the bottom as there is incoming info Actual Result: The log stays in one place, and you have to manually scroll down to get the latest info
| 5 |
1,784 |
TISTUD-5690
|
11/12/2013 03:38:30
|
Configuration: iOS - "iPad" appears in the iOS simulator configuration when profiling or testing on iPhone simulator
|
*Details:* "iPad" appears in the iOS simulator configuration when profiling or testing on iPhone simulator. *This seems like a regression as this bug does not occur on the live stack.* *Steps to reproduce:* 1. Create default Titanium app 2. Select the app 3. Profile As OR Test As iOS Simulator > iPhone 4. Once the simulator is launched, go to Profile As > Profile Configurations ... or Test As > Test Configurations ... *Actual:* "iPad" appears in the configuration (see attachment). *Expected:* "iPad" should not appear in the simulator configuration if profiling or testing on iPhone simulator.
| 5 |
1,785 |
TISTUD-5691
|
11/12/2013 06:33:01
|
Add a toggle entry in launch shortcut pulldown to not auto-run when one is selected
|
After TISTUD-5666 is implemented, selecting a launch shortcut from the global toolbar will automatically launch it. We want to provide a toggle menu item where user could modify the behavior to not auto-launch on selection. The toggle should be available in the launch shortcut dropdown and in all modes, and it should apply globally to the workspace.
| 5 |
1,786 |
TISTUD-5692
|
11/12/2013 09:40:52
|
NPE displayed on Platform Configuration Wizard
|
Steps Followed: 1. On a Clean Mac machine, I downloaded the Studio Installer 2. Run the installer and let the Studio launch Actual Result: The Studio launches and a NPE error message is displayed for 'Platform Configuration Wizard'. Note: I did not open Preference or any other options for configuration I just launched the Studio on my Clean Mac machine. Please observe the attached screen shot and log file for further details.
| 3 |
1,787 |
TISTUD-5693
|
11/12/2013 18:52:12
|
Studio: Intermittent error importing KitchenSink from samples
|
An unexpected error, importing Kitchen Sink from Samples in Appcelerator Studio. Project is being imported though and it is "workable". I cannot reproduce the issue after the project's deletion and reimporting. h5. To reproduce Studio> Samples> Right click> Import sample as project h5. Actual result The project is being imported, but the error occurred
| 5 |
1,788 |
TISTUD-5694
|
11/12/2013 19:46:31
|
Studio 3.2.0 hangs when trying to select a Titanium or Alloy project from the Project Explorer view
|
ENVIRONMENT: Appcelerator Studio, build: 3.2.0.201311121653 Mac OS X 10.8.4 REPRODUCTION: Try to select an Alloy or Titanium project in the Project Explorer view. RESULTS: Appcelerator Studio hangs (the lovely rainbow pinwheel does not stop spinning).
| 3 |
1,789 |
TISTUD-5697
|
11/12/2013 22:24:49
|
Studio: Mobile Web Preview in Browser succeeded after reload only
|
*regression* after fix TISTUD-5527 h5. To reproduce 1. Create a project and run Mobile Web Preview in Browser h5. Actual result 1. Splash screen after first launch Reloading the page will open the app h5.Expected result Successful Mobile Web Preview in Browser
| 5 |
1,790 |
TISTUD-5698
|
11/12/2013 22:52:32
|
Studio: Mobile Web Preview in Browser - same tab used to launch different apps
|
h5. To reproduce 1. Create a project and run Mobile Web Preview in Browser 2. Kitchen Sink> run Mobile Web Preview in Browser h5. Actual result Same tab use to preview h5. Expected result KS should launch in a different tab *regression* does not occur in Studio 3.1.3
| 3 |
1,791 |
TISTUD-5704
|
11/13/2013 01:29:25
|
Studio: Profile as iOS device - "Waiting for profiler to connect" message window does not disappear as it should
|
{code} Node.JS Version: v0.10.13 NPM Path: /usr/local/bin/npm NPM Version: 1.3.2 /usr/local/lib ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] └── [email protected] {code} h5. To reproduce Right click on a project> Profile as iOS device h5.Actual result App is installed on to device via iTunes and it is in state "Waiting for profiler to connect". h5. Expected result Message should appear and disappear shortly
| 5 |
1,792 |
TISTUD-5705
|
11/13/2013 06:38:21
|
Newly created AVDs do not get populated in the Default Emulator drop down list
|
Steps Followed: 1. Navigate to Preferences >>Studio >>Platforms >> Android >> Manage AVDs 2. From the AVD Manager window create a new AVD 3. Observe the Default Emulator drop down list in the Studio >>Platforms >> Android window Actual Result: The newly created AVD does not get reflected in the Default Emulator drop down list in the Studio >>Platforms >> Android window. Expected: The newly created AVD should get populated in the Studio >>Platforms >>Android >>Default Emulator drop down list
| 5 |
1,793 |
TISTUD-5706
|
11/13/2013 11:24:37
|
Loading Certificates error on opening iOS Configuration Preference window
|
Steps Followed: After the Xcode setup from the terminal I opened Preference >> iOS and got the 'Loading Certificate error' prompt. Attaching the log file and screen shot for further reference.
| 3 |
1,794 |
TISTUD-5710
|
11/13/2013 21:43:51
|
Windows: Wrong icon showing for Titanium Studio
|
h5.Description The icon for Titanium Studio from 3.1.4 and up is the Eclipse logo.
| 5 |
1,795 |
TISTUD-5715
|
11/13/2013 23:23:40
|
Configuration: Installing - "iTunes Sync" will be selected in Run Configurations after installing an app to an iOS device
|
*Details:* In Run Configurations, "iTunes Sync" will be selected in the Select Device field after installing an app to an iOS device. *Steps to reproduce:* 1. Create a default app 2. Install app *straight* to an iOS device 3. Next, go to Run Configurations 4. Find the app that was installed straight to an iOS device *Actual:* "iTunes Sync" is selected in the Select Device field (see run_configuration.png). *Expected:* The device that the app was installed to should appear in the Select Device field.
| 3 |
1,796 |
TISTUD-5721
|
11/14/2013 23:00:22
|
During Tizen installation Progress dialog displays "Computing prerequisite plan"
|
Steps: 1. Run Platform Configuration wizard 2. Select Tizen (only) and click Configure and start downloading the SDK. Results: The progress dialog displays the label "Computing prerequisite plan" for the entire download. Expected: The label says "Downloading..." or something.
| 2 |
1,797 |
TISTUD-5722
|
11/14/2013 23:25:42
|
Build failed when running Android app in Debug mode
|
1. Create a default mobile project in studio. 2. Install a distribution APK on device. 3. *Don't* uninstall the distribution app from the device. Run the app in debug mode on device. 4. It shows "Build failed" message during the installing step. The log message is {code} !ENTRY org.eclipse.debug.core 4 125 2013-11-14 15:20:23.526 !MESSAGE Error logged from Debug Core: !STACK 0 java.lang.ClassCastException: org.eclipse.debug.core.Launch cannot be cast to org.eclipse.debug.core.model.IProcess at com.appcelerator.titanium.android.internal.ui.DebugLaunchStatusHandler.handleStatus(DebugLaunchStatusHandler.java:29) at com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate.cleanUp(AndroidInstallerLaunchConfigurationDelegate.java:114) at com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate.access$0(AndroidInstallerLaunchConfigurationDelegate.java:105) at com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate$TitaniumDeployListener.error(AndroidInstallerLaunchConfigurationDelegate.java:94) at com.appcelerator.titanium.core.internal.cli.TitaniumDeployManager.fireError(TitaniumDeployManager.java:67) at com.appcelerator.titanium.core.internal.cli.TitaniumDeployManager.fireError(TitaniumDeployManager.java:59) at com.appcelerator.titanium.android.core.launching.AndroidInstallAppStreamListener.streamAppended(AndroidInstallAppStreamListener.java:85) at org.eclipse.debug.internal.core.OutputStreamMonitor$ContentNotifier.run(OutputStreamMonitor.java:258) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.internal.core.OutputStreamMonitor$ContentNotifier.notifyAppend(OutputStreamMonitor.java:268) at org.eclipse.debug.internal.core.OutputStreamMonitor.fireStreamAppended(OutputStreamMonitor.java:117) at org.eclipse.debug.internal.core.OutputStreamMonitor.read(OutputStreamMonitor.java:157) at org.eclipse.debug.internal.core.OutputStreamMonitor.access$1(OutputStreamMonitor.java:135) at org.eclipse.debug.internal.core.OutputStreamMonitor$1.run(OutputStreamMonitor.java:208) at java.lang.Thread.run(Thread.java:680) {code}
| 3 |
1,798 |
TISTUD-5731
|
11/15/2013 18:33:21
|
iOS: Device Family - Device Family is not passed to the CLI
|
*Details:* When installing/packaging to an iOS device/simulator, Device Family is not passed to the CLI. *Steps to reproduce:* 1. Create a iPhone only app, a iPad only app, or a universal iOS app 2. Install/package app to a device or simulator 3. Check Studio logs *Actual:* Device Family is never passed to the CLI (see attachment). *Expected:* Device Family should be passed to the CLI.
| 3 |
1,799 |
TISTUD-5732
|
11/15/2013 21:40:13
|
iOS: Configuration - Should be able to filter for iPad simulators if installing an iPhone only app
|
*Details:* Currently, if you created an iPhone only app and want to launch a simulator, you can only select the iPhone simulator from the global toolbar (see toolbar.png). However, there should be the option to allow you to select iPad simulators from the global toolbar and Run Configurations. And, this should also apply to iPad only app i.e. if you created an iPad only app, you should *not* be able to select iPhone simulators in the global toolbar and Run Configurations. *Steps to reproduce:* 1. Create an iPhone only app from Studio 2. Go to the device global toolbar and select iOS Simulator *Actual:* Only iPhone simulators are available (see toolbar.png). *Expected:* iPad simulators should appear in the global toolbar. 3. Next, create an iPad only app from Studio 4. Go to Run Configurations for this app; iPhone simulators do not appear in global toolbar 5. Create an iOS Simulator for the app 6. Select Device Profile *Actual:* iPhone simulators appear in the drop down (see device_profiles.png). *Expected:* iPhone simulators should not appear in the Device Profile drop down for iPad only apps. *Note:*
| 3 |
1,800 |
TISTUD-5742
|
11/18/2013 10:28:54
|
Creating a mobile app without services displays Access Denied prompt
|
Steps Followed: 1. Create a Mobile app without activating services. Actual Result: An Access Denied prompt is displayed. Please refer the attached screen shot and log file for further reference.
| 3 |
1,801 |
TISTUD-5747
|
11/18/2013 21:44:00
|
iOS 7.1 beta: Studio does not recognize Xcode 5.1 DP
|
*Details:* Studio does not recognize Xcode 5.1 DP. *Steps to reproduce:* 0. Download Xcode 5.1 DP 1. Right-click in Project Explorer and go to New > Mobile App Project 2. Pick either Alloy or Classic project and click next *Actual:* iPad and iPhone check boxes are not selected (see no_check_box.png) 3. Fill in the required fields and select both iPad and iPhone check boxes 4. Click next *Actual:* Studio will have a window that says iOS is not configured yet (see ios_config.png) *Expected:* Studio should be able to recognize Xcode 5.1 DP *Note:* 1. If you pass the Platform Configuration screen, then you will be able to create the Titanium project. 2. I see this warning error in *ti info -t ios* iOS Issues ! Xcode 5.1 is too new and may or may not work with Titanium SDK 3.2.0. The maximum supported Xcode version by Titanium SDK 3.2.0 is Xcode 5.0..
| 3 |
1,802 |
TISTUD-6033
|
11/19/2013 01:02:11
|
Samples Geocoder sample has warnings - unused styling items
|
h5. Description: The Geocoder Sample has warnings on the following files, all of which are warning of unused styling components app/styles/addAddress.tss app/styles/index.tss app/styles/map.tss h5. Steps to reproduce: 1) import the geocoder sample 2) Open the file app/styles/addAddress.tss 3) Open the file app/styles/index.tss 4) Open the file app/styles/map.tss h5. Result: All have warning indications of unused styling items h5. Expected Result: No warnings
| 5 |
1,803 |
TISTUD-5754
|
11/19/2013 07:41:11
|
Dashboard: Switching between light and dark theme, does not show any effect
|
Dashboard: Switching between light and dark theme, does not show any affect. Steps to reproduce: 1. Open dashboard 2. Switch between light and dark theme under Customize your environment. Expected: Theme changes correctly in response to click. Actual: Themes are not changed and nothing happens.
| 5 |
1,804 |
TISTUD-5755
|
11/19/2013 07:44:47
|
Deleting a closed project shows error log in Studio log
|
Test Steps: 1.Create a mobile project with appcelerator services. 2.Close the project. 3.Delete the same closed project. Actual Result: error {code} !ENTRY com.appcelerator.titanium.acs.ui 4 0 2013-11-19 13:00:01.740 !MESSAGE (Build 3.2.0.201311161724) [ERROR] Resource '/defApp' is not open. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/defApp' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150) at org.eclipse.core.internal.resources.Project.hasNature(Project.java:584) at com.appcelerator.titanium.acs.ui.ACSUIPlugin$1.resourceChanged(ACSUIPlugin.java:52) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:261) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:391) at org.eclipse.core.internal.resources.Resource.broadcastPreDeleteEvent(Resource.java:2030) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:788) at org.eclipse.core.internal.resources.Project.delete(Project.java:344) at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:160) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:223) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.eclipse.core.resources 4 372 2013-11-19 13:00:01.741 !MESSAGE Resource '/defApp' is not open. {code}
| 3 |
1,805 |
TISTUD-5759
|
11/19/2013 09:20:49
|
Windows: Mobile Module Package - Unhandled Loop Exception in log though the packaging is successfull
|
Module Project Packaging: Test steps: 1. Create or use existing MobileWeb Module Project. 2. Package module using all the three available option. Actual Result: Though the packaging is successful with the display of the toast message I observed Unhandled loop exception in the log file. Please refer the attached log file for further reference.
| 5 |
1,806 |
TISTUD-5761
|
11/19/2013 10:03:11
|
Unhandled event loop exception during blocked modal context ( packaging iOS module using all three options )
|
Module Project Packaging: Test steps: 1. Create an iOS Module Project. 2. Package module using all the three available option. Actual Result: No alert is displayed. Studio logs attached .Nothing displayed on console. {code} !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275) at org.eclipse.ui.internal.progress.ProgressManager$3.run(ProgressManager.java:960) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:995) at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:970) at org.eclipse.debug.internal.ui.DebugUIPlugin.launchInForeground(DebugUIPlugin.java:1112) at org.eclipse.debug.ui.DebugUITools.launch(DebugUITools.java:759) at com.appcelerator.titanium.ui.module.AbstractModulePackagingWizard.performFinish(AbstractModulePackagingWizard.java:103) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at com.appcelerator.titanium.ios.internal.ui.launching.module.IOSPackageHandler.execute(IOSPackageHandler.java:34) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.NullPointerException at org.eclipse.debug.internal.ui.launchConfigurations.LaunchDelegateNotAvailableHandler$1.run(LaunchDelegateNotAvailableHandler.java:42) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 75 more {code}
| 5 |
1,807 |
TISTUD-5765
|
11/19/2013 14:48:06
|
Don't pop the Platform Configuration wizard on first use until after Titanium SDK/CLI are prompted and installed
|
I tried a fresh Windows 8 install, and the Platform Configuration Wizard popped up _before_ the update dialog to install Titanium SDK, CLI, etc. We need those installed to be able to do platform configuration. So we need the wizard to only open after those get installed.
| 5 |
1,808 |
TISTUD-5767
|
11/19/2013 21:47:48
|
Receive "invalid values" error when attempting to change theme
|
ENVIRONMENT: Titanium Studio, build: 3.2.0.201311160316 Mac OS X 10.8.4 REPRODUCTION: Open the Preferences dialog. Click on either General > Appearance or Titanium > Themes. RESULTS: Receive the following error: "The currently displayed page contains invalid values." (See first screen shot.) Try to click on the same items again (may need to click off the item first) and the Preference page displays an empty drop-down. (See second and third screen shot.)
| 3 |
1,809 |
TISTUD-5768
|
11/19/2013 21:58:52
|
Titanium SDK location is not persisted to configuration scope preference
|
Steps to reproduce : 1) Modify the Titanium SDK location to a non-default location and save the changes. 2) Studio still interpret the SDKs from the previous stored location (or default location). Though the SDK location is modified, it writes to the instance scope, however it reads from the configuration scope.
| 3 |
1,810 |
TISTUD-5769
|
11/19/2013 23:34:57
|
Sync back the valid Android SDK location to CLI
|
On a clean machine, the CLI is not configured with a valid Android SDK path. In that case, if Android SDK path is configured in Studio, then we should sync back the valid location value to CLI, if CLI is not set with the androidSdkPath. Steps to reproduce : 1) Configure valid Android SDK location in Studio. 2) Remove the android.sdkPath hook from titanium configuration (ti config --remove android.sdkPath). 3) Restart Studio and run code analysis for Android platform Actual : titanium command fails due to the missing android.sdkPath hook in the titanium configuration. Expected : Studio set sync the valid android sdk path to CLI during the startup, as it does not have any valid value set.
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.