diff --git "a/val.csv" "b/val.csv" new file mode 100644--- /dev/null +++ "b/val.csv" @@ -0,0 +1,585 @@ +issuekey,title,description,storypoint,split_mark +TISTUD-5251,Unified Builder error thrown on project creation,"When creating a new default project in Appcelerator Studio, the error:!MESSAGE Errors running builder 'Studio Unified Builder' on project 'sakthi' is shown. This occured for multiple project creations and in attempts to resolve the issue, the SDK was reinstalled and metadata was cleared from workspace. See logfile for further information.",3,val +TISTUD-5257,Platform configuration wizard: Provide progress on the download/install when the platforms are being configured,"After user selects the platforms and clicks ""Configure"", we should provide a progress dialog where we indicate the progress on individual platforms. User should be able to put it in the background or cancel the operation. ",13,val +TISTUD-5263,New remote's branches aren't listed in advanced pull for git,"If a user adds a new remote but doesn't perform an action that would actually fetch or hit the remote, git doesn't ""grab"" the list of branches at that remote. When a user adds a remote through studio we can pass a flag that forces an immediate fetch to help alleviate this.",5,val +TISTUD-5266,Platform Config Wizard: Auto-check if Xcode is already installed in the default location,"This is an extension of TISTUD-5241. When the wizard is opened, we should auto-detect if Xcode is already installed in the default location or if the iOS preference page already has the path (meaning user has configured it). If so, we should display the corresponding version, e.g. XCode 5.0, next to the platform checkbox instead of ""Not Configured"". ",5,val +TISTUD-5267,Platform Config Wizard: Auto-check if Android is already installed or configured,"This is an extension of TISTUD-5242. When the wizard is opened, we should check if Android is already installed in the default location or if the preference page already has a valid SDK path set (meaning user has configured it either through the wizard or set the path directly in preferences). If so, we should display the latest installed version, e.g. Android 4.3, next to the platform checkbox instead of ""Not Configured"". ",3,val +TISTUD-5268,Platform Config Wizard: Auto-check if BlackBerry is already installed or configured,"This is an extension of TISTUD-5243. When the wizard is opened, we should check if BlackBerry is already installed in the default location or if the preference page already has a valid SDK path set (meaning user has configured it either through the wizard or set the path directly in preferences). If so, we should display the installed version next to the platform checkbox instead of ""Not Configured"". ",3,val +TISTUD-5269,Platform Config Wizard: Auto-check if Tizen is already installed or configured,"This is an extension of TISTUD-5246. When the wizard is opened, we should check if Tizen is already installed in the default location or if the preference page already has a valid SDK path set (meaning user has configured it either through the wizard or set the path directly in preferences). If so, we should display the installed version next to the platform checkbox instead of ""Not Configured"". ",3,val +TISTUD-5270,Confirm support for JDK 7,"According to a variety of tickets, it _appears_ that JDK 7.0 should work for both Studio and SDK, but we currently require JDK 6. We should confirm JDK 7 works as expected, or correct (if possible) the reasons that prevent it from working.",5,val +TISTUD-5271,Platform Configure Wizard: Configure the iOS SDK,"Once user clicks ""Configure"" with iOS selected, we should open App Store with Xcode highlighted. Since we have no control on when user actually completes the install, we should poll the installation directory to check when a valid SDK is there and indicate in the progress dialog that it's complete.",8,val +TISTUD-5272,Platform Configure Wizard: Configure the Android SDK,"Once user clicks ""Configure"" with Android selected, we should download the selected versions from their respective URLs. The progress dialog should indicate the proper progress since we have the control on the process.",8,val +TISTUD-5274,Platform Config Wizard: Investigate the steps to setup Tizen on various OSes,"We will host the necessary Tizen installers/zips on our server (TISTUD-5245). However, we need to figure out if we can install silently into a specific location (preferred), if we have to run the installer for users and wait for the completion, and other potential unknowns.",8,val +TISTUD-5277,Allow user to modify the target and src branch used in generating pull request,"When we create a pull request we currently make a number of assumptions about endpoints. We assume the PR should be against the parent repo's default branch and from the current repo's current branch. We should allow the user to modify the ""head"" and ""base"" repo branches used (using a pull-down?).",8,val +TISTUD-5278,Android debug on device does not work,"Android debug on device fail to connect. The log indicates that the app is actually being launched without the debug parameters, so something probably went wrong when refactoring some of the code.",5,val +TISTUD-5281,Studio Building workspace every time I save a file,h3. Steps to Reproduce 1. Open project 2. Edit some thing 3. Run on simulator 4. Building workspace dialog shown 5. Wait for Building workspace dialog complete 6. Edit something 7. Run on simulator 8. Building workspace dialog shown 9. So on h3. Actual Result Building workspace dialog shown every time i save a file h3. Expected Result Building workspace 1 time only,8,val +TISTUD-5279,Unable to set global JSLint options,The preferences page for the JSLint validator used to have an open text field for setting options using JSON. It no longer does. Users can still set options using /*jslint comment directives in their code.,5,val +TISTUD-5282,iOS debug on Simulator fails on a second launch,"# Launch an iOS debug session on a Simulator (iPhone / iPad). # See that the session is up and running in the Debug view. # Without terminating the previous session, launch another debug session. Result: Both sessions, the old and the new, get terminated. Expected: The old session terminated, and the new one is launched.",3,val +TISTUD-5283,"Studio: warn, info, debug not outputting when debugging on phone","*Problem* When debugging an application on the phone (iPhone 4S), the Ti.API.info, warn and debug commands produce no output. *Test case* {code} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); var b1 = Ti.UI.createButton({ title: 'Button', top: 50, height: Ti.UI.SIZE, width: Ti.UI.SIZE }); b1.addEventListener('click', function() { Ti.API.warn('this is warn output'); Ti.API.info('this is info output'); Ti.API.debug('this is debug output'); }); win.add(b1); win.open(); {code} *Output* (nothing - console is blank) *Expected output* {code} [WARN] : this is warn output [DEBUG] : this is debug output [INFO] : this is info output {code} ",8,val +TISTUD-5285,Unable to view file in Resource History for git from editor,"If you right-click in a file opened in the editor that is inside a git attached project, the entry for Team > Show In Resource History is disabled.",3,val +TISTUD-5289,iOS Preference page: the Configure button should open the new platform configuration wizard,"The Configure button currently opens the dashboard. With the platform configuration wizard implemented, it should open the wizard instead, with only iOS item checked by default.",3,val +TISTUD-5290,Android Preference page: the Configure button should open the new platform configuration wizard,"The Configure button currently opens the dashboard. With the platform configuration wizard implemented, it should open the wizard instead, with only Android item checked by default.",3,val +TISTUD-5292,"Diagnostic Log - Xcode Version does not correspond Xcode Version in iOS SDK Home path, which set in Studio Preferences",The Xcode Version in Studio diagnostic log is differ from one set in iOS SDK path via Studio preferences. To compare: 1. Studio>Help>Studio>Run Diagnostic Test 2. Studio>Preferences>Studio>Platforms>iOS Actual result: Different versions of Xcode ,5,val +TISTUD-5293,BlackBerry: 10.2 update prevents Studio from using BB NDK,"h3. Description: BlackBerry has changed the flow of how we can get and install the BB 10 NDK. This prevents Studio users (and in particular, new BB users) from installing and using BB support. h4. Previously: # We get the BB 10 NDK from the BB developer website link: http://developer.blackberry.com/native/download/ provided in the appcelerator docs for BB. # Install the NDK manually. # Point studio to the NDK folder installed in the above step in preferences. h4. The new flow: # When we go to the link to download the NDK, there is no way we can download just the discreet NDK. We instead download the Momentics IDE # The Momentics installs the NDK in new locations with different paths than before. Referencing the path inside Studio prompts the user with an error about missing directories with prefix '[install]' h3. Related They also have changed the flow to get the signing keys. Now it is done through Momentics or through the website. In both cases you have to register for blackberry ID & then only can get the signing keys",5,val +TISTUD-5294,Exception in Studio Console related to loading the Ruble,"h5. Problem description When recompiling a project (Alloy), I've seen the following error in the Studio Console, which seems to be related to loading Ruble. Project is correctly compiled and built. {code} [2013-08-22 13:06:15] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) [2013-08-22 13:06:16] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) [2013-08-22 13:06:16] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) [2013-08-22 13:06:17] An error occurred while processing the invoke block for the command Comment Line / Selection in C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `getDefaultLineDelimiter' for nil:NilClass Comment.newline(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:72) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:223) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) LineComment.add(C:/Users/QEtester/Desktop/Appcelerator_Studio_3.1.2/configuration/org.eclipse.osgi/bundles/340/1/.cp/bundles/source.ruble/lib/comment.rb:217) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:56) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:53) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(C:\Users\QEtester\Desktop\Appcelerator_Studio_3.1.2\configuration\org.eclipse.osgi\bundles\340\1\.cp\bundles\source.ruble\commands\toggle_comment.rb:52) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) {code}",5,val +TISTUD-5295,Add diagnostic tests for troubleshooting npm configuration issues,"If any user has npm installation issues either with or without prefix configured, then it might not be very easy to judge the problem on the user's machine, especially with npm prefix configuration. Instead of asking user each time to run a series of commands on their machine to figure out the underlying problem, we can add those commands in the diagnostic tests and that should let us give a fair idea on what is going on user's machine with just the diagnostic test logs. When the NPM updates are invoked, either during startup or by the user - 1) It verifies whether the package is installed on the machine using 'npm -g ls ' command. 1.1) If the above command fails for any reason, then invokes 'npm -p ls -g' 2) If the package is available on the machine, it figures out the installed version and latest available version using 'npm view version' command. Also, since PREFIX is one of those dark areas, we need to add the prefix configuration to the diagnostic logs. 1) Environment variable : Get the system property for NPM_CONFIG_PREFIX 2) Get the prefix key from the npm configuration : npm config get prefix 3) If only the environment variable is set, then the local prefix config value differs from the global one. That can lead to discrepancies in the installation of npm packages. So we should get the output for : 'sudo npm config get prefix'. However, since we don't hold user's password, this might not be a feasible value to store in the diagnostic tests.",5,val +TISTUD-5296,Validate app id for BlackBerry mobile modules,"Steps to reproduce : 1) New -> Mobile Module Project. 2) Select BlackBerry platform. 3) Enter the AppId as a1.b@~1 The New mobile module wizard does not show any error about malformed appId, as other platforms. It allows to create the project, but all the required files are not generated after the module creation. Expected: Show the error about the malformed appId as other platforms.",5,val +TISTUD-5302,Launch the platform configuration wizard at startup if it is the first run,"If this is the first time user has launched Studio after installation, we should prompt the platform configuration wizard after Studio starts. For subsequent launches, we should not prompt. ",3,val +TISTUD-5307,Platform Config Wizard: Make the version string more clear,The current version displayed for each platform in the wizard is just the number and does not indicate clearly what it is for. It should be prepended by say 'Version' or 'SDK'.,3,val +TISTUD-5308,Platform Config Wizard: Improve the layout for Advanced Settings section,"When the Advanced Settings section is expanded, the section should cover the entire width of the wizard. ",5,val +TISTUD-5309,Platform Config Wizard: Hide Advanced Settings button and section for iOS,"The wizard should allow the ability for a platform to indicate it does not need an Advanced Settings section, e.g. iOS, and hide the section accordingly.",3,val +TISTUD-5310,Platform Config Wizard: Not to resize the wizard width when expanding the Advanced Settings section,"Currently when the Advanced Settings section is expanded and if the SDK location path is long, the wizard will get expanded to a width enough to show the complete path. That looks jarring. Instead, we should maintain the wizard width and set a width hint on the text field.",3,val +TISTUD-5311,"Platform Config Wizard: The ""Advanced Settings"" text should not appear grayed out","The ""Advanced Settings"" text should appear normal like for ""Hide Settings"" when the section is expanded.",2,val +TISTUD-5312,Improve performance of Android preference page,"The preference page of Android does not react immediately to user actions. For instance, - Takes long time to open the preference page. - If Configure button is clicked, then it takes a long time to open the dialog that shows the list of Android SDKs. - It takes a long time to initialize the status based on the new SDK location.",8,val +TISTUD-5327,"When Importing Project, give user option to create a copy of the project directory","When customers are importing projects (especially when moving them from Ti Studio to AppC Studio) would be useful to have an option in the import dialog to make a folder copy to the AppC Studio workspace and then import it. This way any changes made to the app when enabling services in AppC Studio would not impact the original project if we run into any issues getting the customer setup in AppC Studio (e.g. services don't enable correctly, modules fail etc., customer will want to rollback to working copy of the app while we figure things out).",5,val +TISTUD-5314,"Remove help image and link next to unconfigured platforms, use decorators and hover UI from project wizard","The existing UI for unconfigured platforms adds a help/info image which you must click on to view details. Replace with some sort of decorator with details on hover or in some summary section, like we do in the new project wizard.",5,val +TISTUD-5315,"Add an ""Install..."" button to the deploy target section. Enable when user has selected an unconfigured platform","We must enable all the deploy targets by default. If a user selects an unconfigured platform, enable an ""Install..."" button (much like the ""Enable Services"" button in Appc Studio). When clicked the button will open the new config/install wizard with the unconfigured platform(s) selected in tiapp pre-selected in wizard. Show listing of all platforms in case user wants to install multiple at same time (though selecting another platform won't affect tiapp of project that got us here).",5,val +TISTUD-5316,"Add wrench icon after each configured platform in tiapp editor to open platform prefs, remove ""Configure..."" link","We currently have a ""Configure..."" link at bottom of the listing that opens all the pref pages for the platforms. Remove that link and instead have a small wrench icon next to each configured platform that when clicked will open the preference page for that particular platform. May need to do the same next to the titanium SDK drop down to open Titanium SDK pref page?",3,val +TISTUD-5317,"Enable unconfigured platforms, reduce severity of decorators","We currently disable unconfigured platforms in the listing. We should enable them, but not pre-select them. The severity of all warnings/errors about their not being configured should be reduced to Info icons.",3,val +TISTUD-5318,"Remove the ""Configure SDKs"" link",We find the link to be an extreme edge case most users won't need now that we're providing installation of unconfigured platforms inside the wizard.,2,val +TISTUD-5319,"When unconfigured platform is selected, dynamically add install page as next page","If user selects an unconfigured page, disable ""Finish"" and enable ""Next"". Make next page be the install wizard page. Filter that page down to only the selected and unconfigured platforms. When user finishes wizard we'll install unconfigured platforms, then create project. If a platform fails to install we'll need to prompt if it's OK to create project with that platform and let them know how to install it later through tiapp editor?",8,val +TISTUD-5320,"Order Android SDK Versions in Install Wizard sorted vertically, not row with wrapping",Currently we add Android versions into a two column grid layout so the sorting looks a bit odd: {code} 4.3 4.2 4.1 3.2 ... {code} Switch to column sorting: {code} 4.3 3.1 4.2 2.3 4.1 2.2 3.2 {code},3,val +TISTUD-5321,"Install Wizard: Disable installed Android versions, but select them","Disable installed SDK versions, but select them to indicate they're installed, but can not be uninstalled through the wizard.",2,val +TISTUD-5322,"Replace the ""Configure"" Button in Android Pref page with ""Install SDKs...""","The ""Configure"" button now opens the install wizard which seems shoe-horned. Replace the button with an ""Install SDKs..."" button that opens a dialog that contains only the Android SDK listing (currently inside the install wizard's advanced settings section for Android) and lets you choose additional versions to install.",8,val +TISTUD-5324,Make iOS SDK/XCode path uneditable label in pref page,If the user cannot set it through a preference then we should change from a text field to an uneditable label.,3,val +TISTUD-5325,"Replace ""Configure"" button in iOS pref page with ""Install"" or ""Update"" button","Clicking ""Configure"" doesn't make much sense to then bring up the install wizard. If there's a valid XCode detected, replace with an ""Update..."" button that opens Mac App Store to Update tab. If there's no valid Xcode selected, replace with ""Install..."" button that opens Mac App Store to XCode page (like the install wizard does).",5,val +TISTUD-5326,Show some visual indicator in install Wizard UI to indicate when an install will happen for a platform,"We want to be able to indicate to the user when we're going to actually download and install something versus when we'll just take the SDK path and save it. They may have made a typo in typing path to an existing install, so it'd be nice for them to see if we were unable to find an SDK at the path and are going to install one to the path.",8,val +TISTUD-5329,Auto select platform if the advance section details are modified,"In the platform configuration wizard, in case if Android is not selected and if the user modifies any SDK entities in its advance section, then the Android platform has to be selected automatically for the user. This will be application for all platforms in case if the SDK location path is modified.",5,val +TISTUD-5330,"Enable unconfigured platforms, reduce severity of decorators","We currently disable unconfigured platforms in the listing. We should enable them, and the severity of all warnings/errors about them not being configured should be reduced to Info icons.",3,val +TISTUD-5331,"Remove the ""Configure SDKs"" link",We find the link to be an extreme edge case most users won't need now that we're providing installation of unconfigured platforms inside the wizard.,2,val +TISTUD-5332,"When unconfigured platform is selected, dynamically add install page as next page","If user selects an unconfigured platform, disable ""Finish"" and enable ""Next"". Make next page be the install wizard page. Filter that page down to only the selected platform. When user finishes wizard we'll install the unconfigured platform first, then create project. If a platform fails to install we'll need to prompt if it's OK to create project with that platform and let them know how to install it later through tiapp editor?",8,val +TISTUD-5337,Loading iOS provisioning profiles: Improve the error message when CLI is not found,"If the CLI is not installed or if it is installed to a location that is not in user's PATH, user will run into a NPE when the provision profiles are loaded. We should better handle such cases. ",5,val +TISTUD-5339,Android: Emulator: Enable Fastdev for 3.1.3+ SDK,"Application with fastdev enabled in the tiapp.xml when executed in emulator, Fastdev server doesn't run. Fastdev is enabled and server runs with android 2.3.3 on emulator. Issue occurs with Android version 4.1 and later. Steps to reproduce: 1. Create a default project in the appcelerator studio. 2. Add true in the tiapp.xml. 3. Run the app with Android 4.1.2 on emulator. Expected: App should run with fastdev server running. Should get log as "" Fastdev server running, deploying in Fastdev mode"" Actual: Getting log as ""Fastdev enabled but server isn't running"" on the console.",3,val +TISTUD-5338,"Unable to format TSS files in TiStudio 3.1.2 + 3.1.2, works in TiStudio 3.1.1","1. Install Titanium Studio 3.1.2 or 3.1.3 and Update SDKs, install Alloy 2. Create a new Mobile Project, Alloy Default Template 3. Load the App.tss file 4. Click MENU / SOURCE / FORMAT or CMD + Shift + F 5. Error reported in the status bar, ""Unable to format"" and log will show Formatter error: startOffset > endOffset Also reported if you go to Menu > Titanium Studio > Preferences, go to Formatting and click the TSS entry - OSX will ""beep"" and the error is reported in the status bar / log. Does not occur on Titanium Studio 3.1.1 but upgrading to 3.1.2+ will create the behaviour. Reported by user here:- http://developer.appcelerator.com/question/156297/formating-tss-file-formatter-error-startoffset--endoffset with log details.",5,val +TISTUD-5345,Show indefinite progress for iOS SDK configuration with status message,The iOS SDK configuration/installation status does not show any progress and the SDK installation status message 'Installing..' may not be applicable for iOS. 1) Show indefinite progress for the iOS sdk installation. 2) Show the sdk status message indicating that we are waiting for user to install Xcode,3,val +TISTUD-5350,Platform Config Wizard: iOS: move the visual indicator for downloading to the right-most column,"Related to TISTUD-5326. For iOS, currently there is no Advanced Settings section, and the visual indicator will appear in its place, making the UI feel inconsistent. The suggestion is to line it up on the right as indicators for other platforms are.",3,val +TISTUD-5352,Platform Config Wizard: update the description once we are in the progress page,"When we move into the progress page, we should update the description to indicate we are now configuring for the selected platforms.",2,val +TISTUD-5353,Platform Config Wizard: the progress page should only contain the platforms we're configuring,"Currently we show all the platforms, but it feels confusing to me in seeing the other platforms that I didn't choose to configure there. User could feel they can still do something with the other platforms in the mean time even though they always indicated they are not interested in them at this point. We should just show the selected platforms and their progress instead.",5,val +TISTUD-5354,Platform Config Progress Page: remove the progress bar and cancel icon when a platform is completed,"When we finish configuring a platform, we update the status and its icon in the middle, but the cancel icon and progress bar on the right still remain. They should be hidden at this point. Similarly when user cancelled the operation, we should hide the progress bar once the cancellation process is done as well. ",3,val +TISTUD-5355,Platform Config Wizard: modify the status when we finish configuring a platform,"When we finished configuring a platform, we should update the status area to display two lines: the regular check mark and latest installed version on top, and the installation location below. The Settings text and arrow should remain hidden. If the installation is canceled, we should show ""Canceled"" status but without any icon.",5,val +TISTUD-5359,Store platform SDK paths preference in configuration scope instead of instance scope,"Currently we save platform SDK paths in InstanceScope; that means the settings are per workspace, and each time user switches to a new workspace, they need to re-configure the platform SDK paths. The suggestion is to save platform SDK paths in ConfigurationScope so they persist per installation. We need to make sure we migrate existing paths from InstanceScope so users don't need to re-configure after update, and once we make the change, the auto-launch of platform configuration wizard should happen per installation instead of per workspace as well. ",5,val +TISTUD-5360,Platform Config Wizard: Android advanced section: list available SDKs horizontally by major version,"There are a lot of empty spaces to the right when Android advanced settings section is expanded. This is because the versions are listed vertically with a height limit. The suggestion is to list them in three rows: one for 4.x, one for 3.x, and one for 2.x. ",5,val +TISTUD-5362,Platform Config Wizard: modify the wizard description to provide more info,"Currently the description just says ""Select platforms to configure"". It doesn't really add more information to the title in explaining what the wizard does. We should improve the message. A suggestion: ""Download, install, and configure required SDKs for the mobile platforms you would like to develop for."" ",2,val +TISTUD-5364,Platform Config Wizard: disable Finish button when there is an error in inputs,"I entered an Android SDK directory that I do not have write permission to; an error is displayed next to the text field, but the Finish button is still enabled. ",5,val +TISTUD-5365,Platform Config Wizard: selection and enablement of Android SDKs do not get updated when directory changes,"My Android location was pointing to one with existing versions installed. When I switch to a brand new location, the state of checkboxes does not get updated accordingly. I would expect all of them to get enabled with only the minimum version (2.3.3) and probably the most popular version selected. ",3,val +TISTUD-5439,"CLI: Change in required query from ""ioscerts"" to ""certs"" causes Studio NPE and inability to build for iOS device","h5. Description: Trying to build for iOS device with CLI 3.2.0 and SDK 3.2.0 results in failure to open Studio dialog requesting info on developer cert and SDK info. Looking in the log you can see that there is a null pointer exception. Looking at the ti info -t ios -o json output, you can see with 3.1.2 CLI it's: ""iosCerts"": { with 3.2.0 CLI it's: ""certs"": { h5. Steps to reproduce: 1) Install CLI 3.2.0 (sudo npm install -g git://github.com/appcelerator/titanium.git) 2) Acquire a 3.2.0 SDK 3) In studio, try to build a project for iOS device h5. Result: Failure with NPE in studio log h5. Expected Result: Device build succeeds",5,val +TISTUD-5366,Platform Config Wizard: only auto-check the platform entry when the state in advanced settings section is different from original,"Currently we auto-check the platform entry in platform config wizard when user modifies any fields in Advanced Settings section. However, this creates the following situation: 1. Uncheck Android, expand Advanced Settings section and check one of the uninstalled Android versions (e.g. 4.2); this will make Android correctly checked. 2. Then uncheck Android again and uncheck the same Android version (e.g. 4.2); the Android platform will become checked again, even though we are actually back to the original state when the wizard first opened. Expected result: we should only auto-check the platform entry when the state is different from the original.",5,val +TISTUD-5368,Platform Config Wizard: Display the EULAs for selected platforms in separate dialog,"Since we are downloading and installing Android, BlackBerry, and Tizen SDKs directly from the platform config wizard, we need to display the respective EULAs for user to accept. This ticket is to implement the UI for accepting EULA. We will open a separate dialog for EULA when user clicks Finish to configure the list of selected platforms. The dialog will just contain a large multi-line text field where it contains the EULA text for each platform in sequential order. The dialog will have two buttons - Accept and Decline, and user doesn't need to scroll down to the bottom of the text to have Accept enabled. When accepted, we will move to the progress page; when declined, we will close the platform config wizard.",8,val +TISTUD-5369,Tiapp Editor: make the wrench and info icons on the same side,"Currently the wrench icon appears on the left of platform checkbox, while info icon appears on the lower right. Since the two are mutually exclusive, i.e. only one could appear at any time, the suggestion is to line them up on the same side. ",5,val +TISTUD-5370,Tiapp Editor: prompt user when saving tiapp with unconfigured platforms selected,"In 3.2.0, users could select platforms that they haven't configured Studio with yet, and the concern is that it could cause confusion if user doesn't see the Install button and wonders why he/she can't run the app from menus after selecting the platform in tiapp. The suggestion is when tiapp editor is saved, if there are unconfigured platforms selected, we prompt users so they could setup the platforms there. ",3,val +TISTUD-5378,"Formatter fails on javascript ""switch/default"" braces block",var a; switch(a) { case 1: { a = b; break; } case 2: { a = b; break; } default: { /* this braces are the cause of formatter crash */ b = a; } },5,val +TISTUD-5372,Platform Config Wizard: Android: select 4.1.2 and 2.3.3 by default when a new SDK home is specified,"Currently we are only selecting Android 2.3.3 by default. Instead, we should select it and the most popular version, currently 4.1.x (36.6% as of 09/04/13), and make the most popular one the default. ",3,val +TISTUD-5381,Studio: Add support for iOS 7 64 bit simulator ,"h5. Description: Xcode 5 GM seed includes a new simulator that is not exposed via the launch configurations within studio. This new simulator is iOS 7 only, ""iPhone 5 (4-inch 64-bit)"". We should add support for running this simulator to Studio. h5. Steps to reproduce: 1) Install Xcode 5 GM seed 2) Install command-line tools 3) Open iOS simulator and navigate to hardware>device - note the new simulator 4) Open run configuration in Studio for iOS sim h5. Result: No options are available to configure launch of the 64 bit simulator h5. Expected Result: The 64 bit simulator can be configured and launched",5,val +TISTUD-5383,Add platform image to each platform section,"As shown in the screenshot, a image has to be added prior to platform checkbox button. The chopped 1st half of the image should appear in the platform section and the other half in the advance section. So when the advance section is expanded, the complete platform image should appear (as shown in the screenshot).",8,val +TISTUD-5385,Platform Config Wizard: Improve the initial layout,"# Make the Advanced Settings text and arrow right-aligned # Move the arrow to the right of the text # Modify the text to say ""Settings"" when collapsed and ""Hide"" when expanded # Make the status center-aligned # Remove warning icon for ""Not Yet Configured""",5,val +TISTUD-5386,Platform Config Wizard: Change Hide button to Close and remove Cancel button when all platforms are finished configuring,"When all selected platforms are done configuring (or the process got canceled), we should change the Hide button to Close and remove Cancel. ",5,val +TISTUD-5387,"Platform Config Wizard: Change ""Finish"" button to ""Configure""","In the initial page, ""Configure"" makes more sense as an action than ""Finish"". ",1,val +TISTUD-5388,Platform Config Wizard: create a gradient effect from the platform section to its settings section,"To improve the background transition from the main platform section to settings section, a suggestion is to add a gradient in the middle. ",5,val +TISTUD-5389,Platform Config Wizard: improve the wizard image,Tyrus provided the attached image to replace the gear. ,2,val +TISTUD-5390,Platform Config Wizard: Align the start of text in settings section with the platform entry,"The screenshot shows the left bound of settings section matches with the checkbox. The suggestion is to match it with platform name instead. If that causes too much space on the left visually, then we will revert to implement based on this screenshot. ",5,val +TISTUD-5392,Have a separate progress job for the platform configuration process,"Besides the progress bars inside the platform config wizard, we should have a progress job for the overall process as well so it would be available in Progress view, and if user hides the wizard and loses it for some reason, they could still check on the progress in Progress view.",5,val +TISTUD-5393,Show a toast when platform configuration process completes,"When platform configuration process completes, if the wizard is still up, user could just check on the status there, but if user hide the wizard, we should show a toast with message like ""Platforms are configured. Please click to see more details."" When user clicks on the toast, we will re-open the platform config wizard that shows the status and installation location for each platform.",5,val +TISTUD-5394,Mobile Web configuration: load browsers info in the background when platform config wizard is opened,"Currently the browser information is loaded when Dashboard opens. Since we are moving to the new platform config wizard for configuration, the information should be loaded when the wizard opens. ",3,val +TISTUD-5395,Platform Config Wizard: Progress page: use the stop icon for cancel,The current cancel icon looks disabled. The suggestion is to use the stop icon seen in Console and Debug views.,2,val +TISTUD-5400,Show link in the progress job to open the configuration wizard,"If the platform configuration wizard is hidden, then we show the toast message to get back the hidden dialog. However, if the user accidentally closes the toast message, then there is no way to get back the configuration wizard dialog. - As the Eclipse jobs support adding a link with the progress task, add a link in the progress job to allow users to open the hidden configuration wizard dialog. - Parameterize the command so that the wizard dialog shell can be passed around to display back the wizard dialog. ",5,val +TISTUD-5401,Studio 3.2: Search shortcut does not focus on the search bar if focus is in the code,"h2. Steps to reproduce Using Studio 3.2, perform the following steps: (1) Click into an open text file (2) Press Command+F (3) Write something in the search box and do not press enter (4) Click back into the open text file (5) Press Command+F The second time pressing CMD-F does not focus anymore into the search bar. Works fine in 3.1.3",5,val +TISTUD-5403,Platform Config Wizard: Keep status icons and messages vertically-aligned respectively,"The latest screenshot from Tyrus was indicating we wanted to make the middle column center-aligned, and we implemented as part of TISTUD-5385. However, with everything else vertically aligned, it seems to make more sense if we keep both status icons and status messages vertically aligned respectively, while still keeping the overall column as centered as possible.",3,val +TISTUD-5408,Update JDK version included in Studio installer to JDK7,"We currently include JDK6 in Studio installer. Since we confirmed Studio and SDK work with JDK7, we should update the version. ",5,val +TISTUD-5416,Make npm packages required installs and not allow user to dismiss required installs,"We currently prompt for some required installs/updates but not in some cases. An example is that if the user has no Titanium SDK installed we will silently install one for them. But we prompt the user to install Titanium SDK updates, NPM packages (and updates), Node.js. If a given component is required, we should not allow the user to dismiss the install - thus helping to avoid invalid setups because user's didn't accept. Obviously, this will still force sudo prompts on Mac/Linux for some of the installs right now (since npm packages are installed globally, and I think we need sudo rights for installing Node?). From Aditya: {quote} I can't count the number of times over the past several weeks where we have worked with every developer, tester, partner etc. and they only complete half the setup because they don't read the docs. E.g. ""Oh I need Xcode/Android sdk?"" or ""Oh I ignored that failure message on setting up node.js"" or ""oh I need to accept and install all the updates from Studio?"" {quote}",5,val +TISTUD-5417,Inconsistent PATH lookup for Node and other components,"From Aditya: {quote} We also run into issues where the system path has been changed by the dev for some components (e.g. Node.js) but is not the same as the path that we check for our updates, which causes challenges when running updates. This pathing issue is both a Mac issue (where they edit their .bash profile and install paths e.g. VMware put node in /opt instead of the default location and then the installer went into loop checking for node updates and installing) and Windows issue (where IT redirects installs from the user directory to some other path that they standardize on an NFS share for all end users) {quote} I think we need more details here. Are they installing multiple Node.js installations? Does this mean they're pointing at a specific install in the prefs but we're not honoring it? Are we just not picking up existing installs?",5,val +TISTUD-5418,Add detection of existing BlackBerry installs,"Right now we force the user to set the path to their BlackBerry install and then we ""double-check"" it by looking in a known location for the list of installs and matching the path value. The configuration wizard helps in providing default paths that are common for OSes, but still requires the user to go through the wizard (and assumes they have installed to this known default path). Instead we can simply look at the config path where BlackBerry has a listing of SDK installs. We should schedule a job on startup to do this if no valid value is set in prefs. {{BlackBerrySDKLocator.getBlackBerryConfigurationPath()}} and {{SdkManagerActionUtils.getQNXConfigurationPath()}} both deal with looking at this known location and reading the XML files listing the installs.",5,val +TISTUD-5419,Improve detection of existing Node.js installs using registry on Windows,"Our current detection of Node.JS looks in the PATH and some known default locations: For Windows: {code} private static final String PROGRAM_FILES_X86_NODEJS_NODE_PATH = ""%ProgramFiles(x86)%\\nodejs""; //$NON-NLS-1$ private static final String PROGRAM_FILES_NODEJS_NODE_PATH = ""%PROGRAMFILES%\\nodejs""; //$NON-NLS-1$ {code} For Mac/Linux: {code} private static final String USR_LOCAL_BIN_NODE = ""/usr/local/bin""; //$NON-NLS-1$ {code} While that should generally pick up installs if the user's PATh is set properly, it's also possible we can grab information on Node installs from the Windows registry.",5,val +TISTUD-5421,"If user has error in advanced settings and unchecks platform, they're still unable to proceed","If I enter a bad path to Android SDK (not writable or file already exists at that path), then decide to uncheck Android - the wizard won't let me proceed because of the sdk path error.",3,val +TISTUD-5422,UI blocked during install of Selected Platform SDK,"I added Tizen in my tiapp and saved. I was then prompted to set up Tizen, so I chose to. It started installing in the wizard and showing progress. I chose ""Hide"" and saw that the UI is now ""blocked"". I get a black and white ball when I try to interact with the tiapp editor, change editor tabs, change view tabs. I think this may only happen if the wizard is invoked during the tiapp save?",5,val +TISTUD-5423,Invalid thread access exception while changing the tiapp sdk preference,"I have notice the below exception after playing around with tiapp file and sdk locations. ENTRY org.eclipse.equinox.preferences 4 2 2013-09-20 13:48:35.238 !MESSAGE Problems occurred when invoking code from plug-in: ""org.eclipse.equinox.preferences"". !STACK 0 org.eclipse.swt.SWTException: Invalid thread access org.eclipse.swt.SWT.error(SWT.java:4397) org.eclipse.swt.SWT.error(SWT.java:4312) org.eclipse.swt.SWT.error(SWT.java:4283) org.eclipse.swt.widgets.Widget.error(Widget.java:783) org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:574) org.eclipse.swt.widgets.Combo.getSelectionIndex(Combo.java:888) org.eclipse.jface.viewers.ComboViewer.listGetSelectionIndices(ComboViewer.java:124) org.eclipse.jface.viewers.AbstractListViewer.getSelectionFromWidget(AbstractListViewer.java:280) org.eclipse.jface.viewers.StructuredViewer.getSelection(StructuredViewer.java:1045) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppSDKSection.getSupportedPlatformSDKs(TiAppSDKSection.java:436) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.updateControlsEnablement(TiAppDeployTargetsSection.java:370) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection$1.preferenceChange(TiAppDeployTargetsSection.java:167) org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899) org.eclipse.core.internal.preferences.EclipsePreferences.put(EclipsePreferences.java:912) com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.setSDKPath(BaseMobilePlatformConfigurer.java:102) com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.doConfigure(BaseMobilePlatformConfigurer.java:68) com.appcelerator.titanium.tizen.ui.configuration.TizenSDKConfigurer.doConfigure(TizenSDKConfigurer.java:77) com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.configure(BaseMobilePlatformConfigurer.java:44) com.appcelerator.titanium.ui.wizard.PlatformsConfigurationWizard$1.run(PlatformsConfigurationWizard.java:119) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)",3,val +TISTUD-5424,NPE while creating Android advance section details,There are series of NPEs while opening and playing around with the platform configuration wizard : !ENTRY com.appcelerator.titanium.android.ui 2 0 2013-09-20 11:52:15.304 !MESSAGE (Build 3.2.0.201309201506) [WARNING] null !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.android.internal.ui.update.SDKReleaseProvider.collectMainRepositoryItems(SDKReleaseProvider.java:386) com.appcelerator.titanium.android.internal.ui.update.SDKReleaseProvider.getReleases(SDKReleaseProvider.java:103) com.appcelerator.titanium.android.internal.ui.update.SDKReleaseProvider.getEligiblePlatformReleases(SDKReleaseProvider.java:503) com.appcelerator.titanium.android.internal.ui.configuration.AndroidSDKComposite$1.run(AndroidSDKComposite.java:89) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53),3,val +TISTUD-5425,Improve the advance section layout of platforms configuration page in new mobile wizard,"In the new mobile project wizard, if the unconfigured platforms are selected, it adds a new page for configuring the platforms. The layout of advance details section has to be improved to remove the empty space (as shown in the screenshot). ",5,val +TISTUD-5431,Node Package Installer: application npm install location is incorrect,"1. Delete Global Appcelerator NPM Packages. 2. Install Titanium/Appcelerator Studio. 4. Run Studio and accept npm package updates. Result: The updates are locally installed to a folder other than the one studio was run from. See screenshot. Expected Result: The updates are globally installed. Note: If you try to run studio commands that require the npm packages, they will fail. {code} Launching simulator process failed Unable to locate the CLI executable. Please restart Studio or use Help > Check for Appcelerator Updates to install Titanium CLI. {code} Studio looks here no matter what (and the commands fail): {code} /Applications/Appcelerator/Appcelerator_Studio_3.1.3/AppceleratorStudio.app/Contents/MacOS/Password:/usr/local/lib ├── acs@1.0.6 ├── alloy@1.2.2 ├── titanium@3.1.2 └── titanium-code-processor@1.0.3 {code} Workaround: {code} npm set prefix /usr/local {code}",8,val +TISTUD-5433,Unable to run a Mobile Web project with Studio 3.2.0,"ENVIRONMENT: Titanium Studio, build: 3.1.3.201309132423 Appcelerator Studio, build: 3.2.0.201309202153 TiCLI from master 9/18 node-appc from master 9/18 TiSDK 3.1.3.GA and 3.2.0.v20130918150842 Chrome Version 29.0.1547.65 Android 4.2.2 Emulator REPRODUCTION: Create a default project in Studio 3.2.0 and run for Mobile Web in the Browser or Emulator. RESULTS: Receiving a ""Wait for "" message in the browser. App does not run. NOTE: Works fine for Studio 3.1.3 and TiSDK version did not matter.\ Attaching complete diagnosis test and console log of build. ",5,val +TISTUD-5434,Avoid installing npm packages globally,"Studio should install npm packages locally into a folder accessible to the user without sudo permissions (to avoid problems described at TISTUD-5428) In order to accomplish this - 1) Currently we set global flag for any npm package installation. Mark all actions with npm packages without global to make them local installations. 2) The npm packages can not be installed/queries in the .titanium or .npm folders under home directory. The folder name can not start with dot. 3) Remove the check for alias bin files in the /usr/local directory - as the local installation will not create symlink files in /usr/local directory. 4) Cleaning the cache sometimes requires sudo permissions - so we still need to prompt for password. However, use this password only for cleaning the cache. ",8,val +TISTUD-5440,"New Mobile Project wizard: Selecting a Titanium SDK after deselecting deployment targets, reenables all deployment targets","ENVIRONMENT: Mac OS X 10.8.4 Appcelerator Studio, build: 3.2.0.201309202153 REPRODUCTION: 1. From the menu bar, select New > Mobile Project. 2. In the wizard, select any template and click next. 3. Deselect a few deployment targets. 4. Change the Titanium SDK version. EXPECTED RESULTS: Deselected targets stay deselected. ACTUAL RESULTS: All targets are selected.",3,val +TISTUD-5441,Studio doesn't disable platforms that aren't supported by the Titanium SDK version,"Our New project wizard and the tiapp editor, we changed to allow users to be able to select ""unconfgiured/uninstalled"" platforms. We did so by forcing any status validation down to an info level and never disabling platforms. The reality is that there is a definite case where platforms need to be disabled: when the Titanium SDK version chosen has no support for that platform.",3,val +TISTUD-5443,Android:CLI - JSON payload change results in Studio unable to find Android SDK,"h5. Description: Since the JSON payload within the 3.2.0 CLI changed structure, Studio can no longer determine that the Android SDK is configured correctly. This may take a restart of studio or some time to clear the cached data in order to witness. The issue generally manifests itself first as a dialog show in the attachment ""firstDialog.png"" This prevents studio users from being able to build with Android. h5. Steps to reproduce: 1) Use Titanium Studio 3.1.3 2) Install CLI 3.2.0 using: ""sudo npm install -g git://github.com/appcelerator/titanium.git"" 3) Install SDK 3.2.0 (CLI currently has an issue, so use Studio) 4) Set CLI selected SDK to 3.2.0 with: ""ti sdk select "" 5) Restart studio -additional note: you can use command ""ti info -o json -t android"" to see the difference in the structure of the payload regarding the Android SDK. h5. Result: You may see the ""computing SDK info"" error first. The Android SDK is no longer configured correctly and Studio will prompt the user to specify the Android SDK install location when trying to build for Android. Studio dashboard shows Android SDK as not configured. h5. Expected Result: Android SDK still working and user is able to build for Android. ",5,val +TISTUD-5444,Improve the performance of Build workspace job,"The build workspace job is constantly invoking the external process to query the version of node and modules prefix path. The Studio log contains a series of references to the external processes during workspace build operation. !ENTRY com.aptana.core 1 0 2013-09-26 17:12:16.378 !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/node"" ""-v"" Working directory: null Environment: null !ENTRY com.aptana.core 1 0 2013-09-26 17:12:16.417 !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/node"" ""/usr/local/bin/npm"" ""config"" ""get"" ""prefix"" Working directory: null Environment: null Since the values of these parameters are unlikely to change, we should cache those values and reuse them for every inquiry.",5,val +TISTUD-5446,Show EULA dialogs when the platform is installed through new mobile wizard,"We currently show the EULA dialog only when the platforms are installed through Platform configuration wizard. However, if the platforms are initiated to get installed through new mobile app or module wizard, then the EULA dialog is not prompted to the user.",3,val +TISTUD-5452,Modify launch shortcuts to use device profiles rather than generic iPad/iPhone sim targets,"We currently have generic ""iPhone Simulator"", ""iPad Simulator"", ""Android Emulator"" shortcuts defined for generating pre-canned launch configs. We need to move towards pre-defined ""device profiles"". The first step is replacing these generic shortcuts with ones for target devices, like ""iPhone 3.5-inch"" or ""iPhone 4"" (the same listing as XCode). These launch shortcuts will pre-populate the config attributes to toggle tall/retina/etc flags for the user.",8,val +TISTUD-5453,Modify the config UIs to have combo boxes for device profiles rather attribute checkmarks for tall/retina,"Once we have device profiles defined (by CLI, and given to us by ""ti info""?). We should replace the current UI we have in launch configs for tall/retina with a combobox to select from the device profiles. We should ""migrate"" existing configs to pre-select the most applicable/relevant device based on settings. We'll likely also need to pass the device name down to the CLI (or expand out it's args and pass those?)",8,val +TISTUD-5454,Collapse the Run/Debug/Profile/Test/Package icons into UI like XCode/Momentics,"We have each mode broken out as it's own pulldown menu. We should adopt the XCode/Momentics UI where there's a giant ""play""/Run button that is pulldown to select mode (and clickable to launch), and then a trailing combo with the shortcuts/targets to launch. Decision is to not mimic the big stop button for now (and handle version later). This will be available in the global toolbar, and the corresponding icons will be removed from local toolbar of App/Project Explorer.",8,val +TISTUD-5455,Remember last mode/config per-project and change UI to last one when project selection changes,"Once we have the new UI, we should remember the last launched mode/target/config for each project and when project selection changes reset the Ui to match the last chosen for that project.",5,val +TISTUD-5457,Combine update mechanisms,"We currently have two major update mechanisms, prompts and UIs. We have our own for NPM packages, Node, SDK - and then we have the standard eclipse p2 mechanism for updating Studio and plugins. The result is two separate prompts, two separate UIs and an inconsistency in installation. We want to only prompt once, all at the same time and be able to resolve dependencies between the two systems (i.e. if the CLI makes a breaking change that requires a new studio update). ",8,val +TISTUD-5459,Combine our update popups,"We currently have two separate update popups/checks: one is the Eclipse p2 update check and will update Studio itself. The second is our own check for updates to NPM packages, the SDK and other modules/components. This results in an inconsistent UI. We should ideally update Studio through the same update check job and UI. There are wiki pages devoted to how you can alter p2 behavior at http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application#Reassembling_the_UI The basic gist of it is that we may want to copy and fork the p2.ui.sdk.scheduler plugin rather than just include it. That includes the standard automatic updates check and popup. We can then make our version do both checks and present our own UI. Another alternative is to write p2 repository related code to allow loading the SDK metadata/artifacts and NPM package metadata/artifacts and converting them into the p2 model. That would make the same check for update job check all of them, but we'd still need our own custom UI override (though we may then be able to add metadata to the CLI package.json to do dependency checking against Studio?).",8,val +TISTUD-5462,The default user agents for Alloy and Node.ACS should refer to mobile platforms,"The current default preferences for Alloy and Node.ACS project's user agent refers to the browsers such as Chrome, Firefox and IE. For Titanium and Appcelerator Studio, the default user agent should refer to mobile platforms (such as Android, iOS and others if required).",3,val +TISTUD-5465,Studio freezes for a moment when loading Deploy Targets section of tiapp editor,"If Studio is closed with an active TiApp editor, then during the restart of Studio, it tries to activate the TiApp editor from the previous session. While it tries to open the TiApp editor, it ends up in loading the Android AVDs and that causes freeze momentarily. Here is the stacktrace excerpt during the startup of Studio : com.aptana.core.util.ProcessUtil.processData(ProcessUtil.java:232) com.aptana.core.util.ProcessUtil.processData(ProcessUtil.java:187) com.aptana.core.util.ProcessUtil.processResult(ProcessUtil.java:142) com.appcelerator.titanium.core.cli.NodeJSExecuter.runCommand(NodeJSExecuter.java:210) com.appcelerator.titanium.core.cli.NodeJSExecuter.runCommandWithNoLogin(NodeJSExecuter.java:410) com.appcelerator.titanium.android.core.launching.AndroidNodeJSCommandsHelper.getAndroidTargets(AndroidNodeJSCommandsHelper.java:118) com.appcelerator.titanium.android.core.AndroidSDKLocator.getAVDs(AndroidSDKLocator.java:254) com.appcelerator.titanium.android.core.AndroidSDKLocator.initialize(AndroidSDKLocator.java:132) com.appcelerator.titanium.core.mobile.SDKLocator.lazyInitialize(SDKLocator.java:149) - locked <7b0ae4158> (a com.appcelerator.titanium.android.core.AndroidSDKLocator) com.appcelerator.titanium.core.mobile.SDKLocator.getAvailable(SDKLocator.java:274) com.appcelerator.titanium.core.internal.mobile.MobilePlatformsRegistry$LazyMobilePlatform.configurationStatus(MobilePlatformsRegistry.java:310) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.updateControlsEnablement(TiAppDeployTargetsSection.java:456) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.initialize(AbstractTiAppSection.java:72) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.initialize(TiAppDeployTargetsSection.java:208) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.(AbstractTiAppSection.java:55) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection.(TiAppDeployTargetsSection.java:144) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppFormPage.createFormContent(TiAppFormPage.java:100) org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) ",8,val +TISTUD-5467,Clean up icons in the global toolbar,We want to go through each icon in the global toolbar and remove the ones rarely used by users. The suggestion is to remove the following: # Save # Save All # Print # Theme # Run/Debug/Profile/Test related actions (since we will re-design them in TISTUD-5454) # Open URL # Toggle Block Selection # Show Whitespace Characters ,5,val +TISTUD-5468,By default do not show text for the list of open perspectives in global toolbar,"Momentics has the ""Show Text"" off by default, and it saves space in global toolbar. ",2,val +TISTUD-5469,Editor: remove the black folding gutter or color it correctly,We should find a way to not have the black gutter affect the visual appeal. ,3,val +TISTUD-5470,Remove App Explorer,The feeling is App Explorer doesn't add compelling value and feels redundant next to Project Explorer. We will hide/deprecate it from default Studio perspectives but keep the plugin. ,3,val +TISTUD-5471,Remove Local Filesystem from Project Explorer,"It is unlikely user would use Studio to browse local filesystem, and Titanium development is very much project-based, so we should remove the node for Titanium/Appcelerator Studio. We will still keep it for Aptana Studio. ",5,val +TISTUD-5472,Enable global toolbar for the simple Studio perspective,"Once we clean up the global toolbar and add the new UI for device profile, we should re-enable global toolbar for the simple perspective. ",2,val +TISTUD-5473,Default to only applying theme to editor,"A suggestion is to only have the dark theme applied to editor. There is currently a preference to apply theme to all views, so maybe set it to false by default? ",2,val +TISTUD-5475,Syntax error appears on unexpected line,"See screenshot. There is an unfinished line ""Ti.API."", but the error doesn't appear until a few lines below at ""catch (e)"". And the error message ""Syntax Error: unexpected token 'catch'"" isn't really clear on the real error either. ",5,val +TISTUD-5477,Re-skin Studio appearance,"Chris presented a theme/skin that got raves from everyone. We should add it in Studio and make it the default. Once we receive additional feedback, we could tweak the default as needed. ",8,val +TISTUD-5479,Remove the thick dark stroke under global toolbar,See screenshot. There is a dark line under the global toolbar that we should try to remove or re-theme as part of TISTUD-5477. ,5,val +TISTUD-5483,Profile TiApp editor for expensive operations that should be run on non-UI threads,"We should run a profile session on opening TiApp editor and locate the bottleneck. Once located, we should move those operations to be run off the UI thread and have some indication to say the tiapp is loading.",8,val +TISTUD-5484,"Investigate and if necessary, improve the loading time of Build Properties section in TiApp","Investigate if loading tiapp's Build Properties section needs to be improved, and if so, move the time-consuming task to non-UI thread. ",8,val +TISTUD-5489,Appcelerator studio 3.2.0.201310071837 does not show possible platform run options when clicked on run.,h5.Description: 1.Create an app in appc studio 3.2.0.201310071837.Make sure you have all or more than one platforms enabled for the app. 2.Click on run button in studio. h5.Actual result: 1.We see 'run configurations' rather than a list of all possible run options according to the platforms (please refer to the screen shot attached). h5.Expected result: 1.We should see the list of all possible run options for the selected platforms. ,5,val +TISTUD-5492,Update Studio base to Eclipse 4.3.1,"The current base is Eclipse 4.3.0. 4.3.1 was released in September, so it makes sense to update Studio to use the latest version. ",5,val +TISTUD-5495,Views revert back to white/light grey background on redraw when user has editor theme applying to views,"h5.Description: 1. Verify new eclipse theme ""Dashboard"" is being used in Preferences > General > Appearance. 2. Turn on option to apply editor theme to views in Preferences > Studio > Theme. 3. Choose a theme with a dark/black background. Click OK. 4. Right click in a view like the Project Explorer. It will revert back to Dashboard theme's white/light grey BG rather than keeping the black bg from editor. h5.Actual Result: 1. View takes on white BG color. h5.Expected Results: 1. View retains the same BG as the editor. ",5,val +TISTUD-5499,Studio:Updates failed to install,"""Installing Appcelerator Updates"" failed during installation of Appcelerator Studio, Nightly build: 3.2.0.201310091613 h5.Test steps 1. Update Studio to Nightly 2. Check for Studio Updates h5.Actual result: Failed to install updates",8,val +TISTUD-5501,Studio: Studio window cannot be focused at first time after launch,A Studio window and a Studio menu cannot be focused at first launch of Studio. h5.To reproduce 1. Launch Studio 2. Try to click anywhere inside of a Studio window or Studio menu(navbar) h5. Actual result A window cannot be focused h5.Expected result A focused Window h5.Work around Click anywhere outside of a Studio window and back inside.,5,val +TISTUD-5502,Add release notes provider for Studio update,"Since Studio updates now appear in the Titanium update wizard, it has to provide release notes in the wizard similar to Titanium SDK or other npm packages.",8,val +TISTUD-5503,Add license text for Studio updates in update wizard,"As Studio updates will now appear in the Titanium update wizard, users need to accept agreement terms before the Studio updates are installed through the wizard. The wizard already contains the ability to show the license if it is contributed by the release provider.",5,val +TISTUD-5504,Disable the Studio updates from the Eclipse update popup,"Eclipse p2 checks for updates during the startup of Studio and then shows a popup toast to allow install all the updates of the features/plugins. Since Studio updates will now appear in the titanium update wizard, the Eclipse update popup should appear for only non-studio related updates. We need to copy the p2 plugins (especially equinox.p2.ui.scheduler and may be, p2.ui.sdk - for modifying code that is invoked through UpdateHandler) and modify the p2 update checker code to filter out the install units containing the appcelerator specific to standalone.",5,val +TISTUD-5508,Studio Dashboard - Dashboard will display a second view of the tab in the top left corner,"h5.Description Upon opening titanium and going into the ""Learn"" tab of the dashboard a second window is placed inside the first window displaying all components on top of each other in the top left corner. Happens inconsistently. h5.Steps To Reproduce 1. Open Studio and wait for dashboard to load. 2. Select ""Learn"" h5.Result Window is displayed within the tab and the layout is a mess h5.Expected Result Tab should open and display all components in the correct place.",8,val +TISTUD-5510,Studio Dashboard - Dashboard opens twice,"h5.Description When Studio is opened, dashboard is opened twice. One displays an error, the other displays correctly. h5.Steps To Reproduce Unknown, occurs inconsistently. h5.Result Dashboard is displayed twice. h5.Expected Result Dashboard to work and only open once.",5,val +TISTUD-5513,Titanium Studio: Links on Login Splash Screen not working.,"Links such as ""Forgot Password"",""Privacy Policy"" and ""terms and services"" link on Login Splash Screen are not working. Links are not clikable.",5,val +TISTUD-5514,Appcelerator Studio: Can not login with corporate HTTP Proxy,User can not login into Appcelerator studio behind his corporate proxy Attaching log file,8,val +TISTUD-5523,Improve look and feel of Tab font in new UI,"The current tab labels are distracting using a 14px font and black FG color. I originally developed the theme using https://github.com/jeeeyul/eclipse-themes to come up with the CSS. He wrote a custom CTabFolder renderer that supports additional options including the ability to set the color of the tab FG. I tried using the normal CSS route of e4 and it's not working. So we either need to bump down the font size (which also looks bad, IMO) or use a custom renderer (like maybe his, since it's EPL) and color the tab FG as #484850. ",8,val +TISTUD-5526,TiStudio: Alloy - Default Alloy project option does not appear when you want to create a new mobile app project,*Details:* Default Alloy project option does not appear when you want to create a new mobile app project. *This is a regression as this does appear on TiStudio 3.1.4.201310112035.* *Steps to reproduce:* 1. Make sure to be on TiStudio build 3.2.X 2. Right-click on the Project Explorer 3. Go to: New > Mobile App Project *Actual:* Alloy template is not an option (see 3.2.0_tistud.png) *Expected:* Alloy template should be an option when you create a new app (see 3.1.4_tistud.png),5,val +TISTUD-5527,Studio: Mobile Web Preview in Browser - failure to connect to internal server ,"Unable to preview default classic and alloy projects in browsers. *Regression*, does not occur in 3.1.3 Studio ",5,val +TISTUD-5529,Windows - Automatic updates get the wrong address,"h5.Description When opening Studio and checking for updates it throws an error saying it cannot connect to the update sites. h5.Steps To Reproduce 1. Open Studio 2. Check for updates 3. Open Preference -> Install/Update 4. Check another update site and try that one h5.Result Cannot connect to update site h5.Expected Result Should connect to the update site and produce a list of updates +Extra Information+ The links to connect to the update site begins as http://preview.appcelerator.com/appcelerator This uses forward slashes ""/"" After this it uses \studio\standalone\update\/beta This uses back slashes ""\"" When it connects to the internet it changes the ""\"" to ""%5C"" So the final address is: http://preview.appcelerator.com/appcelerator%5Cstudio%5Cstandalone%5Cupdate%5C/beta",3,val +TISTUD-5531, Console: Console view displays two colour:black and white,Test Steps: 1.Create a mobile project. 2.Run the project on emulator/simulator/ local server. 3.Observe the console view .screenshot attached. This ticket is to fix the issue long term (3.2.0 timeframe) with our new skin and old theming system.,5,val +TISTUD-5534,"iOS: Context Menu - In ""Run As"" and ""Debug As"" context menu, simulator.shorcut.label appears","*Details:* In ""Run As"" and ""Debug As"" context menu, %ipad.simulator.shorcut.label and %iphone.simulator.shorcut.label appears instead of the human readable labels. *This is a regression as this does not occur on Titanium Studio, build: 3.1.4.201310152018* *Steps to reproduce:* 1. Create new Titanium project 2. Right-click on the project 3. Go to either ""Run As"" or ""Debug As"" *Actual:* %ipad.simulator.shorcut.label and %iphone.simulator.shorcut.label appears instead of the human readable labels (see attachments). *Expected:* ""iPad Simulator"" and ""iPhone Simulator"" label should appear in the ""Run As"" and ""Debug As"" context menu.",2,val +TISTUD-5538,TiApp: Deployment Targets - The spinners to the left of the Deployment Targets are frozen,*Details:* The spinners to the left of the Deployment Targets in the TiApp Editor do not spin after creating an app. *Steps to reproduce:* 1. Create a new app from Studio 2. Wait for the TiApp Editor to open *Actual:* The spinners to the left of the Deployment Targets do not spin (see no_spin.png) *Expected:* The spinners should spin and show the expected icons (see icons.png) *Note:* The expected icons appear if you switch to a different tab and back to the TiApp Editor tab; reopening the TiApp Editor does not fix the issue.,5,val +TISTUD-5539, Android: Emulator: Remove Fastdev for 3.2.0+ SDK,"We are deprecating FastDev in SDK 3.2.0+ Thus, we should remove the option to launch with FastDev enabled ",3,val +TISTUD-5541,Add packaging to new launch mode drop-down UI,"The new UI has a drop down for mode, but we also wanted to add packaging to it. Technically packaging is not a mode. So we need to find some way to add that on as well.",8,val +TISTUD-5542,Add e4 Theme picker to our Theme Preference Page,"Add the e4 theme picker to our pref page (and label clearly one as ""Overall"" and other as ""Editor"") - so the user can modify themes/colors from the same place.",5,val +TISTUD-5543,"Create a dark e4 theme (that is similar to our new ""Dashboard"" theme)",We should have a dark e4 theme for users to choose from.,5,val +TISTUD-5544,Remove the option to apply editor theme to views,The old theming hack and the new e4 themes do not play nice together. We should remove the option to apply the old theming outside the editor entirely.,8,val +TISTUD-5545,Set new e4 and editor theme defaults,"Set new defaults for e4 and editor themes? dark with dark or light with light. maybe different defaults for TiStud vs AppcStud. Seems like community may prefer dark themes, enterprise light.",3,val +TISTUD-5546,"Context Menu: Run As - In the Run As contextual menu, it is difficult to distinguish between iOS device and Simulator.","*Details:* In the Run As contextual menu, it is difficult to distinguish between iOS device and Simulator. For example, Run As > iOS Device and Run As > iPad gives the impression of installing to a either a physical iOS device or a physical iPad device (respectively). But in reality, Run As > iPad means running on iPad Simulator. *Steps to reproduce:* 1. Create a new app in Studio 2. Right-click on the project 3. Go to Run As *Actual:* Run As > iOS Device and Run As > is not distinguishable (see 3.2.0_run_as.png) *Expected:* ""Simulator"" label should be appended to the (see 3.1.4_run_as.png)",5,val +TISTUD-5547,Mobile Web: Run Configurations doesn't allow to use other browser than the default one,"When I open Run Configurations, and try to set my Web Browser for a Mobile Web Previewer configuration, Appc will only work if I choose ""Default system web browser"". If I choose Chrome, IE, or Firefox, I see the following error when I run the app: ""Could not launch external web browser for http://127.0.0.1:8020/index.html. Check the Web Browser preferences."" ",5,val +TISTUD-5551,NullPointerException trying to run simulator for a project,"!ENTRY org.eclipse.core.jobs 4 2 2013-10-20 00:14:07.754 !MESSAGE An internal error occurred during: ""Launching Appcelerator iPhone Simulator - foobar"". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.mobile.cli.IOSCommandsHelper.getIOSTargetDevice(IOSCommandsHelper.java:368) com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.runOnSimulator(IOSNodeJSCommandsHelper.java:358) com.appcelerator.titanium.mobile.cli.nodejs.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:578) com.appcelerator.titanium.mobile.ui.iphone.launch.IOSSimulatorLaunchConfigurationDelegate.launch(IOSSimulatorLaunchConfigurationDelegate.java:66) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)",3,val +TISTUD-5556,Platform Config Wizard: remove the requirement of having Android 2.3.3 installed,"The new CLI for Android build no longer requires Android 2.3.3. User would still need it for pre-3.2.0 Titanium SDKs, but we don't need to install 2.3.3 by default in the platform configuration wizard. This is to not have the checkbox selected by default, make it selectable, and remove the info icon next to the version. ",3,val +TISTUD-5557,"Error in Studio log on ""cannot find templates/release_notes.html""",See the following exception when starting up Appcelerator Studio 3.2.0.201310181700: {code} !ENTRY com.appcelerator.titanium.update.core 4 0 2013-10-21 14:20:37.200 !MESSAGE (Build 3.2.0.201310181700) [ERROR] Cannot find templates/release_notes.html !STACK 0 java.io.IOException: Cannot find templates/release_notes.html org.eclipse.core.internal.runtime.FindSupport.openStream(FindSupport.java:274) org.eclipse.core.runtime.FileLocator.openStream(FileLocator.java:188) com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.getTemplate(DefaultReleaseNotesProvider.java:136) com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.applyTemplate(DefaultReleaseNotesProvider.java:117) com.appcelerator.titanium.update.core.GitHubReleaseNotesProvider.getReleaseNotes(GitHubReleaseNotesProvider.java:88) com.appcelerator.titanium.update.core.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:99) com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:453) com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:518) org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) org.eclipse.jface.window.Window.create(Window.java:432) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) com.appcelerator.titanium.update.ui.internal.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66) com.appcelerator.titanium.update.ui.TitaniumUpdateStartup$1$1$1.openMessageDialog(TitaniumUpdateStartup.java:81) com.aptana.ui.util.UIUtils$3.runInUIThread(UIUtils.java:498) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) org.eclipse.swt.widgets.Display.observerProc(Display.java:3566) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4918) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5296) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1101) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1093) org.eclipse.swt.widgets.Display.windowProc(Display.java:5556) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code} ,3,val +TISTUD-5558,Error creating a new Android module project,"h5. Problem description Creating a new module project returns an error. h5. Steps to reproduce - Create a new Mobile Module Project for Android. Result: an error is thrown: {code} Traceback (most recent call last): File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 387, in main(sys.argv) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 384, in main module = ModuleProject(config['platform'],project_dir,config) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 63, in __init__ self.platform_delegate = ModulePlatform.create_platform(platform, project_dir, config, self) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 34, in create_platform return platform_module_class(project_dir, config, module) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/android/android.py"", line 23, in __init__ self.sdk = androidsdk.AndroidSDK(module_project.sdk) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/android/androidsdk.py"", line 49, in __init__ self.set_api_level(api_level) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/android/androidsdk.py"", line 53, in set_api_level self.find_platform_dir() File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/android/androidsdk.py"", line 131, in find_platform_dir raise Exception(""No \""%s\"" or \""%s\"" in the Android SDK"" % ('android-%s' % api_level, android_api_levels[api_level])) Exception: No ""android-10"" or ""android-2.3.3"" in the Android SDK Aborting Traceback (most recent call last): File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 387, in main(sys.argv) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 384, in main module = ModuleProject(config['platform'],project_dir,config) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 63, in __init__ self.platform_delegate = ModulePlatform.create_platform(platform, project_dir, config, self) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/module.py"", line 34, in create_platform return platform_module_class(project_dir, config, module) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/module/android/android.py"", line 23, in __init__ self.sdk = androidsdk.AndroidSDK(module_project.sdk) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/android/androidsdk.py"", line 49, in __init__ self.set_api_level(api_level) File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/android/androidsdk.py"", line 53, in set_api_level self.find_platform_dir() File ""/Users/fcasali/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.v20131018154951/android/androidsdk.py"", line 131, in find_platform_dir raise Exception(""No \""%s\"" or \""%s\"" in the Android SDK"" % ('android-%s' % api_level, android_api_levels[api_level])) Exception: No ""android-10"" or ""android-2.3.3"" in the Android SDK Aborting {code} Works fine for iOS. Reproducible also using previous TiSDK. ",3,val +TISTUD-5559,"Project explorer: The project cannot be imported from git, Titanium SDK could not be found","The git project cannot be imported, if SDK it was built with is not in mobilesdk folder. h5.To reproduce Using project explorer (right click), Import > Appcelerator> Existing Mobile Project h5.Actual result The error Titanium SDK could not be found h5.Expected result Projects should be imported successfully Note: This is *regression*, in Studio 3.1.4 SDK is being updated to the latest build and import is successful",5,val +TISTUD-5561,Studio finds the globally installed npm packages over the local ones,"If the npm packages are globally installed through command line, then Studio will recognize the npm packages that are installed globally rather than the local ones (in .npm directory). Since the executable is available in the system PATH, they are found prior to the common locations path.",3,val +TISTUD-5562,The mode and device dropdowns in Studio global toolbar are not populated until a selection is made in Project Explorer,"When I updated to the latest 3.2.0 build (Appcelerator Studio, build: 3.2.0.201310181700), the global toolbar does not show any items in the mode and device dropdowns. Only when a project is selected in Project Explorer, both combo-boxes would then get populated.",5,val +TISTUD-5563,Intermitant issue : Appcelerator Studio gives null pointer exception on Restart,"I was trying to update Studio by following the below steps when I faced this issue: 1. From the Help menu, select Install New Software... to open an Install pop-up window. 2. In the Work with: text box of the Install window, type the URL http://ec2-50-16-19-245.compute-1.amazonaws.com/appcelerator/appc-studio/standalone/update/nightly/ for the update site, and hit the Enter key. Close the Install window. 3. From the Help menu, select Check for Updates. 4. After successful update Studio prompts for Restart. 5. Restart 6. Observe the attached screen shot for the Null Pointer Exception I encountered on Studio restart Also I faced the same issue when I run a mobile project using iOS simulator and restarted my Studio. Please refer the attached log file and screen shot for further reference. ",5,val +TISTUD-5565,Quitting Studio from the login screen hangs indefinitely,"h2. Description Quitting Appcelerator Studio (3.1.3) from the login screen hangs indefinitely. The only way to kill the app is to Force Quit. h2. Logs {code} !SESSION 2013-10-21 18:25:22.091 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_65 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/tl67467/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/tl67467/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.net 1 0 2013-10-21 18:25:24.358 !MESSAGE System property http.proxyHost has been set to webproxy.wlb2.nam.nsroot.net by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2013-10-21 18:25:24.358 !MESSAGE System property http.proxyPort has been set to 8080 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2013-10-21 18:25:24.359 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2013-10-21 18:25:24.360 !MESSAGE System property https.proxyHost has been set to webproxy.wlb2.nam.nsroot.net by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2013-10-21 18:25:24.360 !MESSAGE System property https.proxyPort has been set to 8080 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.ui.workbench 4 2 2013-10-21 18:25:26.479 !MESSAGE Problems occurred when invoking code from plug-in: ""org.eclipse.ui.workbench"". !STACK 0 org.eclipse.swt.SWTException: Widget is disposed org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.SWT.error(SWT.java:4168) org.eclipse.swt.widgets.Widget.error(Widget.java:774) org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:894) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.doEventLoop(TitaniumSplashHandler.java:826) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.init(TitaniumSplashHandler.java:290) org.eclipse.ui.internal.Workbench$8.run(Workbench.java:790) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:806) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2528) 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) !ENTRY org.eclipse.ui 4 0 2013-10-21 18:25:26.487 !MESSAGE Could not instantiate splash !STACK 0 org.eclipse.swt.SWTException: Widget is disposed org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.SWT.error(SWT.java:4168) org.eclipse.swt.widgets.Widget.error(Widget.java:774) org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:894) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.doEventLoop(TitaniumSplashHandler.java:826) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.init(TitaniumSplashHandler.java:290) org.eclipse.ui.internal.Workbench$8.run(Workbench.java:790) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:806) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2528) 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) !ENTRY org.eclipse.ui 4 4 2013-10-21 18:25:26.489 !MESSAGE Exception in Workbench.runUI after display was disposed !ENTRY org.eclipse.ui 4 1 2013-10-21 18:25:26.489 !MESSAGE Exception in Workbench.runUI after display was disposed !STACK 0 org.eclipse.swt.SWTException: Device is disposed org.eclipse.swt.SWT.error(SWT.java:4282) org.eclipse.swt.SWT.error(SWT.java:4197) org.eclipse.swt.SWT.error(SWT.java:4168) org.eclipse.swt.widgets.Display.error(Display.java:1065) org.eclipse.swt.widgets.Display.checkDevice(Display.java:619) org.eclipse.swt.widgets.Display.addListener(Display.java:478) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2578) 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) !ENTRY com.aptana.usage 4 0 2013-10-21 18:25:27.125 !MESSAGE (Build 3.1.3.1377024923) [ERROR] Unable to log analytics information !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.usage.internal.TitaniumAnalyticsUserManager$1.(TitaniumAnalyticsUserManager.java:27) com.appcelerator.titanium.usage.internal.TitaniumAnalyticsUserManager.getUser(TitaniumAnalyticsUserManager.java:24) com.aptana.usage.AnalyticsEvent.init(AnalyticsEvent.java:140) com.aptana.usage.AnalyticsEvent.(AnalyticsEvent.java:71) com.aptana.usage.UsagePlugin.stop(UsagePlugin.java:61) org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) java.security.AccessController.doPrivileged(Native Method) org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:565) org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1161) org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:595) org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:691) org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:598) org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198) 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) !ENTRY org.eclipse.core.jobs 4 2 2013-10-21 18:25:27.130 !MESSAGE An internal error occurred during: ""Sending Analytics Ping ..."". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.usage.internal.TitaniumAnalyticsUserManager$1.(TitaniumAnalyticsUserManager.java:27) com.appcelerator.titanium.usage.internal.TitaniumAnalyticsUserManager.getUser(TitaniumAnalyticsUserManager.java:24) com.aptana.usage.internal.DefaultAnalyticsEventHandler$1.run(DefaultAnalyticsEventHandler.java:77) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}",8,val +TISTUD-5566,Unable to Profile a Mobile App Project using iOS simulator,Steps Followed: 1. Create a Mobile App Project 2. Try to Profile it by Project Context Menu >> Profile as >> iOS(iPhone/iPad simulator) Actual Results: It fails prompting an error message on the screen. Pleaser refer the attached log file and screen shot for further reference.,5,val +TISTUD-5567,Code Analyzer : Fails with a missing plugin error prompt,Steps Followed: 1. Create a Mobile App Project 2. Try to run Code Analysis using any of the options available in the Project Context Menu >> Code Analysis >> iOS(iPhone/iPad)or Multiple or Android Actual Results: It fails prompting an error message on the screen. Pleaser refer the attached log file and screen shot for further reference.,5,val +TISTUD-5568,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,val +TISTUD-5570,"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,val +TISTUD-5571," 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,val +TISTUD-5573,Studio:Typo in error message ,"Typo in error message (see the screenshot) h5.Actual result ""retreiving"" instead of ""retrieving""",1,val +TISTUD-5575,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,val +TISTUD-5576,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,val +TISTUD-5577,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,val +TISTUD-5578,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,val +TISTUD-5579,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,val +TISTUD-5582,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,val +TISTUD-5585,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,val +TISTUD-5587,"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,val +TISTUD-5588,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,val +TISTUD-5594,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,val +TISTUD-5598,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 ""mxia@appcelerator.com"". 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,val +TISTUD-5603,"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,val +TISTUD-5605,"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,val +TISTUD-5623,Android: Ti.map module not available for addition to tiapp.xml ,"Ti.map module is not available in the tiapp.xml. Ti.map is listed in previous sdk build: 3.2.0.v20131024120843 Steps to reproduce: 1. Create a Default titanium project. 2. Edit tiapp.xml , select sdk build 3.2.0.v20131027201356 and click on add module. Expected : Ti.map module should be displayed in the list. Actual: Ti.map module is not listed.",5,val +TISTUD-5610,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,val +TISTUD-5611,"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,val +TISTUD-5614,"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,val +TISTUD-5619,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,val +TISTUD-5620,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,val +TISTUD-5621,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,val +TISTUD-5622,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,val +TISTUD-5624,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,val +TISTUD-5625,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,val +TISTUD-5628,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,val +TISTUD-5629," 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,val +TISTUD-5631,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,val +TISTUD-5632,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,val +TISTUD-5633,"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,val +TISTUD-5634,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,val +TISTUD-5635,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,val +TISTUD-5636,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,val +TISTUD-5641,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,val +TISTUD-5642,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 """" +Extra Information+ Building from CLI works because I used ""--developer-name"" """" ",3,val +TISTUD-5796,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,val +TISTUD-5643,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,val +TISTUD-5644,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,val +TISTUD-5648, 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,val +TISTUD-5649,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 java.util.Collections$EmptyList.get(Collections.java:2976) com.appcelerator.titanium.ios.core.IOSSDKLocator.initialize(IOSSDKLocator.java:180) com.appcelerator.titanium.ios.core.IOSSDKLocator$3.run(IOSSDKLocator.java:205) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}",2,val +TISTUD-5650,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,val +TISTUD-5651,"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,val +TISTUD-5652,"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,val +TISTUD-5653,"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,val +TISTUD-5654,"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,val +TISTUD-5655,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,val +TISTUD-5657,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,val +TISTUD-5659,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,val +TISTUD-5660," 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,val +TISTUD-5661,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,val +TISTUD-5662,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,val +TISTUD-5663,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,val +TISTUD-5664,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,val +TISTUD-5665,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,val +TISTUD-5666,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,val +TISTUD-5668,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,val +TISTUD-5671,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,val +TISTUD-5672,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,val +TISTUD-5673,"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,val +TISTUD-5675,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,val +TISTUD-5676,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,val +TISTUD-5677,"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,val +TISTUD-5679,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,val +TISTUD-5680,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,val +TISTUD-5681,"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,val +TISTUD-5682,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,val +TISTUD-5684,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,val +TISTUD-5779,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,val +TISTUD-5686,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,val +TISTUD-5687,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,val +TISTUD-5689,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,val +TISTUD-5690," 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,val +TISTUD-5691,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,val +TISTUD-5692,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,val +TISTUD-5693,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,val +TISTUD-5694,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,val +TISTUD-5697,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,val +TISTUD-5698,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,val +TISTUD-5704,"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 ├── acs@1.0.7 ├── alloy@1.3.0 ├── npm@1.3.2 ├── titanium@3.1.2 └── titanium-code-processor@1.0.3 {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,val +TISTUD-5705,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,val +TISTUD-5706,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,val +TISTUD-5709,Ubuntu Unity: alert user for the issue where menu won't show inside Studio,"h5.Description Studio will successfully open, however trying to open a menu ('File' for example) will not show anything. h5.Steps To Reproduce 1. Run Ubuntu 13.10 2. Open Studio 3. Click 'File' h5.Expected Result File menu should drop down giving me multiple options h5.Actual Result Nothing is displayed after clicking 'File' +Extra Information+ Opening terminal and running 'sudo chmod +x' on the TitaniumStudio.sh file and executing it will open Studio and have the menus work as they should. Also, using the keyboard shortcut to open the 'File' (Alt+F) will open the 'File' menu and Studio will then recognise the menu, but will not populate it with text, only buttons.",8,val +TISTUD-5710,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,val +TISTUD-5712,Studio:Global toolbar - unexpected icons ,"When relaunched Appcelerator Studio, I noticed an extra icons on a global toolbar, what should be hidden. It is an intermittent issue. Due to the new UI, it is unclear if it is a regression.",5,val +TISTUD-5715,"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,val +TISTUD-5716,Studio: App explorer does not work with global toolbar run options,"h5. Description: It is still possible to enable the App Explorer pane within Studio. When this is done, the selected project is not associated with the global toolbar run settings. For example, if you have an iOS-only project selected in the project explorer, and you open an Android-only project in the app explorer, the global toolbar run settings will reflect the options for the iOS-only project and if run is selected, the iOS-only app will be built regardless of what project you have selected in App Explorer. h5. Steps to reproduce: 1) Create two projects, one iOS-only and one Android-only 2) In Project explorer, select the iOS only project and configure the run settings in the global toolbar 3) Open App explorer with Window>Show View>Other>Studio>App Explorer 4) Select the Android-only project in App explorer 5) Press the ""Run"" button in the global toolbar h5. Result: The iOS-only project will be built h5. Expected Result: The Android-only project will be built",5,val +TISTUD-5721,"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,val +TISTUD-5722,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 com.appcelerator.titanium.android.internal.ui.DebugLaunchStatusHandler.handleStatus(DebugLaunchStatusHandler.java:29) com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate.cleanUp(AndroidInstallerLaunchConfigurationDelegate.java:114) com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate.access$0(AndroidInstallerLaunchConfigurationDelegate.java:105) com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate$TitaniumDeployListener.error(AndroidInstallerLaunchConfigurationDelegate.java:94) com.appcelerator.titanium.core.internal.cli.TitaniumDeployManager.fireError(TitaniumDeployManager.java:67) com.appcelerator.titanium.core.internal.cli.TitaniumDeployManager.fireError(TitaniumDeployManager.java:59) com.appcelerator.titanium.android.core.launching.AndroidInstallAppStreamListener.streamAppended(AndroidInstallAppStreamListener.java:85) org.eclipse.debug.internal.core.OutputStreamMonitor$ContentNotifier.run(OutputStreamMonitor.java:258) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.debug.internal.core.OutputStreamMonitor$ContentNotifier.notifyAppend(OutputStreamMonitor.java:268) org.eclipse.debug.internal.core.OutputStreamMonitor.fireStreamAppended(OutputStreamMonitor.java:117) org.eclipse.debug.internal.core.OutputStreamMonitor.read(OutputStreamMonitor.java:157) org.eclipse.debug.internal.core.OutputStreamMonitor.access$1(OutputStreamMonitor.java:135) org.eclipse.debug.internal.core.OutputStreamMonitor$1.run(OutputStreamMonitor.java:208) java.lang.Thread.run(Thread.java:680) {code}",3,val +TISTUD-5731,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,val +TISTUD-5732,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,val +TISTUD-5735,Android simulator run configuration dialog layout is stretched,"1. In Studio select Run > Run Configurations... 2. Open an existing run config, or create a new one. 3. Reduce the the dialog's window's width by 1/3 or 1/2. Results: The dialog's buttons (New, Browse, etc) aren't visible. See attached. Expected: Layout better conforms to dialog window size.",3,val +TISTUD-5740,Windows: Error for Unknown iOS SDK in log file,Steps Followed: 1. Clean installed Studio and observed the log file. Actual Result: Log file contains error message for 'Unknown iOS SDK'. Please refer the attached log file for further details.,3,val +TISTUD-5741,NPE found in log file on creating a Classic Mobile App,Steps Followed: 1. Create a Classic Mobile App with or without Cloud Services. Actual Result: NPE found in the log file. Please observe the attached log file for further clarification. {code} !ENTRY com.appcelerator.titanium.core 4 0 2013-11-18 15:09:50.442 !MESSAGE (Build 3.2.0.201311161724) [ERROR] null !STACK 0 java.lang.NullPointerException com.sun.org.apache.xml.internal.dtm.ref.dom2dtm.DOM2DTM.getLocalName(Unknown Source) com.sun.org.apache.xpath.internal.patterns.NodeTest.execute(Unknown Source) com.sun.org.apache.xpath.internal.axes.PredicatedNodeTest.acceptNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.AxesWalker.nextNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.WalkingIterator.nextNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.NodeSequence.nextNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.NodeSequence.runTo(Unknown Source) com.sun.org.apache.xml.internal.dtm.ref.DTMNodeList.(Unknown Source) com.sun.org.apache.xpath.internal.objects.XNodeSet.nodelist(Unknown Source) com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.getResultAsType(Unknown Source) com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.eval(Unknown Source) com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.evaluate(Unknown Source) com.appcelerator.titanium.core.tiapp.TiAppModel.getNodes(TiAppModel.java:384) com.appcelerator.titanium.core.tiapp.TiAppModel.getValues(TiAppModel.java:286) com.appcelerator.titanium.core.tiapp.TiAppModel.getValue(TiAppModel.java:350) com.appcelerator.titanium.core.tiapp.TiAppModel.getTiAppValue(TiAppModel.java:1306) com.appcelerator.titanium.core.tiapp.TiAppModel.hasDeployTargetEnabled(TiAppModel.java:1268) com.appcelerator.titanium.core.TitaniumProject.isDeployTarget(TitaniumProject.java:330) com.appcelerator.titanium.core.expressions.TitaniumProjectPropertyTester.test(TitaniumProjectPropertyTester.java:115) org.eclipse.core.internal.expressions.Property.test(Property.java:58) org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53) org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:287) org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.getLaunchShortcuts(LaunchConfigurationManager.java:717) com.appcelerator.titanium.ui.LaunchAppToolbarContribution.loadShortcuts(LaunchAppToolbarContribution.java:136) com.appcelerator.titanium.ui.LaunchAppToolbarContribution.access$4(LaunchAppToolbarContribution.java:130) com.appcelerator.titanium.ui.LaunchAppToolbarContribution$ProjectExplorerSelectionListener$1.run(LaunchAppToolbarContribution.java:122) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145) org.eclipse.swt.widgets.Shell.WM_ENTERIDLE(Shell.java:2239) org.eclipse.swt.widgets.Control.windowProc(Control.java:4627) org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:340) org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627) org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2075) org.eclipse.swt.widgets.Display.windowProc(Display.java:4990) org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) org.eclipse.swt.widgets.Menu._setVisible(Menu.java:257) org.eclipse.swt.widgets.Display.runPopups(Display.java:4211) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3753) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) --------------- linked to ------------------ javax.xml.xpath.XPathExpressionException com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.evaluate(Unknown Source) com.appcelerator.titanium.core.tiapp.TiAppModel.getNodes(TiAppModel.java:384) com.appcelerator.titanium.core.tiapp.TiAppModel.getValues(TiAppModel.java:286) com.appcelerator.titanium.core.tiapp.TiAppModel.getValue(TiAppModel.java:350) com.appcelerator.titanium.core.tiapp.TiAppModel.getTiAppValue(TiAppModel.java:1306) com.appcelerator.titanium.core.tiapp.TiAppModel.hasDeployTargetEnabled(TiAppModel.java:1268) com.appcelerator.titanium.core.TitaniumProject.isDeployTarget(TitaniumProject.java:330) com.appcelerator.titanium.core.expressions.TitaniumProjectPropertyTester.test(TitaniumProjectPropertyTester.java:115) org.eclipse.core.internal.expressions.Property.test(Property.java:58) org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53) org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:287) org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.getLaunchShortcuts(LaunchConfigurationManager.java:717) com.appcelerator.titanium.ui.LaunchAppToolbarContribution.loadShortcuts(LaunchAppToolbarContribution.java:136) com.appcelerator.titanium.ui.LaunchAppToolbarContribution.access$4(LaunchAppToolbarContribution.java:130) com.appcelerator.titanium.ui.LaunchAppToolbarContribution$ProjectExplorerSelectionListener$1.run(LaunchAppToolbarContribution.java:122) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145) org.eclipse.swt.widgets.Shell.WM_ENTERIDLE(Shell.java:2239) org.eclipse.swt.widgets.Control.windowProc(Control.java:4627) org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:340) org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627) org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2075) org.eclipse.swt.widgets.Display.windowProc(Display.java:4990) org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) org.eclipse.swt.widgets.Menu._setVisible(Menu.java:257) org.eclipse.swt.widgets.Display.runPopups(Display.java:4211) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3753) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.NullPointerException com.sun.org.apache.xml.internal.dtm.ref.dom2dtm.DOM2DTM.getLocalName(Unknown Source) com.sun.org.apache.xpath.internal.patterns.NodeTest.execute(Unknown Source) com.sun.org.apache.xpath.internal.axes.PredicatedNodeTest.acceptNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.AxesWalker.nextNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.WalkingIterator.nextNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.NodeSequence.nextNode(Unknown Source) com.sun.org.apache.xpath.internal.axes.NodeSequence.runTo(Unknown Source) com.sun.org.apache.xml.internal.dtm.ref.DTMNodeList.(Unknown Source) com.sun.org.apache.xpath.internal.objects.XNodeSet.nodelist(Unknown Source) com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.getResultAsType(Unknown Source) com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl.eval(Unknown Source) ... 61 more {code},3,val +TISTUD-5742,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,val +TISTUD-5747,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,val +TISTUD-5752,Can't clean imported projects as they are not shown in the project list to be cleaned,"h5.Description: 1.Import a project not created in the studio you are using, from any where in the filesystem or put it in the workspace & then import it.(2 scenarios) 2.In studio go to ""project ---> clean"". h5.Actual Result: 1.We do not see the app in the app list to be cleaned. 2.As a double confirmation, build the app so that it has a build folder & now try to clean.You still wont see the app in the to be cleaned list. h5.Expected Result: 1.We should see the imported app in the list to be cleaned. ",5,val +TISTUD-6033,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,val +TISTUD-5754,"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,val +TISTUD-5755,Deleting a closed project shows error log in Studio log,Test Steps: 1.Create a mobile project with appcelerator services. 2.Cllose 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. org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150) org.eclipse.core.internal.resources.Project.hasNature(Project.java:584) com.appcelerator.titanium.acs.ui.ACSUIPlugin$1.resourceChanged(ACSUIPlugin.java:52) org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:261) org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:391) org.eclipse.core.internal.resources.Resource.broadcastPreDeleteEvent(Resource.java:2030) org.eclipse.core.internal.resources.Resource.delete(Resource.java:788) org.eclipse.core.internal.resources.Project.delete(Project.java:344) org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:160) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:223) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) 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,val +TISTUD-5759,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,val +TISTUD-5761,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) org.eclipse.swt.SWT.error(SWT.java:4397) org.eclipse.swt.SWT.error(SWT.java:4312) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275) org.eclipse.ui.internal.progress.ProgressManager$3.run(ProgressManager.java:960) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:995) org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:970) org.eclipse.debug.internal.ui.DebugUIPlugin.launchInForeground(DebugUIPlugin.java:1112) org.eclipse.debug.ui.DebugUITools.launch(DebugUITools.java:759) com.appcelerator.titanium.ui.module.AbstractModulePackagingWizard.performFinish(AbstractModulePackagingWizard.java:103) org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) com.appcelerator.titanium.ios.internal.ui.launching.module.IOSPackageHandler.execute(IOSPackageHandler.java:34) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.NullPointerException org.eclipse.debug.internal.ui.launchConfigurations.LaunchDelegateNotAvailableHandler$1.run(LaunchDelegateNotAvailableHandler.java:42) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 75 more {code},5,val +TISTUD-5765,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,val +TISTUD-5767,"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,val +TISTUD-5768,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,val +TISTUD-5769,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,val +TISTUD-5770,"Studio constantly updates iOS info, sometimes multiple times at once.","h5.Description Studio will constantly check for updates in the iOS info. This check will run through and then sleep, staying in the progress tab. Also, it will sometimes check the iOS info twice.",3,val +TISTUD-5774,Refreshing Studio workspace takes too long,"h5.Description Every time I open Studio it refreshed my workspace, sometimes runs a ""building workspace"" too. Having KitchenSink installed or any other large project can really slow down the process. For me it took just a little over 10 minutes before I could start properly working with Studio. +Extra Information+ The processor usage increased significantly as it tried to run the two Studio commands, I have attached a screenshot of the Activity Manager.",8,val +TISTUD-5775,Studio: Cannot update Appcelerator Studio ,"h5. To reproduce 1. Appcelerator Studio> Help > Check for Appcelerator Updates 2. Accept License and click Install h5. Actual result Nothing happens h5. Expected result Succes in update and the dialog window to restart Studio If I add http://ec2-50-16-19-245.compute-1.amazonaws.com/appcelerator/appc-studio/standalone/update/rc/ and point to this url, it cannot be found Steps: (Help> Install New software) ",5,val +TISTUD-5776,Android devices are not detected by Studio,"Steps to reproduce: 1. Create a titanium project 2. In the launch menu, check to see if the attached android device shows up 3. Run ti info -t android and verify that the device appears Expected result: The plugged in device should show up Actual result: The device doesn't show up, but it does from ti info on the command line.",3,val +TISTUD-5777,Profiling fails on android device with StringIndexOutOfBoundsException error,"h5.Description: 1.Profile any app in studio for android device. 2.Monitor the build & launch process. h5.Actual Result: 1. We get error & the build process fails: {code} !ENTRY com.appcelerator.titanium.android.core 2 0 2013-11-20 13:33:30.265 !MESSAGE (Build 3.2.0.201311200357) [WARNING] Aborting app launch. Installation process returned exit code 143 !ENTRY org.eclipse.core.jobs 4 2 2013-11-20 13:33:30.351 !MESSAGE An internal error occurred during: ""Launching Appcelerator Android Application Installer - commonapp"". !STACK 0 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 java.lang.String.substring(String.java:1937) com.appcelerator.titanium.android.core.launching.AndroidInstallerLaunchConfigurationDelegate.launch(AndroidInstallerLaunchConfigurationDelegate.java:214) com.appcelerator.titanium.android.ui.launching.device.AndroidDebugOnDeviceLaunchConfigurationDelegate.launch(AndroidDebugOnDeviceLaunchConfigurationDelegate.java:139) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code} h5.Expected Result: 1.The profiling process should be successful & not fail because of StringIndexOutOfBoundsException error.",3,val +TISTUD-5778,"Studio: Alloy sample projects marked with invalid warnings due to ""TT Unused Rules"" validator","h5. Description: After importing many (possibly any) of our Alloy-based sample projects, the project is showing warnings for unused styling items. These warnings are not accurate as the items are not unused. h5. Steps to reproduce: 1) Import any Alloy sample (e.g., Alloy Todo List Sample) 2) Verify that there are warnings on the files (e.g., /app/styles/add.tss) 3) Choose a warning and hover h5. Result: The warning is for unused styling items, but the items are not unused. h5. Expected Result: No invalid warnings",5,val +TISTUD-5780,Unable to configure Android SDK on a Mavericks machine,"On a Mavericks machine I tried configuring Android SDK in my Studio. Steps followed: 1. Downloaded Studio and launched it. 2. Studio prompted for the Platform Configuration screen. 3. From the configuration screen I selected the required Android SDK versions and clicked 'Configure' button to complete the configurations at the Default location. 4. The Installation screen opened and the process completed. 5. I clicked on the 'Close' button. Actual Result 1. Reopened the Studio Dashboard but still the Android SDK was not configured. 2. Restart the Studio but still the no use. 3. The Preference >> Studio >> Platforms >> Android SDK Home page prompts for error message. 4. I checked the Default location where the Android SDK was installed, the folder location showed the proper installation contents. Note: I have already successfully configured my Studio with iOS and Tizen SDKs. Please refer the attached screen shot and log file for further reference.",5,val +TISTUD-5781,Studio: Java NPE occured while launching Studio on clean Ubuntu system,"1) Used clean Ubuntu 12.04 64-bit system 2) Installed all the pre-requisites (Java, NodeJS and other dependecies) 3) Downloaded and launch latest Appcelerator Studio Actual Result - Error popup appears as soons as Studio launched. See the attached log file and screen shot Expected Result - Studio should launch successfully without any error",3,val +TISTUD-5784,Package - target Mobile Web - no output in the console,"When package for Mobile Web, using Studio options, there is no any output in the console. h5.Expected result Should see build process output",5,val +TISTUD-5785,Global launch toolbar looks cramped on Windows,"There are spacing issues with the global launch toolbar on Windows. The spacing is not properly layouted between launch icon, mode and shortcut. Due to this layout issue, user might not differentiate the launch icon and launch mode as separate actions. Improve the layout of global launch toolbar on Windows similar to Mac.",3,val +TISTUD-5794,No property tester contributes a property org.eclipse.core.resources.projectNature to type class org.eclipse.ui.ide.FileStoreEditorInput,"I'm seeing lots of these exceptions in my log, for every launch shortcut type we have. {code} !ENTRY org.eclipse.debug.ui 4 0 2013-11-22 14:02:57.767 !MESSAGE Launch shortcut 'com.appcelerator.titanium.mobile.ui.android.device.launchShortcut' enablement expression caused exception. Shortcut was removed. !STACK 1 org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.core.resources.projectNature to type class org.eclipse.ui.ide.FileStoreEditorInput org.eclipse.core.internal.expressions.TypeExtensionManager.getProperty(TypeExtensionManager.java:123) org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:96) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53) org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:287) org.eclipse.debug.ui.actions.LaunchShortcutsAction.isApplicable(LaunchShortcutsAction.java:262) org.eclipse.debug.ui.actions.LaunchShortcutsAction.fillMenu(LaunchShortcutsAction.java:166) org.eclipse.debug.ui.actions.LaunchShortcutsAction.access$0(LaunchShortcutsAction.java:157) org.eclipse.debug.ui.actions.LaunchShortcutsAction$2.menuShown(LaunchShortcutsAction.java:278) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) org.eclipse.swt.widgets.Menu.gtk_show(Menu.java:667) org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2055) org.eclipse.swt.widgets.Display.windowProc(Display.java:4563) org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2288) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3361) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) org.eclipse.equinox.launcher.Main.main(Main.java:1426) !SUBENTRY 1 org.eclipse.core.expressions 4 201 2013-11-22 14:02:57.768 !MESSAGE No property tester contributes a property org.eclipse.core.resources.projectNature to type class org.eclipse.ui.ide.FileStoreEditorInput {code}",3,val +TISTUD-5788,Debugger does not work on iOS simulator/device,"[~cbarber] tried to run/debug iOS app on Retina iPhone 4 simulator, however Studio failed to launch the app. The error indicates that --device-family is passed as ""unknown"" for running the Retina iPhone4 simulator. We should pass in a valid --device-family value to allow launch the app on simulator/device.",5,val +TISTUD-5790,Modules: Studio fails when installing modules into a project,h5.Description Installing a module into a project will fail saying the module already exists. Then fail and add an Android folder with nothing inside. h5.Steps To Reproduce 1. Download a module from the marketplace. 2. Create a default project. 3. Help -> Install Mobile Module... 4. Install the module into the default project h5.Expected Result Module should install successfully h5.Actual Result Studio fails to install the module,5,val +TISTUD-5962,iOS 7: No application-level logs,"h3. Steps to Reproduce Since the last update this week, when I launch iOS simulator (iPad or iPhone), only log of build is shown.. No logs of app. 1) Open FieldService project 2) Add some Ti.API.info / Ti.API.error in code 3) Build in simulator iOS7 (or iOS6) h3. Actual Result No log (with or without LiveView) h3. Expected Result Show Ti.API.info logs of app",5,val +TISTUD-5793,Studio: Updates -intermittent unexpected Appcelerator Updates pop up before finishing Studio updates,"It is an intermittent issue, updating Appcelerator Studio build. Please, refer to the screenshot. QE could not reproduce it on another machine. h5. Steps Appcelerator> Help> Check for Updates h5. Actual result When restart studio dialog appears, the Appcelerator Updates window with Appcelerator Studio build offer pops up, you cannot dismiss it, but can uncheck the box. Force to quit and check for Appcelerator Updates - no Appcelerator Studio build will be offered since changes already took effect.",5,val +TISTUD-5797,Android 2.3 is still listed as the required SDK,"# Install only Android SDK 4.* version # Try to create a project and notice that the Android SDK is still shown as invalid. After I create a project for only Android platform, the global run toolbar is disabled - as the Android platform is treated as invalid (due to missing 2.3.* sdk). Expected : With 3.2.0, SDK doesn't have dependency to have 2.3.3 installed. It just requires at least one SDK >= 2.3.3",3,val +TISTUD-5807,Tizen - Run>Tizen device builds app to Tizen Emulator ,"When Run the app as Tizen Device via Studio, Tizen Emulator launches as a result. I had the device plugged in and Emulator up. {code}Olgas-MacBook-Pro:tools oromero$ ./sdb devices List of devices attached emulator-26101 device Tizen 0000dada0000ad1e device device--1{code} h5.To reproduce 1. Titanium Studio> Run As Tizen Device h5. Actual result Application launches in Tizen Emulator h5.Expectedr result Application should launch on the device",5,val +TISTUD-5808,Alloy sample projects missing files on import,"Using Studio 3.3.0.201311252045 on OS X. Steps: 1. Open Samples view. 2. Expand Alloy samples folder 3. Right click on any Alloy sample and select 'Import...'. 4. After import, open new folder. Result: Folder contains three files and one Resources folder: tiapp, License, and readme. Expected: All required files are generated.",3,val +TISTUD-5810,Studio: Global toolbar - no visual feedback on click,h5. To reproduce Global Toolbar > Click on Run h5.Actual result No visual feedback h5.Expected result Visual feedback (e.g. home icon),3,val +TISTUD-5811,Android Avd not being refreshed when configured for the first time,When configuring TiStudio for Android the first time around. The avd's are not being picked up instantly. You can get around the problem by restarting studio. Have gone over the issue with [~pinnamuri] is familiar with the issue. ,5,val +TISTUD-5812,New platform shortcuts are not loaded after adding the platform in the TiApp,"# Add additional platform in the TiApp, for example to include Tizen. # The platform shortcuts are not refreshed/loaded forever. # If there is only one project in the explorer, then we need to unselect the project in the explorer to get the shortcuts related to Tizen. Otherwise, create a dummy project and change the selection between them to get the new platform launch shortcuts.",3,val +TISTUD-5814,Windows: Android - Platform Configuration window shows Latest version installed: unknown,I did not have Android configure on my system. Steps followed: 1. Launched Studio. 2. From Dashboard Android>> Install or Update Android SDK >> Platform Configuration window 3. It prompted for installing Android 4.4 I completed it successfully. Actual Result: After the successful installation the Platform Configuration window shows Latest version installed: unknown. Expected: The installed version of Android SDK should be displayed instead of unknown version message. Please refer the attached screen shot for more clarification. ,5,val +TISTUD-5821,No editor descriptor for id com.appcelerator.titanium.ui.ide.tiappEditor,h3. Steps to Reproduce 1 - Close Studio and save the workspace with tiapp.xml tab open 2 - Open studio again TO fix: Close the file and open again. h3. Actual Result Image attachments (No editor descriptor for id com.appcelerator.titanium.ui.ide.tiappEditor) h3. Expected Result GUI for tiapp.xml ,5,val +TISTUD-5816,ArrayIndexOutOfBoundsException when computing SDK info,"I took the studio updates restated my Studio. On restart I got the error prompt for 'An internal error occurred Computing SDK info'. Please refer the attached screen shot and log file for more clarification. {code} !ENTRY org.eclipse.core.jobs 4 2 2013-11-29 10:54:52.375 !MESSAGE An internal error occurred during: ""Computing SDK Info..."". !STACK 0 java.lang.ArrayIndexOutOfBoundsException: -1 java.util.ArrayList.elementData(ArrayList.java:400) java.util.ArrayList.get(ArrayList.java:413) com.appcelerator.titanium.android.core.AndroidSDKLocator.updateTiInfo(AndroidSDKLocator.java:454) com.appcelerator.titanium.android.core.AndroidSDKLocator.initialize(AndroidSDKLocator.java:209) com.appcelerator.titanium.core.mobile.SDKLocator.lazyInitialize(SDKLocator.java:153) com.appcelerator.titanium.core.mobile.SDKLocator.getInitializationStatus(SDKLocator.java:84) com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationHelper.getSDKInitializationStatus(MobileSDKConfigurationHelper.java:330) com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController.refreshSDK(MobileSDKActionController.java:347) com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:124) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}",3,val +TISTUD-5822,"Add a ""Refresh"" menu to manually refresh the list of Android and iOS Devices","h5.Description After plugging in an Android device I must wait 30 seconds before the run drop down is refreshed, displaying the device. This is a long time to wait for a device to be detected, it needs to be quicker.",5,val +TISTUD-5823,"MobileWeb: ""MobileWeb preview in emulator"" creates a new Android emulator.",h5.Description Running a MobileWeb project on an emulator will create a new Android emulator. The new studio requires the user creates the Android emulators themselves. However in this case Studio creates an emulator and ignores the users default Android choice. h5.Steps To Reproduce 1. Create a MobileWeb project 2. Run the project on emulator h5.Expected Result The project should build and install onto my chosen default Android emulator. h5.Actual Result Studio creates a new Android emulator and installs the application onto it.,8,val +TISTUD-5824,Studio updates fail with certificate error,"Tried all three preview links to install the update to 3.2 and cannot get past the following error during the software update: {code} An error occurred while collecting items to be installed session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.branding,3.3.0.1384563768. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile6574483185919399456.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile6574483185919399456.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.core,3.1.2.1385585178. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile7245106961147142599.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile7245106961147142599.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.rcp,3.3.0.201311272028. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile2785206651167591676.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile2785206651167591676.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.rcp.studio,1.0.0.201311272028. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile2479563730471450049.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile2479563730471450049.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.studio.rcp.override,1.0.0.201311272028. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile8442992676643988469.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile8442992676643988469.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.ui,1.1.0.1385600555. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile1429540028732507931.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile1429540028732507931.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.ui.ide,1.1.0.1385072181. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile2246925954441441870.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile2246925954441441870.jar Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.usage,1.0.0.1384993009. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile7821445931792401098.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile7821445931792401098.jar Problems downloading artifact: org.eclipse.update.feature,com.appcelerator.titanium.feature,3.3.0.1385072181-7E7B-7GIZUMJS_Wf5_aWDbUFZA2s. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile4160586145906849227.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile4160586145906849227.jar Problems downloading artifact: org.eclipse.update.feature,com.appcelerator.titanium.feature.rcp,3.3.0.201311272028-837_FA-FFBdWG4WIGnswU7DC08HJ. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile8559155449362296246.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile8559155449362296246.jar Problems downloading artifact: org.eclipse.update.feature,com.appcelerator.titanium.studio,3.3.0.1385605866-7T79382kFEI67z0Ie. Error reading signed content:/var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile8952509947482424607.jar An error occurred while processing the signatures for the file: /var/folders/83/bgbv34ld7f7cd349nrp3mvtc0000gr/T/signatureFile8952509947482424607.jar {code} ",5,val +TISTUD-5825,Cannot distribute Blackberry apps,"Null pointer exception. {code} !ENTRY com.aptana.core 1 0 2013-12-02 14:23:04.825 !MESSAGE (Build 3.2.0.201311120644) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""status"" ""-o"" ""json"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_HOME=/Users/penrique/Documents/android-sdk, ANDROID_NDK=/Users/penrique/Documents/android-ndk, ANDROID_SDK=/Users/penrique/Documents/android-sdk, APTANA_VERSION=3.2.0.1364103230, Apple_PubSub_Socket_Render=/tmp/launch-HWoPah/Render, GOOGLE_APIS=/Users/penrique/Documents/android-sdk/add-ons/addon-google_apis-google-8, HOME=/Users/penrique, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=penrique, NDK_CCACHE=/usr/local/bin/ccache, NUM_CPUS=4, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/Applications/bbndk/target_10_1_0_1483/qnx6//Applications/Momentics.app/host_10_1_0_231/darwin/x86//bin:/Users/penrique/Documents/android-sdk/platform-tools:/Users/penrique/Documents/android-sdk/tools:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/go/bin, PWD=/Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS, QNX_HOST=/Applications/Momentics.app/host_10_1_0_231/darwin/x86, QNX_TARGET=/Applications/bbndk/target_10_1_0_1483/qnx6, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-BRZ1Fi/Listeners, STUDIO_NAME=Titanium Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.2.0.201311120644, TMPDIR=/var/folders/52/zqyjkgrn0fqg6gbcfv8k3t400000gp/T/, USER=penrique, __CF_USER_TEXT_ENCODING=0x1F6:0:0, __CHECKFIX1436934=1, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2013-12-02 14:23:06.083 !MESSAGE (Build 3.2.0.201311120644) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""info"" ""-o"" ""json"" ""-t"" ""ios"" ""--sdk"" ""3.2.0.v20131028170320"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_HOME=/Users/penrique/Documents/android-sdk, ANDROID_NDK=/Users/penrique/Documents/android-ndk, ANDROID_SDK=/Users/penrique/Documents/android-sdk, APTANA_VERSION=3.2.0.1364103230, Apple_PubSub_Socket_Render=/tmp/launch-HWoPah/Render, GOOGLE_APIS=/Users/penrique/Documents/android-sdk/add-ons/addon-google_apis-google-8, HOME=/Users/penrique, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=penrique, NDK_CCACHE=/usr/local/bin/ccache, NUM_CPUS=4, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/Applications/bbndk/target_10_1_0_1483/qnx6//Applications/Momentics.app/host_10_1_0_231/darwin/x86//bin:/Users/penrique/Documents/android-sdk/platform-tools:/Users/penrique/Documents/android-sdk/tools:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/go/bin, PWD=/Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS, QNX_HOST=/Applications/Momentics.app/host_10_1_0_231/darwin/x86, QNX_TARGET=/Applications/bbndk/target_10_1_0_1483/qnx6, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-BRZ1Fi/Listeners, STUDIO_NAME=Titanium Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.2.0.201311120644, TMPDIR=/var/folders/52/zqyjkgrn0fqg6gbcfv8k3t400000gp/T/, USER=penrique, __CF_USER_TEXT_ENCODING=0x1F6:0:0, __CHECKFIX1436934=1, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2013-12-02 14:23:11.053 !MESSAGE (Build 3.2.0.201311120644) [INFO] com.aptana.core/debug/shell Searching for node in PATH locations: /Applications/bbndk/target_10_1_0_1483/qnx6//Applications/Momentics.app/host_10_1_0_231/darwin/x86//bin, /Users/penrique/Documents/android-sdk/platform-tools, /Users/penrique/Documents/android-sdk/tools, /usr/bin, /bin, /usr/sbin, /sbin, /usr/local/bin, /usr/local/go/bin !ENTRY com.aptana.core 1 0 2013-12-02 14:23:11.054 !MESSAGE (Build 3.2.0.201311120644) [INFO] com.aptana.core/debug/shell Found executable on PATH: /usr/local/bin/node !ENTRY com.appcelerator.titanium.blackberry.core 4 0 2013-12-02 14:23:11.061 !MESSAGE !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.blackberry.internal.core.launching.BlackBerryNodeJSCommandsHelper.build(BlackBerryNodeJSCommandsHelper.java:89) com.appcelerator.titanium.blackberry.internal.core.launching.BlackBerryNodeJSCommandsHelper.packageProject(BlackBerryNodeJSCommandsHelper.java:252) com.appcelerator.titanium.blackberry.internal.core.launching.BlackBerryPackagerLaunchConfigurationDelegate$1.run(BlackBerryPackagerLaunchConfigurationDelegate.java:91) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}",3,val +TISTUD-5827,MobileWeb: Cannot package mobileweb project,"h5.Description Packing a Mobile Web project will fail, creating no packaged application and displaying no error. h5. Steps To Reproduce 1. Create a Mobile Web project 2. Package the project h5. Expected Result A packaged project should have been created. h5. Actual Result Nothing happens, with no error messages to display a problem either.",5,val +TISTUD-5832,Dashboard is not detecting Android SDK if version 2.3.3 is not installed,"Precondition: I have added -Dtitanium.sdkRequirementsUrl=http://preview.appcelerator.com/dashboard/sdk_info.json after ""-vmargs"" to the .ini file. Test Steps: 1. Launch Appcelerator Studio on a clean machine. 2. Configure Android SDK with default 4.4 version from Dashboard. 3.Preferences > Studio > Platforms > Android --> Verify that android SDK is accepted in Preferences and no error should be thrown. Actual Result: Studio Dashboard is not detecting Android SDK.One possible reason is Android 2.3.3 version is not installed.",5,val +TISTUD-5833,Check for spaces in Android NDK path,"Some of the scripts inside Android NDK do not handle spaces well. If there is a space in the sdk path, it's likely that building the module will fail. Studio should check for spaces in the ndk path to avoid this.",5,val +TISTUD-5834,Android : Studio does not have an option to create & support an android keystore with different keystore & key password ,"h5.Description: 1.In CLI 3.2.0-beta we have an option to provide two different ""keystore"" & ""key"" passwords while packaging an android app for dist-playstore. 2.Studio does not have any option to create a keystore with different ""keystore"" & ""key"" passwords. 3.Also, using a keystore with different ""keystore"" & ""key"" passwords to package an app in studio which as of now only supports providing""keystore password"" while packaging, throws error {code}[ERROR] : Missing required option: --key-password {code} h5.Expected: 1. Studio should be able to create an android keystore with diferent ""keystore"" & ""key"" passwords. 2.Using a keystore with different ""keystore"" & ""key"" passwords to package an app in studio should not fail",8,val +TISTUD-5838,Studio: Project Nature - Project Nature is not set to mobile if you create an app from the CLI,"*Details:* If you create a mobile project from the CLI and import the project into Studio, you will not be able to build the project unless you change the project nature to mobile; web is the only selected project nature. *This is a regression. If you create a project using GA CLI and import the project into GA Studio, the project nature will already have mobile as the primary nature.* *Steps to reproduce:* 1. From the cli, create a project 2. Import the project into TiStudio as an Existing Mobile Project *Actual:* You will not be able to install project to device from the toolbar (see toolbar.png) 3. Right-click on the project and go to Project Natures *Actual:* Mobile nature is not selected and not the primary (see nature.png) *Expected:* Importing a project made from CLI should have *mobile* set as the primary nature. *Note:* After import, if you change the project nature to mobile, then you will be able to build the app from the toolbar.",3,val +TISTUD-5841,Running a iPad only app on iPad simulator starts the app in iphone simulator,"When trying to build a iPad only app for iPad simulator using SDK 3.1.2.GA on the latest Studio kicks of a iphone simulator build. studio log {code} !ENTRY com.aptana.core 1 0 2013-12-04 10:58:00.059 !MESSAGE (Build 3.2.0.201311271528) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""build"" ""--platform"" ""ipad"" ""--sdk"" ""3.1.2.GA"" ""--log-level"" ""trace"" ""--target"" ""simulator"" ""--ios-version"" ""7.0"" ""--device-family"" ""iphone"" ""--skip-js-minify"" ` {code} Steps to Reproduce. 1. Create a new iPad only app with SDK set 3.1.2.GA 2. Run for iPad Simulator. Actual Result. iphone simulator starts up. Expected Result. Selected iPad simulator starts up. ",5,val +TISTUD-5843,Alloy keyboard shortcuts don't work for platform-specific folder structure,"Steps: 1. Import attached project to Studio. 2. Open {{views/ios/index.xml}} 3. Use keyboard shortcut/file menu to open the view's associated controller (Cmd+Shift+C, e.g.). 4. A menu appears asking to select #1) Comment line/selection or #2) Controller File. 5. Select #2) Controller file. Results: Nothing happens. Expected: In this case, I would expect {{controllers/ios/index.js}} to open. In general, I'd expect Studio to open the platform-specific file, if one exists, otherwise open the platform-default version.",5,val +TISTUD-5844,Package Alloy Geocoder sample in Studio,"Currently for Alloy samples, we call ""alloy new"" to create the default app and then unzip the sample content on top of it, but for Geocoder sample in 3.2.0, due to the complexity related to ALOY-891, we decide that it will contain the full-fledged app in a zip, and we will define the sample using our existing sample extension point.",3,val +TISTUD-5845,"Titanium Studio: ""Computing SDK Info..."" errors are being displayed and eventually Studio freeze","h5. Problem description 1. After updating to Titanium Studio 3.2.0.201312031529, every time Studio is started, an error popup is shown: An internal error occurred during: ""Computing SDK Info..."". java.lang.AbstractMethodError Also, after closing the error message and editing a project, Studio freeze and it has to be killed. Attaching screenshot and log. ",3,val +TISTUD-5846,Appcelerator studio intermittently becomes unresponsive & on a force quit & restart gives errors.,"h5.Description: 1. Use the studio version mentioned in environment field. h5.Actual Result: 1. You would intermittently see studio become unresponsive & the wait spinning circle spinning. 2. It does not become responsive again & only way is to force restart. 3. After force restarting we get dialog ""multiple errors have occurred"" showing a NPE. NOTE 1: Have attached screenshot, studio logs & diagnostic test for reference. NOTE 2: The error are different everytime. NOTE 3: If you try to open any file it will throw errors. h5.Expected result: 1. Studio should not become unresponsive & on restart should not get any errors.",3,val +TISTUD-5847,Usability: Toolbar not forced visible after update,"Updating from Appcelerator Studio 3.1.4 to 3.2.0, my toolbar remained hidden (which is the default in 3.1.4) This is a big problem, as all Run/Debug/Profile… options have been moved from the view to the global toolbar. The workaround is to use Window >Show Toolbar, but that's not obvious to many people.",5,val +TISTUD-5849,'File Open Error' after stopping & resuming JDK installation,"Steps: 1. Run Windows installer on system without JDK installed. 2. Once you start the JDK part of the installation click ""STOP"" to return to the 'Confirm installation' screen. 3. Click Install agagin. Result: Error dialog (see attached). ",8,val +TISTUD-5853,Studio freezes on Startup when selecting a run-configuration,"When opening the latest RC of Titanium Studio and trying to select a run-configuration (iOS/Android-device-/simulator), the Studio freezes for about 30-50 seconds without errors and then can be used without problems. The bug occurs on every start of the Studio. I hope it is reproducible!",5,val +TISTUD-5855,Appc Studio deadlock after startup while loading SDK info,"On Appcelerator Studio startup, it tries to load the SDK information from TiApp file (that is left open before restart) and got into deadlock. It froze forever and didn't recover from the deadlock. I tried updating Appc Studio to the latest RC build, but that still didn't help. The only workaround I can think of is to move to a new workspace that doesn't have any TiApp file opened from the previous session.",5,val +TISTUD-5858,Geocoder sample is named as 'harness' and not as 'Geocoder' ,"Test Steps: Window > Show view > Samples > Geocoder. Check the name of the app in tiapp.xml Actual Result: Geocoder app is named as 'harness'.Please find tiapp.xml below. {code} 52a1a950c85feb5439000032 https://secure-identity.cloud.appcelerator.com https://api.cloud.appcelerator.com YsIMG56CFdWckNgBNsqWETcQ6yOCeHaz geissWBYsnJf2W2w1r3Bd8dfVTCHVV60 sg1bHq1j5yZmV8GoKqXRl5L5ngXWaRjs VWbpElFjqrqQyyQohIbzY2JSK07RkEYu Bm4BX60fEYdL2n8ewJLfhGkFbB9SN54k xr8SU4h38Z4e1VngOahkkBTCTAiWktDl true true true true true true 3.2.0.v20131206002446 com.appcelerator.Geocoder Harness 1.0 tlukasavage http:// not specified 2012 by tlukasavage appicon.png false false default false false false true 92f97a58-b1da-4de6-a761-0a4a33892dbc system Ti.UI.PORTRAIT Ti.UI.PORTRAIT Ti.UI.UPSIDE_PORTRAIT Ti.UI.LANDSCAPE_LEFT Ti.UI.LANDSCAPE_RIGHT true true default com.appcelerator.apm com.soasta.touchtest com.soasta.touchtest com.soasta.touchtest com.soasta.touchtest ti.cloud com.appcelerator.apm ti.map ti.map ti.alloy com.soasta.touchtest.android 6656.155 CFBundleURLTypes CFBundleTypeRole Editor CFBundleURLName com.appcelerator.Geocoder CFBundleURLSchemes touchtest-25203bc1-eb08-4412-8ffa-46aa02225c8a 164651 {code}",5,val +TISTUD-5859,Studio: Installing new SDK from CLI causes Blackberry and Tizen to gray out,"h5.Description Installing a later SDK than a version I already have, while creating a project with an older version of the SDK will create the project successfully. However when I change to the later SDK in the tiapp.xml that is automatically created the Blackberry and Tizen deployment targets gray out. h5.Steps To Reproduce 1. Download and install the latest SDK through CLI 2. Create a new project in Studio using the latest SDK you have before the new one is installed. 3. Leave the tiapp.xml file open. 4. Once the new SDK has finished installing select it in the tiapp.xml h5.Expected result The SDK should change with no other visible difference on the tiapp.xml page h5.Actual Result Blackberry and Tizen gray out",3,val +TISTUD-5865,Some top-level Alloy methods/properties don't appear in code hints,"Steps: 1. Type {{Alloy.create}} in a controller file and press {{Ctrl+Space}} to invoke code hints. Results: Code hints don't appear for top-level methods (createController, createModel, etc). Expected: Code hints appear for all Alloy methods.",5,val +TISTUD-5866,Line/block comment keyboard shortcuts not working,"Titanium Studio, build: 3.2.0.201312081251. Mac OS 1. In any JavaScript file, position cursor at beginning of line and press {{Cmd + /}}. Results: Comment not applied to current line. Expected: That. (Related: The associated menu commands are kind of buried under Commands > Source > Comments. In Android Dev Tools, for comparison, they are the first items under the Source menu.)",5,val +TISTUD-5868,NavigationGroup element appears twice in code hints,"1. Open an Alloy view/xml file and start typing ""Navigation"" until code hints appears. Results: Code hints contain two ""NavigationGroup"" items (see screenshot) Expected: Only contains one mention.",3,val +TISTUD-5869,Tiapp: the app id gets automatically pasted into any field in the tiapp editor when the field gains focus,"*Details:* After running, debugging, or packaging an app, you will be able to automatically paste the app id into any field in the tiapp editor. *This is a regression as this does not occur on the GA stack.* *Steps to reproduce:* 1. Create a default app; leave the tiapp editor open 2. Run, debug, or package the app to device or simulator 3. Wait for Studio to finish its process i.e. if installing to simulator, wait for simulator to launch. Or if packaging, wait for studio to finish packaging the app. 4. Then, click on any fields in the tiapp editor *Actual:* The app id will automatically be copied to any of the fields; see https://drive.google.com/file/d/0B_5IL30seqpAN3l1ZDk2cDNpYVE/edit?usp=sharing *Expected:* The app id should not be automatically copied to any of the tiapp editor fields.",5,val +TISTUD-5872,Android : Debugging not working in alloy for android,h5.Description: 1. Create an alloy app & set a breakpoint in the index.js file in the app 2. Run debug on device & emulator h5.Actual result: 1. The app gets installed & the debug session starts successfully but the breakpoint is not hit & the app does not halt at the breakpoint. h5.Expected Result: 1. The breakpoint should be hit & the app should halt at the breakpoint. NOTE : I used the default alloy app from studio template for testing.,5,val +TISTUD-5873,Profiling in windows on Android device uses old build scripts instead of new CLI,"Steps to reproduce: 1. Run profiler on device 2. Observe console logs Expected: Output logs should say that it's using the new CLI Actual: We get logs saying it's using the old build scripts In the logs, I see: {code} !ENTRY com.aptana.core 1 0 2013-12-10 14:01:36.059 !MESSAGE (Build 3.2.0.201312091648) [INFO] com.aptana.core/debug/shell Running process: Process: ""C:\Users\Thomas Anderson\AppData\Local\Appcelerator Studio\plugins\com.appcelerator.titanium.python.win32_1.0.0.1338515509\python\python.exe"" ""C:\Users\Thomas Anderson\AppData\Roaming\Titanium\mobilesdk\win32\3.2.0.v20131209192649\android\builder.py"" ""install"" ""alloytest"" ""C:\Users\Thomas Anderson\Desktop\titaniumstuff\android-sdk-windows"" ""C:\Users\Thomas Anderson\Documents\Appcelerator_Studio_Workspace\alloytest"" ""com.alloytest"" ""1"" """" ""adb:52681"" ""profiler"" Working directory: null {code}",3,val +TISTUD-5874,Studio falls back to legacy builds when build fails,"Steps to reproduce: 1. Build an app for distribution 2. Install using adb push /built_apk/ /sdcard/ 3. Browse to the apk on the phone and install 4. Run a debug build of the same app from studio Expected: The app should fail to install, and we should see an error why Actual: Build fails, and Studio falls back to old python scripts",2,val +TISTUD-5875,Package Mobile Web dialog location field does not accept ~ paths,"When I package an mobile web app for distribution and set the location to ""~/something"", it apparently builds, but I have no idea where the files went.",3,val +TISTUD-5886,Android : Provision to build to all connected devices at the same time through studio ,h5.Description: In CLI we have the ability to provide {code}--device-id all{code} if we have more than one connected android devices. This builds & runs the app on all the connected devices simultaneously. As of now studio does not have any such feature & this would be a great addition for whom who wants to build to multiple device at the same time.,8,val +TISTUD-5887,User is in the offline mode though the saved credentials are valid,"Though I have seen this happening only my development environment, I'm afraid that it can happen even in the RC builds. However, since I couldn't reproduce it whenever on the RC builds after my multiple attempts, I assume this happens only on the development. Here is the exception that is logged in the Studio logs during its startup. There is a very small timing window when Titanium360ServicesControl tries to add to the UserManager listeners, when UserManager is already notifying about the logged in event. java.util.ConcurrentModificationException java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) java.util.AbstractList$Itr.next(AbstractList.java:343) com.appcelerator.titanium.core.user.TitaniumUserManager.signIn(TitaniumUserManager.java:218) com.appcelerator.titanium360.internal.core.Titanium360Manager.login(Titanium360Manager.java:233) com.appcelerator.titanium360.internal.core.Titanium360Manager.checkLoginUser(Titanium360Manager.java:688) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler$2.run(TitaniumSplashHandler.java:258) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) ",3,val +TISTUD-5888,Sync Titanium SDK default location with CLI,"From 3.2.0, CLI supports multiple locations for detecting Titanium SDKs. Specifically for Windows, titanium CLI choose the default location for SDKs as C:\ProgramData\Titanium (according to the new best practices of Windows Vista and Win7), however Studio will has the default path as C:\Users\[user]\AppData\Local\Titanium This could cause inconsistency if user installs SDK from CLI - that will be installed into ProgramData folder, however Studio will not be able to detect it as it might be watching for Users AppData folder. Studio should sync with CLI to get the default SDK installation location and set it in preferences. The below command gives the information about the defaultInstallLocation and installed SDKs. ti sdk -o json ",5,val +TISTUD-5892,Module Project: Clean Mobile Module project showing java.lang NullPointerException,"Defect: On cleaning the Mobile Module project,it is showing java.lang NullPointerException. Steps to Reproduce: 1. MobileWeb Module Project. 2. Call project Clean. Actual Result: Project cleans shows java.lang NullPointerException. Expected Result: Project should cleans without error. Refer to the attached screenshot for your reference. Note: Severity is not shown, so it set as: Severity: Major",3,val +TISTUD-5923,Appcelerator Studio: Top menu bar not appearing,"h6.Issue description When opening Appcelerator Studio IDE, 9 times out of 10 it will not open the studio window, only shows the ""Appcelerator Studio"" main menu in the task bar without the rest of the menu items. Developer have to force quit the Studio and try re-opening it. This takes at least 10 tries before it fully opens the studio. Another developer also has this same issue with Appcelerator Studio and he is running on OSX Mavericks. h6.Work around To move the default workspace ~/Documents/Appcelerator_Studio_Workspace to another location, re-import the projects from previous workspace into the new one and then re-launch Studio. Very likely due to a corrupted workspace. ",5,val +TISTUD-5895,Studio: Cannot create project if selecting and de-selecting a platform that isn't installed,"h5.Description If I create a new project and don't have a platform installed (Example: Tizen) and select it, then de-select the platform I can no longer finish the project creation. Clicking ""finish"" will do nothing. h5.Steps To Reproduce 1. Open the create project wizard 2. Select all platforms, making sure one of them is not installed/set up 3. De-select the platform that isn't set up 3. Click Finish h5.Expected Result Create the project with the desired platforms selected h5.Actual Result Nothing happens. Can only cancel the wizard and start again. +Extra Information+ {code} !ENTRY org.eclipse.ui 4 0 2013-12-12 15:49:39.741 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.getSelectedPlatforms(PlatformsListConfigurationPage.java:190) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectCreationPage.getPlatformsToInstall(NewMobileProjectCreationPage.java:414) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectWizard.performFinish(NewMobileProjectWizard.java:119) org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:98) org.eclipse.jface.action.Action.runWithEvent(Action.java:499) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code}",3,val +TISTUD-5897,Android: Add support for Genymotion emulator,This presumes Genymotion has already been installed. This is for adding any necessary support around the UI to configure and run Genymotion emulators,8,val +TISTUD-5921,Code-Sense is not configured properly for Alloy Applications,"Create a new Alloy project in either Titanium Studio or Appcelerator Studio. Open a javascript file (ex. controllers/index.js) Test code-sense for this file by typing ""Ti.UI."" and note that you do not get a pop-up as expected. ISSUE ----- The problem is that under configuration (Preferences -> Studo -> Content Assist) projects with an Alloy Nature are not properly configured. FIX --- User must go to the application preferences (Studio -> Content Assist) and manually select Android, Blackberry, iPad, Iphone, MobileWeb & Tizen for Alloy Project Nature Expecation ---------- This should be configured for Alloy projects by default",3,val +TISTUD-5912,Studio: Tizen SDK location disappears from Studio preferences on launch,"h5.Description When dashboard loads after Studio is opened it shows Tizen is not set up. I will set up Tizen in my Studio preferences and it will work fine from then. The next time I open Studio, Tizen will no longer be set up and request me to locate the Tizen SDK folder. h5.Steps To Reproduce 1. Set up the Tizen preference in Studio 2. Restart Studio 3. Check the Tizen preferences h5.Expected Result Tizen to still be set up h5.Actual Result Tizen is not set up any more",5,val +TISTUD-5913, Alloy: Support Data Binding attributes,"For the XML markup, content assist does not suggest: * Collection, Model or Widget for tags. (Alloy and Require work.) * formFactor, platform for attributes. (id, class and ns work.) See the tables at the end of the 'Introduction' section, http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_XML_Markup There is also dataCollection, dataFilter, and dataTransform attributes for Ti proxies that support data binding, such as TableView and View. Tony introduced some other ones for Alloy 1.1.0. 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,val +TISTUD-5914,Alloy: Support Proxy child tags such as RightNavButton,"For the XML markup, content assist does not suggest: * Collection, Model or Widget for tags. (Alloy and Require work.) * formFactor, platform for attributes. (id, class and ns work.) See the tables at the end of the 'Introduction' section, http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_XML_Markup There is also dataCollection, dataFilter, and dataTransform attributes for Ti proxies that support data binding, such as TableView and View. Tony introduced some other ones for Alloy 1.1.0. 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,val +TISTUD-5915,Refresh AVD listing in pref page when we detect new AVDs in our background refresh of ti info,"If a user opens the AVD manager through the Android pref page and then deletes all their AVDs, then we'll generate a default one for them. But that won't ever get shown in the UI until you close the pref page and re-open. We need some sort of listener on the pref page to update the drop down when the underlying SDK locator's listing is changed.",3,val +TISTUD-5916,"When clicking link to show hidden platform config wizard, we should focus the wizard dialog","Clicking the link does open the wizard, but it doesn't focus it. The user needs to click on it to be able to hover over the spinner to see details on progress.",2,val +TISTUD-5917,The platform config wizard's job doesn't pass through install details properly,"You can hover over the wizard spinner in the UI dialog to get details of where the progress is at for the job, but the actual job doesn't show those details in the progress view. It just always says ""Computing prerequisite plan"".",5,val +TISTUD-5918,Filter packaging launch configurations in the configuration dialog,# Select Packaging mode in the global launch # Select Configurations... in the launch shortcuts menu # It shows the launch configurations of both Packaging and Run modes. Expected: It should show only the configurations for package mode. ,3,val +TISTUD-5919,iPad: Simulator - Cannot launch any iPad simulator from studio using SDK 3.1.4,"*Details:* If you use the above environment setup (specifically, SDK 3.1.4.v20131213162008 and latest CLI from github.com/appcelerator/titanium.git#3_2_X), then you will not be able to launch any iPad simulators. *This is a regression as you were able to launch iPad simulators from the GA stack.* The workaround is to use ""\-\-device\-family"" ""ipad"" flag instead of ""\-\-device\-family"" ""universal"" in the iPad simulator build command: {code:title=Using studio commands:} ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""build"" ""--platform"" ""ipad"" ""--sdk"" ""3.1.4.v20131213162008"" ""--log-level"" ""trace"" ""--target"" ""simulator"" ""--ios-version"" ""7.0.3"" ""--device-family"" ""ipad"" ""--sim-version"" ""7.0.3"" ""--retina"" ""--sim-64bit"" ""--skip-js-minify"" {code} {code:title=From terminal:} ti build --platform ipad --target simulator --ios-version 7.0.3 --device-family ipad --sim-version 7.0.3 --retina --sim-64bit {code} *Steps to reproduce:* 1. Create a default app 2. Launch any iPad simulators from studio *Actual:* No iPad simulators will be launched. Only iPhone simulators will be launched. Below is the command that studio uses to launch iPad simulators: {code} ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""build"" ""--platform"" ""ipad"" ""--sdk"" ""3.1.4.v20131213162008"" ""--log-level"" ""trace"" ""--target"" ""simulator"" ""--ios-version"" ""7.0.3"" ""--device-family"" ""universal"" ""--sim-version"" ""7.0.3"" ""--skip-js-minify"" {code} *Expected:* Studio should be to launch iPad simulators.",3,val +TISTUD-5924,NPE while opening TiApp during Studio startup on Windows,"If TiApp is opened in the previous session, then Studio tries to re-open the TiApp and at some instances, it fails to open the TiApp editor with the below failure : java.lang.NullPointerException com.aptana.theme.ThemePlugin.applyToAllEditors(ThemePlugin.java:346) com.aptana.theme.internal.ThemeManager.setCurrentTheme(ThemeManager.java:219) com.aptana.theme.internal.ThemeManager.getCurrentTheme(ThemeManager.java:194) com.aptana.editor.common.CommonSourceViewerConfiguration.getCurrentTheme(CommonSourceViewerConfiguration.java:612) com.aptana.editor.common.CommonSourceViewerConfiguration.getThemeBackground(CommonSourceViewerConfiguration.java:462) com.aptana.editor.common.CommonSourceViewerConfiguration.getContentAssistant(CommonSourceViewerConfiguration.java:200) org.eclipse.jface.text.source.SourceViewer.configure(SourceViewer.java:464) com.aptana.editor.common.viewer.CommonProjectionViewer.configure(CommonProjectionViewer.java:168) org.eclipse.ui.texteditor.AbstractTextEditor.createPartControl(AbstractTextEditor.java:3424) org.eclipse.ui.texteditor.StatusTextEditor.createPartControl(StatusTextEditor.java:54) org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.createPartControl(AbstractDecoratedTextEditor.java:447) com.aptana.editor.common.internal.AbstractFoldingEditor.createPartControl(AbstractFoldingEditor.java:123) com.aptana.editor.common.AbstractThemeableEditor.createPartControl(AbstractThemeableEditor.java:327) com.aptana.editor.xml.XMLEditor.createPartControl(XMLEditor.java:78) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppXMLSourcePage.createPartControl(TiAppXMLSourcePage.java:129) org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:243) org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:325)",3,val +TISTUD-5928,AppC Studio / Ti Studio Does not Recognize All Profiles for Ad-Hoc Builds,"Hey Guys, Just noticing this and I've heard of some others talking about this the last few days. Not all iOS ad-hoc provisioning profiles are shown in the Ti / AppC Studio configuration screen. What I see: http://www.screencast.com/t/xjw53dTGTM - Some of them are there but I'm expecting to see other ad-hoc profiles etc. When I go to the settings I see all of my profiles, which many of them are adhoc / ent profiles - http://www.screencast.com/t/w7K4fx5VO This can consistently be reproduced on Ti Studio and AppC Studio.",3,val +TISTUD-5935,Builds fail if workspace is on a windows server (UNC path),"h5.Description Connecting to a Windows Server using the following path as, an example {code}\\WINSERVER2008\UserAccount\Studio_Server_Workspace{code} will succeed. Even creating a project will succeed. However when you build the project it will fail. h5.Steps To Reproduce 1. Set up a windows server environment 2. Open studio on another computer 3. Connect to the workspace on the server 4. Create and build a project h5.Expected Result Project to build succesfully. h5.Actual Result Studio fails to connect to the workspace +Extra Information+ Setting the network to a drive location will fix this problem. In command prompt, run {code}net use (drive letter) \\computername\location {code} or in this case {code}net use X: \\WINSERVER2008\UserAccount\ {code} Then connect to the workspace X:\Studio_Server_Workspace",3,val +TISTUD-5936,Studio:Appcelerator Updates - required updates can be deselected,"Since it is a new feature to make updates ""uncheckable"", I will skip the label ""regression"" When Appcelerator updates are available and are required, it is possible to deselect them. There is no other steps to proceed, but to select them again or restart Studio. h5. To reproduce In my case I reverted node.js to the older version and got the update request, following Appcelerator Studio> Help> Check for Appcelerator updates ",3,val +TISTUD-5937,Windows: Re-launching app on Android simulator does not kill previous session node processes,"Steps to reproduce : 1) On Windows, launch an app on Android simulator. 2) After the 1st launch is successful, re-launch the same app on same simulator. Process Explorer shows the node process instance created during the 1st time launch still exists along with the node process from the 2nd launch. Since multiple node processes are running in parallel, it can create inconsistency with the android logcat output on the same device/simulator.",8,val +TISTUD-5942,Studio freezes when restarting Studio with proxy settings on and a tiapp editor open,"Ran into a deadlock in Appcelerator Studio after the following steps: 1. Launch Studio and log out; 2. Launch Studio, enter proxy settings (https://wiki.appcelerator.org/display/tools/Internal+Proxy+Server) and log in; 3. Have a tiapp.xml open and re-launch Studio. After Studio is re-launched, it would beach-ball and had to be force-killed. And each time afterward, Studio would freeze upon launch. Attached the jstack log. ",5,val +TISTUD-5943,Studio UI: Global toolbar - Mobile Web Preview in Emulator - not enough space to show types of emulator,h5. To reproduce Studio> Run> Mobile Web Preview in Emulator h5. Actual result Please see the screenshot,3,val +TISTUD-5944,Studio freezes if the user enter only credentials without proxy settings after logout from proxy,"This is an edge case where the Studio freezes if the proxy details are already saved in preferences, but user logs out in the previous session. Steps to reproduce : 1) Login into Studio and set proxy server details. 2) Now, logout from Studio. 3) In the login screen, enter only user login credentials (the proxy server details are not shown in the proxy dialog, though they are saved in the preferences). 4) Studio prompts for proxy user id & pwd. If the details are not submitted before the dashboard is opened, then Studio freezes. Workaround : Restarting Studio will help fix this problem. Ideally, we should load the proxy server preferences during the login screen of splash handlers. Since we didn't load any of the proxy details, we didn't end up with setting the simple proxy authenticator, thereby Eclipse prompts to enter the proxy user id/pwd. Since dashboard also tries to make network connection at the same time, it end up in a deadlock.",3,val +TISTUD-5963,Android: Missing Java SDK. Please make sure Java SDK is on your PATH,h3. Steps to Reproduce not sure what I did wrong. It was working perfectly before. I have set the Java Path in system variables. h3. Actual Result Missing Java SDK. Please make sure Java SDK is on your PATH h3. Expected Result Open android emulator,3,val +TISTUD-5953,Android: Show warning in TiApp if the minSdkVersion attribute references to a version less than min required,"If the TiApp contains the minSdkVersion attribute of android referencing to a version less than minimum version, then there are no errros/warnings in the TiApp, but running the app on emulator/device might fail with ""[ERROR] Minimum Android SDK version must be 10 or newer"" Steps to reproduce: # Modify the TiApp to contain the minSdkVersion on the similar lines : # Run the app on Android emulator. ",8,val +TISTUD-5961,BlackBerry: Authentication failed,"# Run -> Blackberry Device # Studio: 3.2.0 GA # Titanium SDK: 3.2.0 GA No matter I change the password in Studio, the password in the command always display as '^˝õM'(see below) {code} [Command] :source /Applications/Momentics.app/bbndk-env_10_2_0_1155.sh && blackberry-deploy -installApp -launchApp -device 169.254.1.1 -package ""/Users/stevenlam/Documents/Titanium_Studio_Workspace/AppDemo/build/blackberry/arm/o.le-v7/AppDemo.bar"" -password ^˝õM. Info: Package created: /Users/stevenlam/Documents/Titanium_Studio_Workspace/GeoTrackingDemo/build/blackberry/arm/o.le-v7/AppDemo.bar Error: Command failed: Error: Authentication failed. There have been 1 of 5 failed attempts Error: Authentication failed. There have been 1 of 5 failed attempts {code} Password and IP for bb10 device are correct, but the Studio said Authentication fails. This work for the previous version of Studio and SDK, but fails in the latest version. ",5,val +TISTUD-5956,Package iOS module wizard is not appearing from the toolbar,Test Steps: 1.Create an iOS module project. 2.Try to package it in the existing project from the toolbar. Actual Result: It automatically packages to the Titanium SDK option. Also the Package module wizard doesn't appear. Note: Module Packaging wizard from toolbar appears for android module packaging as well as for mobileweb module packaging.,5,val +TISTUD-5960,Dashboard: Themes: Unable to set theme to 'Dark',"h3. Steps to Reproduce 1. Update Titanium Studio 2. Customize Your Environment 3. Select 'Dark' in Default Titanium Studio Theme 4. Restart Titanium, but the interface appears like 'Light' theme, but in my preferences is select 'Dark' theme h3. Actual Result Always when I enter to Titanium the theme is wrong h3. Expected Result That I dont have to select always 'Dark' when I open Titanium Studio",3,val +TISTUD-5958,"Installer: When opening the dmg, the Ti icon is super pixelated in a macbook pro retina","h4. Problem Description When installing the latest Titanium/Appcelerator Studio from the developer.appcelerator.com, the dmg includes a low resolution icon, looking pixelated in Mac OSX running in a Macbook Pro Retina. ",5,val +TISTUD-5969,Can no longer use & in app title to create &,"used to be able to use the following to create an & in the app title iOS one&two android one&amp;two Now using either combination on android or blackberry causes the application to say it is installed but does not appear on the device or launch from the studio [INFO] : Installing apk: /Users/Martin/Documents/Titanium_Studio_Workspace/OneandTwo/build/android/bin/One&Two.apk [INFO] : Installing app on device: GT-I8190 [INFO] : App successfully installed [INFO] : Starting app: com.anvilgroup.globetracker/.OneTwoActivity Works correctly on iOS but not android or blackberry, replacing & with and builds and runs correctly on android and blackberry",5,val +TISTUD-5964,File-> Close All is not working from the drop down menu,"If you attempt to ""Close All' from the File Menu dropdown in Studio, you will notice that nothing happens. Expectation - All open files should close. NOTE: Shortcut commands do not work either",5,val +TISTUD-5965,Unable to assign CMD+1 to custom Ruble commands,"When creating custom ruble commands, i am unable to assign a ruble to CMD+1 on mac. Previous versions of Studio supported this. ",5,val +TISTUD-5966,TiApp shows the invalid configuration status for Blackberry platform though it is valid,"If Studio is launched with Java 7, then though BlackBerry platform is configured to a valid location, TiApp still reports that BlackBerry platform is not configured and there is no tooltip message available to the help icon. Steps to reproduce : # Launch Studio with Java 7 # Configure BlackBerry SDK to a valid location. # Open TiApp and notice that it still does not recognize the valid BlackBerry platform configuration. # The Help icon (indicating about the unconfigured status) does not show any tooltip message about the configuration.",5,val +TISTUD-5970,Mac: Mac DMG includes an old copyright notice (yr 2012).,"h4. Problem Description When installing in a new machine, the dmg will show an old copyright notice (from 2012)",5,val +TISTUD-5971,Breakpoint hit opens hidden file in alloy debug process,Test Steps: 1.Create an alloy project with alloy:1.3.1-beta or with alloy:1.3.0.GA 2.Open App > Controllers > Index.js. 3.Set the breakpoint at line no. 1 (function doClick()) of the below code: {code} function doClick() { alert($.label.text); } {code} 4. Debug the app on any android device ( eg. Google Nexus 7) Actual Result: A new file Index.js from hidden folder Resources > Alloy opens and hits the breakpoint. Please see the attached screenshot. Expected Result: Breakpoint should be hit at index.js of app folder. ,5,val +TISTUD-5972,BlackBerry: Fall back to default SDK path if the configuration file is not available,"On a completely fresh install of Titanium Studio (meaning absolutely no Titaniums or mobile SDKs installed yet) I follow the dashboard ""getting started"" section to install Android and Blackberry. Android worked as expected. Blackberry also appeared to install as expected, adding ""bbndk"" to my C:\ folder and showing the 1st attached screenshot after completion. When returning to the getting started page, though, it still indicates the BB is not installed, as in 2nd screenshot. I tried closing and re-opening the dashboard, as well as restarting Studio, but the problem remained. Again, it appears the installation was a success, the getting started section is not reflecting that.",5,val +TISTUD-5975,Mobileweb Configuration in dashboard shows as misconfigured on Windows,"Despite setting up an appropriate browser in the Studio settings, I am still seeing the red X indicating that my MobileWeb browser is not set up correctly. I have included snapshots showing the issue, and the fact that I have an approrpriate browser configured.",5,val +TISTUD-5976,Dashboard help for Mobileweb configuration shortcuts to the wrong preference section,When you click the help links to configure mobileweb in the getting started dashboard (screenshot #1) it takes you to the platforms section of the preferences (screenshot #2). It should instead take you to the mobileweb preferences one level lower (screenshot #3),2,val +TISTUD-5977,Node.ACS Bindings are deleted on compile of Alloy Applications,"When Importing Node.ACS bindings within an Appcelerator Mobile App Project, the binding is created under the Resources directory of the application. This is overwritten during the alloy compile. For Alloy Applications, a lib folder should be created under the 'app' directory and the binding file created there to follow Alloy project folder conventions and to prevent the deletion of the binding file. ",5,val +TISTUD-5981,Error creating Alloy app from Studio if alloy and CLI are installed without restarting,"Creating an app from an alloy template is failing. {code} !SESSION 2014-01-03 17:28:55.256 ----------------------------------------------- eclipse.buildId=unknown java.version=1.7.0_40 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.ui 2 0 2014-01-03 17:30:28.870 !MESSAGE Warnings while parsing the images from the 'org.eclipse.ui.commandImages' extension point. !SUBENTRY 1 org.eclipse.ui 2 0 2014-01-03 17:30:28.870 !MESSAGE Cannot bind to an undefined command: plug-in='com.appcelerator.titanium.android.ui', id='com.appcelerator.titanium.mobile.command.run_on_device.android' !SUBENTRY 1 org.eclipse.ui 2 0 2014-01-03 17:30:28.870 !MESSAGE Cannot bind to an undefined command: plug-in='com.appcelerator.titanium.android.ui', id='com.appcelerator.titanium.mobile.command.debug_on_device.android' !ENTRY com.aptana.scripting 4 0 2014-01-03 17:30:31.012 !MESSAGE (Build 3.2.0.201312191455) [ERROR] Failed to load bundle C:\Users\Matt\AppData\Local\Appcelerator Studio\plugins\com.appcelerator.titanium.core_3.1.2.1387411434\bundles\titanium_mobile.ruble !STACK 0 org.yaml.snakeyaml.error.YAMLException: Cannot create property=children for JavaBean=bundle ""titanium_mobile"" { bundle_precedence: APPLICATION path: C:\Users\Matt\AppData\Local\Appcelerator Studio\plugins\com.appcelerator.titanium.core_3.1.2.1387411434\bundles\titanium_mobile.ruble\bundle.rb author: Thomas Aylott/Appcelerator copyright: null description: null repository: null } ; Cannot create property=icon for JavaBean=project_sample ""Geocoder"" { id: null category: com.appcelerator.titanium.mobile.samples.category name: Geocoder location: null description: A sample Master/Detail app that uses native maps to plot locations. With it you can forward geocode addresses and add them as annotations to the map. } ; No single argument constructor found for interface java.util.Map org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:290) org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct2ndStep(Constructor.java:191) com.aptana.scripting.model.BundleCacher$BundleElementsConstructor$ConstructBundleElement.construct(BundleCacher.java:816) org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:181) org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:140) org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:126) org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:296) org.yaml.snakeyaml.Yaml.load(Yaml.java:290) com.aptana.scripting.model.BundleCacher.load(BundleCacher.java:328) com.aptana.scripting.model.BundleCacher.load(BundleCacher.java:286) com.aptana.scripting.model.BundleManager$BundleLoadJob.run(BundleManager.java:110) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create property=icon for JavaBean=project_sample ""Geocoder"" { id: null category: com.appcelerator.titanium.mobile.samples.category name: Geocoder location: null description: A sample Master/Detail app that uses native maps to plot locations. With it you can forward geocode addresses and add them as annotations to the map. } ; No single argument constructor found for interface java.util.Map org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:290) org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct2ndStep(Constructor.java:191) com.aptana.scripting.model.BundleCacher$BundleElementsConstructor$ConstructProjectSampleElement.construct(BundleCacher.java:921) org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:181) org.yaml.snakeyaml.constructor.BaseConstructor.constructSequenceStep2(BaseConstructor.java:275) org.yaml.snakeyaml.constructor.BaseConstructor.constructSequence(BaseConstructor.java:246) org.yaml.snakeyaml.constructor.Constructor$ConstructSequence.construct(Constructor.java:502) org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:181) org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:287) ... 11 more Caused by: org.yaml.snakeyaml.error.YAMLException: No single argument constructor found for interface java.util.Map org.yaml.snakeyaml.constructor.Constructor$ConstructScalar.construct(Constructor.java:372) org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:181) org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:287) ... 19 more !ENTRY org.eclipse.equinox.security 1 0 2014-01-03 17:30:31.941 !MESSAGE New keyring password generated. !ENTRY org.eclipse.e4.ui.css.core 4 0 2014-01-03 17:30:32.203 !MESSAGE CSS property 'maximize-visible' has been deprecated: renamed as swt-maximize-visible !ENTRY org.eclipse.e4.ui.css.core 4 0 2014-01-03 17:30:32.205 !MESSAGE CSS property 'minimize-visible' has been deprecated: renamed as swt-minimize-visible !ENTRY com.appcelerator.titanium.ui.ide 4 0 2014-01-03 17:30:38.114 !MESSAGE (Build 3.2.0.201312191455) [ERROR] com.appcelerator.titanium.core/debug/dashboard Unknown SDK ios !ENTRY com.aptana.projects 2 0 2014-01-03 17:59:53.055 !MESSAGE Internal error: !STACK 1 org.eclipse.core.runtime.CoreException: com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:253) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327) com.aptana.projects.wizards.AbstractNewProjectWizard.doCreateProject(AbstractNewProjectWizard.java:321) com.aptana.projects.wizards.AbstractNewProjectWizard$2.run(AbstractNewProjectWizard.java:374) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: org.eclipse.core.runtime.CoreException:  .__ .__ _____ | | | | ____ ___.__. \__ \ | | | | / _ < | | / __ \| |_| |_( <_> )___ | (____ /____/____/\____// ____| \/ \/ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:153) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:300) com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:249) ... 5 more !SUBENTRY 1 com.aptana.projects 4 0 2014-01-03 17:59:53.055 !MESSAGE !STACK 1 org.eclipse.core.runtime.CoreException:  .__ .__ _____ | | | | ____ ___.__. \__ \ | | | | / _ < | | / __ \| |_| |_( <_> )___ | (____ /____/____/\____// ____| \/ \/ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:153) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:300) com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:249) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327) com.aptana.projects.wizards.AbstractNewProjectWizard.doCreateProject(AbstractNewProjectWizard.java:321) com.aptana.projects.wizards.AbstractNewProjectWizard$2.run(AbstractNewProjectWizard.java:374) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 2 com.aptana.core 4 1 2014-01-03 17:59:53.055 !MESSAGE  .__ .__ _____ | | | | ____ ___.__. \__ \ | | | | / _ < | | / __ \| |_| |_( <_> )___ | (____ /____/____/\____// ____| \/ \/ !ENTRY com.appcelerator.titanium.core 4 0 2014-01-03 18:00:26.915 !MESSAGE (Build 3.2.0.201312191455) [ERROR] Resource Not Found !STACK 1 org.eclipse.core.runtime.CoreException: Resource Not Found com.appcelerator.titanium360.internal.core.Titanium360Manager.handleResponse(Titanium360Manager.java:547) com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:468) com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getAppData(ThreeSixtyProject.java:430) com.appcelerator.titanium360.internal.core.ThreeSixtyProject.is360(ThreeSixtyProject.java:599) com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.getState(Titanium360TiappContributor.java:423) com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.createControls(Titanium360TiappContributor.java:392) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection.createControls(TiAppCloudSection.java:68) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.initialize(AbstractTiAppSection.java:71) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.(AbstractTiAppSection.java:55) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection.(TiAppCloudSection.java:47) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppFormPage.createFormContent(TiAppFormPage.java:123) org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:471) org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1083) org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:603) org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:362) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:142) org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:96) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:323) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:606) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857) org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119) org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333) org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254) org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53) org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685) org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:90) org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41) org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) org.eclipse.swt.widgets.Display.syncExec(Display.java:4688) org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205) org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38) org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80) org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58) org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:576) org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:543) org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:610) org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1031) org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3112) org.eclipse.ui.internal.WorkbenchPage.access$21(WorkbenchPage.java:3034) org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:3016) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3012) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2976) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2967) org.eclipse.ui.ide.IDE.openEditor(IDE.java:534) org.eclipse.ui.ide.IDE.openEditor(IDE.java:493) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.openIndexFile(BasicNewTitaniumProjectWizard.java:140) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectWizard.openIndexFile(NewMobileProjectWizard.java:221) com.aptana.projects.wizards.AbstractNewProjectWizard.createAndRefreshProject(AbstractNewProjectWizard.java:432) com.aptana.projects.wizards.AbstractNewProjectWizard.performFinish(AbstractNewProjectWizard.java:356) com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.performFinish(BasicNewTitaniumProjectWizard.java:237) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectWizard.performFinish(NewMobileProjectWizard.java:127) org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135) org.eclipse.jface.action.Action.runWithEvent(Action.java:499) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:50) com.appcelerator.titanium.ui.TitaniumUIPlugin$6.runInUIThread(TitaniumUIPlugin.java:425) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:606) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) !SUBENTRY 1 com.appcelerator.titanium.360.core 4 404 2014-01...",3,val +TISTUD-5984,Studio: Debug perspective went blank with no views when switching to it,"Allen saw an issue when switching between Studio and Debug perspectives where the debug perspective would go completely blank with no views, and in one instance Studio beachballed, although running jstack showed no blocking thread. The Studio log contains the following repeated exceptions: {code} !ENTRY org.eclipse.ui 4 0 2014-01-06 14:23:20.056 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Widget.error(Widget.java:783) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573) at org.eclipse.swt.widgets.Control.getBounds(Control.java:1606) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppDeployTargetsSection$5.getDecorationRectangle(TiAppDeployTargetsSection.java:536) at org.eclipse.jface.fieldassist.ControlDecoration$5.paintControl(ControlDecoration.java:626) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:230) 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.Control.drawWidget(Control.java:1244) at org.eclipse.swt.widgets.Widget.drawRect(Widget.java:749) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5534) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4918) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5296) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3645) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code} ",5,val +TISTUD-5986,Remove the blackberry device settings from preferences page,"Steps to reproduce : 1) Configure the BlackBerry device settings such as Device IP, password and debug token in the preferences. 2) Launch an app on BlackBerry device - It prompts a dialog with the configured BlackBerry device settings and they are automatically saved to the launch configuration. 3) Change the password on the device, or get a new device with a different password - then it is more likely that user will update the preferences with the new device password. 4) Run the same app on BlackBerry device assuming that the new password is updated in the preferences. The launch will fail with authentication problem as launch configuration still references to the old password, though the new password is updated in the preference. In order to fix this problem and to avoid confusion with passwords stored in multiple locations, we should not have the settings saved in the launch configuration. Every time an app is launched on BlackBerry device, we need to get the updated device settings from the preference.",5,val +TISTUD-5987,ConcurrentModificationException while installing Node and npm ,"This is an intermittent issue that happened on a clean machine, while trying to install SDK, NodeJS, npm packages and modules. After the Studio is restarted, the exception does not happen any more and the installation of NodeJS and npm packages happened without any issues. java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.remove(LinkedHashMap.java:364) at com.appcelerator.titanium.update.core.TitaniumSDKUpdater.fireUpdateCompletedEvent(TitaniumSDKUpdater.java:795) at com.appcelerator.titanium.update.core.TitaniumSDKUpdater.access$1(TitaniumSDKUpdater.java:787) at com.appcelerator.titanium.update.core.TitaniumSDKUpdater$5.done(TitaniumSDKUpdater.java:875) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)",3,val +TISTUD-5989,Intellisense Auto Code Completion is not working,"h3. Steps to Reproduce I updated my Titanium Studio to 3.2.0 and since that day the Intellisense hasn't been working. I just spend another 3 hours trying to find a solution, but now I'm giving up. I've tried to remove TS and reinstall it, but everytime I open it and start to write code the auto completion of TS SDK is not showing any API after the .UI API. So if I type T, then I can see option for API's such as Ti. Titanium. , And If I use Ti. then I can see all API related to Ti, but they are grey and say 'No description available'. If I select 'Ti.UI'. then I can't se any API for creating new object. such as createView, createImageView and so on. h3. Actual Result No Intellisense Auto Code Completion h3. Expected Result Intellisense Auto Code Completion",5,val +TISTUD-5990,Studio: TiApp Editor - setting platform to true in tiapp.xml won't show this platform in Deployment Targets in Overview,"h5. To reproduce 1. Create a mobile app project only with android platform. 2. Open Tiapp.xml and set {code} true {code} 3.Switch immediately to TiApp Editor (Overview) and verify whether iPhone target has been newly set or not. h5. Actual result The platform check-box accepts the newly set device platform for fraction of second. Immediately the target selection is gone. However iOS will be shown in platform shortcuts in the Global toolbar. Please, refer to the screenshot.",5,val +TISTUD-5991,Configure Android SDK - Android platform is not configured after fresh CLI install,"h5. To reproduce: 1. First uninstall 'titanium' and 'alloy' NPM packages. 2. Restart Studio and it will prompt to install both the NPM packages. 3. After installation try to create a new mobile app without restarting Studio h5. Actual Result: Platform ""Android"" is not checked on project creation, although Android platform is configured in Studio Preferences. Restart Studio and this problem is solved.",5,val +TISTUD-5997,Studio freezes when trying to log back into Studio after proxy server is set ,"h5. Steps to reproduce 1. Set the HTTP proxy through Studio Preferences, Connect: 50.17.15.139 Port: 8080 Username: qetester Password: lynx64-fixer 2. logout from Studio and try to log back in. h5. Actual Result: Studio freezes after prompting a workspace setup before login screen.",5,val +TISTUD-5999,Unable to install development target if you cancel the license for Android.,"h5.Description If you have no development targets installed and decide to install them from the tiapp.xml you should get the Platform Configuration wizard. If you check Android to install, but decline the license, then the ""configure"" button will change to ""hide"" and you will be unable to install any platform from that point on, unless you close the wizard and start again. h5.Steps To Reproduce 1. Create a project without any development platforms installed. 2. Open the configuration wizard by clicking install with Android checked. 3. Click configure, and decline the Android license. h5.Actual Result ""Configure"" changes to ""Hide"" h5.Expected Result You should be brought back to the Platform Configuration screen, ""Configure"" should still be shown next to ""Cancel"".",3,val +TISTUD-6007,Studio fails to validate Android SDK after a new path is configured in preferences,"h3. Steps to Reproduce Window > Preferance > Platform > Android By providing SDK path it's not configuring. Installed Android SDK 4.4,4.3,4.2,4.0 h3. Actual Result It must be configured after providng path h3. Expected Result It must be configured after providng path",5,val +TISTUD-6006,Android: Titanium requires Android platform 5.0,h5.Description Titanium Studio asks for Android platform 5.0 to be installed (Android version 2.0) and will not work until it is installed. h5.Steps To Reproduce 1. Rename your Android SDK folder if you have one installed. 2. Open Titanium Studio. 3. Check the Android configuration on the dashboard screen. h5.Expected Result Titanium shouldn't require a minimum Android SDK h5.Actual Result Titanium requires Android SDK 5.0,5,val +TISTUD-6009,Breakpoints are not hit for the application files in /Resources/ios directory ,"h3. Problem *Steps:* 1) Create a new project with the test case below 2) Set a breakpoint in Titanium Studio on line 2 of /Resources/ios/test.js 3) Launch the project in debug on iOS simulator *Actual result:* The popup appears and the execution does not stop at breakpoint. *Expected result:* The execution should stop at breakpoint. h3. Test Case {code:title=Resources/ios/test.js} module.exports = function () { alert(""iOS""); }; {code} {code:title=Resources/app.js} var test = require(""test""); test(); {code}",5,val +TISTUD-6010,Installing android SDK through studio installs the SDK but gives error at the end ,"NOTE: I could reproduce on windows 8.1, windows 7 & MAC OSX 10.8.5 h5.Description. 1. Install android SDK from the studio preferences. 2. Let the installation progress complete. h5.Actual Results: 1. We get an error at the end of the installation process. (refer attached screenshot) NOTE: 1. Even though we get an error the android SDK installs fine. 2. We have to refresh the dashboard page to see the successful install status of the android SDK. h5.Expected Results: 1. We should not see any error after the android SDK installation is over. ",5,val +TISTUD-6012,Ubuntu: Android configuration wizard missing Android versions,"h5.Description Android configuration wizard only shows 4.2.2 as well as spelling ""location"" wrong. h5.Steps To Reproduce 1. Open Studio 2. Configure the Android SDK from Studio dashboard h5.Expected Result All Android versions to be shown and able to download h5.Actual Result Can only download Android version 4.4.2",5,val +TISTUD-6018,Object property content assist missing inside object declaration,"h3. Steps to Reproduce This should be a subtask to : https://jira.appcelerator.org/browse/TISTUD-5989 After Installing the current Beta version of TS (Titanium Studio, build: 3.2.2.201401101920) I was able to see the fix for Auto Code Completion, but it doesn't work 100% :) It is tru that you can now type Ti.UI. and get the next LVL of API's but after creating a new object, the Auto Code completion stops working inside the object. So You cant see what properties the object have. Screen 2: {code} var foo = Ti.UI.createView({ // Does not show options }); {code} Screen 3: {code} var foo = Ti.UI.createView(); foo. // does show options. {code} h3. Actual Result No Auto Code Completion h3. Expected Result Auto Code Completion ",5,val +TISTUD-6016,Android: Default emulator is not auto created on windows,"h5.Description: 1. Install the android SDK manually or from studio. 2. Go to run android emulators & check if you se any emulators. 3. Also, open AVD manager & check if studio has auto created the default emulator. h5.Actual Result: 1. We do not see any default emulator/avd created by studio. h5.Expected Result: 1. We should see at least one default emulator/avd created by studio.",5,val +TISTUD-6027,"Invalid ""--ios-version"" value ""7.0""","I just updated TitaniumStudio to 3.2.0.GA and followed the instructions to modify tiapp.xml with 3.2.0.GA. However, when building and deploying my application, I encounter the error: [ERROR] : Invalid ""--ios-version"" value ""7.0"" 7.0.3 Accepted values: 7.0.3 For help, run: titanium help build [ERROR] : Invalid ""--sim-version"" value ""7.0"" I can build and deploy the application fine using the CLI (`titanium build --platform ios --ios-version 7.0.3`), but I cannot use the studio because it errors. Thanks!",5,val +TISTUD-6029,Automatically set the active SDK for CLI to the latest stable version after update,"Currently when Studio updates SDK to the latest stable version, running ""ti sdk"" from command line still shows the previous SDK as selected. This could cause issues since we don't pass in ""--sdk "" for all the commands, and when it's not, CLI will use the one set as active and could return inaccurate information. So we should call ""ti sdk select "" after update. For custom SDK installed from a URL, we should not update the selected SDK since it may not be stable and fully tested. ",3,val +TISTUD-6031,Windows: SplashScreen links lead to incorrect URL,"h5.Description The SplashScreen on Windows shows 3 links. 'Learn More', 'Forgot Password' and 'Proxy Setup' 'Learn More' and 'Forgot Password' will link to the users default search engine and search 'DelegateExecute'. Users cannot use the Forgot Password button as it links to the wrong address. h5.Steps To Reproduce 1. Open Appcelerator Studio 2. Click the links on the SplashScreen h5.Expected Result Links lead to the correct web addresses h5.Actual Result Links lead to default search engine and searches 'DelegateExecute'",5,val +TISTUD-6037,"After SDK update fails, cannot cancel the process","After encountering an error during the SDK configuration process (screenshot4.png) I was unable to cancel the studio process ""Installing/Updating a Mobile SDK"" (screenshot1.png). Even after waiting 5 minutes it did not cancel and needed a Studio restart to resolve. I spoke to [~mxia] about the issue and the reason you need to cancel the studio process is because after the update error in the SDK tool occurs, the only option you have is to ""hide"". Previously that button would have been ""configure"". Attached the studio and diagnostic logs. Let me know if I need to clarify. {code} !ENTRY com.appcelerator.titanium.update.core 4 2 2014-01-15 14:30:51.435 !MESSAGE Problems occurred when invoking code from plug-in: ""com.appcelerator.titanium.update.core"". !STACK 0 java.util.ConcurrentModificationException java.util.LinkedHashMap$LinkedHashIterator.remove(LinkedHashMap.java:364) com.appcelerator.titanium.update.core.TitaniumSDKUpdater.fireUpdateCompletedEvent(TitaniumSDKUpdater.java:795) com.appcelerator.titanium.update.core.TitaniumSDKUpdater.access$1(TitaniumSDKUpdater.java:787) com.appcelerator.titanium.update.core.TitaniumSDKUpdater$5.done(TitaniumSDKUpdater.java:875) org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) !ENTRY org.eclipse.ui 4 0 2014-01-15 15:07:34.376 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException org.eclipse.jface.fieldassist.ControlDecoration.addControlListeners(ControlDecoration.java:602) org.eclipse.jface.fieldassist.ControlDecoration.(ControlDecoration.java:476) org.eclipse.jface.fieldassist.ControlDecoration.(ControlDecoration.java:428) com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite.setError(BasePlatformConfigurationComposite.java:949) com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite.validate(BasePlatformConfigurationComposite.java:924) com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite$1.widgetSelected(BasePlatformConfigurationComposite.java:228) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:50) com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:79) com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationProcessor$1.run(MobileSDKConfigurationProcessor.java:126) {code}",5,val +TISTUD-6038,"Android: Keystore - When creating a new Android keystore, there should be a drop down list to select the different signature algorithm","*Details:* Depending on which Java version is being used by the machine, there should be a drop down list as to which signature algorithm should be used when creating an Android keystore. For instance, Java 1.6.X only ships with SHA1withRSA, so there should be a signature drop down list that has only SHA1withRSA selected. Java 1.7.X ships both SHA1withRSA and SHA256withRSA, so there should be a signature drop down list for both signatures. By having this option when creating an Android keystore, a user can: 1. Package their app to a non-KitKat (< 4.4) device using only the SHA1withRSA signature 2. Package their app to a KitKat device with either SHA1withRSA *or* SHA256withRSA. ",5,val +TISTUD-6077,Remove the requirement of Android 2.3.3 when running MobileWeb app on simulator,"The MobileWeb app fails to run on (Android) simulator, if the Android SDK 2.3.3 is not installed on the machine. Currently when Studio run app on simulator, it still runs using python script 'builder.py' command and that enforces to have Android SDK 2.3.3 installed.",5,val +TISTUD-6076,Old version liveview path in paths.hooks can cause failure in running mobile apps,"Steps to reproduce : # Run a mobile app using liveview using 3.2.0 of Studio, SDK and CLI. # Update CLI, SDK and Studio to RC 3.2.1 # Run a mobile app without liveview The paths.hooks in 'titanium config' still references to old version of the liveview (pre-3.2.1.). Since there are breaking changes of CLI in handling hooks, the old version of liveview path can lead to failure of CLI to run mobile apps on simulator or device.",3,val +TISTUD-6084,Studio: Can't tell keystores apart when path is reasonably long,"When you have multiple keystores, and they are all a similar path (like, say, a common ""dev"" folder inside a user directory), you cannot easily tell them apart. See screenshot. Expected: You should see more of the path, or perhaps just the keystore file name Workaround: Select each keystore in your list, and then move the cursor to the end of the string to see which keystore is which. Labor intensive if you work on more than a couple apps.",5,val +TISTUD-6086,"When behind a proxy, Appcelerator Studio would login in offline mode on restart","Workaround is to logout, restart and enter proxy settings/login again. If user enters in proxy settings and logs in to splash screen that will work. But when we try to log them in automatically in the background on restart, it will report being offline and the proxy settings don't get applied properly. On the failed login restart we see the following in the logs: {code} !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.141 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.141 !MESSAGE System property http.proxyHost is not set but should be webproxy.wlb2.nam.nsroot.net. !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.150 !MESSAGE System property http.proxyPort is not set but should be 8080. !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.151 !MESSAGE System property https.proxyPort is not set but should be 0. !ENTRY org.eclipse.core.net 1 0 2014-01-22 17:00:17.153 !MESSAGE System property https.proxyPort is not set but should be 0. {code} Which shows that preferences contain valid values, but system properties do not.",8,val +TISTUD-6094,Studio : Cannot switch provision profiles,"I am on Titanium Studio, build: 3.2.0.201312191547. I have several run profiles setup. However, it does not seem like I can switch provision profiles and have that new provision profiles save to the run configuration. I read a ticket on the Q&A today where somebody posted the same question yesterday. It seems like a possible bug. ",5,val +TISTUD-6102,Links in Node.ACS release notes displayed in Studio update dialog 404,Steps: 1. Remove your Node.ACS install from your system 2. Open Studio and check for Studio updates 3. Click on any link in the Node.ACS change log Results The links lead to wrong locations ,5,val +TISTUD-6101,Widget-is-disposed exception in the log when installing Android via platform config wizard,Saw the exception below after performing following steps: 1. Clear Android SDK from Studio preference and Titanium CLI; 2. Open Dashboard and click on the link in Get Started > Configure Native SDKs > Android SDK section to open the platform wizard; 3. Specify a directory and install Android SDK; 4. Click Hide to close the wizard; 5. Click Run in Background to close the progress bar; 6. Wait until the job finishes. {code} !ENTRY org.eclipse.ui 4 0 2014-01-28 13:31:57.222 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) org.eclipse.swt.SWT.error(SWT.java:4397) org.eclipse.swt.SWT.error(SWT.java:4312) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: org.eclipse.swt.SWTException: Widget is disposed org.eclipse.swt.SWT.error(SWT.java:4397) org.eclipse.swt.SWT.error(SWT.java:4312) org.eclipse.swt.SWT.error(SWT.java:4283) org.eclipse.swt.widgets.Widget.error(Widget.java:783) org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573) org.eclipse.swt.widgets.ProgressBar.getSelection(ProgressBar.java:183) org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:139) com.appcelerator.titanium.ui.wizard.ProgressDistributor$5.run(ProgressDistributor.java:118) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 23 more {code},3,val +TISTUD-6109,+F find doesn't highlight the search bar when multiple editor windows are open in side-by-side tabs,"When editing code in Titanium studio 3.2, pressing +F is supposed to open the 'find/replace' dialog and highlight the finding search term. This does not work correctly when multiple editor windows are open side-by-side in a studio instance. ie. 1/ Open multiple source files in studio 2/ Drag one of these windows to the side so that you have split window editing 3/ Press +F to open the find/replace control 4/ Type your search term = the cursor is not correctly focused in the find/replace control and your search term is incorrectly entered into the source code you are editing instead of in the find/replace control This is really, really annoying if you are editing in split windows. Split windows are pretty much the major reason I choose to use studio instead of sublime.",5,val +TISTUD-6105,Navigate the event handlers into the controller code from View,"The View files in Alloy can contain event handlers such as onClick, onFocus events. The functions referenced as the event handlers are 'mostly' defined in the corresponding controller code. Since Studio has knowledge of the controller code, it should allow to navigate the event handler functions to the controller code (similar to the F3 or method definition navigation in JDT Eclipse).",8,val +TISTUD-6106,Navigate the class types to the Style code from View,"The View files in Alloy can contain class types for each UI element. The types referenced in the View are definitely defined in the corresponding Style code. Since Studio has knowledge of the Style code, it should allow to navigate the class type to the Style code (similar to the F3 or method definition navigation in JDT Eclipse).",8,val +TISTUD-6108,"Add a debug scope to output the result from ""ti info -t "" calls","Sometimes in addition to know the exact ""ti info"" commands Studio calls, we also want to know the output at the time it is executed, since the output may change when running the same command later on. This ticket is to introduce a new scope to show the output in Studio log when enabled. ",3,val +TISTUD-6113,Appcelerator Studio: JS library causes Studio to hang during index,"h6.Issue description Including the attached file (source here -> https://github.com/mbostock/d3/blob/master/d3.min.js) in an Appcelerator Studio project, causes the ""building workspace, indexing"" task to hang indefinitely. The task cannot be cancelled and requires studio to be forcibly shut down (top menu bar gets stuck and no possible action can be done) E.G. BuildingWorkspace_Indexing.jpg h6.Actual behaviour Appcelerator Studio to hang and require a force quit if a specific file is added to a project. h6.Steps to reproduce Attach JS library attached and monitor indexing progress (E.G. BuildingWorkspace_Indexing_IDE.jpg). h6.Additional information Once, library is included the workaround is to store this library in a folder that is marked derived in studio, so it does not index. {quote} (1) In Project Explorer view, click on the drop-down arrow on the upper-right corner and select Customize View...; (2) In the Filters tab, uncheck Titanium Resources Folder and click OK; (3) The ""Resources"" folder should now appear under the alloy project; (4) Right-click on the Resources folder and select Properties; (5) Make the ""Derived"" attribute checked and click OK. {quote}",8,val +TISTUD-6116,Alloy: Show description for the content assist types in View file,"Studio does not show any description (in the tooltip) for the types shown in the content assist in the Alloy View file. Though Studio is able to display description in the tooltip for the types in the controller file, it does not show any tooltip in the View file.",8,val +TISTUD-6122,Prefer HTTP proxy in the proxy setup dialog from splash screen,Right now we prefer the HTTPS proxy. So far all our experience with customers has shown HTTP to be the only proxy we've seen used. Let's make it the default.,3,val +TISTUD-6123,Alloy: add New > Alloy View for creating a new view,"If a user creates a view file, the very next thing would be to create a corresponding style file and controller file. Studio should provide a way those corresponding files through menu items or context menus. So, the corresponding files should be created with the same name of View file, but under styles and controllers folders.",5,val +TISTUD-6124, Alloy: add New > Alloy Style for creating a new style,"Alloy provides a command ""alloy generate style "" to generate a style file. We should surface the capability in Studio with a New > Alloy Style menu. It should prompt user for the style name and run the command.",5,val +TISTUD-6125, Alloy: add hover info for property names in Alloy .tss file,"h5. Improvement description Alloy projects .tss files should also present the hover info like for .js files. When passing the mouse over a .tss style, information should be displayed as a popup like for objects in the .js files.",8,val +TISTUD-6129, Alloy: add hover info for attribute names in Alloy .xml file,"h5. Improvement description Alloy projects .xml files should also present the hover info like for .js files. When passing the mouse over an .xml element, information should be displayed as a popup like for objects in the .js files.",8,val +TISTUD-6137,"Alloy: when creating 'Alloy Model' from the contextual menu, 'properties' adapter option is missing","h5. Problem description As explained here: http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Sync_Adapters_and_Migrations-section-36739597_AlloySyncAdaptersandMigrations-Ready-MadeSyncAdapters when creating a new Alloy Model, also the 'properties' adapter should be supported. Creating it through Studio, only sql and localStorage options are displayed. Not a regression, also present in Studio 3.2.0.GA Running: {code} alloy info adapters {code} from Terminal returns the correct output: {code} { ""properties"": { ""description"": ""Local persistence adapter that uses Ti.App.Properties storage"", ""platforms"": [ ""android"", ""ios"", ""mobileweb"", ""tizen"", ""blackberry"" ] }, ""sql"": { ""description"": ""Local persistence adapter that uses SQLite storage"", ""platforms"": [ ""android"", ""ios"", ""blackberry"" ] }, ""localStorage"": { ""description"": ""Local persistence adapter that uses HTML5 localStorage API"", ""platforms"": [ ""mobileweb"", ""tizen"" ] } } {code} h5. Additional notes localStorage adapter should probably be deprecated in favor of just properties (and sql). See https://jira.appcelerator.org/browse/ALOY-950",5,val +TISTUD-6142,Appcelerator Studio: Implement a method for distribution of FSA that avoids pulling from active development repo,"h5. Description: When changes are made to the FSA in the active development git repo, these changes are immediately available to anyone importing the sample. This does not allow changes to be evaluated prior to release. h5. Steps to reproduce: Please note: it is not recommended you follow these steps. They are provided for completeness 1) Edit the FSA app code and push change to git 2) Open appcelerator studio and import FSA from sample pane 3) Evaluate the area of changed code from step 1 h5. Result: The imported sample contains the code change h5. Expected Result: New versions of FSA are released in a controlled manner",3,val +TISTUD-6144,TSS syntax error when there is an additional comma at the end,"If the TSS file contains an additional comma delimiter at the end of the last attribute, then Studio shows error as ""cannot recover from syntax error"" at the beginning of the TSS file and shows another error at the end ""unexpected end-of-file token"", though Alloy compiler can successfully compile and run the TSS file. Create a simple tss file with contents such as- ""#class"":{ }, ""#attribute"": { }, Studio shows false compilation errors though they might not be the real errors while running the app.",5,val +TISTUD-6148,Add App Explorer to the Window > Show View menu,"App Explorer is no longer shown by default. However, I find it to be the better view than Project Explorer: - you're far less likely to launch the wrong project using App Explorer than Project Explorer - The view is simpler, because you don't see a ton of unrelated files/projects (which is important for developers with many projects) - App Explorer includes a ""search-whole-project"" text field, which is handy My preference is to have App Explorer returned to being the default file tree view. In lieu of that, having it conveniently accessible on the Window > Show View menu will suffice.",2,val +TISTUD-6151,Release Notes: Studio release notes are missing images,"*Details:* If you update to the latest Studio builds, then the release notes are missing some images. *Steps to reproduce:* 1. Make sure to have Studio 3.2.0 2. Update to Studio 3.2.1 on stable stream 3. Check release notes *Actual:* Release notes are missing images (see attachment). *Expected:* Release notes should not have missing images.",3,val +TISTUD-6153,Release Note: Cannot open Jira links in release notes,"*Details:* If you update to the latest Studio builds and try to click on the Jira links in the release notes, Jira links will not open. *We were able to reproduce this on Mac and Ubuntu. Not on Windows.* To workaround this, you can right-click on the link and copy the link. *Steps to reproduce:* 1. Make sure to have Studio 3.2.0 2. Update to Studio 3.2.1 on stable stream 3. Check release notes 4. Click on Jira links *Actual:* Jira links will not open *Expected:* Should be able to launch links in an external browser or internal browser. ",5,val +TISTUD-6155,AppC Studio 3.2.1 not compatable with Java 1.7,"During an enterprise on-boarding a customer had a 100% clean environment, IE no pre-requisites installed. We used the AppceleratorStudio.exe to install the Java that Studio recommended (1.7). Studio would not launch and would throw an error. We restarted the computer and the same result happened. [~pinnamuri] joined the call to help fix the problem. We were able to get studio to launch only after uninstalling Java 1.7 and installing Java 1.6 32-bit.",5,val +TISTUD-6162,Titanium Studio shows psuedoproperty assignments as errors,"The pseudo property assignment operator 'get' as shown here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/get isn't parsed correctly by Studio, so shows up as an error, even though the script is valid. Running the attached script ('node error.js') returns the following: someResult1 someResult2 operatorResult1 as expected, but as you can see in the screen shot, the line 'get operator1' is flagged as an error. This parse error also cascades, causing Studio to have difficulty parsing the next few lines. Attachments: 1. error.tiff <-- a screen shot of error.js in studio showing the red x for parse error 2. error.js a simple script that demonstrates the issue 3. should.js a more complex script that shows the issue (at line 1210) and the parse issues cascading down the script.",8,val +TISTUD-6167,Studio: 3.2.1 always asks to allow for network connect on Mavericks,"h3. Steps to Reproduce Using the most recent update for all components, launch Studio. h3. Actual Result Every time, prompted to allow network connection h3. Expected Result This should occur once and store the result.",8,val +TISTUD-6174,Unable to format any TSS file in Titanium Studio,"When I want to format my TSS file, I've got an error : ""Unable to format. See error log for details"". I see log and I've : !ENTRY com.appcelerator.titanium.editor.tss 4 0 2014-02-13 12:57:32.822 !MESSAGE (Build 3.2.1.201402041146) [ERROR] Formatter error: startOffset > endOffset !STACK 0 java.lang.IllegalArgumentException: Formatter error: startOffset > endOffset .....",3,val +TISTUD-6170,Consolidate push notification and acs api url settings into single property in tiapp.xml,"Apart from guppy and shark, all other environments need these two properties setup in tiapp.xml {code} https://api.dev.comerica.appcelerator.com https://api.dev.comerica.appcelerator.com/v1/ {code} We need to consolidate these in single setting in tiapp.xml and have that stored in dashboard config",5,val +TISTUD-6179,"AppC Studio title bar says ""Titanium Studio Dashboard""","Steps: 1. Open Dashboard in Appc Studio and look at title bar. Results: Title bar text is set to ""Studio - Titanium Studio Dashboard - Appcelerator Studio"". Expected: Not sure, but maybe just ""Appcelerator Studio - Dashboard"". ",3,val +TISTUD-6181,"Studio: Typing ""label1"" at certain pace causes autofill with ""Ti.API.log('info',})""","h5. Description: At certain typing rates, typing ""label1"" results in the text being replaced with ""Ti.API.log('info',})"". Not only is this not ideal, the text throws an error in the editor which is ""Syntax error: Unexpected token ""}"" h5. Steps to reproduce: 1) Open any js file in studio. 2) Type ""label1"" h5. Result: If your typing rate was conducive, the text will be replaced. If not, it will work as expected. h5. Expected Result: ""label1"" Text remains as entered h5. Notes: Typing fast or slow may not produce the issue. Michael mentioned that: This problem happens due to that there is only one proposal for the case of label1 when '1' is typed, and the proposal is a code snippet. To turn the behavior off, there is the option in Preferences > Studio > Content Assist > ""Insert single proposals automatically.""",8,val +TISTUD-6182,Allow to open Run configuration dialog directly with Cmd+Click on launch shortcut,"In Eclipse, we can directly open the run configuration for a shortcut directly with Cmd+Click on that shortcut. It avoids a long effort to open a generic run configurations dialog and search for the specific launch shortcut. After Studio introduced the global launch shortcuts, we loose the capability of directly opening the specific launch configuration.",8,val +TISTUD-6183,Intermittent NPE while opening TiApp editor,"At times when the state of the project or services is corrupted, TiApp fails to open and throws NPE : java.lang.NullPointerException com.appcelerator.titanium360.internal.core.ServiceInstance.getState(ServiceInstance.java:49) com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.create360ServiceList(Titanium360TiappContributor.java:633) com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.createSectionContents(Titanium360TiappContributor.java:538) com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.createControls(Titanium360TiappContributor.java:393) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection.createControls(TiAppCloudSection.java:68) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.initialize(AbstractTiAppSection.java:71) com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.(AbstractTiAppSection.java:55) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppCloudSection.(TiAppCloudSection.java:47) com.appcelerator.titanium.ui.ide.tiappEditor.TiAppFormPage.createFormContent(TiAppFormPage.java:123) org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:471) org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1083) org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:603)",3,val +TISTUD-6187,Allow navigation between Alloy files under a hierarchical structure,"A suggestion from a user in TISTUD-3295: I have one suggestion that can cover one use case that is being missed by this feature. In our app/controller folder, we have a hierarchical structure that organizes our controllers in a logical fashion. For instance, we have the following: app/ app/assets/ app/controllers/ app/controllers/file1.js app/controllers/file2.js app/controllers/file3.js app/controllers/file4.js app/controllers/file5.js app/controllers/templates/another_controller1.js app/controllers/templates/another_controller2.js app/controllers/templates/another_controller3.js app/controllers/templates/another_controller4.js lib/ lib/... ... The same controller structure is mirrored for the styles and the views. Now, when you open a controller, style or view that is not directly sitting in the folders app/controllers/, app/styles/ or app/views/, then you will not be able to use the new simplified navigation to open the other related files. The option will be greyed out. It would be nice to have that use case supported. ",8,val +TISTUD-6190,Alloy debugging does not suspend at expected line numbers with default preferences,"With the default JavaScript debugging preferences ON especially with Suspend of errors and Suspend on debugger keyword, the debugger does not suspend at the breakpoints. They do suspend at random lines, but never stop the breakpoints. If both of these preferences are set to OFF, then the thread suspends and breakpoints are hit as expected.",8,val +TISTUD-6191,"Linux Ti Studio ask to update on every startup, failing each time","After startup, Studio on linux show me a list of updates. I'm forced to install them to close the dialog, type in admin password and then Studio fails saying like Node udpate can be done only on Win/Mac Npm not found Npm not found Npm not found Really annoying.. Regards ",8,val +TISTUD-6198,Studio: Cannot change alias for Android app publication,"Trying to publish an app in the Play market. There must be a bug in the Studio that makes you cannot CHANGE the alias in the alias field on the Run Configurations once it is launch the first time (well, you can change it, but it recovers the first name you wrote the first time because the Apply button is not enabled to save it, see screenshot). In my case I wrote a BAD alias that launched the next error: {code} For help, run: titanium help build [ERROR] Missing required option: --alias {code} To fix it, I deleted the configuration and I created a new one, with the right alias name. Then it worked. But must be fixed to avoid confusions.",3,val +TISTUD-6195,Syntax Highlight and Autocomplete Fail,"While I'm working in a project the syntax hightlight and autocompletion stops working. {code} !ENTRY com.aptana.editor.js.formatter 4 0 2014-02-26 15:23:35.838 !MESSAGE (Build 3.2.1.201402041146) [ERROR] com.aptana.formatter.epl/debug Cannot recover from the syntax error !STACK 0 beaver.Parser$Exception: Cannot recover from the syntax error beaver.Parser.recoverFromError(Parser.java:601) com.aptana.js.core.parsing.JSParser.recoverFromError(JSParser.java:489) beaver.Parser.parse(Parser.java:498) beaver.Parser.parse(Parser.java:439) com.aptana.js.core.parsing.JSParser.parse(JSParser.java:374) com.aptana.js.core.parsing.JSParser.parse(JSParser.java:331) com.aptana.parsing.ParsingEngine.noCacheParse(ParsingEngine.java:424) com.aptana.parsing.ParsingEngine.parse(ParsingEngine.java:229) com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:230) com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:217) com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:200) com.aptana.editor.js.formatter.JSFormatter.format(JSFormatter.java:245) com.aptana.formatter.ScriptFormattingStrategy.doFormat(ScriptFormattingStrategy.java:185) com.aptana.formatter.ScriptFormattingStrategy$1.run(ScriptFormattingStrategy.java:115) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) com.aptana.formatter.ScriptFormattingStrategy.format(ScriptFormattingStrategy.java:111) org.eclipse.jface.text.formatter.MultiPassContentFormatter.formatMaster(MultiPassContentFormatter.java:193) org.eclipse.jface.text.formatter.MultiPassContentFormatter.format(MultiPassContentFormatter.java:142) org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:979) org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1507) org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:128) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:126) org.eclipse.jface.action.Action.runWithEvent(Action.java:499) org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:285) org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:504) org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:555) org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:376) org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:322) org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:84) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.filterEvent(Display.java:1080) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4165) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1503) org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1499) org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:496) org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) org.eclipse.swt.widgets.Display.windowProc(Display.java:5648) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) org.eclipse.swt.widgets.Composite.keyDown(Composite.java:594) org.eclipse.swt.widgets.Display.windowProc(Display.java:5558) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code} Steps to Reproduce: 1. Create a new Mobile Application (Alloy). 2. Create a new Controller. 3. Paste the following code in the controller file. {code} var args = arguments[0] || {}; var requestComments = function(){ var xhr = Ti.Network.createHTTPClient({ onload: function() { Ti.API.info('Comments: '+this.responseText); var comentarios = JSON.parse(this.responseText); for (var idx in comentarios) { var row = Ti.UI.createTableViewRow({ backgroundColor: '#fff', width: Ti.UI.SIZE, height: Ti.UI.SIZE, }); var rowLabel = Ti.UI.createLabel({ text: comentarios[idx].message, font: { fontSize: 10, fontFamily: 'Helvetica Neue', }, color: '#0e0e0e', left: 5, top: 5, }); row.add(rowLabel); $.detailTView.appendRow(row); } var rowMore = Ti.UI.createTableViewRow({ backgroundColor: '#fff', font: { fontSize: 12, }, height: 30, }); var rowMoreTxt = Ti.UI.createLabel({ title: 'Ver Mas', tintColor: '#34aadc', }); $.detailTView.appendRow(rowMore); }, }); xhr.open('POST',Alloy.Globals.serverRequest); xhr.send({ request: 'comments', postId: args.id }); }; function onClickCancel() { $.detailWin.close(); } function sendComment() { alert('Comment Sent.'); } $.detailWin.addEventListener('open', function(){ var secretRow = Ti.UI.createTableViewRow({ width: Ti.UI.SIZE, height: Ti.UI.SIZE, backgroundColor: '#fff', layout: 'vertical', }); var secretText = Ti.UI.createLabel({ text: args.message, top: 10, left: 10, right: 10, font: { fontSize: 12, fontFamily: 'Arial', }, }); var spaceView = Ti.UI.createView({ height: 10, width: Ti.UI.FILL, }); secretRow.add(secretText); secretRow.add(spaceView); secretRow.selectionStyle = Ti.UI.iPhone.TableViewCellSelectionStyle.NONE; $.detailTView.appendRow(secretRow); $.detailTView.appendRow(Ti.UI.createTableViewRow({backgroundColor: '#fff', height: 35, selectionStyle: Ti.UI.iPhone.TableViewCellSelectionStyle.NONE})); $.detailTView.appendRow(Ti.UI.createTableViewRow({height:10, selectionStyle: Ti.UI.iPhone.TableViewCellSelectionStyle.NONE})); requestComments(); }); var backBtn = Ti.UI.createImageView({ width: 14, height: 21, image: 'icon_left_white.png', }); backBtn.addEventListener('click',function(){ $.tabGroupDetail.close(); }); $.detailWin.leftNavButton = backBtn; $.comentario.keyboardToolbar = $.footerComment; /* $.comentario.addEventListener('change', function() { $.autoHeightLabel.text = $.comentario.value; $.comentario.height = $.autoHeightLabel.height; $.footerComment.height = $.autoHeightLabel.height; }); */ {code} Thanks",5,val +TISTUD-6194,The global launch toolbar should show tooltip if the shortcuts are disabled,"If the launch global toolbar is disabled for a valid project, then it should show tooltip with the cause (such as no platforms selected in TiApp or fails to list the emulators/devices for the selected platforms). The tooltip should help to fix the problem with the Titanium project in case if there is a version mismatch or any errors with the project configuration. ",5,val +TISTUD-6196,No option to Publish Android application for Appcelerator Studio on Windows,"When you install the latest version of Appcelerator Studio on Windows with the Android SDK properly installed, there is no option to publish your applications to the Google Play Store. We have done a couple of workshops with customers that are running Studio on Windows and were trying to illustrate the process of publishing android applications. Of course, this option is not available. Let me know if you need more details. I have uploaded the sample project setup for Android and there is no option available. ",5,val +TISTUD-6199,Alloy : Allow to create event handler from View file,"If a user includes event handlers for the a UI element in the View file, there is no way to directly create the event handler in the controller file. Currently, they have to manually switch back to controller file and then create the event handler. It would be easy if the user is able to Cmd/Ctrl + Click the event handler method referenced in the View file to directly create the method in the controller file.",8,val +TISTUD-6200,Alloy: Create a style section for 'id' from the View file,"If a user defines style element such as 'id' for the a UI element in the View file, there is no way to let user define the style element block directly in the style file. Currently, they have to manually switch back to style file and then create the style data block using the Id defined for the UI element. It would be easy for the user for a quick fix kind of mechanism, where they can press something similar to Cmd/Ctrl + 1 on the id value, and then create the style block in the tss file.",8,val +TISTUD-6201,Alloy: Show warning if the event handler referenced in the View file is not defined,"If a user includes event handler for the a UI element in the View file, currently there is no indication that the event handler is a valid method. The user will only get to know about undefined handler while launching the app on device/simulator. Since, we already have the indexed methods from the javascript files of the project, we should be able to figure out the referenced method is valid and then, show a warning, if it not defined.",8,val +TISTUD-6205,Enforce builds fail if code coverage drops,"Currently we only record code coverage on nightly builds for display/info purposes. We should set minimum thresholds which fail the test build (and therefore end up disallowing pushes/syncs to QE/Beta/RC) if we don't meet the value. We should also enforce that the minimums rise every time we raise our coverage level - so that we effectively enforce our code coverage must not get worse over time (and hopefully will only increase, rather than stay flat).",13,val +TISTUD-6209,Navigate the ID types to the Style code from View,"The View files in Alloy can contain ID types for each UI element. The types referenced in the View are probably defined in the corresponding Style file. Since Studio has knowledge of the Style code, it should allow to navigate the ID type to the Style code (similar to the F3 or method definition navigation in JDT Eclipse).",8,val +TISTUD-6213,Dashboard: BlackBerry native SDK is not configured ,"When Studio Installed on a clean machine, Configure Native SDK for BlackBerry fails. h5.To reproduce 1.Studio Dashboard>Get Started>Configure Native SDKs> BlackBerry SDK h5.Actual result Configuration fails (log attached) h5.Work around 1.Download and Install Momentics from the following link: https://developer.blackberry.com/native/downloads/ 2.Close all popups that appear until on the main screen. 3.Help --> Update API Levels... 4.Open the ""Gold"" Tab and install the latest stable SDK",8,val +TISTUD-6350,Profile: iOS - Profile on device hangs with LiveView enabled,"h5. To reproduce 1. Enable Live View in Studio 2. Profile app on device h5.Actual result It does work with iOS Simulator. This issue occurs, profiling on iOS device - Profile on iOS Device window is not dismissed and ""The profiler is waiting for you to launch the app on your device"" after the app launched on the device. h5.Expected result Either the application should run on device successfully and open the profiling perspective, or throw an error saying that LiveView does not work with profiling. Note: Will investigate if it is a regression and update the ticket. ",5,val +TISTUD-6217,Android: Default emulator is not created on windows after android tools update to rev.22.6,"h4. NOTE : This issue will affect a user if he is doing a clean install. The studio will not create a default emulator for him. h5.Description: 1. On windows, delete all available avd from the avd manager. 2. Run appcelerator studio. 3. Select an app & click refresh devices. h5. Actual Results: 1. A default avd does not get created by studio. This issue started after updating the android SDk tools & android sdk build tools to rev.22.6 & 19.0.3 respectively. We tested the same scenario on an windows machine which was not updated & everything worked fine as expected. NOTE: We saw that studio runs the command to create an avd in studio logs ,but somehow it fails I guess. If the same command is run manually it creates the emulator fine. h5. Expected Results: 1. Default avd should get created if none exist.",5,val +TISTUD-6218,Fix the relationship between titanium unit tests and acs/alloy code,"Right now our unit test suite for titanium is messed up in that it relies on installing the titanium feature, which is in the RCP, to then run. This is because titanium-core doesn't contain the alloy or acs plugins. They are broken out to separate features which live underneath the umbrella feature in the RCP repo. So we need to fix that up by doing one of the following: * Remove the ACS/Alloy features and their separate builds, and just include the plugins in our titanium-core feature. * Move the ACS/Alloy features and their associated unit tests out to their own repository. Break out unit test jobs for each.",8,val +TISTUD-6219,Move from Emma code coverage to Jacoco for Ruby unit tests,"We currently still run emma code coverage on our ruby unit tests. We've already moved to Jacoco for the nightly builds, we should do the same for all builds that do code coverage.",3,val +TISTUD-6220,Move from Emma code coverage to Jacoco for PHP unit tests,"We currently still run emma code coverage on our php unit tests. We've already moved to Jacoco for the nightly builds, we should do the same for all builds that do code coverage.",3,val +TISTUD-6224,Install and configure Github PR Builder plugin,,5,val +TISTUD-6225,Set up PR builder job for studio3,,5,val +TISTUD-6226,Set up PR Builder job for titanium-core,,5,val +TISTUD-6227,Set up PR Builder job for appcelerator-core,,5,val +TISTUD-6228,Run unit tests as part of studio3-core PR builder,,8,val +TISTUD-6229,Run unit tests as part of titanium-core PR builder,,5,val +TISTUD-6230,Run unit tests as part of appcelerator-core PR builder,,5,val +TISTUD-6234,Combine the core and unit tests builds for studio3,I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build. Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds).,5,val +TISTUD-6235,Combine the core and unit tests builds for titanium,I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build. Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds).,5,val +TISTUD-6236,Combine the core and unit tests builds for appcelerator,I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build. Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds).,5,val +TISTUD-6237,Error on project creation & Alloy is not an option when creating a new project,"When the customer tries to create a new project, the Alloy option is missing from the template selection area. If they close the window and try again, they will have the option to select Alloy. When trying to create a project, they are greeted with a creation error. We were unable to repro this in house, but the customer can consistently show it on webEx. Steps to reproduce: 1. Open Studio 2. go to File->New->Mobile App Project 3. Witness that there is no option to select Alloy 4. Close the ""Create project"" window 5. Again, go to File->New->Mobile App Project 6. Witness that you can now select Alloy 7. Try to create an Alloy project 8. Witness the creation error in the screenshot Additional Notes: The customer was having trouble enabling services. We discovered that they were trying to log into dashboard with the wrong password and thought Studio may have the wrong password. We logged him out and back in with the ""new"", correct password. He then started getting these problems on project creation.",3,val +TISTUD-6239, Alloy: Create a style section for 'class' from the View file,"If a user defines style element such as 'class' for the a UI element in the View file, there is no way to let user define the style element block directly in the style file. Currently, they have to manually switch back to style file and then create the style data block using the 'class' element defined for the UI element. It would be easy for the user for a quick fix kind of mechanism, where they can press something similar to Cmd/Ctrl + 1 on the class element value, and then create the style block in the tss file.",8,val +TISTUD-6240,Create a Index reader to index all style elements defined in tss file,"Studio has to index all the style element sections defined in the TSS file. Currently Studio has only knowledge about the list of the id/class(es) referenced from the View file. However, it has to parse and store the information of all the id/class sections for each TSS file in order to show any annotations of unused elements. The indexer should differentiate the Id and class elements, and might need to store the style elements correspondingly. ",8,val +TISTUD-6241,Alloy: Create a Styles validator to validate the undefined style elements in View file,"After all the style elements are indexed, then the View file need to validate the missing style elements of 'class' and show any annotations if the class definitions are missing the corresponding style file or in the global file.",8,val +TISTUD-6246,"iOS:Faild to import projects from Studio Samples, if iOS SDK Home is not specified in Studio Preferences ","h5.To reproduce 1. Set Xcode path, using the Terminal {code} sudo xcode-select -switch /Applications/Xcode.app {code} 2. In Finder move Xcode to another location 3. Import Kitchen Sink from Studio Samples h5.Actual result Error, cloning git repo (screenshot) h5. Expected result No error, importing the project ",5,val +TISTUD-6250,Studio 3.2.3 and 3.3.0 does not show new iOS simulators in Run configurations,"h3. Issue While debugging into the new issues reported by the user (TISTUD-5614), I have run into an issue with Studio, that it incorrectly use the obsolete cache to detect iOS simulators and SDKs. Due to this, Studio always displays simulator version such as 7.0.3, even though 7.1 or 6.1 are available on the machine. h3. Workaround To workaround the issue, delete the files under /.metadata/.plugins/com.appcelerator.titanium.core/* and then, restart Studio. It should refresh the iOS info and show all the valid simulators.",5,val +TISTUD-6251,Studio should use the default selected SDK for ti info command,"Currently for finding out the iOS and Android emulators/devices info, Studio uses the latest SDK for the ti info command. If the user has SDKs installed from master branch (such as 3.3.X), then the ti info commands for iOS/Android didn't return correct results while querying the platforms info, with 3.3.X SDK. Though user has different GA SDKs installed including the ones from master branch, the ti info command should always pick up the SDK that is configured as the default one in the ti config. Since most of them select the default SDK as the GA version, Studio should not pass in any SDK flag which will force CLI to use the default selected SDK for ti info command.",3,val +TISTUD-6258,Studio: Theme resets with every update,h3. Steps to Reproduce update studio h3. Actual Result theme changes back to white background h3. Expected Result remember my theme,5,val +TISTUD-6253,Investigate and setup local http transparent proxy using squid,"In order to verify whether the proxy settings are reflected in the preferences once they are set, we need to configure a proxy server that always works and reliable for our unit tests. As Chris suggested, one of the approach would be to use the squid to setup a local HTTP transparent proxy that we rely, instead of relying on a dynamic list of public servers. We need to investigate and setup local proxy server on the unit tests machine.",8,val +TISTUD-6256,Android: ti.info not showing Android Ndk version ,"Missing Android Ndk version while setting the path from Studio. Steps to Reproduce: 1. Download Android ndk and Open Appcelerator Studio. 2. Open Prefrences>Studio>Platform>Android. Set the android ndk path and apply and save. 3. Now launch terminal and run ""ti.info"" Actual Result: Android Ndk version is missing.However it shows the Android Ndk Path Expected Result: Should get correct Android Ndk version. But if we set the android ndk path from Terminal using command ti.config android.ndkPath pathtoandroidndk After this run ""ti.info"" We get the Ndk Version ",5,val +TISTUD-6261,Fails to launch iOS app after XCode update,"h3. Issue After upgrading the XCode SDK to 7.1 from 7.0.3, and if the User launches the titanium app on iOS simulator, then the launch fails with the error 'invalid SDK version 7.0.3'. While launch the app, Studio does not validate SDK version stored in the launch configuration and it launches the app with the same old SDK version that is persisted in the launch configuration. h3. Workaround To workaround the issue, open the launch configuration and set the SDK to 7.1 and then relaunch it.",5,val +TISTUD-6263,Investigate removing use of swt-webkit,"A very long time ago, Max hooked up Chromium to work as an SWT browser for us. I think the original reasons were that we wanted a bleeding edge browser embedded in Studio, and we had issues with videos in the Dashboard. Since that time, its been many years and now Eclipse even supports WEBKIT based browsers on some systems in the same way as Mozilla browsers. We should investigate if we can ""get away"" with removing our use of it. It adds roughly 80Mb in install size on my Mac. And I'm not sure we even really need it anymore.",8,val +TISTUD-6265,NPM executable should not need to coexist with node executable folder on Mac for recognizing npm,"On Mac, the npm executable should co-exist in the node executable folder for Studio to find npm executable. If they are installed through any other means that would cause node and npm executables under different directories, then Studio fails to recognize npm executable, though it is accessible on terminal.",5,val +TISTUD-6279,iOS Developer Certificate encoding issue,"h2. Description of the problem When the Developer Certificate name contains an international character (e.g. ä), Studio is unable to build. The error shown says that the ""--developer-name"" is invalid, and the character is replaced by ??",5,val +TISTUD-6270,"Create feature, builder, and Jenkins job for publishing AirWatch integration plugin(s)","Add the corresponding feature, builder, and Jenkins job to publish AirWatch integration plugin(s) to an external update site so it could be installed on top of Studio 3.2.0. The feature will eventually be folded into Appcelerator Studio.",5,val +TISTUD-6271,Implement publishing to Airwatch App Store using their API,Using the API in https://wiki.appcelerator.org/display/tools/AirWatch+Integration to publish the package to Airwatch app store. The information needed could be retrieved from the project itself and the publishing wizard.,8,val +TISTUD-6272,Add a publish provider for publishing to AirWatch App Store,Using the API in https://wiki.appcelerator.org/display/tools/AirWatch+Integration to add a publish provider for Airwatch. Could reference our Nukona and Testflight implementations.,5,val +TISTUD-6273,Make AirWatch plugins installable only onto Appcelerator Studio,"AirWatch integration will be eventually rolled into Appcelerator Studio 3.3.0. In the mean time, it should be installable only to Appcelerator Studio, not Titanium Studio.",2,val +TISTUD-6275,NPE during startup while initializing iOS config wizard,java.lang.NullPointerException com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.(IOSSDKConfigurer.java:45) com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.(IOSSDKConfigurer.java:39) com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer.doCreateComposite(IOSSDKConfigurer.java:141) com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.createConfigurationContents(BaseMobilePlatformConfigurer.java:122) com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createConfigurationContents(PlatformsListConfigurationPage.java:181) com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createControl(PlatformsListConfigurationPage.java:155),3,val +TISTUD-6276,Alloy: Debug on Simulator fails to hit break point,"Debug breakpoint is never reached when using the latest TiStudio. h3.Steps to reproduce * Create a default Alloy using lastest TiSDK (3.2.3.v20140327115429) with all services enabled. * Place a breakpoint inside index.js doclick() function. * Run the app in Debug mode. * Click on ""Hello World"" h3.Expected Result * BreakPoint should be hit and no alert should be shown. h3. Actual Result * Alert is shown without hitting the breakpoint. h3.This is a regression : h3.Does not happen with Appc Studio :: 3.2.1.201402061120",5,val +TISTUD-6277,Add marker resolution/command for generating skeleton style files for Alloy,"While working on quick fixes for generating id/class rulesets in TSS for unused classes/ids specified int he views, Tim mentioned that alloy has a command to do that in bulk: http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Tasks_with_the_CLI-section-37536785_AlloyTaskswiththeCLI-GeneratingaStyle We should hook up a command/marker resolution/quick fix (whatever makes most sense) to give that as an option to resolve these in batch for a user.",8,val +TISTUD-6278,Creation of a new project fails with not enough info if there is a number as first character of the name,"h5. Problem description Creation of a new project fails with unsufficient informations to the user if there is a number as first character of the project name h5. Steps to reproduce 1. Create a new project in Studio. As project name use a number as first character (ex. 123test). Result: project fails to create with not enough information for the user. See screenshot. 2. Create a new project using CLI.As project name use a number as first character (ex. 123test). Result: CLI is not allowing the user to use a project name with a number of first character, as expected. {code} [ERROR] The first character of the project name must be a letter. {code}",3,val +TISTUD-6280,"Studio not able to package after the keystore file, alias and password are entered in wizard","h3. Issue When customer is trying to package the app trough Studio and after including the keystore file, password and alias they receive an error in console regarding and N reference not being recognized as a command. During a webex call we try using different SDK throwing the same error, when building from CLI the package build process runs without any problems. h3. Console Log {code} 'N' is not recognized as an internal or external command {code} h3. Attached Files We are including the Studio log and the Studio Diagnostics ",5,val +TISTUD-6281,Set up Windows AWS build node tied to studio-jenkins.appcelerator.org,We need to set up a build node on a Windows AWS box in the new infrastructure to transition the installer builds over to the new setup.,8,val +TISTUD-6282,Fix documentation shown for Javascript properties in content assist,,3,val +TISTUD-6283,Some properties aren't getting flagged as deprecated properly,"Look at parent screenshot #1, 'contentURL' property is not flagged as deprecated, but should be.",5,val +TISTUD-6284,Deprecated properties not being detected when used in dictionary/object passed to create* functions,,8,val +TISTUD-6290,Fix the download button on the new aptana.github.io download page,"The download button on the new setup is busted. It probably does some form submission to a server to get the download URL, when we should be able to bake that logic into client-side Javascript to get the correct URLs.",5,val +TISTUD-6291,Windows: Studio installer does not recognize the installed JDK,"Even though a JDK version is already installed on the Windows machine (could it be 64-bit or IBM Java or Java 8), at times, Studio doesn't recognize the existing Java installation and tries to install it again. Since we are currently looking at the registry for finding Java installation path, if Java is not installed through standard means or a different variant of Java is installed (such as IBM Java, or a different arch), there is a chance that the registry is not updated with the expected values. In that case, Studio will fail to recognize the installed Java version. We need to fall back looking to PATH env variable for java/javac executable (as we are more keen to have JDK installation) if the registry lookup fail to return a valid Java executable.",8,val +TISTUD-6292,Create POC replacement installer using Advanced Installer,,8,val +TISTUD-6293,The controller/style file is not opened automatically after applying quick fix,"After the quick fix is applied to create a event listener, the corresponding Controller file should be opened and set the cursor in the new created event method. Similarly, the styles file should be opened after applying quick fix to create style ruleset for id/class. After recent refactoring changes, the files are not opened and the new methods are not immediately accessible to the user.",3,val +TISTUD-6294,The problem markers in editor should disappear after applying quick fix,"After the quick fix is applied either through quick fix context menu or Problems view, the problem markers disappear in the Problems view, but the marker annotations in the editor does not disappear. Currently we need to do a quick edit in the View file for the reconciler to be kicked back and only then the problem annotations disappear in the editor. After the quick fix is applied, either we need to get hold of the editor problem annotations and remove them, or trigger the reconciler on View file.",5,val +TISTUD-6295,Improve the context menu UI of Alloy View quick fix proposals,"The quick fix proposals context menu is a simple and pale option available in the context menu. There is no padding to the beginning of the quick fix proposals and also, it might look better if an icon is added to the proposal.",5,val +TISTUD-6296,Apply multiple quick fixes together from Problems view,"If there are multiple quick fixes available for the same category (such as creating style id ruleset) for a bunch of UI elements, then the user should be able to select all of the similar problems and apply quick fix by grouping them together.",5,val +TISTUD-6297,TSS file does not recognize a selector if it is not trimmed,"If there is a space between the selector (id/class) and colon (""#container' : {...}), then the TSS file does not recognize it as a selector and incorrectly considers it as a String constant. It has trim the space between the selector id and colon and always shows the selector syntax color.",3,val +TISTUD-6299,Update CLI calls to old module create/build python scripts,Chris Barber is planning on rewriting the module create scripts to move away from the legacy python to the new titanium CLI. We'll need to update our code to call this new command to generate module projects now.,8,val +TISTUD-6302,Breakpoints Never Hit within Appcelerator Studio,"When using the Appcelerator Studio build 3.2.1 with the 3.2.2 GA SDK, and placing a breakpoint within the code, whenever using Debug mode, breakpoints are never triggered and entered within the studio environment. Prior to upgrading to the Appcelerator Studio platform, we had issues in the past with the Titanium IDE, which were resolved by placing breakpoints in the Resource files. Now, post upgraded to Appcelerator Studio, we can no longer hit any breakpoints within our code.",8,val +TISTUD-6303,Studio freezes momentarily and CPU usage is around 100%,h5.Description: 1. Update your current 3.2.3 studio to the latest 3.2.3 studio i.e 3.2.3.201404031900. 2. Run appcelerator studio. 3. Use it for sometime. h5.Actual Result: 1. Appcelerator studio is sluggish & consumes lot of cpu (more than 100%) & very frustrating to use with lot of freezes & delays. h5.Expected Results: 1. Appcelerator studio should not be sluggish & run smoothly.,8,val +TISTUD-6304,Studio: Preferences - Platforms - iOS: Refresh button does not work,"h5. To reproduce 1. Open Studio> Preferences>Platforms>iOS 2. Change Xcode path, using CLI command {code} xcode-select --print-path sudo xcode-select -switch /path to a different Xcode version, if you happened to have it {code} 3. Click Refresh button in Studio> Preferences h5. Actual result No changes h5. Expected The user should see a new path, which was updated, using CLI. Run the command {code} ti info {code} to make sure the ""new"" Xcode is set as a default. ",5,val +TISTUD-6306,Multiple duplicate platform SDK entities are added,"After the fix for TISTUD-6216, Studio has been repeatedly adding the SDK entities for iOS and Android. In the packaging wizard, choose the 'Select SDK version' and a numerous duplicate entities are shown for both Android and iOS. For Android and iOS, as we are loading the titanium info for every 30 secs, we are constantly adding the entities without resetting them.",5,val +TISTUD-6307,Add diagnostic information to investigate the debugging issues,"There are multiple reports that the breakpoints does not hit while debugging the Alloy apps. Currently, we have very limited information available to quickly investigate the underlying root cause of this problem. We might need to add additional diagnostic information such as - # The list of current breakpoints, before the debug session is initiated. # If the breakpoints are added after the debug session is initiated, then we need to log that info. # As the debugger tries to resolve the original source mappings, we need to log whether we were unable to resolve the original sources.",5,val +TISTUD-6308,MobileWeb: Analytics - wrong deploy type executing the packaged app,"While testing mobile web analytics, I encountered the wrong deploy type in the console output. h5. To reproduce 1. Create the default 2 tab app 2. Change label text (e.g I am a Window2) to test:Ti.App.deployType 3. Package the app for MobileWeb 4. Run it on the device h5. Actual result 4. Label's text is ""development"" Analytics: {code} {""city"":""San Francisco"",""region_code"":""CA"",""country_code"":""US"",""country_name"":""United States"",""postal_code"":"""",""latitude"":37.774898529053,""longitude"":-122.41940307617,""area_code"":415,""continent_code"":""NA"",""ip_address"":""38.110.144.252"",""region_name"":""California"",""id"":""6A04AF7D-6C78-4C89-A9D3-F26CF9CACA0D"",""mid"":""2BA27B22-254B-4AF0-94EC-1364EB50459F"",""rdu"":null,""type"":""ti.start"",""aguid"":""dafd5792-d568-4e72-a809-dddaef152db6"",""event"":""ti.start"",""seq"":1,""ver"":""2"",""deploytype"":""development"",""sid"":""1FEBE79A-921D-46DB-9749-5543EEC2278F"",""ts"":""2014-04-08T17:18:17.028+0000"",""data"":{""tz"":420,""deploytype"":""development"",""os"":""mobileweb"",""osver"":""Linux armv7l"",""version"":""3.2.3"",""platform"":""mobileweb"",""model"":""Mozilla\/5.0 (Linux; Android 4.2.2; en-us; SAMSUNG-SGH-I337 Build\/JDQ39) AppleWebKit\/535.19 (KHTML, like Gecko) Version\/1.0 Chrome\/18.0.1025.308 Mobile Safari\/535.19"",""un"":null,""app_version"":""1.0"",""nettype"":null}} {code} It is a Studio issue, as i ran the CLI command {code} ti build --platform mobileweb --deploy-type production {code} and it shows the correct deploy type in the device's browser. Here is the command from Studio log {code} Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""build"" ""--platform"" ""mobileweb"" ""--sdk"" ""3.2.3.v20140403105720"" ""--build-type"" ""production"" ""--log-level"" ""trace"" ""--project-dir"" ""/Users/oromero/Documents/Appcelerator_Studio_Workspace2/testdeploy"" ""--skip-js-minify"" {code} showing ""--build-type""? instead of --deploy-type h5.Expected 4. Should be production ",5,val +TISTUD-6310,Titanium Studio: Commenting shortcut returns # instead of //,h3. Steps to Reproduce Command + / h3. Actual Result # ... [2014-04-09 00:49:01] An error occurred while building environment variables for the 'editor' context property in the 'Comment Line / Selection' command (/Applications/Titanium Studio/configuration/org.eclipse.osgi/bundles/2838/1/.cp/bundles/source.ruble/commands/toggle_comment.rb): (NameError) cannot load Java class com.aptana.editor.common.AbstractThemeableEditor h3. Expected Result // ,5,val +TISTUD-6309,Appcelerator studio becomes sluggish & consumes a lot of cpu after update to 3.2.3.201404031900,h5.Description: 1. Update your current 3.2.3 studio to the latest 3.2.3 studio i.e 3.2.3.201404031900. 2. Run appcelerator studio. 3. Use it for sometime. h5.Actual Result: 1. Appcelerator studio is sluggish & consumes lot of cpu (more than 100%) & very frustrating to use with lot of freezes & delays. h5.Expected Results: 1. Appcelerator studio should not be sluggish & run smoothly.,8,val +TISTUD-6314,iOS: Packaging - Cannot package for Adhoc or iTunes store,"*Details:* Cannot package for Adhoc or iTunes store. Latest AppcStudio Beta build is passing ""--deploy-type"" ""production"" when packaging for Adhoc or iTunes Store e.g. {code} ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""build"" ""--platform"" ""ios"" ""--sdk"" ""3.2.3.v20140403105720"" ""--deploy-type"" ""production"" ""--log-level"" ""trace"" ""--project-dir"" ""/Users/tester/Documents/Appcelerator_Studio_Workspace/Xcode511"" ""--distribution-name"" ""Michael Asher (WY35J6ST95)"" ""--ios-version"" ""7.1"" ""--keychain"" """" ""--pp-uuid"" ""95B8E578-1273-4D3A-93B4-0607CFE8CFEC"" ""--target"" ""dist-appstore"" {code} However, AppcStudio GA (3.2.1.201402061120) is passing ""--build-type"" ""production"" when packaging for Adhoc or iTunes Store e.g. {code} ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""build"" ""--platform"" ""ios"" ""--sdk"" ""3.2.2.GA"" ""--build-type"" ""production"" ""--log-level"" ""trace"" ""--project-dir"" ""/Users/wluu/Documents/Appcelerator_Studio_Workspace/checkingMonkey"" ""--distribution-name"" ""Michael Asher (WY35J6ST95)"" ""--ios-version"" ""7.1"" ""--keychain"" """" ""--pp-uuid"" ""C2AF8ADC-F3DC-485D-ADAB-CAB2B9B5D2D3"" ""--target"" ""dist-adhoc"" ""--output-dir"" ""/Users/wluu/Desktop"" ""--skip-js-minify"" {code} *Workaround:* From CLI, use ""\-\-build\-type"" ""production"" instead of ""\-\-deploy\-type"" ""production"" *Note:* 1. This is a regression from AppcStudio GA (3.2.1.201402061120) 2. This is not a blocker because of the workaround. *However,* this is a *critical* ticket because the workaround is not intuitive. 3. Using the latest AppcStudio build, you can still package an app for the *Android* store, *however*, AppcStudio is passing ""--deploy-type"" ""production"" as well: {code} ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""build"" ""--platform"" ""android"" ""--sdk"" ""3.2.3.v20140403105720"" ""--deploy-type"" ""production"" ""--log-level"" ""trace"" ""--project-dir"" ""/Users/tester/Documents/Appcelerator_Studio_Workspace/Xcode511"" ""--target"" ""dist-playstore"" ""--android-sdk"" ""/Users/tester/Library/android-sdk-macosx"" ""--output-dir"" ""/Users/tester/Desktop"" ""--api-level"" ""10"" ""--alias"" ""wluu"" ""--keystore"" ""/Users/tester/Desktop/package.keystore"" ""--store-password"" ""**********"" ""--key-password"" ""**********r""​ {code} *Steps to reproduce:* 1. Create a default Classic or Alloy app 2. Package app for Adhoc or iTunes Store *Actual:* The following error appears in the console view: {code} [ERROR] : Invalid ""--deploy-type"" value ""production"" Accepted values: test development For help, run: titanium help build {code} *Expected:* You should be able to package your app for Adhoc or iTunes Store without any workarounds.",5,val +TISTUD-6315,Breakpoints don't work after running profiler,"h3. Description If you set break points in your app then run in debug mode then switch to Performance Profiler and then back to debugging, the break points are all turned off and cannot be turned back on. h3. Reproduction # Create a simple app # Add breakpoints # Run the app in Debug mode and confirm they work # Run the app in Profile mode # Re-run the app in Debug mode Result: Breakpoints are all disabled and cannot be enabled h3. Workaround # Restart Studio",5,val +TISTUD-6316,Auto complete doesn't work on new project and workspace until clean all projects,h3.Description Auto complete does not work in Appcelerator Studio 3.2.1 with a brand new project and a brand new workspace. h3.Reproduction Download the latest version of Studio (3.2.1.201402061120) and install Create a new workspace Create a new project Open the XML or TSS file and try to get Mobile Code Complete suggestions Result: No suggestions or non-titanium suggestions will be made Workaround: Project > Clean > Clean All Projects,8,val +TISTUD-6317, Update the 360 client library to pick up fixes,"We have been operating with an exploded copy of an old version of the client library. We've since made changes to the code and haven't pushed a PR upstream (specifically around proxies and the httpclient code). We need to submit a PR to push that upstream, then update our copy of the client (we also need their fixes that handle non-JSON server responses).",5,val +TISTUD-6323,Auto detect the genymotion executables path in preferences,"CLI 3.3.0 now output the information about Genymotion in the 'ti info -t android' or 'ti info -t genymotion' command. As Studio queries for Android emulators/devices information, we might need to cache the genymotion information and the Android preferences can used the cached data to display the Genymotion executables.",8,val +TISTUD-6324,Load and store new property constant values from JSCA in JS' model for properties,We need to be able to parse out the new property values from the JSCA in our parser that handles the file.,5,val +TISTUD-6326,Add CA proposals for property values in TSS editor,Once the model/index stores the possible constant values for a given property we need to suggest CA proposals for those values when invoked in the right area of a TSS file.,8,val +TISTUD-6330,Replace NSIS Installer with Advanced Installer,,8,val +TISTUD-6331,iOS: Dashboard displays iOS as not installed,"h5.Description When Studio is first opened, the dashboard displays iOS as not installed. Closing and reopening the dashboard then marks iOS as installed and set up. h5.Steps To Reproduce 1. Install the latest version of Studio 2. Install Xcode 3. Open Studio h5.Expected Result Studio should detect Xcode and display it on the dashboard as installed and set up. h5.Actual Result Dashboard does not detect Xcode on the first launch.",8,val +TISTUD-6336,NPE after first launch of Studio,This is a regression. Test Steps: 1. Uninstall Xcode *or* move Xcode to a directory in which the CLI cannot pick up 2. Launch Studio with a new workspace 3. Wait untill Studio loads. Actual Result: NPE occurs. {code} !ENTRY org.eclipse.e4.ui.css.core 4 0 2014-04-16 10:13:06.457 !MESSAGE CSS property 'maximize-visible' has been deprecated: renamed as swt-maximize-visible !ENTRY org.eclipse.e4.ui.css.core 4 0 2014-04-16 10:13:06.458 !MESSAGE CSS property 'minimize-visible' has been deprecated: renamed as swt-minimize-visible !ENTRY org.eclipse.ui 4 4 2014-04-16 10:13:33.613 !MESSAGE An internal error has occurred. !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.defaultSDKPath(IOSSDKConfigurer.java:51) com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.createAdvancedSettingsComposite(IOSSDKConfigurer.java:59) com.appcelerator.titanium.ui.mobile.BasePlatformConfigurationComposite.(BasePlatformConfigurationComposite.java:322) com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.(IOSSDKConfigurer.java:41) com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer$IOSConfigurationComposite.(IOSSDKConfigurer.java:39) com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer.doCreateComposite(IOSSDKConfigurer.java:141) com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.createConfigurationContents(BaseMobilePlatformConfigurer.java:122) com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createConfigurationContents(PlatformsListConfigurationPage.java:181) com.appcelerator.titanium.ui.wizard.PlatformsListConfigurationPage.createControl(PlatformsListConfigurationPage.java:155) org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) org.eclipse.jface.window.Window.create(Window.java:432) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) com.appcelerator.titanium.ui.wizard.PlatformsConfigurationHandlerUtil.openWizard(PlatformsConfigurationHandlerUtil.java:48) com.appcelerator.titanium.ui.TitaniumUIPlugin$6.runInUIThread(TitaniumUIPlugin.java:425) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) 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:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code},3,val +TISTUD-6337, Windows OS: Incorrect default path is set for Titanium SDK in Studio as well as in CLI ,Test Steps: On a clean Windows 8 machine: 1. Install Appcelerator Studio 2. Accept and install all the appcelerator components. 3. Observe the default location for Titanium SDK set in Studio preferences. Actual Result: C:\ProgramData\Titanium is set in the default location for Titanium SDK in Studio preferences. But actual installation (appcelerator modules) happens at the location C:\Users\Global\AppData\Roaming\Titanium Expected Result: Default location for Titanium SDK should be: C:\Users\Global\AppData\Roaming\Titanium Note: CLI also shows the same default SDK location path: C:\ProgramData\Titanium,5,val +TISTUD-6338,Android:Top Project Context shows Android Application Installer option instead of Android Devices when multiple android devices is attached,"When multiple iOS Devices are attached, Project Context menu has option ""iOS Devices"" under which list of devices are shown. But for multiple android devices attached it shows ""Android Application Installer"" option instead of ""Android Devices"" Refer to screenshot attached.",3,val +TISTUD-6343,Android Configuration gives error message on Platform Configuration Wizard,This is a regression. Configure Android SDK through Platform Configuration Wizard. Let the process complete. Actual Result: After the installation process is completed an error message is displayed on Platform Configuration Wizard. Please observe the attached screen shot for the error message.,8,val +TISTUD-6558,"Alloy: Multiple Classes throw ""unused""-warning","When adding multiple classes to an Alloy-Element, the corresponding .tss file throws an ""unused"" warning although it is used. Example: ",3,val +TISTUD-6352,Titanium SDK 3.3.0 results in application configuration Error ,"When Titanium SDK build 3.3.0 installed altogether with 3.2.3 Library/Application Support/Titanium/mobilesdk/osx it results in the configuration error (no description). h5. To reproduce: 1. Using Studio, create the default project and check tiapp.xml Overview h5. Actual result: No description. However, the project can be installed on device and ran. Note: the app should be started manually {code} [TRACE] : ** BUILD SUCCEEDED ** [DEBUG] : Waiting for device logs to sync [INFO] : Installing app on device: iphone 5s [INFO] : App successfully installed on device: iphone 5s [INFO] : Project built successfully in 18s 135ms Please manually launch the application or press CTRL-C to quit {code} h5. To compare tiapp.xml {code} 3.2.3.v20140418101718 not specified {code} {code} 3.3.0.v20140418162516 {code} ",3,val +TISTUD-6358,Remove Tizen from the dashboard,"Although Tizen platform is not indicated as a deployment target, it set to false in tiapp.xml {code} false {code} and the Studio log returns {code} !MESSAGE (Build 3.3.0.201404221437) [ERROR] com.appcelerator.titanium.core/debug/dashboard Unknown SDK tizen {code} Note: The command, ran from studio {code} Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""create"" ""--platforms"" ""android,blackberry,mobileweb,ios"" ""--type"" ""app"" ""--id"" ""kd.f"" ""--sdk"" ""3.3.0.v20140418162516"" ""--workspace-dir"" ""/Users/oromero/Documents/Appcelerator_Workspace3"" ""--name"" ""jdkf"" ""--verbose"" ""--force"" Working directory: {code} ",3,val +TISTUD-6359,Errors using shortcuts (CMD+/ or CMD+delete) in tiapp.xml,"h5. Problem description Using CMD+/ and CMD+delete is not possible when editing tiapp.xml. Reproducible on Appcelerator Studio versions 3.2.1.201402061120 - 3.2.3.201404181520 - 3.3.0.201404221437 h5. Steps to reproduce 1. Open a project and edit tiapp.xml file 2. Press CMD + / on a line Expected result: line is commented out Result: nothing happens and following error is displayed {code} [2014-04-23 14:47:47] An error occurred while processing the invoke block for the command Comment Line / Selection in /Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/source.ruble/commands/toggle_comment.rb: (NoMethodError) undefined method `replace' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `replace' for nil:NilClass Ruble::Editor.[]=(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/77/1/.cp/framework/ruble/editor.rb:202) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:229) #.run(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/123/1/.cp/framework/ruble/ui.rb:249) Ruble::Editor.[]=(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/77/1/.cp/framework/ruble/editor.rb:193) LineComment.add(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/source.ruble/lib/comment.rb:233) #.define_command(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/source.ruble/commands/toggle_comment.rb:56) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/source.ruble/commands/toggle_comment.rb:53) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1603) #.define_command(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/source.ruble/commands/toggle_comment.rb:52) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) {code} 3. Press CMD + delete on the end of a line Expected result: line get all deleted Result: nothing happens and the following error is displayed in console {code} [2014-04-23 14:49:21] An error occurred while processing the invoke block for the command Delete to Beginning of Line in /Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/text.ruble/commands/delete_to_beginning_of_line.rb: (NoMethodError) undefined method `replace' for nil:NilClass org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `replace' for nil:NilClass Ruble::Editor.[]=(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/77/1/.cp/framework/ruble/editor.rb:202) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:229) #.run(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/123/1/.cp/framework/ruble/ui.rb:249) Ruble::Editor.[]=(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/77/1/.cp/framework/ruble/editor.rb:193) #.define_command(/Applications/AppceleratorStudio/Appcelerator_Studio_322GA_32bit/Appcelerator Studio/configuration/org.eclipse.osgi/bundles/122/1/.cp/bundles/text.ruble/commands/delete_to_beginning_of_line.rb:11) org.jruby.RubyProc.call(org/jruby/RubyProc.java:274) org.jruby.RubyProc.call(org/jruby/RubyProc.java:233) {code} 4. Edit another .xml file, for example an index.xml of an Alloy project. Use and on a line of code Result: shortcuts work as expected. ",8,val +TISTUD-6386,"Set up signing for master/release windows installers, fire off builds to get signed","I need to port over the manual signing to happen for master/release windows installer builds (because they're not yet on Advanced Installer). I also need to fire off a build on each, so that the full artifacts are signed properly now that we renewed the certs.",5,val +TISTUD-6389,Android: Remove Android SDK version drop-down list from Package dialog,"The Package for Android App Store dialog has a drop-down list from which you select an Android API version. It is labeled to suggest that this will determine the minimum version of Android on which your app will run. However, that is determined in your tiapp.xml with the minSdkVersion tag. Best practices for Android specify that you should use the latest API tools available, setting compatibility targets with your tiapp.xml. For this reason, as of version 3.2, the CLI uses the newest version of the Android SDK installed. I suggest that the SDK version drop down list be removed from the Package dialog.",5,val +TISTUD-6395,"Copy Advanced installer projects and set up for ""online"" installer","We have an Advanced installer project file for each of Aptana Studio, TitaniumStudio and Appcelerator Studio. We need to copy each of those and then modify them in Advanced Installer to set them up to create a ""thin"" installer that separates the MSI from the EXE. This will also involve modifying the ant build script to add a target to build the thin installer version.",5,val +TISTUD-6396,Create/Modify build job for building online installer,"We have build jobs for the windows installers for the fat installer. We either need to clone those to create a job for building the thin installer, or we need to modify the existing jobs to generate both.",8,val +TISTUD-6397,"Modify the sync job(s) to push online installer artifacts to same location as ""fat"" installer",If the thin installer is generated as part of a separate job (or even with the normal jobs) we may need to modify our sync scripts to copy over the thin installer files (the MSI and EXE).,5,val +TISTUD-6399,"""java.lang.NullPointerException"" starting Studio ","h5. Problem description After starting Appcelerator Studio , a java.lang.NullPointerException is thrown. From the log, it seems to be related to updating Android info. Everything still works as expected after that and the Android emulators are correctly working. Studio log: {code} !ENTRY org.eclipse.core.jobs 4 2 2014-05-01 10:00:09.926 !MESSAGE An internal error occurred during: ""Update Android info"". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.android.internal.core.Emulator.hashCode(Emulator.java:304) java.util.HashMap.put(HashMap.java:372) java.util.HashSet.add(HashSet.java:200) java.util.AbstractCollection.addAll(AbstractCollection.java:305) com.aptana.core.util.CollectionsUtil.union(CollectionsUtil.java:755) com.aptana.core.util.CollectionsUtil.getNonOverlapping(CollectionsUtil.java:343) com.appcelerator.titanium.android.core.AndroidSDKLocator.parseTiInfo(AndroidSDKLocator.java:287) com.appcelerator.titanium.android.core.AndroidSDKLocator.updateTiInfo(AndroidSDKLocator.java:216) com.appcelerator.titanium.android.core.AndroidSDKLocator.access$0(AndroidSDKLocator.java:213) com.appcelerator.titanium.android.core.AndroidSDKLocator$1.run(AndroidSDKLocator.java:233) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code} h5. Environment Appcelerator Studio 3.3.0.201404301307 TiSDK 3.3.0.v20140430151716 Android SDK Tools 22.6.3 Xcode 5.1.1 Android AVDs: . Android 2.3.3 - ARM . Android 2.3.3 - Intel x86 . Android 4.4.2 - Intel x86 ",3,val +TISTUD-6402,Error enabling Appcelerator services during app creation,"When creating the default app, I encountered the error during enabling of appcelerator services. Please, see the attachment. Note: I noticed Environment choice(screenshot), which is not working.",3,val +TISTUD-6403,Alloy: TSS undefined value should be accepted,"h5. New Feature description As per https://jira.appcelerator.org/browse/ALOY-822 , undefined is now accepted as a TSS value. For example, {code} '#index': { backgroundColor: '#fff', modal: undefined } {code} is now valid. Studio shouldn't therefore display the Syntax Error warning when undefined is used as a property for TSS styles.",5,val +TISTUD-6407,Alloy Template creation is unstable using Rubles in Studio,"When creating Alloy templates, i have noticed that this behavior is unstable - projects will be created successfully on some occasions, other time they will not. I'm happy to sit down and have a session on this, but we are seeing a great deal of interest in the collaboration capabilities of our platform around content and this needs to work flawlessly. Below is a link to an installer for a Ruble bundle that will demonstrate what we are trying to do - it could be that how we have implemented it is problematic, but its to spec based on the work i did with Michael Xia and the documentation. https://www.dropbox.com/s/wu3spmrriqsftcb/appcelerator-app-templates.dmg ",8,val +TISTUD-6410,BlackBerry: Missing device IP address option,"When trying to set BB Run configuration in Studio Preferences, there is only option for IP address is Simulator. 3.2.3 Studio has both Simulator and Device. ",5,val +TISTUD-6419,BlackBerry: Cannot build for device from Studio,"I cannot build default project for device, using Studio. Studio log does not have any output, but ""Unhandled event loop exception"" attached in log.txt The buid command works in CLI. I am able to launch BB simulator. h5.To reproduce: 1. Create a default project 2. Set IP address and password for BB device in Studio preferences 3. Build for device h5. Unhandled event loop exception ",3,val +TISTUD-6420,Alloy: warnings relative to Custom TSS styles not being used should not be displayed,"h5. Problem description Studio is displaying warning messages also for CustomTSS conditionals in Styles. See new feature: ALOY-871 h5. Steps to reproduce 1. Create an Alloy project and use the following code: h6. alloy.js {code} Alloy.Globals.someProperty = true; {code} h6. index.xml {code} {code} h6. index.tss {code} ""Window"":{ layout:""vertical"", backgroundColor:'white', top:20 } /* Class selector applied to labels of class=label */ "".label"": { color: 'blue' } /* Component selector applied to all labels, though will be overridden */ ""Label"":{ top:10, text: ""Default label text"", font: { fontSize: '14dp' } } /* Custom TSS overrides component and class selectors if someProperty is true */ ""Label[if=Alloy.Globals.someProperty]"":{ text: ""Custom TSS: Alloy.Globals.someProperty==true"" } {code} 2. Check styles.tss file Result: Studio is displaying a warning next to CustomTSS style (see screenshot too). Expected results: CustomTSS styles queries should probably be ignored or handled differently. ",5,val +TISTUD-6421,Importing general project from existing folder throws Java.lang.NullPointerException,In Titanium Studio and Appcelerator Studio: File > Import... > General > Existing Folder as New Project Throws Java.lang.NullPointerException (screenshot #1). From the same dialog selecting Appcelerator/Titanium > Existing Mobile Project will display an incorrect dialog (screenshot #2) and the user will not be able to complete the import. Close the Import dialog and select Appcelerator/Titanium > Existing Mobile Project again and the correct dialog is displayed (screenshot #3).,3,val +TISTUD-6422,Override Add Node ACS service handler in 360,"We allow adding a node acs service underneath an existing project (definitely Ti Mobile projects, maybe any project nature?). When we do this we have a command handler which eventually call acs new. In 360 we need to override the handler and prompt user for org/env and pass that down to acs new call.",8,val +TISTUD-6423,Prompt user for org/env when using Node.ACS Deploy provider,"A user can also hook up a project to Node.ACS using our ""Deploy provider"" mechanism. When they do so under 360 we need to be able to prompt them for the service name, org and environment (based on if the project is 360 or not we may have some of this data already). Then we need to pass the org and env id down to the underlying acs new call.",5,val +TISTUD-6424,"Constant error ""Uploading debug symbols"" after Packaging for iOS","I had an existing project with Appcelertor services enabled. h5. To reproduce 1. Package iOS iTunes Store 2. Package iOS Adhoc/Enterprise h5. Actual result Application packaged and can be installed and run on devices However, there is the error uploading debug symbols (see attached) It happens each time you package the app.",5,val +TISTUD-6425,"Intermittent: ""Failed to create the part's controls"" in tiapp.xml ","I had caught this intermittent behavior (twice) on creation of a default classic project . The project shows up in the Studio Workspace, however tiapp.xml cannot be seen (see the attachment) Restart Studio and the tiapp.xml can be entered and viewed ",3,val +TISTUD-6426,NPE while opening update wizard during startup,"During the startup of Studio, there is an error while showing the Titanium update wizard. java.lang.NullPointerException java.net.URI$Parser.parse(URI.java:3004) java.net.URI.(URI.java:577) java.net.URI.create(URI.java:839) com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.getReleaseNotesURI(DefaultReleaseNotesProvider.java:77) com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.getReleaseNotes(DefaultReleaseNotesProvider.java:88) com.appcelerator.titanium.update.core.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:131) com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:456) com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:521) org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) org.eclipse.jface.window.Window.create(Window.java:432) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) com.appcelerator.titanium.update.ui.internal.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:99)",3,val +TISTUD-6427,"Module Package options are broken in studio 3.3.0.201405011408 , for modules built with 3.3.0 sdk","h5. This is a regression. We can see package options for module in 3.2.3 studio created with 3.3.0 sdk. h5.Description: 1. Create a module (any platform) with latest 3.3.0 sdk or mentioned in the description. 2. After its created, try to package it. h5.Actual Results: 1. We do not see any options for packaging modules. All options are greyed out. This is only seen when the module is built with 3.3.0 sdk in studio 3.3.0. If we build a module with 3.2.3 sdk in 3.3.0 studio we can see packaging options. h5.Expected Result: 1. We should see packaging options for modules. ",5,val +TISTUD-6430,Default Titanium Studio Theme not selected on first launch,"This is not a regression since it occurs on 3.2.3 build also. Default Titanium Studio Theme does not appears to be selected any of the radio button of Light or dark on launching the studio for the first time. However, Titanium Studio UI shows correct radio button selected by default. Note: Once we select any of the radio button either light or dark and on restarting the studio, previously selected theme gets retained. Please refer to the attached screenshot for your reference.",5,val +TISTUD-6432,Intermittent: Appcelerator Services gets automatically disabled after restarting Studio,Test Steps: 1.Create a project with appcelerator services enabled. 2.Observe Tiapp Editor and make sure all the sevices must be enabled. 3.Restart Studio. 4.Reopen Tiapp Editor of the same app created in first step. Actual Result: Appcelerator Services gets automatically disabled on Tiapp Editor after restarting Studio. ,5,val +TISTUD-6434,Add code coverage to development branch builds (not just nightlies),We currently record code coverage for nightly builds and PHP/Ruby. We should add code coverage to the normal development branch builds: - studio3-core-development - appcelerator-core-development - titanium-core-development ,3,val +TISTUD-6435,Enforce code coverage doesn't drop for normal development builds,"Once we have code coverage recorded for the three normal builds that run unit tests, we should enforce the coverage never drops like we do for nightlies. This way we can catch if a commit will break the build because of this earlier in the process.",2,val +TISTUD-6436,Add code coverage to PR builders,We should enable tracking code coverage on the PR builders.,3,val +TISTUD-6437,Enforce that PR builders code coverage doesn't drop or they fail,"Once the mainline builds and PR builders are recording code coverage results, we should enforce that the PR doesn't pass unless it builds, passes all the tests and doesn't drop coverage from the current level on the target merge branch.",5,val +TISTUD-6438,Switch to using Findbugs rank over priority,"Findbugs (and the Jenkins plugin) defaults to using ""priority"" for sorting issues into high/normal/low. The reality is that ""priority"" was defined as closer to ""confidence level"" in the way it's used. With Findbugs 2.0 they introduced ""rank"" which is the notion of how ""scary"" a bug is. I'd argue that's a better thing for us to track and determine the high/normal/low values and thresholds to use. The plugin doesn't let you change how the mapping is done, so I looked at the source and it appears to be: 1-4: High 5-9: Normal 10+: Low. (Compare this to Findbugs definition: scariest (rank 1-4), scary (rank 5-9), troubling (rank 10-14), and of concern (rank 15-20).)",2,val +TISTUD-6442,Merge build job definitions from development to release,"We have our jobs set up differently between release/master and development (different number of builds, different dependencies). Once we being merging the code over we also need to merge the build definitions on jenkins from development to release.",5,val +TISTUD-6443,Merge Studio3 repo from development to release and master,"As part of 3.3.0 release, Merge Studio3 repo from development to release and master",5,val +TISTUD-6444,Merge titanium_studio repo from development to release and master,"As part of 3.3.0 release, Merge titanium_studio repo from development to release and master",5,val +TISTUD-6445,Merge titanium_studio_rcp repo from development to release and master,"As part of 3.3.0 release, Merge titanium_studio_rcp repo from development to release and master",3,val +TISTUD-6446,Merge titanium_studio_360 repo from development to release and master,"As part of 3.3.0 release, Merge titanium_studio_360 repo from development to release and master",3,val +TISTUD-6447,Merge titanium_studio_dashboard repo from development to release and master,"As part of 3.3.0 release, Merge titanium_studio_dashboard repo from development to release and master",2,val +TISTUD-6449,"""Unknow request parameter type"" when creating a new OpenShift application","1. Install the latest OpenShift Plugin (you will need to install Ruby and PHP first) from http://preview.appcelerator.com/appcelerator/studio/openshift/update/stable-new 2. Create a New PHP or Rack project 3. Get error ""Unknow request parameter type integer"" I believe this _may_ be fixed by an update to the OpenShift library: https://github.com/openshift/openshift-java-client/pull/71/files ",5,val +TISTUD-6450,Create builder for OpenShift plugin,It appears that the OpenShift Jenkins builder is no more. We should re-createdit.,3,val +TISTUD-6451,"Titanium Studio 3.2.3: ""can't be opened because it is from an unidentified developer""","h5.Description Trying to open Titanium Studio 3.2.3.GA will fail due to a signing issue. A warning will appear telling the user that the software is unidentified and therefore will not be opened h5.Steps To Reproduce 1. Download the following file: http://titanium-studio.s3.amazonaws.com/latest/Titanium_Studio.dmg 2. Attempt to run the application +Make sure that your security settings are set to default in system preferences. It should be set to ""App Store and Identified Developers""+ h5.Expected Result A warning to tell the user the risk of opening the software, or open without a prompt. h5.Actual Result Warning states that the user cannot open the file due to the risk Note. You _may_ have already created an exception for Titanium Studio. you have to revoke it: For example: {code} # List the rules sudo spctl --list --type execute 3512[UNLABELED] P0 allow execute [/Applications/Titanium Studio/TitaniumStudio.app] cdhash H""da9cced6cbb48fd8f6837ea67720ebe5a14717fc"" or cdhash H""5b0667814e309d89caebefb4f0745755a2b3a63e"" # remove the rule in question sudo spctl --remove --rule 3512 {code}",5,val +TISTUD-6454,Titanium Studio creates recursive folder on startup,"Titanium Studio creates an deep structured, non-sense folder, see attachment. Titanium Studio has updated the SDK to 3.2.3, but always checks and receives an update notification for sdk 3.2.3, node.acs 1.0.14 and alloy 1.3.1.",5,val +TISTUD-6455,Move Openshift code out to separate repo,"We currently have the openshift code in the titanium core repo. It has no dependencies on titanium at all right now (just studio3 core), and it's highly inactive in terms of development. We also don't ship it as part of titanium studio. We should just move it out to it's own repo so it doesn't constantly rebuild when we do checkins related to titanium.",5,val +TISTUD-6456,Move Testflight out to it's own repo,Testflight is a separate feature and one we don't ship in titanium by default. It should be moved out to its own repo so it doesn't constantly rebuild when we check in to titanium core.,5,val +TISTUD-6457,Move Nukona out to it's own repo,Nukona is a separate feature and one we don't ship in titanium by default. It should be moved out to its own repo so it doesn't constantly rebuild when we check in to titanium core. I'm not even sure it does anything right now.,5,val +TISTUD-6458,Import sample project shows two contributions of enabling Appcelerator Services,The samples import wizard now shows two contributions to enable Appcelerator Services. Seems the new extra contribution is coming from NodeJS services contribution.,5,val +TISTUD-6465,Services cannot be enabled for a project that does not have the Mobile Project Nature assigned.,Services cannot be enabled for a project that does not have the Mobile Project Nature assigned. This occurs mainly when importing a project from Git where the .project file is not included. To simulate this do the following: 1. Right click on a project that does not have services enabled and go to Properties. 2. Selet Project Natures 3. Uncheck Mobile Steps to reproduce: 1. Open up the tiapp.xml from the project modified above 2. Click on enable services 3. Notice that a progress bar appears and things seem to download 4. Notice that services are not enabled and the tiapp.xml is not correctly modified.,3,val +TISTUD-6490,Studio passes older sdk in the build command even though sdk version in tiapp has been changed.,"h5.Description: 1. Create any app with latest 3.3.0 sdk. 2. Change the sdk in tiapp.xml to any other build. 3. Build & run on device/emulator. h5.Actual Result: 1. In the console logs we see the previous sdk set being user rather than the new one. 2. If you save & run the app again we see that it uses the latest sdk set in the tiapp.xml. 3. E.g If I create an app with latest 3.3.0 sdk , change the sdk to 3.2.3 in tiapp.xml & build it, studio passes the 3.3.0 sdk as below: {code} Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""build"" ""--platform"" ""android"" ""--log-level"" ""trace"" ""--sdk"" ""3.3.0.v20140514121712"" ""--target"" ""emulator"" ""--android-sdk"" ""/Users/lokeshchoudhary/Desktop/android-sdk-macosx"" ""--device-id"" ""Android_4.4.2"" ""--skip-js-minify"" ""--skip-js-minify"" {code} h5. Expected Result: 1. Studio should reflect the sdk changes made in the tiapp.xml ",5,val +TISTUD-6492,Studio calls multiple iOS info commands at the same time,"h5. Description: 1. While studio running open studio logs. 2. Look at the ios info commands run by studio. h5. Actual Results: 1. We see multiple ios info commands run at the same time. This can be see below by looking at the time they are sent: {code} !ENTRY com.aptana.core 1 0 2014-05-14 17:34:22.565 !MESSAGE (Build 3.3.0.201405121247) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""info"" ""-o"" ""json"" ""-t"" ""ios"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Users/lokeshchoudhary/Desktop/android-ndk-r9, ANDROID_SDK=/Users/lokeshchoudhary/Desktop/android-sdk-macosx, APTANA_VERSION=3.3.0.1384563768, Apple_PubSub_Socket_Render=/tmp/launch-OPfjOf/Render, Apple_Ubiquity_Message=/tmp/launch-dQgiVB/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/lokeshchoudhary, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=lokeshchoudhary, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/platform-tools:/usr/local/bin, PWD=/Users/lokeshchoudhary/Desktop/3.3.0_Appcelerator_Studio/AppceleratorStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-RnPbVy/Listeners, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.3.0.201405121247, TI_DEBUG=0, TMPDIR=/var/folders/35/nwgw558n55951fnpxmxkjqmr0000gp/T/, USER=lokeshchoudhary, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2014-05-14 17:34:26.506 !MESSAGE (Build 3.3.0.201405121247) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""info"" ""-o"" ""json"" ""-t"" ""ios"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Users/lokeshchoudhary/Desktop/android-ndk-r9, ANDROID_SDK=/Users/lokeshchoudhary/Desktop/android-sdk-macosx, APTANA_VERSION=3.3.0.1384563768, Apple_PubSub_Socket_Render=/tmp/launch-OPfjOf/Render, Apple_Ubiquity_Message=/tmp/launch-dQgiVB/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/lokeshchoudhary, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=lokeshchoudhary, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/platform-tools:/usr/local/bin, PWD=/Users/lokeshchoudhary/Desktop/3.3.0_Appcelerator_Studio/AppceleratorStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-RnPbVy/Listeners, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.3.0.201405121247, TI_DEBUG=0, TMPDIR=/var/folders/35/nwgw558n55951fnpxmxkjqmr0000gp/T/, USER=lokeshchoudhary, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2014-05-14 17:34:28.279 !MESSAGE (Build 3.3.0.201405121247) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""info"" ""-o"" ""json"" ""-t"" ""ios"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Users/lokeshchoudhary/Desktop/android-ndk-r9, ANDROID_SDK=/Users/lokeshchoudhary/Desktop/android-sdk-macosx, APTANA_VERSION=3.3.0.1384563768, Apple_PubSub_Socket_Render=/tmp/launch-OPfjOf/Render, Apple_Ubiquity_Message=/tmp/launch-dQgiVB/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/lokeshchoudhary, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=lokeshchoudhary, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/platform-tools:/usr/local/bin, PWD=/Users/lokeshchoudhary/Desktop/3.3.0_Appcelerator_Studio/AppceleratorStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-RnPbVy/Listeners, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.3.0.201405121247, TI_DEBUG=0, TMPDIR=/var/folders/35/nwgw558n55951fnpxmxkjqmr0000gp/T/, USER=lokeshchoudhary, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2014-05-14 17:34:28.761 !MESSAGE (Build 3.3.0.201405121247) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""info"" ""-o"" ""json"" ""-t"" ""ios"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Users/lokeshchoudhary/Desktop/android-ndk-r9, ANDROID_SDK=/Users/lokeshchoudhary/Desktop/android-sdk-macosx, APTANA_VERSION=3.3.0.1384563768, Apple_PubSub_Socket_Render=/tmp/launch-OPfjOf/Render, Apple_Ubiquity_Message=/tmp/launch-dQgiVB/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/lokeshchoudhary, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=lokeshchoudhary, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/platform-tools:/usr/local/bin, PWD=/Users/lokeshchoudhary/Desktop/3.3.0_Appcelerator_Studio/AppceleratorStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-RnPbVy/Listeners, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.3.0.201405121247, TI_DEBUG=0, TMPDIR=/var/folders/35/nwgw558n55951fnpxmxkjqmr0000gp/T/, USER=lokeshchoudhary, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY com.aptana.core 1 0 2014-05-14 17:34:28.835 !MESSAGE (Build 3.3.0.201405121247) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""info"" ""-o"" ""json"" ""-t"" ""ios"" Working directory: null Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Users/lokeshchoudhary/Desktop/android-ndk-r9, ANDROID_SDK=/Users/lokeshchoudhary/Desktop/android-sdk-macosx, APTANA_VERSION=3.3.0.1384563768, Apple_PubSub_Socket_Render=/tmp/launch-OPfjOf/Render, Apple_Ubiquity_Message=/tmp/launch-dQgiVB/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/lokeshchoudhary, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=lokeshchoudhary, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools:/Users/lokeshchoudhary/Desktop/android-sdk-macosx/platform-tools:/usr/local/bin, PWD=/Users/lokeshchoudhary/Desktop/3.3.0_Appcelerator_Studio/AppceleratorStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-RnPbVy/Listeners, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=3.3.0.201405121247, TI_DEBUG=0, TMPDIR=/var/folders/35/nwgw558n55951fnpxmxkjqmr0000gp/T/, USER=lokeshchoudhary, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} {code} h5. Expected Result: 1. Multiple commands should not be run at the same time & preferably after an appropriate interval.",5,val +TISTUD-6495,Debugging doesn't suspend breakpoints with liveview,"When an app is launched in debug mode along with liveview, then the breakpoints are not suspended either for Alloy app or classic app.",8,val +TISTUD-6496,Alloy commands in the 'New' menu are not correctly displayed ,h5. Problem description Alloy command in the 'New' menu are displayed incorrectly. h5. Steps to reproduce Go into a project and right-click on any file in the project. Go to 'New' Result: List of possible options is displayed. Alloy commands are displayed incorrectly - see attached screenshot. ,3,val +TISTUD-6498,Alloy commands in the 'New' menu are not correctly displayed ,h5. Problem description Alloy command in the 'New' menu are displayed incorrectly. h5. Steps to reproduce Go into a project and right-click on any file in the project. Go to 'New' Result: List of possible options is displayed. Alloy commands are displayed incorrectly - see attached screenshot.,3,val +TISTUD-6501,Update the release notes with the new format template,"Doc team is currently working on coming up with the new format templates for displaying the release notes in the update wizard. Currently Studio has their own formatting template, but Doc team is coming up a template that will make the release notes unified and consistent.",3,val +TISTUD-6503,MobileIron Plugin: Cannot publish to MobileIron after you package for Android Store,"ENVIRONMENT: Appcelerator Studio, build: 3.3.0.201405121247 Appcelerator Mobile Iron Integration 1.0.0.1396893006-3--59KDJJBAC9 Mac OS X 10.8.5 CLI version 3.3.0-dev Titanium SDK version 3.3.0.v20140512124113 REPRODUCTION: Package an application for the Android App Store. Package an application for MobileIron with an Android target RESULTS: Packaging for MobileIron with an Android target fails with the following alert dialog message: Attribute ATTR_MINIFY is not of type boolean. OTHER INFO: Initially was testing to make sure that packaging for the Android App Store worked. When packaging earlier for MobileIron with an Android target, the command was putting the keystore password in for the alias option. Restarting Studio had no effect, but switching workspaces did.",3,val +TISTUD-6504,MobileIron Plugin: Fails to upload Android App to Mobile Iron,"ENVIRONMENT: Appcelerator Studio, build: 3.3.0.201405121247 Appcelerator Mobile Iron Integration 1.0.0.1396893006-3--59KDJJBAC9 Mac OS X 10.8.5 CLI version 3.3.0-dev Titanium SDK version 3.3.0.v20140512124113 REPRODUCTION: Package an application for MobileIron with an Android target RESULTS: Application builds and a package is created, but fails to upload to MobileIron. Studio displays the following alert dialog message: No message body writer has been found for response class RuntimeException. ",5,val +TISTUD-6505,"UI difference in Studio for creating Alloy controller, migration, model, view, style and widget",This is a regression. Test Steps : 1. Create an alloy project. 2.Select the project and launch File > New > Alloy Controller .Observe the UI. Actual Result : UI difference noticed. Screenshot attached. ,3,val +TISTUD-6526,Geocoder: Android: Alloy sample is crashing after filling an address,"h5. Problem description Geocoder Alloy sample on Android is crashing when filling in an address. Reproducible only with Alloy 1.4.0 - so is a regression h5. Steps to reproduce 1. From Studio, import the Geocoder sample app. 2. Edit tiapp.xml and remove targetSdkVersion (looged a separate ticket: https://jira.appcelerator.org/browse/ALOY-1020) 3. Run the sample on Android (tested on Google Nexus Galaxy 4.3) 4. Click on the textfield and search for an Address Result: app crashes Crash log: {code} [WARN] : dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x415cf700) [DEBUG] : HTTPClient: The persistent handle is disposed. [ERROR] : Crittercism: java.lang.ClassCastException: ti.map.AnnotationProxy cannot be cast to ti.modules.titanium.map.AnnotationProxy [ERROR] : Crittercism: ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:273) [ERROR] : Crittercism: ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:242) [ERROR] : Crittercism: com.google.android.maps.ItemizedOverlay.populate(ItemizedOverlay.java:309) [ERROR] : Crittercism: ti.modules.titanium.map.TiMapView$TitaniumOverlay.setAnnotations(TiMapView.java:265) [ERROR] : Crittercism: ti.modules.titanium.map.TiMapView.doSetAnnotations(TiMapView.java:953) [ERROR] : Crittercism: ti.modules.titanium.map.TiMapView.doUpdateAnnotations(TiMapView.java:714) [ERROR] : Crittercism: ti.modules.titanium.map.TiMapView.handleMessage(TiMapView.java:603) [ERROR] : Crittercism: android.os.Handler.dispatchMessage(Handler.java:95) [ERROR] : Crittercism: android.os.Looper.loop(Looper.java:137) [ERROR] : Crittercism: android.app.ActivityThread.main(ActivityThread.java:5103) [ERROR] : Crittercism: java.lang.reflect.Method.invokeNative(Native Method) [ERROR] : Crittercism: java.lang.reflect.Method.invoke(Method.java:525) [ERROR] : Crittercism: com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737) [ERROR] : Crittercism: com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) [ERROR] : Crittercism: dalvik.system.NativeStart.main(Native Method) [DEBUG] : dalvikvm: GC_CONCURRENT freed 1456K, 9% free 15722K/17216K, paused 3ms+4ms, total 39ms [DEBUG] : dalvikvm: WAIT_FOR_CONCURRENT_GC blocked 21ms [ERROR] : TiApplication: (main) [261349,262305] Sending event: exception on thread: main msg:java.lang.ClassCastException: ti.map.AnnotationProxy cannot be cast to ti.modules.titanium.map.AnnotationProxy; Titanium 3.3.0,2014/05/16 00:25,df56177 [ERROR] : TiApplication: java.lang.ClassCastException: ti.map.AnnotationProxy cannot be cast to ti.modules.titanium.map.AnnotationProxy [ERROR] : TiApplication: ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:273) [ERROR] : TiApplication: ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:242) [ERROR] : TiApplication: com.google.android.maps.ItemizedOverlay.populate(ItemizedOverlay.java:309) [ERROR] : TiApplication: ti.modules.titanium.map.TiMapView$TitaniumOverlay.setAnnotations(TiMapView.java:265) [ERROR] : TiApplication: ti.modules.titanium.map.TiMapView.doSetAnnotations(TiMapView.java:953) [ERROR] : TiApplication: ti.modules.titanium.map.TiMapView.doUpdateAnnotations(TiMapView.java:714) [ERROR] : TiApplication: ti.modules.titanium.map.TiMapView.handleMessage(TiMapView.java:603) [ERROR] : TiApplication: android.os.Handler.dispatchMessage(Handler.java:95) [ERROR] : TiApplication: android.os.Looper.loop(Looper.java:137) [ERROR] : TiApplication: android.app.ActivityThread.main(ActivityThread.java:5103) [ERROR] : TiApplication: java.lang.reflect.Method.invokeNative(Native Method) [ERROR] : TiApplication: java.lang.reflect.Method.invoke(Method.java:525) [ERROR] : TiApplication: com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737) [ERROR] : TiApplication: com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) [ERROR] : TiApplication: dalvik.system.NativeStart.main(Native Method) [INFO] : Process: Sending signal. PID: 8929 SIG: 9 {code} Not reproducible using Alloy version 1.3.1",5,val +TISTUD-6507,Prompt to update after changing the stream in updates preference,"If users change the build stream at Preferences > Studio > Updates., then user has to manually select the option from Help > Check for Appcelerator Updates to get the latest build updates. Since we are already accommodating the updating in Studio now, we should prompt to check for updates once user changes the stream.",5,val +TISTUD-6508,Studio: Shows NullPointerException error on Refresh Devices when Android SDK is not configured,Pr-requisite - Android SDK was not configured Steps - 1. Launch Studio 2. Don’t configure Android SDK. Only iOS and Blackberry SDK had shown configured. 3. Create a default classic project from Studio. 4. Select the created project. 5. Select “Refresh Devices” option from shortcut launch menu (See the attached screen shot) Actual Result - Shows NullPointerException error message. See the attached screen shot and log file. Expected Result - Should not show NullPointerException error message while refreshing devices.,3,val +TISTUD-6510,Android Module packaging to a project is throwing java.lang.reflect.InvocationTargetException,This is a regression issue. It didn't happen in 3.2.3 release. Precondition: Add Android NDK in Studio preferences path. Install gperf and make sure its in your path. I have Platform 10 and platform 19 Google API intalled. Test Steps: 1. Create an android module. 2. Package it to a mobile project. Actual Result: Error occurs. Screenshot and logs attached. {code} !MESSAGE Error within Debug UI: !STACK 0 java.lang.reflect.InvocationTargetException org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275) org.eclipse.ui.internal.progress.ProgressManager$3.run(ProgressManager.java:960) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:995) org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:970) org.eclipse.debug.internal.ui.DebugUIPlugin.launchInForeground(DebugUIPlugin.java:1112) org.eclipse.debug.ui.DebugUITools.launch(DebugUITools.java:759) com.appcelerator.titanium.ui.module.AbstractModulePackagingWizard.performFinish(AbstractModulePackagingWizard.java:82) org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) com.appcelerator.titanium.android.internal.ui.launching.distribution.AndroidModulePackageHandler.execute(AndroidModulePackageHandler.java:34) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) com.appcelerator.titanium.ui.launching.AbstractPackagingLaunchShortcut.launch(AbstractPackagingLaunchShortcut.java:47) org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:434) com.appcelerator.titanium.ui.LaunchAppToolbarContribution$3.widgetSelected(LaunchAppToolbarContribution.java:390) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.NullPointerException com.appcelerator.titanium.android.internal.ui.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:82) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1104) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.NullPointerException com.appcelerator.titanium.android.internal.ui.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:82) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1104) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} ,3,val +TISTUD-6511,Node.ACS: NPE while creating new node acs project,Getting NPE while creating new node acs project. Refer to attached screenshot and logs. {code} !ENTRY org.eclipse.ui 4 0 2014-05-19 15:03:29.825 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException org.eclipse.core.runtime.Path.append(Path.java:261) com.appcelerator.titanium.acs.internal.ui.wizards.NewNodeACSProjectWizard.openIndexFile(NewNodeACSProjectWizard.java:118) com.aptana.projects.wizards.AbstractNewProjectWizard.createAndRefreshProject(AbstractNewProjectWizard.java:432) com.aptana.projects.wizards.AbstractNewProjectWizard.performFinish(AbstractNewProjectWizard.java:356) org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) org.eclipse.jface.window.Window.runEventLoop(Window.java:826) org.eclipse.jface.window.Window.open(Window.java:802) org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:98) org.eclipse.jface.action.Action.runWithEvent(Action.java:499) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:606) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code} ,3,val +TISTUD-6528,iOS: Unable to package iOS module,"iOS: Unable to package iOS module Steps to reproduce: 1. Create an iOS module. 2. Package it to titanium sdk Expected: Module should be packaged to sdk Actual: Getting error as "" /usr/bin/python: can't open file '/Users/paras.mishra/Documents/Appcelerator_Studio_Workspace2/mod1/build.py': [Errno 2] No such file or directory """,5,val +TISTUD-6514,Allow selecting the base repo and branch for a pull request,"We allow generating Pull Requests from a forked repo. It currently assumes a lot and I'm bumping against the limitations now. It assumes that the current branch is the ""compare"" on the current repo. That seems fine to keep. The problem is that we can't change the base, which is hard-coded to be the parent repo (that the fork came off of) and that repo's default branch. At the very least we should allow selecting the base branch. Ideally we'd also allow changing the base repo to any repo in the network of forks.",8,val +TISTUD-6541,Studio Formatter behaves incorrectly causing JSHint errors,"I have noticed that the formatter used within the Studio application has a number of issues that are causing me and my team a lot of difficulties when working with different tools and attempting to maintain a high level of code quality. 1. Studio reformats functions and var declarations within functions incorrectly. I say incorrect as it can cause JSHint errors afterwards also existing formatting applied, say by developer A, gets reformatted by Studio when developer B edits the documents. Here is an example of a small function example that has been formatted with Sublime Text 2 and passes JSHint. It is also the style that I wish to use, which also is recommended in many books regarding code quality with JavaScript. {code:title=FormattingCorrect.js|borderStyle=solid} /** * Test File for Appcelerator Studio Formatting Bug * * @author Ketan Majmudar */ /** * Example Function that maintains a space after the function parantheses and the braces. * variable declaration within is indented for readibility and also allows for git merges * to be easily reviewed. The * * ""use strict""; is used internally and is another issue when the Studio foramtter is used, * it throws errors when using JSLint and should respect certain code style guide conventions. * */ function exampleFunction() { ""use strict""; var myVar1, myVar2, myVar3; switch (myVar1) { case true: myVar3 = true; break; case false: myVar3 = false; break; default: myVar3 = null; } Ti.API.log(myVar1 + myVar2 + myVar3); } exports.exampleFunction = exampleFunction; {code} If this is copy/pasted into Studio, and you use the Source Format option, by default or with custom settings, a few things happen that break the styling and flow. The ""use strict""; statement is placed immediately to the right of the opening brace, the variables are all moved onto a single line, and switch statements re-indent themselves. This is very frustrating when you are working on multiple branches of a project and the commits are going back and forth due to formatting changes made by the product. Take a look at what Studio does to the code example: {code:title=FormattingBroken.js|borderStyle=solid} /** * Test File for Appcelerator Studio Formatting Bug * * @author Ketan Majmudar */ /** * Example Function that maintains a space after the function parantheses and the braces. * variable declaration within is indented for readibility and also allows for git merges * to be easily reviewed. The * * ""use strict""; is used internally and is another issue when the Studio foramtter is used, * it throws errors when using JSLint and should respect certain code style guide conventions. * */ function exampleFunction() {""use strict""; var myVar1, myVar2, myVar3; switch (myVar1) { case true: myVar3 = true; break; case false: myVar3 = false; break; default: myVar3 = null; } Ti.API.log(myVar1 + myVar2 + myVar3); } exports.exampleFunction = exampleFunction; {code} The case should be indented with the switch, the vars should stay on a newline and the ""use strict""; should not move. This raises a wider question as why we can't use JSBeautifer rules/tags for certain settings. The formatting options and rules probably would better serve us if they adopted more of this standard approach that is more widely adopted. (just an idea). My main issue is this current reformatting. Key Issues that need to be addressed: * ""use strict""; should not reflow immediately after the brace * var declarations on newlines should not all be placed on a single line * switch statements should not indent cases.",9,val +TISTUD-6516,Timeout waiting for uploading debug symbols ,"Debug symbols upload error occurs, when the app first installed onto device, using Studio. h5. To reproduce: 1. I used the default classic app with: app.js {code} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); var label = Ti.UI.createLabel({ text:""who is who ""+Ti.Analytics }); win.add(label); win.open(); {code} The error occurs after the app is installed onto device h5. to work around uncheck the box ""Enable Appcelerator Services"" when creating a New Mobile App Project",8,val +TISTUD-6517,Appcelerator Services: Test is not being enabled during project creation,"h5. To reproduce 1. Create the default project, using Studio 2. Enable Appcelerator services h5. Actual result Test Service can be enabled manually only h5. Expected result Appcelerator services should be enabled during project creation",8,val +TISTUD-6520,Intermittent: Deleting multiple projects from workspace results error for open files,This is specific to Windows . I could not recreate this issue on Mac. Test Steps: 1. Create multiple projects in your workspace ( more than 3) 2.Make sure few .js files and .xml files must be open . 3. Delete all those projects ( check delete from workspace too) Actual Result: Error occurs. Screenshot attached. {code} !ENTRY org.eclipse.e4.ui.workbench 4 0 2014-05-20 15:51:54.371 !MESSAGE !STACK 0 java.lang.ClassCastException: org.eclipse.core.internal.resources.File cannot be cast to java.io.File com.appcelerator.titanium.ui.ide.tiappEditor.TiAppEditor.addPages(TiAppEditor.java:144) org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138) org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:358) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:142) org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:96) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:323) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857) org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119) org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333) org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254) org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53) org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685) org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1147) org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:65) org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41) org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) org.eclipse.swt.widgets.Display.syncExec(Display.java:4688) org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205) org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38) org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80) org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58) org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$10.widgetSelected(StackRenderer.java:936) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1081) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:778) org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3080) org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1772) org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:279) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) !ENTRY org.eclipse.e4.ui.workbench 4 0 2014-05-20 15:52:11.513 !MESSAGE !STACK 0 java.lang.ClassCastException: org.eclipse.core.internal.resources.File cannot be cast to java.io.File com.appcelerator.titanium.ui.ide.tiappEditor.TiAppEditor.addPages(TiAppEditor.java:144) org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138) org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:358) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:142) org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:96) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:323) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857) org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119) org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333) org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254) org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53) org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685) org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1147) org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:65) org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41) org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) org.eclipse.swt.widgets.Display.syncExec(Display.java:4688) org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205) org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38) org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80) org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58) org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$10.widgetSelected(StackRenderer.java:936) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1081) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:778) org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3080) org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1772) org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:279) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 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:354) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) org.eclipse.equinox.launcher.Main.run(Main.java:1450) !ENTRY org.eclipse.ui 4 4 2014-05-20 15:52:21.060 !MESSAGE Unable to create part !ENTRY org.eclipse.core.filebuffers 4 0 2014-05-20 15:52:21.060 !MESSAGE The file does not exist. !STACK 1 org.eclipse.core.runtime.CoreException: The file does not exist. org.eclipse.core.internal.filebuffers.ResourceFileBuffer.create(ResourceFileBuffer.java:237) org.eclipse.core.internal.filebuffers.TextFileBufferManager.connect(TextFileBufferManager.java:112) org.eclipse.ui.editors.text.TextFileDocumentProvider.createFileInfo(TextFileDocumentProvider.java:559) org.eclipse.ui.editors.text.TextFileDocumentProvider.connect(TextFileDocumentProvider.java:478) com.aptana.editor.common.CommonDocumentProvider.connect(CommonDocumentProvider.java:31) com.aptana.editor.common.SimpleDocumentProvider.connect(SimpleDocumentProvider.java:26) org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:4230) org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:237) org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1480) com.aptana.editor.common.AbstractThemeableEditor.doSetInput(AbstractThemeableEditor.java:1160) org.eclipse.ui.texteditor.AbstractTextEditor$19.run(AbstractTextEditor.java:3217) org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1829) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1826) org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:3235) org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:3262) com.aptana.editor.common.AbstractThemeableEditor.init(AbstractThemeableEditor.java:640) org.eclipse.ui.internal.EditorReference.initialize(EditorReference.java:359) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:306) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857) org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119) org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333) org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254) org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53) org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685) org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1147) org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:65) org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41) org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) org.eclipse.swt.widgets.Display.syncExec(Display.java:4688) org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205) org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38) org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) org.eclipse.osgi.fra...,3,val +TISTUD-6521,"Studio: Default modules (com.appcelerator.apm, ti.cloud) are not showing under Modules section in tiapp.xml overview screen after creating the project","Steps - 1. Launch Studio 2. Create a default classic project. 3. Observed the Modules section on TiApp Editor Overview screen. Actual Result - No modules are showing under the Modules section. See the attached screen shot and log file. Note - Close the tiapp.xml file and reopen again. Now default modules (com.appcelerator.apm, ti.cloud) are showing under Modules section on TiApp Editor Overview screen Expected Result - Should show the default modules (com.appcelerator.apm, ti.cloud) under Modules section on TiApp Editor Overview screen.",5,val +TISTUD-6523,"""Enable Javascript Minification"" is enabled for apps with services enabled","h5. This is a regression h5.Description: 1. Create an alloy/classic app in appcelerator studio 2. Package it for android. h5.Actual Result: 1. The ""Enable Javascript Minification"" option is enabled for the app with services enabled. NOTE: Refer attached screenshot for reference. h5.Expected Result: 1. The ""Enable Javascript Minification"" option should be disabled for the app with services enabled.",3,val +TISTUD-6524,ACS version error when creating new a Node.ACS app doesn't make sense,Steps: 1. File > New > Node.ACS project. 2. Give project a name and click Create. Results: ACS version error dialog appears (see attached) but the message seems a bit garbled and doesn't make much sense.,5,val +TISTUD-6531,Unable to package 3.3.0 module,"iOS: Unable to package iOS module Steps to reproduce: 1. Create an iOS module. 2. Package it to titanium sdk Expected: Module should be packaged to sdk Actual: Getting error as "" /usr/bin/python: can't open file '/Users/paras.mishra/Documents/Appcelerator_Studio_Workspace2/mod1/build.py': [Errno 2] No such file or directory """,5,val +TISTUD-6533,SDK Release has to extract the entire body release notes,"Currently Studio depends on the xcode path class 'api-doc' for extracting the release notes content. There is no api-doc tag anymore for SDK release notes, so it should default to entire body contents. If we can't find the content in the expected tag, then we don't apply the template.",2,val +TISTUD-6534,Studio release has to extract only from guide-container,"The release notes of Studio should extract the contents from 'guide-container' class div, and then apply the style template.",2,val +TISTUD-6535,"BlackBerry: ""Argument cannot be null"" error on Run Configuration",h5. To reproduce 1. In Studio Project Explorer choose the project and Run configuration 2. Choose Appcelerator BlackBerry Simulator or Appcelerator BlackBerry Application Installer h5. Actual result An error has occurred. Argument cannot be null h5. Expected result To set the desirable configuration and run it ,3,val +TISTUD-6537,AirWatch: Add preference page,"Add a preference page to allow Add, Edit or Delete the AirWatch publish targets. Though we have the basic infrastructure to create the pref page for publish providers, it might need to provide the table columns, label provider and publish target comparator.",8,val +TISTUD-6538,AirWatch: Create a register publish provider dialog,"Create a new register publish target dialog to allow users to input user/pwd/host/alias, similar to existing mobileiron register dialog.",5,val +TISTUD-6539,AirWatch: Authenticate the given publish target,"Once the user inputs the credential details in the register dialog, it would have created a publish target based on the credentials. However, we need to authenticate the target based on the user input and return the appropriate error message.",5,val +TISTUD-6542,Studio: iOS SDK option does not show on Platform Configuration Wizard if Xcode is not installed on system,Pre-Requisite - Removed Xcode and Android SDK from System. Steps - 1. Launch Studio 2. Observe the SDK options available on Platform Configuration Wizard. Actual Result - iOS SDK option does not show on Platform Configuration Wizard. Only Android and BlackBerry SDK options are showing. See the attached screen shot. Expected Result - Should show the iOS SDK option on Platform Configuration Wizard. Note - Shows the iOS SDK on Platform Configuration Wizard if using Studio 3.2.3 GA,8,val +TISTUD-6543,Mobile Web - files are not generated when packaging Mobile Web to new project,"This is not a regression issue. Steps to reproduce: 1. Package default Titanium project for Mobile Web 2. Select ""Create a new project for the Mobile Web app"" 3. Open newly created Web project Actual: index.html does not appear in the web project created on packaging. Only 'Connection' appears down the folder hierarchy of the packaged web project. See attached screen shot and log file for more clarification. Expected: The packaged mobile web should contain the index.html in order to preview the app.",3,val +TISTUD-6548,Studio installer version on Mac displays 3.0 despite being 3.3.0,h5.Description Studio displays version 3.0 for all installers of Titanium Studio and Appcelerator Studio. Tested back to Studio 2.1.2 and that also showed version 3.0. h5.Steps To Reproduce 1. Download the installer for Studio 2. Click on the Studio executable h5.Expected Result Should show the correct version number h5.Actual Result Shows version 3.0 +Extra Information+ Checking the executable information (cmd + i) shows the copyright information in the version field. and the actual version is not shown anywhere. Attached screenshots of the Studio executable version and the executable info window. This is not a regression.,5,val +TISTUD-6549,"MobileWeb: Package MobileWeb Project wizard shows ""OK"" after selecting location path","This is a Regression since it does not occur in 3.2.3.GA build. While packaging mobile app project for Mobileweb, text “Package the mobile web application” is replaced by “OK” on selecting the Location path. Steps to Reproduce: 1. Create a default project. 2. Package to Mobile web. Actual Result: Text ""Package the mobile web application” is replaced by “OK” on selecting the Location path. Expected Result: Text ""Package the mobile web application” should not get change after selecting the location. Refer to the attached screenshots for your reference.",3,val +TISTUD-6550,"Support .jshintrc files, use that as override for indent setting on our formatter",JSHint rc files are pretty common in Javascript-land nowadays. We should support at least finding them and using the indent value as an override for our formatter for files under that directory/project.,5,val +TISTUD-6552,Download and index Node.js core modules for user (for version they have),We do support Node/NPM fairly well and can handle module require's decently. But one big hole in our support is that we don't try and force the user to grab the Node.js sources for the version they're using and index those core modules (where we can). This means we can't jump to core modules or give any useful content assist on them.,8,val +TISTUD-6556,"Debugger Exception: No ""android-10"" or ""android-2.3.3"" in the Android SDK in the device console log","Steps Followed: 1. Create a Titanium project and debug it on a device. Actual Result: The debug process is completed successfully and the breakpoints are also hit. But the device console logs show some Android 2.3.3 dependency error. Note: The same error is observed for profiler also. Also if Android 2.3.3 or API level 10 is installed than this error does not occur. {code} Traceback (most recent call last): File ""/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/builder.py"", line 2497, in launch_logcat() File ""/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/builder.py"", line 124, in launch_logcat adb_location = AndroidSDK(android_sdk_location).get_adb() File ""/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/androidsdk.py"", line 49, in __init__ self.set_api_level(api_level) File ""/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/androidsdk.py"", line 53, in set_api_level self.find_platform_dir() File ""/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/androidsdk.py"", line 131, in find_platform_dir raise Exception(""No \""%s\"" or \""%s\"" in the Android SDK"" % ('android-%s' % api_level, android_api_levels[api_level])) Exception: No ""android-10"" or ""android-2.3.3"" in the Android SDK {code}",5,val +TISTUD-6561,"After building, Studio is still showing 'Launching delegate' in progress","h5. Problem description After building an application, it could happen that the app is built and runs fine, but Appc-Studio seems to be still doing something in the background - specifically, ‘Launching delegate’, displaying an ongoing activity in the bottom-right corner, staying stuck at 57%. h5. Steps to reproduce 1. Create an iOS app and build for iOS device Result: app is built and run correctly. However, in the bottom-right corner of Studio, there is an ongoing process (see Screen Shot 2014-05-28). Expected result: Studio should show no ongoing process. 2. Click on the bottom-right progress bar Result: Progress window is displayed, showing details on the ongoing process (""Launching delegate"" progress information is shown). See Screen Shot 2014-05-28. Expected result: no ongoing Studio progress should be shown. See the attached screenshots 3. Perform further actions on the app project (build, clean workspace etc...) Result: It is actually possible then to do everything (build, clean workspaces etc…). It seems Studio is not really hang in there, but it shows to stay in the state as shown in the screenshots. So far has been reproduced when building/running an App on iOS device. h5. Additional notes It seems there could be a memory issue too - still not sure if related to this, but at the time of writing and while experiencing the described behavior, checking Activity Monitor, Appc-Studio is using ~400MB of memory which seems to be too much. Investigating.",5,val +TISTUD-6574,NPE on a project creation when no SDKs are installed,"When trying to create a default project using Studio, we get java.lang.NullPointerException in the log. No project is being created. {code} java.lang.NullPointerException com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectCreationPage.validatePlatforms(NewMobileProjectCreationPage.java:281) com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectCreationPage.createControl(NewMobileProjectCreationPage.java:224) org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) org.eclipse.jface.window.Window.create(Window.java:432) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:95) org.eclipse.jface.action.Action.runWithEvent(Action.java:499) {code} To work around check for appcelerator updates and accept required installs. ",3,val +TISTUD-6576,3.3.0 Studio Installer: Studio is installed in the wrong location,"h5.Description The 3.3.0 Studio installer downloads the temporary files into the AppData folder. After the temp files have been obtained it moves the entire program into the Program Files folder. Once all the files have been moved it attempts to remove the temp files, but fails to remove the root folder in the AppData location, only the files inside it. h5.Steps to Reproduce 1. Download the 3.3.0 Studio offline installer. 2. Install the program. 3. Check your AppData/roaming folder 4. Check your Program Files folder h5.Expected Result Studio should be installed in the AppData folder h5.Actual Result Studio is installed in the Program Files folder, leaving unused files and folders inside the AppData location.",5,val \ No newline at end of file