diff --git "a/test.csv" "b/test.csv" new file mode 100644--- /dev/null +++ "b/test.csv" @@ -0,0 +1,585 @@ +issuekey,title,description,storypoint,split_mark +TISTUD-6577,3.3.0 Studio Installer: Status bar resets back to zero as install progresses,"h5.Description As you are installing Studio using the 3.3.0 Studio offline installer, the progress bar starts to increase, but drops back down to 0%. The overall progress of the installer is actually increasing, as indicated by the icon on the desktop taskbar (gradually changes green as program installs) but the Studio installer display isn't increasing. h5.Steps To Reproduce 1. Download the 3.3.0 Studio offline installer 2. Install the software. 3. Watch the progress bar h5.Expected Result Progress bar should increase until it hits 100% h5.Actual Result Progress bar drops back to 0%",5,test +TISTUD-6578,Update content assist to support FixedSpace tag,Alloy 1.4 adds support for shortcut notation for a fixed space button. is a shortcut for {code} 3. In the index.js file, type '$' followed by '.' to show content assist with objects from index.xml Actual Result: Content assist shows the ids from the view as properties off $, but nothing like toString() or isPrototypeof(). Expected Result: Content assist should show Object instance methods for $, such as isPrototypeOf() and toString().",8,test +TISTUD-6931,Provide more comprehensive CA on JS constructor invocations,Related to screenshots from TISTUD-1541. In this case: {code:javascript} var com = { aptana: { myFunction: function() {} } }; var instantiate = new com.| {code} We should offer the following proposals: com.constructor com.hasOwnProperty com.isPrototypeOf com.propertyIsEnumerable com.toLocaleString com.toString com.valueOf com.aptana,3,test +TISTUD-6933,Unable to create Android Modules in Windows 8.1,Android Modules can not be created in Windows 8.1 machine. But module can be created using CLI. h5. Steps To Reproduce 1. Launch the studio on windows 8.1 machine 2. Create an android module h5. Actual Result: Module can not be created. It fails with an error message. Please see the attachment for more info. Studio log is also attached. h5. Expected Result: Module should be created without any issues. Error: {code} !ENTRY com.aptana.projects 2 0 2014-09-16 13:04:30.070 !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: java.lang.NullPointerException com.appcelerator.titanium.core.internal.cli.NodeTitaniumSDKCommandsHandler.createModuleProject(NodeTitaniumSDKCommandsHandler.java:222) com.appcelerator.titanium.ui.ide.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:254) 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-09-16 13:04:30.070 !MESSAGE !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.core.internal.cli.NodeTitaniumSDKCommandsHandler.createModuleProject(NodeTitaniumSDKCommandsHandler.java:222) com.appcelerator.titanium.ui.ide.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:254) 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) {code},5,test +TISTUD-6938,NPE while refreshing roles when organization information is still not updated ,Refreshing the roles in the Create project wizard when the role information has not been fetched gives a NPE ,3,test +TISTUD-7013,MobileWeb: Unable to launch mobileweb projects in Android Emulator,Unable to preview mobile web projects in Android Emulators. (!) This is a *regression* since same scenario is observed in 3.3.0 GA. h5. Steps to reproduce 1. Create a mobileweb app 2. Run in emulator ( Run As > Mobile Web Preview: titanium_1_WVGA800) h5. Actual Result Console log says project is built successfully. There is no sign to failure but *App is not launched in Emulator*. Please see the *attachment* Following log is observed in Studio log file {code} !ENTRY com.appcelerator.titanium.mobileweb.ui 4 0 2014-09-17 17:26:11.885 !MESSAGE (Build 3.4.0.201409161950) [ERROR] Could not launch the Android's internal browser. error: more than one emulator error: more than one emulator {code} h5. Expected Result Mobileweb app should run in Emulator as it's appearing in Context menu.,5,test +TISTUD-6940,Content Assist not showing many of the methods and properties of objects,"Content Assist in a js file (both classic and alloy projects) missing a lot of options. Like it does not display any of the create method under TI.UI or Ti.API. does not show content assist. This is a regression. The issue did not occur in Studio 3.3.0 Steps to Reproduce: 1. Create a sample project and open its js file 2. Type Ti.UI 3. Add ""."" and type 'c' Actual Result: The content assist only shows 'clipboard'. Refer to attached screenshot Expected Result: The content assist should show all the methods and properties.",8,test +TISTUD-6941,Studio: Copying project into workspace while importing projects does not work on the second time,"Selecting the copy project into workspace while importing projects every second time would not copy the project into the workspace.Every second time while importing the project, the checkbox for copy project into workspace is already enabled. -This is not a regression as it can also be found in Appcelerator studio 3.3.0 Steps to reproduce: 1. Launch studio 2. Go to file > import 3. Choose appcelerator > existing mobile project 4. Browse for any existing mobile app project and ensure copy project into workspace is enabled. 5. Click Finish 6. Import another project by following steps 2-5 Actual Results: 5. Imported project appears in studio's project explorer and also it can be found in the workspace folder 6. This time while importing you will notice that the checkbox for copy project into workspace is already enabled. However, when importing is finished you will notice that the master version of the project is displayed in the studio' project explorer and the project is not found in your workspace (check your finder) Expected Results: 6. The project must be copied into the workspace and the master version of the project must not be displayed in studio's project explorer instead the copied project must be shown. Note: At step 6 if you were to uncheck the copy project into workspace option and check again, it works as expected and the project is copied into the workspace while importing.",5,test +TISTUD-6943,Support multiple Titanium SDK roots like CLI does,"The CLI supports multiple SDK root paths. If users have installs in each path, the CLI behaves fine but Studio is ""missing"" SDKs they have installed. Studio should support looking in multiple root folders for Titanium SDKs, like the CLI does and should sync those folders up between itself and CLI. http://developer.appcelerator.com/question/177797/cannot-use-340-rc-sdk#answer-282483",8,test +TISTUD-6944,Studio intermittently fails to retrieve the new Node.ACS version,"Can't create a Node.ACS project in Windows The attached screen shot shows the error when trying to create a new Node.ACS project. (!) *Node ACS Projects can be created on Mac OSX 10.9.4 with same Appc configurations as mentioned in Environment section* h5. Steps To Reproduce 1. In Appcelerator Studio, File>New>Node.ACS Project 2. Name the project 3. Select an organization 4. Click Finish h5. Actual Result Project creation fails with error message. Please see the attachment. h5. Expected Result Project should be created successfully like Mac OSX",5,test +TISTUD-6949,BlackBerry: Installing through BlackBerry SDK through Studio does not install Momentics correctly,h5.Description When the Blackberry SDK is installed using Studio the Momentics IDE is not installed correctly. This means that an app can only be built to simulator as you cannot set up the environment to be able to build to device. h5.Steps To Reproduce 1. Install the Blackberry SDK through Studio. h5.Actual Result Momentics is installed incorrectly h5.Expected Result Momentics should be installed correctly,8,test +TISTUD-6951,Studio: FSA sample when imported sometimes fails to enable ACS service because GUID already exists,"h5. Description: While testing Field Service App (FSA) I repeatedly imported the sample, got it running, and then ran on simulator. For 3 runs, two failed service enablement (one test service, one cloud) on the initial creation attempt to enable services. Enabling after creation works. According to Praveen this is due to the service enablement timing conflicting with the task of changing the default GUID to a unique one, which happens for imported samples. If the service enablement occurs too quickly (before the unique GUID is generated), then the service enablement will fail. This does not seem to be a regression, as the process has not changed. But it is intermittent. Studio log shows the following when failure occurs: {code} !ENTRY com.appcelerator.titanium.360.core 4 0 2014-09-24 13:48:04.475 !MESSAGE (Build 3.4.0.201409231834) [ERROR] {""message"":""Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists.""} !STACK 1 org.eclipse.core.runtime.CoreException: {""message"":""Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists.""} com.appcelerator.titanium360.internal.core.Titanium360Manager.handleResponse(Titanium360Manager.java:439) com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:360) com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getACSKeys(ThreeSixtyProject.java:849) com.appcelerator.titanium360.core.services.ACS360Service.installService(ACS360Service.java:74) com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installService(Titanium360ProjectUtil.java:177) com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installServices(Titanium360ProjectUtil.java:87) com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil$2.runInWorkspace(Titanium360ProjectUtil.java:313) org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 com.appcelerator.titanium.360.core 4 400 2014-09-24 13:48:04.475 !MESSAGE {""message"":""Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists.""} {code} h5. Steps to reproduce: 1) Import the FSA sample 2) Watch for service enablement to fail during the import process If no failure, delete the FSA with ""remove from disk"" option checked and try again. h5. Result: Log records failure, tiapp.xml editor shows failure to enable service h5. Expected Result: Service enabled correctly, with the appropriate GUID",5,test +TISTUD-6954,Studio doesn't prompt for latest RC npm package update when there was previous RC version installed,"With the new RC/Beta update process, users can switch the update stream to RC/Beta in Preferences > Studio > Update, and then, Studio should prompt for latest RC tagged releases for npm packages. However, if the user already have alloy@1.5.0-rc2 installed on their machine, the even though the update stream references to RC stream, Studio does not prompt for alloy@1.5.0-rc5 release.",5,test +TISTUD-6957,Add default selected SDK information and ti info output in the diagnostic logs,"With the number of issues with iOS8, we need to figure out the default selected SDK on the machine and also ask the user for ti info output. Instead of asking this information repeatedly to the user, it might be better to show the below details : - The ti info output for both iOS and Android platforms. - Since we are already displaying the SDK details, we should indicate whether the SDK is a default selected one.",3,test +TISTUD-6958,Studio: Studio should handle secure storage corruption more elegantly,"h5.Description It is thought that the secure storage is corrupted when the user has multiple Studios and they each try to access the file, as a result of the file becoming corrupted when services are attempted to be enabled then Studio believes that they have been but because of the file being corrupted the keys do not show up in the tiapp.xml and the user is not easily alerted to the reason why unless they check in the logs and see the error. The error is attached. h5.Steps To Reproduce 1. Corrupt the file in the .eclipse folder 2. Attempt to enable an app for services h5.Actual Result Studio says that the app is enabled for services but there are no keys, the user is not told what the issue is h5.Expected Result The app should not be enabled for services and the user should be alerted to the problem and studio should let the user know what needs to be done",5,test +TISTUD-6962,CLI: Running iOS application on iPhone Retina (4-inch 64-bit) simulator gives invalid --device-id error.,"Description: The test machine is having the installation as mentioned in the environment. Running the iOS application with iPhone Retina (4-inch 64-bit) simulator by setting ti SDK to 3.3.0.GA in tiapp.xml gives an error ""invalid device id value"". This is a regression.This simulator works with App Studio 3.3.0 and Titanium SDK 3.3.0.GA. With CLI3.4.0-rc4 and ti SDK 3.3.0.GA , the project built successfully and shows the simulator iPhone Retina (4-inch 64-bit) with black screen. The application didn't launch on it and the execution terminates.This happen 2-3 times. But after that the application get launches successfully on 64bit Retina simulator with CLI. ti build -p ios -T simulator --sim-64bit --retina STEPS TO REPRODUCE: 1. Create an application for iOS platform in Studio. 2. Set the Titanium SDK in tiapp.xml to 3.3.0.GA. 3. Run the application on iPhone Retina (4-inch 64-bit) simulator. EXPECTED RESULT: 3. The application should build and launched successfully on iPhone Retina (4-inch 64-bit) Simulator. ACTUAL RESULT: 3. The application does not build and gives the error ""invalid --device-id value"". Please refer the attachment for details. With other simulators, its working successfully. The problem is with iPhone Retina (4-inch 64-bit) Simulator only. ",3,test +TISTUD-6961,Error loading rubles with Eclipse 4.4.1,"JRuby is explicitly casting System.getProperties as String keys and values. However, Eclipse 4.4.1 is now pushing an anonymous null object as a value for some of them, and we need to explicitly call toString() on it to get a String. The fix here may be to apply a small patch to JRuby, or to upgrade to the latest JRuby release. {code} !ENTRY org.eclipse.core.jobs 4 2 2014-09-26 14:09:53.781 !MESSAGE An internal error occurred during: ""Loading bundle: /Users/cwilliams/Documents/Aptana Rubles/ruby.ruble"". !STACK 0 java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String org.jruby.util.OSEnvironment.getAsMapOfRubyStrings(OSEnvironment.java:90) org.jruby.util.OSEnvironment.getSystemPropertiesMap(OSEnvironment.java:75) org.jruby.RubyGlobal.defineGlobalEnvConstants(RubyGlobal.java:393) org.jruby.RubyGlobal.createGlobals(RubyGlobal.java:358) org.jruby.Ruby.init(Ruby.java:1078) org.jruby.Ruby.newInstance(Ruby.java:186) org.jruby.embed.internal.SingletonLocalContextProvider.getRuntime(SingletonLocalContextProvider.java:95) org.jruby.embed.internal.EmbedRubyRuntimeAdapterImpl.runParser(EmbedRubyRuntimeAdapterImpl.java:166) org.jruby.embed.internal.EmbedRubyRuntimeAdapterImpl.parse(EmbedRubyRuntimeAdapterImpl.java:93) org.jruby.embed.ScriptingContainer.parse(ScriptingContainer.java:1163) org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1223) com.aptana.scripting.ScriptingEngine.getInitializedScriptingContainer(ScriptingEngine.java:292) com.aptana.scripting.model.ScriptLoadJob.run(ScriptLoadJob.java:76) com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:144) com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:180) com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:274) com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:243) com.aptana.scripting.model.BundleManager.loadScript(BundleManager.java:2032) com.aptana.scripting.model.BundleManager$BundleLoadJob.run(BundleManager.java:129) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}",5,test +TISTUD-6965,"Sign OS X application with ""Version 2"" of developer signature","From Apple: Beginning November 1, 2014, apps submitted to the Mac App Store must be signed with signatures created with OS X Mavericks 10.9 or later (v2 signatures). Apps without v2 signatures will be automatically rejected on upload. If you build code with an older version of OS X, use OS X Mavericks 10.9 or later to sign your app and create v2 signatures using the codesign tool. Structure your bundle according to the signature evaluation requirements for OS X Mavericks 10.9 or later. Considerations include: * Signed code should only be placed in directories where the system expects to find signed code.  * Resources should not be located in directories where the system expects to find signed code.  * The --resource-rules flag and ResourceRules.plist are not supported. Make sure your current and upcoming releases work properly by testing on OS X Mavericks 10.9.5 and OS X Yosemite 10.10 Developer Preview 5 or later. Apps signed with v2 signatures will work on older versions of OS X. For more details, read “Code Signing changes in OS X Mavericks” and “Changes in 
 OS X 10.9.5 and Yosemite Developer Preview 5” in OS X: https://developer.apple.com/library/mac/technotes/tn2206/_index.html See also related bugs in Eclipse: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=445015 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=445050",8,test +TISTUD-6968,Studio: Marketing banner is not shown in dashboard,h5.Description In Studio the marketing banner is not shown on the Dashboard tab. This happens in both 3.3.0 and 3.4.0 studio h5.Steps To Reproduce 1. Open the Dashboard tab h5.Actual Result The marketing banner is not shown at the top of the page h5.Expected Result The marketing banner should be shown,5,test +TISTUD-6969,Node processes are not killed when re-launching projects to Android device,"h5.Description When rebuilding to an Android device the node processes are not terminated and get stacked up causing high memory usage on the system. The screenshot below shows Appcelerator Studio in activity monitor after 3 launches. *Notes* This happens on both Windows and OSX. When run from the CLI this does not occur as the CLI requires the user to terminate the process before allowing them to rebuild If the user manually terminates by pressing the red square then it is terminated as expected. h5.Steps To Reproduce 1. Build a project in Studio to Android device. 2. a. On OSX, in terminal run ps aux | grep node b. On Windows, in command prompt run tasklist /v | findstr node 3. Relaunch the project to device h5.Actual Result 2. The output shows only one process, as expected 4. The output now shows 2 processes h5.Expected Result 2. The output shows only one process. 4. The output should still show only one process. ",5,test +TISTUD-6972,Studio hangs with incorrect password during update,"Steps to reproduce : - If there are any updates to NPM packages (alloy, CLI, acs...), then Studio prompts for system password in order to install the packages globally on the system. - However, if the user provides an invalid password, then Studio hangs forever. When an invalid password is provided, the sudo process prompts back to let users for another attempt to provide correct password. However, Studio waits for the sudo password process to exit without knowing that it is waiting on input.",8,test +TISTUD-6974,3.4.0 GA upgrade or installation should alert users of dependancy for Xcode 6,"After upgrading to 3.4.0 GA, compiling and building of the App fails as it requires Xcode to be at version 6.0. The download / upgrade should be alerting the users about this dependency",5,test +TISTUD-6976,Unable to set genymotion player path in studio preferences,"h5. Description: 1. In the genymotion preference for android in studio enter the path for genymotion player. 2. Click apply & then ok to save the preference. 3. Open the android preferences again & check if the genymotion player path is set in studio. h5.Actual Result: 1. The genymotion player path does not get saved in studio preference. 2. If I manually set ""genymotion.executables.player"" in ti config then studio saves the preference. h5. Expected Result: 1. Studio should save preference for genymotion player",5,test +TISTUD-6978,Update content assist for new ActionView tag,"Alloy 1.6 will support as a child of . For proper functioning, developers should specify the showAsAction property in XML or TSS.",8,test +TISTUD-6979,Studio should revert back to using Windows path format for alloy.js sourcemaps,"Currently Studio works-around the source maps of alloy.js/app.js generated source map path by looking for portable OS string rather than Windows specific path format. ALLOY-1140 has addressed the issue that the path is always in the OS specific format. With Alloy 1.6.0, Studio might fail to suspend at breakpoints on Windows, as we are looking for a specific path format (/path/to/index.js) instead of \path\to\index.js. So, Studio should start using OS specific path formats against Windows as well now. ",5,test +TISTUD-6980,Content assist: Update for WindowToolbar tag for setting window.toolbar property,"Alloy 1.6 will support a new tag which is used to specify the array of views for the window.toolbar property. This new tag is valid only w/in the Window tag and can contain the same children as the tag (buttons, text fields, FlexSpace, FixedSpace, ImageView and perhaps a few more)",5,test +TISTUD-6982,Update fails to install properly; Password/ folder created,"I was prompted to install an update for Node.ACS (moving from 1.0.20 to 1.0.21). No matter how many times the update was installed, I was prompted to install the update again. This started happening after changing from 32 bit Studio to 64 bit Studio on Mac. This command was used to install an ACS update: {code} ""sudo"" ""-p"" ""password:"" ""-S"" ""-H"" ""--"" ""/usr/local/bin/node"" ""/usr/local/bin/npm"" ""-g"" ""install"" ""acs"" ""--color"" ""false"" {code} The update was not properly installed and a ""Password/"" folder was created in my AppceleratorStudio.app/Contents/MacOS folder and in my home folder. Install location was: {code} /Users/ewieber/Password:/Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/Password:/Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/Password:/usr/local/lib/node_modules/acs/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws {code} Running the above command without the -H option resolved the issue.",5,test +TISTUD-6995,Signing in using the home control does not login into dashboard,"If Appcelerator Studio is launched without user signed in, then 'Sign In' link appears in the status bar (home control). It opens a sign in dialog and after user input the login credentials, it lets the user to login and set the user name in the home control. However, when we try to create the projects, the organizations of the logged in user are not loaded. Refreshing them doesn't help. Signing in using the home control sign in dialog will login only into API server, and not to the 360 dashboard.",5,test +TISTUD-6997,Defer Node.ACS CLI installation until the node.acs project is created,"As every user doesn't use Node.ACS projects, there is no need to install node.acs CLI until the users are actually working with node.acs projects. So, if node.acs CLI is not installed, and the user attempts to create a node.acs project, then we should prompt and install acs CLI before we create the project.",8,test +TISTUD-7000,Studio should provide a wizard for generating keys / certs etc,There are many cases were specific certs or keys need to be generated in order for features to work or builds to be created. Appcelerator Studio should provide ways to simplify these tasks for the end user. EX - * Google Map Key (SHA1) * Google Keystore * Apple Certs for development and distribution builds * etc.,8,test +TISTUD-7001,NPE during studio startup,NPE during studio startup java.lang.NullPointerException com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationHelper.getVersionInfo(MobileSDKConfigurationHelper.java:133) com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationProcessor.computeStatus(MobileSDKConfigurationProcessor.java:74) com.aptana.configurations.processor.AbstractConfigurationProcessor.getStatus(AbstractConfigurationProcessor.java:154) com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:127) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54),3,test +TISTUD-7002,The Launch options are disabled after closing and reopening projects,"Steps to reproduce : - Close all projects in workspace. - Re-open only one project in the workspace. - The launch options are disabled for the project, though the app should be allowed to launch on iOS/Android devices. Workaround: Reopen a different project in workspace and switch back the project selections in the explorer.",5,test +TISTUD-7005,Resize the launch button in global toolbar,"Currently the launch mode button is too small and many users are not aware whether it is a button or a label. We need to resize the launch button to a bigger size, so it is clearly evident to the users that hitting the button will do the magic (launching the app based on the selected launch mode and shortcut).",8,test +TISTUD-7007,Redundant browse buttons exists for setting genymotion preferences in appcelerator studio,h5.Description: 1. For genymotion preferences in studio some of the browse buttons are redundant. 2. On MAC OSX: The browse buttons for genymotion path & genymotion player are redundant as the executables are inside the app contents of the genymotion.app & we can't browse to it using the browse button. 3. On Windows: The browse button for genymotion path is redundant as we are setting a path & not a path for an .exe file. For more info about genymotion preferences refer : http://docs.appcelerator.com/titanium/latest/#!/guide/Installing_Genymotion h5. Expected Result: 1. The redundant buttons should be removed or replaced with an alternative. ,5,test +TISTUD-7009,Surface the error from 360 login to the user,"During a customer call, I have noticed that the user has set the incorrect proxy settings on their Windows machine. As Studio is unable to connect/authenticate against 360 server, it gets a json feed indicating that the ""proxy authentication is required"". However, Studio still shows an error message that the ""username/password combination is incorrect"". The error message is completely misleading even though the underlying issue is due to incorrect proxy configuration. Studio should show the same error message that we receive from 360/dashboard login API.",5,test +TISTUD-7010,Prompt for Node.ACS CLI installation if acs app is launched to run on local server,"In case Node.ACS CLI is not installed on the machine, and if the user tries to launch an existing acs app onto local server, then Studio should prompt for Node.ACS CLI installation before we launch the project.",5,test +TISTUD-7011,Prompt for Node.ACS CLI installation before publishing the app,"In case Node.ACS CLI is not installed on the machine, and if the user tries to publish a acs app, then Studio should prompt for Node.ACS CLI installation before we publish the app.",5,test +TISTUD-7012,Avoid installing Node.ACS CLI using Update wizard,"In case Node.ACS CLI is not installed on the machine, then we would like to defer its installation until it is actually required. So, we should not prompt to install during the update wizard dialog either during the startup or even if the user check for updates. However if it is already installed on the machine, then we do need to check for its updates.",5,test +TISTUD-7015,Studio creates android L x86_64 bit emulator rather than an arm emulator by default if no emulator exists,"h5.Description: 1. You should have android L sdk installed. 2. Make sure you should not have any android emulators in the avd manager. 3. Launch appcelerator studio. 4. Now goto avd manager & check the default emulator created. h5.Actual result: 1. The android L x86_64 bit emulator is created by default. This should be avoided as this emulator has some issues on getting stuck on black screen & need some setting tweaks to make it work. Also it has a dependence on HAXM. 2. In the studio logs we see studio runs this command to create an avd: {code} ""/Users/lokeshchoudhary/Desktop/android-sdk-macosx/tools/android"" ""create"" ""avd"" ""-n"" ""titanium_1_WVGA800"" ""-t"" ""9"" ""-s"" ""WVGA800"" ""--abi"" ""x86_64"" ""-f"" ""-c"" ""/Users/lokeshchoudhary/.titanium/titanium_1_WVGA800.sdcard"" ""-c"" ""128M"" {code} h5. Expected Result: 1. An arm or other x86 emulator having no dependencies or issues is created.",5,test +TISTUD-7018,Yosemite: Node.ACS update is not listed in Studio update wizard,"When *acs* is installed through the studio update wizard, it's not listed in update components list. Please refer the attached screenshots to see the difference between OSX10.10 and 10.9.5 *10.10.png* : Screenshot from OSX 10.10 with 3.4.0 GA live-stack *10.9.5.png* : Screenshot from OSX 10.9.5 with same 3.4.0 live-stack h5. Steps To Reproduce 1. Uninstall ACS from your machine 2. Open Studio 3. Check for Appcelerator Updates h5. Actual Result Studio doesn't list the node.acs component in update list, but release notes are correctly displayed. h5. Expected Result Studio should list the acs component in update list. 10.10.png and 10.9.5.png should be identical. ",8,test +TISTUD-7026,Breakpoint doesn't hit for Node.ACS services with Alloy/Classic Apps,Breakpoint doesn't not hit for Node.ACS services added with Alloy/Classic Apps. Note: This is *not a regression* since same issue occurring 3.3.0 GA as well. h5. Steps To Reproduce 1. Create an Alloy/Classic Project 2. Add the Node.ACS Service 3. Insert a breakpoint in acs/.../app.js in a reasonable location 4. Debug the Service h5. Actual Result Breakpoint doesn't hit for any scenario. h5. Expected Result Breakpoint should hit as usual.,5,test +TISTUD-7028,Studio needs to handle environments that may not have ACS/Node.ACS urls,"This ticket is to encapsulate any changes needed by Studio to support APPTS-6273. Some environments may not have an ACS/Node.ACS, so the Studio use cases should take this into account.",8,test +TISTUD-7032,The default size of modules table in tiapp is reduced,"After the fix for TISTUD-7018, the size of the tiapp modules table depends on the number of added modules. If there are no modules, then the size is shrinked, and if we add more than 6 modules, then it overflows. The tiapp modules table has to set a default size (as earlier) and as number of modules in the table increases, user should be able to scroll through the list.",5,test +TISTUD-7034,Appcelerator Studio: Preproduction - Test Service fails to enable first time after creating an app,"Appcelerator Studio: Preproduction - Test Service fails to enable first time after creating an app Steps to Reproduce: 1. Create an application in Appcelerator Studio(Classic or Alloy) and enable the services. 2. Error message pops up saying ""Enablement failed for Test Service. Contact an IT administrator to enable services"" All other services were enabled successfully. Once the app is created, clicking in ""Enable Service"" again enables the test services successfully. Actual Behavior: Test service is not getting enabled the first time for an app. Once the app is created, clicking on ""Enable services"" enables the test services successfully Expected Behavior: Test service should get enabled the first time without clicking on ""Enable services"" again Attaching the studio log and screenshot for reference",5,test +TISTUD-7039,Studio -> tiapp.xml -> Button Icons for Platform Configurations are not visible,"Open tiapp.xml - next to the platform checkboxes, notice that the wrench icons that the user can click to open up the platform configuration dialogs are not visible. However if you click around, you will see that in some cases they exist, but are just hidden.",8,test +TISTUD-7043,Memory Leak with repeated debugging android app on device,"If we attempt to debug a mobile app onto android device repeatedly, then there is a leak in Studio. The processes (so called daemon thread - Output stream monitor) that are created as part of debug session are terminated even though the launch is terminated. This can impact the performance of Studio process (or also, consume memory issues) as these threads are hanging in.",8,test +TISTUD-7044,Alert users they will need to install Android SDK 21 to use Titanium SDK 3.4.2,"Titanium SDK 3.4.2 brings a requirement to use Android SDK 21 as the ""targetSDK"" We should prompt users to install that version (if they have not), and perhaps display a warning/error join the tiapp..xml",8,test +TISTUD-7051,Windows: Uninstaller - The uninstaller does not remove upgraded files from AppcStudio directory,"*Details:* If you are on the AppcStudio RC/nightly stream, continually update your AppcStudio on the RC/nightly stream, then the uninstaller will not remove all the files. *Note:* One workaround is to manually remove all files from: C:\Users\\AppData\Roaming\Appcelerator *Steps to reproduce:* 1. Download and install AppcStudio; make sure it is pointing to the RC or nightly stream 2. Update the AppcStudio on the RC or nightly stream 3. Next, uninstall the current version of AppcStudio via Control Panel > Programs and Features 4. Install AppcStudio version GA; from the wild 5. Next, update AppcStudio either on the RC stream or on stable stream (new build) *Actual:* You will not be able to update your AppcStudio; see attachments. *Expected:* Uninstalling AppcStudio from Windows should remove all files.",8,test +TISTUD-7052,Need to update release notes style sheet to hide edit button,"An edit button was added to the guides pages on the docs website. Since Studio is overriding the style sheet from the docs website, need to add the following lines to hide the Edit button when Studio displays the Studio Release Notes page: {code} #editButton { display: none; } {code}",5,test +TISTUD-7053,"Internal error ""Index out of bound"" creating a new project and editing tiapp.xml","h5. Problem description Internal error ""Index out of bound"" is thrown when creating a new project from Studio. h5. Steps to reproduce 1. Create a new project (both Alloy or Classic) from Appcelerator Studio Result: project is created but an internal error is thrown. 2. Dismiss the error and edit tiapp.xml Result: error is shown again. Tiapp.xml editor presents display issues. See screenshots and log file attached.",3,test +TISTUD-7055,Toolbar: Border - A black border is appearing underneath the toolbar,*Details:* A black border is appearing underneath the toolbar. *Note:* This is a *regression* since the black border does not appear in GA AppcStudio (3.4.1.201410281743) on Yosemite 10.10.1; see ga_appc_studio.png. *Steps to reproduce:* 1. Open AppcStudio 2. Check underneath the toolbar *Actual:* A black border appears underneath the toolbar; see new_studio.png. *Expected:* A black border should not appear. ,5,test +TISTUD-7056,Appcelerator Studio Android Package does not retain entered values,Appcelerator Studio Android Package does not retain entered values Subsequent packaging requires me to continually re enter: Keystore location Keystore Password Key Alias iOS packaging is OK and does resin previously entered information (see screen shots),5,test +TISTUD-7057,Dashboard on First Run needs to pop-up much faster,"When loading up studio for the first time, the dashboard can take several seconds to load and during that time the user is staring at a blank screen. We should be optimizing this flow so that as studio opens the dashboard is immediately visible",8,test +TISTUD-7061,'Mobile web preview in emulator' display issue in the device list menu ,h5. Problem description Visualization issue in the device list menu for the 'Mobile Web preview in emulator'. 1. Select a project 2. Choose 'Run' and select a target device. Result: 'Mobile Web preview in emulator' entry is displayed incorrectly. See screenshot. ,3,test +TISTUD-7066,Runtime error with Studio-generated function event handlers,"Steps: 1. Create a new Alloy project. 2. Open views/index.xml and add a new Label element (e.g.) with an event hander that specifies a function that doesn't exist in the controller, e.g. {{}}. 3. Press Cmd+1/Ctrl+1 to open the 'Create event listener in controller file' dialog and press Enter to create the new handler. 4. Save all files and build for simulator/device. Results: Runtime error, ""Can't find variable fooBar"" (ios) or ""fooBar is not defined"" (Android). Expected: No runtime error with generated event handler. One fix is to add {{var}} before the function statement: {code} // this var blah = function(e) { }; // instead of this blah = function(e) { }; {code} Or, to be consistent with the default Alloy template's {{onClick}} handler: {code} function fooBar(e) { } {code}",3,test +TISTUD-7067,Using git to push to a remote branch other than master results in error,"When working with a project that is leveraging git as source control to a remote repository, you are unable to push to a remote branch other than master. * Add a new project from a project on github. * Create a new branch (check track) * make sure your project is currently selected to the branch you just created * Make changes to your project * commit the changes * attempt to push the changes from studio note the error in the console: fatal: The upstream branch of your current branch does not match the name of your current branch. To push to the upstream branch on the remote, use git push . HEAD:master To push to the branch of the same name on the remote, use git push . ",5,test +TISTUD-7068,Studio: The link for getting new iOS certs is invalid,"h5. Description Currently the link for the 'Get New...' button in Preferences->Studio->Platforms->iOS points to a dead link, the updated link should be https://developer.apple.com/account/ios/certificate/certificateList.action h5. Steps to reproduce 1. In Studio go to Preferences->Studio->Platforms->iOS 2. Click 'Get New...' h5. Actual Result When the web browser loads I am shown Access Denied h5. Expected Result I should be taken to the Apple website where I can create a new cert, the link is above.",2,test +TISTUD-7076,Improve the build command passed by Studio to the CLI,"h5.Description An example of the command used by Studio is as follows {code} ""/usr/local/bin/titanium"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""build"" ""--platform"" ""iphone"" ""--log-level"" ""trace"" ""--sdk"" ""3.6.0.v20141201145716"" ""--project-dir"" ""/Users/eharris/Documents/Appcelerator_Studio_Workspace/TIMOB17350"" ""--target"" ""device"" ""--ios-version"" ""8.2"" ""--device-family"" ""universal"" ""--developer-name"" ""QE Department (C64864TF2L)"" ""--device-id"" ""f8052c8714f0b9585a8f89274f447bbd4eda1601"" ""--pp-uuid"" ""f0a56225-0b09-4694-aecd-630953506ca6"" ""--skip-js-minify"" ""--skip-js-minify"" {code} As we now show the users in Studio the command used this should be improved to remove any unnecessary flags and use the correct values. For example the second ""\-\-skip-js-minify"" should be removed and use ""\-\-platform"" ""ios"" instead of ""--platform"" ""iphone"" h5.Steps To Reproduce 1. Build a project for iOS 2. Check the Studio logs for the command, or if using the latest SDK from master branch Studio will print the logs for you in the console ",3,test +TISTUD-7085,Samples: TiApp.xml of Studio samples doesn't set with latest stable SDK release version,"tiapp.xml of studio samples doesn't set with latest GA SDK version. As of now, they all should have 3.4.1 GA version as its tiapp.xml value. Following is the list of SDK versions of Samples || || Sampes || SDK version || | (x) | Todo List - Alloy | Highest available in local machine () | | (/) | Todo List - Classic | 3.4.1 | | (x) | RSS Reader - Alloy | Highest available in local machine | | (x) | RSS Reader - Classic | Highest available in local machine | | (/) | KitchenSink | 3.4.1 | | (x) | Geocoder - Alloy | 3.3.0 | | (/) | Geocoder - Classic | 3.4.1 | | (x) | FieldService - Alloy | 3.3.0 | *Note:* Interesting thing is, some of the samples are containing (saved) the highest SDK version from the local machine which is imported to. h5. Steps To Reproduce 1. Import the samples from Studio 2. Open tiapp.xml file 3. See the SDK version from xml file h5. Actual Result Highest available (on the local machine) is saved in tiapp.xml file. In my machine, it's 3.5.0.v20141212180914. h5. Expected Result It should contain latest stable SDK version. As of now, it should be 3.4.1 GA",5,test +TISTUD-7087,Remove call to Dashboard api/v1/user/trial endpoint,"Trials as a concept is being removed from Dashboard for its 3.0.0/On-Demand release. Studio is calling the api/v1/user/trial endpoint to retrieve information about the org's trial status. For the time being, it will return a benign payload, but the call to it should eventually be removed.",3,test +TISTUD-7096,Migrate the required JSON classes from socketio into jackson,"As the JSON references are spread out everywhere, we need to consolidate all the required classes from socketio into json.simple. Also, we need to refactor the referencing classes to make sure they point to json.simple now.",8,test +TISTUD-7097,Migrate the serialization functionality into json.simple,"Indexing functionality heavily use the serialization and de-serialization of the JSON objects such as .fromJSON(..) and .toJSON(..). We need to migrate the specific classes to json.simple and make sure it reference only json.simple, for json specific changes.",8,test +TISTUD-7098,Consolidate JSON parse into a single method interface,"Currently JSON.parse() returns either JSONObject, Object, or Map<> from different plugins. Since we are consolidating all of those JSON classes, we should have only one parse() method, that should possibly return a Object, which can be casted to JSONObject, or JSONArray. Then, utility methods should be provided to convert the JSONObject into Map<>.",8,test +TISTUD-7108,Build packages plugin bundle through Jenkins,"The packages installer provides an ability to add plugins, in order to handle the pre-requisites of Studio. Building the packages plugin from XCode takes a couple of seconds now. - Find out the command to build the packages plugin to integrate into installer. - Add a jenkins job to build the plugin bundle.",8,test +TISTUD-7109,Build packager for Mac native installer,"- We already know the location of the Studio payload, but we need to pass in the payload location to the packager build command to include before it is build. - Find out the command required for building the packer (mac native installer) - Integrate the command into Jenkins, to build the mac native installer. ",8,test +TISTUD-7110,Include resources to packager installer build,The packager (mac native installer) has to be included with the resources/images required to display the installer UI. The jenkins job has to make sure that the required resources are added to the packager before the installer is build.,5,test +TISTUD-7111,Sign mac native installer after it is build through jenkins,"The mac native installer (packager) will be build through Jenkins job. Once it is built, we need to sign the installer, similar to the way we are currently signing the Studio application.",5,test +TISTUD-7112,Allow to install Studio silently on Mac,"The Mac native installer currently opens up UI to let user go through different stages such as configuring destination/disk, handling pre-requisites, license agreements and finally showing the progress for installing Studio payload. Add the ability to let to install Studio on mac through command line silently. Customers should have a command with a few options/flags to let Studio and its prerequisites installed silently.",5,test +TISTUD-7119,Changing the default android emulator does not get saved in android preferences,"h6. Not sure if its a regression as I don't have studio 3.4.0 to check. h5.Description: 1. In appc studio go to preferences/ android. 2. Note that the ""default emulator"" field is set to the first available value. 3. Now change the default emulator using the dropdown to some other emulator. 4. Click apply & OK button to close the preference window. 5. Now again go to preferences/android & check if the new default emulator value is saved. h5.Actual Result: 1. The new default emulator value does not get saved & it reverts back to the first available value. h5.Expected Result: 1. The new default emulator value should get saved.",3,test +TISTUD-7122,Improve UI of Installer prerequisites plugin,"As per feedback from Neeraj the following issues will be handled through this ticket 1.Node and Java should appear on next lines (as a column) and show the progress indicator next to each other. After installation, show a green check mark. 2. If all pre-reqs are already installed, then skip showing prereqs page.",8,test +TISTUD-7123,Samples: Alloy Geocoder sample SDK is set to 3.3.0.GA,"h5.Description When importing the Geocoder Alloy sample app the SDK is set to 3.3.0.GA, when importing all the other samples the SDK is set to 3.5.0.GA, or the latest SDK. h5.Steps To Reproduce 1. In Studio import the Geocoder Alloy sample app 2. Open the tiapp.xml and check the Titanium SDK setting h5.Actual Result The SDK will be set to 3.3.0.GA h5.Expected Result The SDK should be set to 3.5.0.GA",8,test +TISTUD-7125,Handle Node and JDK installation through silent installer on Windows,"The Windows installer already handles the silent installation of Appcelerator Studio using the below command {code} ""C:\Users\User\Downloads\Appcelerator_Studio.exe"" /qn {code} However, it does not install the pre-requisites such as Node during the silent installation of Studio. We need to handle a special case for installing Node as part of silent installation.",8,test +TISTUD-7126,Handle JDK installation with the silent installer on Windows,"The Windows installer already handles the silent installation of Appcelerator Studio using the below command {code} ""C:\Users\User\Downloads\Appcelerator_Studio.exe"" /qn {code} However, it does not install the pre-requisites such as JDK during the silent installation of Studio. We need to handle a special case for installing JDK as part of silent installation.",8,test +TISTUD-7127,Handle Node installation with Mac silent installer,"Running the Mac native installer in silent mode does not install the pre-requisites such as Node along with the Appcelerator Studio payload. A pre-install script has to be added to the installer script to take care of detecting and installing NodeJS, as part of configuring prerequisites.",8,test +TISTUD-7128,Handle JDK installation with the Mac silent installer,"Running the Mac native installer in silent mode does not install the pre-requisites such as JDK along with the Appcelerator Studio payload. A pre-install script has to be added to the installer script to take care of detecting and installing JDK, as part of configuring prerequisites.",8,test +TISTUD-7129,Install JDK and Node through one sudo prompt,Install JDK and Node through one sudo prompt by calling into the AuthorizationExecuteWithPrivileges system level API. Also customize the sudo prompt message and the icon. ,8,test +TISTUD-7132,Cleanup downloading prerequisites with Mac Native installer,We have noticed a couple of problems with the Mac native installer and need to address them: 1. Files downloaded to temp folder should be cleaned up after installation completes 2. Download should use a buffer and flush mechanism (particularly to handle download of large files).,5,test +TISTUD-7133,JS content assist does not show dotted properties in new-statements,JS content assist does not show dotted properties in new-statements. Technically this is *not a regression* since 3.4.1 GA also shows the same behavior. But 3.4.0 GA Release works as expected. h5. Steps To Reproduce 1. Create a classic default app 2. Paste the following code in app.js file {code} var com = { aptana: { myFunction: function() {} } }; var invoke = com.aptana.myFunction(); var instantiate = new com. {code} 3. Place your cursor at the end of line 8 in app.js file 4. Press Ctrl+Space shortcut h5. Actual Result Content-assist is not open. It's just placing the word *prototype* instead of opening several suggestions in content-assist. h5. Expected Result Content-assist window should open. It works fine in 3.4.0 GA release. ,8,test +TISTUD-7135,Make the Windows installer UI consistent with Mac installer,"Since we have finalized on the design on the Mac native installer, we would like to have the Windows installer UI consistent to Mac installer. [~tsmalley] has suggested and provided a few prototypes for the Windows installer and the designs are attached. We need to incorporate those designs into Windows installer. In order to achieve this, the dialogs in the Windows installer should be customized to allow the logos and the coloring scheme similar to the prototypes.",8,test +TISTUD-7137,AppceleratorStudio: There is no icon of the Appcelerator Studio at Apps Screen nor the main Screen at Windows 8.1,"h4. Problem Description After installing Appcelerator Studio in Windows 8.1 Pro, you won't find an icon of the software at the Apps screen nor the Main Screen. You will have a direct access link at the Windows Desktop, but without an actual icon. ",5,test +TISTUD-7141,Run Configuration's 'Common' tab not present for devices,"When looking at the run configurations for simulators and devices. The 'Common' tab on the right side is missing from devices, but is present for simulators. *Steps to reproduce issue*: 1. Open Studio 2. Open run configurations 3. Select a device's run configuration 4. Notice that the 'Common' tab is not present on the right side (next to Main) *Expected Result*: The 'Common' tab is present and configurable",3,test +TISTUD-7144,Allow Studio dashboard to dynamically inject samples into Studio.,"Currently, the samples should be contributed either through extension points, or added through rubles during startup, or added through alloy samples output. However, based on the user login, if the dashboard would like to inject samples from the user github or gitio, then there is no way to access the sample. We need to add a provision in Studio to let dashboard inject samples.",5,test +TISTUD-7149,Windows: Cryptic error message in tiapp.xml editor that needs to be reworded,"As shown in the attached screen, hovering over the error indicator for the ""windows"" key in the list of deployment targets shows a confusingly worded message: ""is not facet-valid with respect to enumeration"" means what?? This should be clarified and simplified to something like: ""Value 'windows' is not a valid platform. Supported values include: ..."" Also, what is ivi and why is it in the list of supported platforms?",3,test +TISTUD-7171,Studio: Existing versions of Appcelerator and Titanium Studio are unable to create a project with an SDK greater than 4.0.0,"h5.Description When attempting to create a project using Ti SDK version 4.0.0.v20150203133250 the project creation fails with the error. *The requested SDK version does not have an assigned commands-handler* When looking in the logs there is no logging that seems related to the project creation, When attempting to create the project from the CLI, the project is created successfully. *This means that every existing installation of Studio will break. A user must upgrade to the 4.0.0 version of Studio if they wish to develop applications with an SDK greater than 4.0.0* h5.Steps To Reproduce 1. Install the latest SDK using *ti sdk install -b master -d* 2. Attempt to create a project using Studio 3.4.1 *or* 3.5.1 h5.Actual Result The project creation will fail with *The requested SDK version does not have an assigned commands-handler*. h5.Expected Result The project should be created with no errors.",5,test +TISTUD-7172,Studio: Visual change in the Studio GUI in version 4.0,"h5.Description After upgrading to Studio 3.5.1.201501281610, there is a significant change between the previous version(3.4.1) and the new version. The changes I see are * The font used for text has changed * There is now a black bar between the buttons at the top of the screen and the text editor/project panels. * The background color has changed * Buttons have moved around at the top of Studio * Tabs are different I have attached a screenshot of the previous and new version of Studio for comparison h5.Steps To Reproduce 1. Install Appcelerator Studio beta from http://preview.appcelerator.com/appc-studio/ 2. Open Studio and observe h5.Actual Result There are changes in the UI of Studio h5.Expected Result ",5,test +TISTUD-7174,Studio: Mac: Options relating to Windows projects appear in Studio on Mac,"h5.Description When creating a project in Studio on Mac the option is given to create a Windows project. As with iOS applications on Windows this option should not be given. The option is greyed out so it can't be selected, if you hover over it then a dialog appears saying that *Titanium SDK does not support the Windows platform* There are also Windows related UI elements in the tiapp.xml, both the modules table and the deployment targets contain Windows as well as Preferences->Studio->Platforms->Windows h5.Steps To Reproduce 1. In Studio 3.5.1 create a new Alloy or Titanium project. 2. Click next to get to the screen where you enter information. h5.Actual Result The option for Windows will be present but not able to be selected. h5.Expected Result The option for Windows should not be present.",3,test +TISTUD-7180,Studio: Windows: Unable to update Studio to 4.0.0,"h5.Description When attempting to upgrade Studio from 3.4.1 or 3.5.1 to 4.0.0 using [this update link|http://preview.appcelerator.com/appcelerator/appc-studio/standalone/update/beta/], Studio throws the error *Appcelerator Studio updates has encountered a problem* I have attached the log files a studioLogs.txt. After talking to Praveen it is due to having the Windows Plugin installed on the system. To workaround this I just uninstalled Studio and then re-installed it and it works fine. h5.Steps to reproduce 1. From Studio upgrade to the nightly builds by adding [this link|http://preview.appcelerator.com/appcelerator/appc-studio/standalone/update/beta/] to Preferences->Install/Update->Avaliable Sofware Sites 2. Update Studio by Help->Check for Appcelerator Updates h5.Actual Result Studio does not update and errors with *Appcelerator Studio updates has encountered a problem* h5.Expected Result Studio should update with no errors",3,test +TISTUD-7186,Would be nice to be able to associate a file with a source editor,"In node, we have scripts that are in JS for /bin but studio thinks they are plain text and doesn't do proper JS code editor for them. In Sublime, you can just associate the file as a specific type (in this case, Javascript). Would be nice if there was a way to do this in Studio.",8,test +TISTUD-7187,Improve JS editor performance in taking the user input,"If a user try to type keys very fast in the JS editor, then there is a lag in showing up the text on the editor. However, if anyone type the keys with the same speed on any other editor, then there is no lag in the keys showing up in the editor. We need to figure out whether Studio/Eclipse is doing any background work as soon as user started typing on the editor, to narrow down the root cause of the performance impact.",8,test +TISTUD-7191,Mac Installer: Layout of the prerequisites are overlapped when going back and forth the installer steps,"Prerequisites: no java 1.7 and node.js should be installed in the computer. The installer has several steps and when it comes to prerequisites it prompts node and java1.7 to be installed if you click 'continue' the display of the progress of download is fine. However, instead if you go back and forth the steps in the installer, then the words and progress of the download of node and java overlaps as shown in the attachment. Steps to reproduce: 1.Download the studio installer for OS X 2. Open the appcelerator studio package to install studio 3. Click continue until you hit the 'prerequisites' step 4. Click 'back' button in prerequisites step 5. Click continue again to go to prerequisites page 6. Click on continue Actual Results: 2. Installer UI opens up 3. Prerequisites page is shown with Java and node to be installed 4. 'Installation type' is shown 5. Prerequisites page is shown with Java and node to be installed 6. The installation starts however the display of the progress is overlapped with the words as shown in the attachment Expected Results: 6. The words and the progress bar for both node and java should not be overlapped. Note: If you do not go back and forth the overlap of the words and the progress bar does not happen. ",8,test +TISTUD-7196,Mac Installer: Cancel button should be included to allow the user to terminate installation once it has started,"Once the download of the prerequisites or studio starts there is no way to stop the installation. * For the prerequisites, all the buttons are disabled once the downloads starts and hence it cannot be terminated. * For the studio, once the installation starts only the back button is enabled which allows the user to go back to the previous steps but no option to cancel installation unless force quit is attempted. So it would be good to have a cancel button to allow the user to terminate download once it has started. ",5,test +TISTUD-7198,Cannot install update to Studio: Backup of version.txt failed,"When attempting to update Studio I am greeted with the below error. Studio says the update is complete, but no change is observed. {code} Error encountered during update An error occurred while uninstalling session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]com.appcelerator.titanium.feature.360.rcp_root 4.0.0.201502041613-877VFA2FF6gOdqiNOLPdbdZOOBWh --> null, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction). Backup of file /Applications/Appcelerator_Studio/version.txt failed. File that was copied to backup could not be deleted: /Applications/Appcelerator_Studio/version.txt {code} *Steps to reproduce issue*: 1. Open Studio 2. Check for Appcelerator updates 3. Attempt to install updates 4. Witness the above error *Expected results*: I am able to install the update without error *Notes*: Please see the attached screenshot of the error, as well. Initial investigations of the issue pointed to a permission issue between the 'sudo install' process and the non-elevated permissions during updates.",5,test +TISTUD-7208,Remove Blackberry from Studio,"Studio 4.0 or higher versions should not support any BlackBerry functionality, even with previous Titanium SDKs.",5,test +TISTUD-7209,Studio Platform Configuration broke Android SDK setup,"h5. Problem description Appcelerator Studio 'Platform Configuration' tab appeared after installing Appcelerator Studio from scratch, then eventually breaking Android SDK setup. This issue has been encountered once and I'm currently not able to reproduce. It might be an intermittent issue. h5. Steps performed 1. Download and performed a new installation of Appcelerator Studio 4.0.0.201502111458 (64bit zip) 2. Launched Studio, performed the login and choosed the same workspace used for previous installed versions Result: Appcelerator Studio 'Platform Configuration' tab appeared, even if both iOS and Android platforms were correctly installed and Android SDK location was correctly detected. As also showing in the attached screenshot, the Android SDK Location is detected, however the ""No Android SDKs were found under the specified SDK location"" text appears. Also, Android SDKs installed versions are detected (note: Android platform checkbox was selected too). 3. Clicked on configure Result: Next screen appeared showing correct versions installed and clicked on finish. However, from then on, Android SDK was no longer recognized or found under the specified SDK location 4. From CLI, do ""ti info"" Result: an error relative to Android SDK is displayed: {code} fcasali-MBP:~ fede$ ti info Titanium Command-Line Interface, CLI version 3.6.0-dev, Titanium SDK version 4.0.0.v20150217154015 Copyright (c) 2012-2014, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ / /usr/local/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:185 throw e; ^ TypeError: Invalid Version: android.0.0 at new SemVer (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:273:11) at compare (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:460:10) at gte (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:509:10) at cmp (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:526:22) at Comparator.test (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:599:10) at testSet (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:922:17) at Range.test (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:914:9) at Function.satisfies (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/node_modules/semver/semver.js:935:16) at /Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/node-appc/lib/version.js:156:33 at Array.some (native) --------------------------------------------- at async.setImmediate (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/async/lib/async.js:96:15) at /Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/async/lib/async.js:696:21 at Array.forEach (native) at _each (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/async/lib/async.js:32:24) at _insert (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/async/lib/async.js:681:11) at q.push (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/async/lib/async.js:708:15) at async.parallel.sdk (/Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/titanium-sdk/lib/android.js:92:10) at /Users/fede/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.v20150217154015/node_modules/async/lib/async.js:524:25 {code} 5. Open android SDK folder / build-tools Result: I had in there an invalid ""android-4.4.2"" folder. Removing it, fixed the problem - both in Studio and in CLI. h5. Note I'm not able to reproduce the Configuration Panel being shown when starting up Studio, therefore right now a new Studio installation works as expected, also changing workspace or deleting Android SDK entries in Studio /configuration/.settings/com.appcelerator.titanium.rcp.prefs file. Keeping an eye open and tracking any further information in this ticket. ",8,test +TISTUD-7210,Create Release Notes Provider for Appcelerator Unified CLI,As access to CHANGELOG.md will be restricted for the appc-cli project we need a different mechanism(other than github) to read release notes .. probably from a different uri ,5,test +TISTUD-7231,Mac Installer: java 1.7 does not get saved even though it shows successful installation,"When there is no java 1.7 installed in the path: /Library/Java/JavaVirtualMachines, the mac installer prompts the user to download java1.7 as a prerequisites. However, java 1.7 does not get saved in this path even though the installer shows successful installation of java. When you try to install studio again using the installer, it again prompts the user to download java 1.7 The beta version 4.0.0.201502111458, was working fine and java got successfully installed. Steps to reproduce: No java 1.7 should be installed in the computer 1. Download the installer 2. Click next to go to the prerequisites page 3. Click next 4. Type system password and then the installation of studio starts 5. Go to the following file path ""/Library/Java/JavaVirtualMachines"" 6. Start the installation process again Actual Results: 1. Installer downloads successfully 2. Prerequisites page shows java 1.7 to be downloaded 3. Java 1.7 installation starts and shows a progress bar, once the installation is 100% prompts the user to type system password 4. Once the installation is completed, a successful installation message is displayed. 5. No java folder is found 6. Installer prompts user to download java 1.7 again Expected Results: 5. java 1.7 folder should be found 6. installer should detect the previously installed java 1.7 and should not prompt the user to install it again",5,test +TISTUD-7232,Windows Installer: Installer does not prompt to download JDK 1.7 when 1.6 is installed,"When java 1.6 is already installed in the computer, the installer does not prompt the user to download 1.7. Only when the version of java is below 1.6, the installer downloads java1.7 as a prerequisites. Hence, the minimum java version has to be brought up to 1.7 to be consistent with the mac installer Steps to reproduce; Java 1.6 should be installed 1. Download the installer 2. Launch installer Actual Results: 1. Installer downloads successfully 2. Installer starts the download for studio as it has found all the prerequisites. Expected Results: 2. The installer should first prompt the user to download java 1.7 as a prerequisites, even though java 1.6 is already installed.",5,test +TISTUD-7233,Import any folders as project by drag and drop onto Project Explorer,"After TISTUD-7184, We have an ability to import an existing projects by drag and drop onto explorer. However, we need to address the case if the user wants to import a non-eclipse project using drag and drop. Since we need to create a .project file to convert it as Eclipse project, we can give an option to the user whether they would like to link the project or copy it (as they might not have write permissions on the project folder).",8,test +TISTUD-7234,Latest Beta OS X Installer Shows silent_installer folder,Reproduction: Download and launch the latest Beta installer from the preview site (Beta - 4.0.0.201502181719). Actual Results: The Installer dialog displays the silent_installer folder and PKG file. See attached screen shot. Expected Results: Should only display the PKG file.,8,test +TISTUD-7243,Mac Installer: Pre-requisite shows as installed even on cancel of system password prompt,"Steps to Reproduce: 1. Remove Node and Java from the system if present 2. Start installing Appcelerator Studio using the 64-bit Mac installer 3. On the pre-requisite screen, the Node.js and Java are shown for installation. Click on continue. It start to download and install Node.js and Java 4. For installation of the prerequisite the prompt for system password is shown. 5. Click on Cancel button in the prompt Actual Result: The prerequisite does not get installed but is shown as installed in the installer. The installer then continues to install the studio. Expected Result: The prerequisite should be shown as not installed.",5,test +TISTUD-7244,Mac Installer: The installer crashes when system password prompt is cancelled for node.js install,"The mac installer crashes when the system password prompt is cancelled while installing Node.js through the installer. This happens only when the current logged in user has admin rights on the system. For non-admin user it does not crash and wrongly shows Node.js as installed. Another ticket is already logged for that. Steps to Reproduce: 1. Remove Node from the system if present 2. With an admin user login, start installing Appcelerator Studio using the 64-bit Mac installer 3. On the pre-requisite screen, the Node.js are shown for installation. Click on continue. It start to download and install Node.js 4. For installation of the Node.js the prompt for system password is shown. 5. Click on Cancel button in the prompt Actual Result: The installer crashes. Refer to the attached screenshot and the logs. ",5,test +TISTUD-7249,"On First Load of Dashboard, dispatch function is not detected","when opening studio, the initial dashboard load does not detect the dispatch function. Subsequent loads of the dashboard detect it fine. ",5,test +TISTUD-7251,Nightly: Update - Cannot update to the nightly builds from Appc Studio GA to use the Arrow integration,*Details:* Cannot update to the nightly builds from Appc Studio GA to use the Arrow integration. *Steps to reproduce:* 1. Make sure you are pointing to the nightly stream: http://preview.appcelerator.com/appcelerator/appc-studio/standalone/update/nightly/ 2. Go to Help > Check for Appcelerator Updates to get the nightly build *Actual:* Cannot update to the nightly build and the following error appears: {code} Error encountered during update Operation details Cannot complete the install because one or more required items could not be found. Software being installed: Appcelerator Studio 4.1.0.201503110244-11032015024520 (com.appcelerator.titanium.rcp.product 4.1.0.201503110244-11032015024520) Missing requirement for filter properties ~= $0: Eclipse e4 Rich Client Platform 1.3.100.v20140606-1445 (org.eclipse.e4.rcp.feature.group 1.3.100.v20140606-1445) requires 'org.eclipse.swt.cocoa.macosx [3.103.0.v20140605-2012]' but it could not be found Cannot satisfy dependency: From: Appcelerator Studio 4.1.0.201503110244-867dFEkFGvmPi8vnnwYKXm8ROBXH (com.appcelerator.titanium.feature.360.rcp.feature.group 4.1.0.201503110244-867dFEkFGvmPi8vnnwYKXm8ROBXH) To: org.eclipse.platform.feature.group [4.4.0.v20140606-1558] Cannot satisfy dependency: From: Appcelerator Studio 4.1.0.201503110244-11032015024520 (com.appcelerator.titanium.rcp.product 4.1.0.201503110244-11032015024520) To: com.appcelerator.titanium.feature.360.rcp.feature.group [4.1.0.201503110244-867dFEkFGvmPi8vnnwYKXm8ROBXH] Cannot satisfy dependency: From: Eclipse Platform 4.4.0.v20140606-1558 (org.eclipse.platform.feature.group 4.4.0.v20140606-1558) To: org.eclipse.rcp.feature.group [4.4.0.v20140606-1445] Cannot satisfy dependency: From: Eclipse RCP 4.4.0.v20140606-1445 (org.eclipse.rcp.feature.group 4.4.0.v20140606-1445) To: org.eclipse.e4.rcp.feature.group [1.3.100.v20140606-1445] {code} *Expected:* Should be able to update to the nightly build from Appc Studio GA.,8,test +TISTUD-7252,Windows: Installer: Appc CLI is not installed when installing Studio via the nightly Windows installer,"h5.Description When installing Appc Studio from the nightly stream on preview.appcelerator the install runs and shows no errors with the installation. However when attempting to open Studio and login the login fails. After looking into this it appears that although the NPM package for appcelerator is installed into the Appcelerator Studio location, Appc CLI is not actually installed onto the machine. When checking the install folder inside the .appcelerator folder there are no installs. I have installed the Appc CLI via command prompt and have managed to install it successfully, *please note* that to install via the CLI you will need to add an environment variable named APPC_ENV set to preproduction in order to get it to install properly, even with this it does not install fully from the Studio installer h5.Steps To Reproduce 0. Ensure you have no Appc CLI pre-existing on your system and delete Users\\.appcelerator 1. Download the nightly installer from http://preview.appcelerator.com/appc-studio/ 2. Install Studio using the .exe file 3. Check the install folder in Users\\.appcelerator h5.Actual Result There will be no Appc CLI installed in the installs folder h5.Expected Result Appc CLI should be installed in the installs folder of .appcelerator",5,test +TISTUD-7253,Studio does not pick Titanium SDK's from path set in preferences if default path exists,"This is a Regression as the issue does not exist in studio 3.4.2 and 3.4.1 If the path ~/Application Support/Titanium/mobilesdk/osx exists then the studio does not get the titanium SDK's from the Titanium SDK Home path set in studio preferences. Steps to Reproduce: 1. Ensure you have more than one titanium SDK version installed in ~/Application Support/Titanium/mobilesdk/osx 2. Create a folder anywhere in the system. 3. Inside the folder created in step2, create folders mobilesdk -> osx 4. Copy a titanium SDK version folder inside the OS X folder 5. In studio, go to Preferences -> Studio -> Platforms 6. Change the path of ""Titanium SDK Home"" to the folder created in step 2 7. Restart Studio. Upon restart, try to create a new titanium project. Check the list of SDK's available Actual Result: The list of SDK's shown would be those available in ~/Application Support/Titanium/mobilesdk/osx instead of those in the new created folder",5,test +TISTUD-7254,Improve license text for Appcelerator Studio stream-based updates,"h5. Description: When a user updates using the Studio streams, license text is displayed that is in all caps with strange language that refers to the customer as ""it"" {code} APPCELERATOR STUDIO SOFTWARE LICENSE AGREEMENT PLEASE READ THIS SOFTWARE LICENSE AGREEMENT BEFORE INSTALLING OR USING THE PRODUCT. BY INSTALLING OR USING THE PRODUCT, CUSTOMER SIGNIFIES ITS ASSENT TO THIS AGREEMENT. IF YOU ARE ACTING ON BEHALF OF AN ENTITY, THEN YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO ENTER INTO THIS AGREEMENT ON BEHALF OF THAT ENTITY. IF CUSTOMER DOES NOT ACCEPT THE TERMS OF THIS AGREEMENT, THEN IT MUST NOT USE THE PRODUCT. To read the complete software license agreement, please visit http://www.appcelerator.com/legal/eula/ {code} h5. Steps to reproduce: 1) Install using the Nightly version of the 4.1 Appcelerator Studio mac installer 2) Set the update stream to nightly 3) Check for updates 4) When the Appcelerator Studio update option is available, click on the line item to display the license text h5. Result: The license text is as show above h5. Expected Result: The license text matches the license text shown in the Mac installer version",3,test +TISTUD-7261,Mac Installer: Error while installing node.js pre-requisite,"Error while installing the Node v0.10.34 pre-requisite. Steps to Reproduce: 1. Remove node.js from the system 2. Start installing Appcelerator Studio using the 64-bit mac installer 3. At one of the steps during installation it prompts to install the pre-requisites. Hence it requires to install Node.js v0.10.34 4. Click on Continue to install pre-requisite. Actual Result: The installer downloads Node.js and starts to install it. Then it shows an error that installation of Node.js failed. However, if you check the node version from terminal it does install the node.js but v0.10.13 Refer to attached screenshots",5,test +TISTUD-7262,Load Dashboard Page first in Startup Order,"Currently we load the Studio Dashboard last in the startup order of the application. The end user behavior, is actually pretty poor as a result - you look at a blank space for quite some time as we check for updates etc. It would be better if we could load the Studio Dashboard first, and then check for any updates in the background.",5,test +TISTUD-7263,Studio Dashboard needs on offline state,"Right now - if studio is offline, the dashboard state provides a pretty poor experience (see screenshot attacehd). We need to enhance this so that users have at least some understanding of whats going on and not feel like studio is broken.",5,test +TISTUD-7282,"Studio: Improve text on password mismatch dialog to reflect ""password reset"" destination for provided link","h5. Description: When attempting to log in and a bad password/username combination is entered, a dialog can be presented that shows a dialog with a link. The states ""for more information click here"". When the link is clicked you are delivered to a platform page which allows a password reset. The URL is here: https://dashboard.appcelerator.com/#/auth/forgot The text should describe the password reset, since it does not provide ""more information"" h5. Steps to reproduce: 1) Do not point to preprod with an environment variable 2) Simulate a clean install (may not be needed) 3) Attempt to log in with bad credentials 4) Dialog appears, read text h5. Result: The text does not describe the link with enough detail h5. Expected Result: Something added after ""That username/password combination is incorrect"" that states ""To reset your password, click here""",3,test +TISTUD-7283,Studio Installer: Appc CLI installation text is different point size in mac installer,"h5. Description: The point size of the text for the Appcelerator CLI installer is smaller than the other installed item, Node.js. See attached screen h5. Steps to reproduce: 1) Simulate clean install 2) Run the mac installer 3) At the ""Prerequisites"" Step, note the font size h5. Result: The font size is smaller than other items h5. Expected Result: The font size matches other installed items",3,test +TISTUD-7284,Studio installer: Appcelerator CLI text prior to start of installation is cut off at the bottom,"h5. Description: When presented with the prerequisite pane in the Mac 64 bit installer, the ""Appcelerator CLI"" text has the bottoms of each ""p"" cut off as if the field is not tall enough for the text. See attached screen shot h5. Steps to reproduce: 1) Remove appcelerator CLI 2) run the installer 3) Navigate to the ""Prerequisites"" pane 4) Note the text h5. Result: The text is cut off h5. Expected Result: Normal text appearance",3,test +TISTUD-7289,Mac Installer: The installer prompts for install of app cli dependency even though its already installed,The mac 64-bit installer prompts for install of Appc Cli as the pre-requisite even though the Appc CLI already exists (installed manually or through the installer earlier) Steps to Reproduce: 1. Run the studio mac installer. Allow it to install Appc CLI during the installation process. or 1. Install the Appc CLI manually 2. Now again run the studio mac installer Actual Result: The installer prompts to install Appc CLI again even though it is already installed. ,5,test +TISTUD-7292,"Dashboard: On Windows, Dashboard throws error on load","When Dashboard loads, an error is shown in the console: {code} [""Unable to set property 'sdkInfo' of undefined or null reference"",""http://2b213d4307b7a1bb059a7858fe0671be12201b13.cloudapp-enterprise-preprod.appctest.com/?uid=null&id=5e5ce16d-2f8c-4382-9599-5826fa6ee372&v=4.0.0.201503191548&subscription=-1&ts=1426883535165&fg=000000&p=O&bg=ffffff&ch=f0f0f0&nl=en_US"",196] {code} *Steps to reproduce issue*: 1. Open Studio on Windows 2. Open the dashboard and have it load 3. Notice the above error in the console *Expected Results*: No error message is shown *Notes*: Issue could be causing sample's background images to not load. See related ticket.",5,test +TISTUD-7295,Appc Studio launched through download zip hangs on Configuration if no Node.js installed,"If Node.js is not installed and the user downloads the zip file for Appcelerator Studio, then upon launching it gets stuck on the splash screen while trying to perform configuration Steps to Reproduce: 1. Remove Node.js from the system 2. Download the 64-bit zip for Appcelerator Studio 3. Unzip it and launch the Appcelerator Studio Actual Result: The splash screen of Appcelerator Studio shows with Configuration process on it. The configuration continues to happen and does not proceed further. While testing gave it around 25-30 minutes before killing it. Find the attached logs",5,test +TISTUD-7300,"Studio is not detecting Appc Alloy install, only global. So templates for alloy not offered in new project wizard","h5. Description: No Alloy templates are available in new project wizard when no global alloy exists.I tried restarting studio to be sure, then installed alloy globally. After that the templates were available. h5. Steps to reproduce: 1) Launch studio with no global alloy installation 2) Try to create a new project in the wizard h5. Result: No alloy templates are shown h5. Expected Result: Alloy templates available",3,test +TISTUD-7301,Installer: Studio appears unresponsive while installing the Appcelerator CLI,"h5.Description When opening Studio for the first time on Windows if the Appc CLI is not installed then Studio will install it for the user. During this time Studio appears to be unresponsive as just the splashscreen is shown, on Mac a progress bar is shown with the text configuring. h5.Steps to reproduce 0. Ensure the Appc CLI is not installed on your system 1. Download the latest Studio installer for Windows from the beta stream on preview.appcelerator.com/appc-studio 2. Run the installer and install Studio 3. Open Studio, while Studio is fully installing the CLI it will appears unresponsive and provide no visual feedback h5.Actual result There is no visual feedback telling the user why Studio is taking so long to open h5.Expected result Studio should provide should some sort of visual feedback",5,test +TISTUD-7306,Login: When logging in Studio should not present two login dialogs,"h5.Description When I was logging into Studio I was entering my login info and during this Studio presented me with another dialog to login. See the attached image for reference. h5. Steps to reproduce *I am unsure of the steps to reproduce here as I believe it is a hard to reach scenario* 1. Log out of the Appc CLI 2. Open Studio h5.Actual result You will be prompted to login, sometimes you will be shown multiple login dialogs h5.Expected result Studio should only present one login dialog to a user",5,test +TISTUD-7313,"Installer: DMG background lists ""desktop"" as an option","See background image for incorrect text. We need to remove ""desktop"" as part of the text.",3,test +TISTUD-7314,Grab Release Notes from Platform docs instead of Titanium docs,"Since Titanium docs will not longer be updated, Studio needs to grab the release notes from the Platform docs. http://docs.appcelerator.com/platform/latest/#!/guide/Studio_Release_Notes Any links directing to http://docs.appcelerator.com/titanium should now point to http://docs.appcelerator.com/platform",3,test +TISTUD-7315,Samples will not build without platform GUID,"h5. Description: I was testing a fix to Kitchensink, and could not build due to what I assume is a non-platform GUID. I then tried the new Studio dashboard sample import and ran into the same problem: {code}[ERROR] : Application not registered. titanium exited with exit code 100{code} This issue will affect any application where the GUID is not in the new platform format. h5. Steps to reproduce: 1) Import a sample from the Studio dashboard 2) Attempt to build h5. Result: Build fails with error above h5. Expected Result: GUID generated from platform and used in app, build succeeds.",5,test +TISTUD-7316,Dashboard: Uncaught reference error on http://appc-studio.appcelerator.com/,"h5.Description On http://appc-studio.appcelerator.com/ if I open my console then I get Uncaught reference errors which increase every second originating from studio.js line 268, the code is the following {code} if(dispatch != undefined){ {code} I believe the code should be the following {code} if(this.dispatch != undefined){ {code} After some investigation with Praveen we believe this could be causing some crashes in Studio on Windows. h5.Steps to reproduce 1. In a web browser go to http://appc-studio.appcelerator.com/ 2. Open your web browser console h5.Actual result There will be uncaught reference errors in the console h5.Expected result There should be no uncaught reference errors in the console",2,test +TISTUD-7320,Mac Installer: The installer crashes while trying to install Node.js pre-requisite,"The 64-bit mac installer for Appc Studio crashes while trying to install Node.js. Steps to Reproduce: 1. Remove Node.js from the system 2. Run the studio installer 3. On the pre-requisite screen when it shows for installation on Node and Appc CLI, click on continue. The download of Node.js occurs. 4. Then to install the Node pre-requisite it prompts for a system password. Provide password and click Ok on the password prompt Actual Result: The installer crashes.",5,test +TISTUD-7321,Mac Installer: Error while installing Appc CLI pre-requisite,"The installer is not able to install the Appc CLI pre-requisite and shows an error. 1. Run the Studio 64-bit installer 2. On the pre-requisite screen when it shows for installation of Appc CLI, click on Continue. 3. Provide the system password on the password prompt Actual Result: An error is shown regarding failure to install. Refer to attached screenshot Expected Result: The installer should successfully install the Appc Cli pre-requisite ",5,test +TISTUD-7322,Error message for different error conditions during studio login are same,"The error message shown for different error conditions for studio login should be based on the error conditions. Currently the same message is shown. This is a regression as in earlier versions of Studio the messages were different for different scenarios. Steps to Reproduce: 1. Install and launch Studio. 2. On the login screen enter invalid credentials and click on Login or 2. With no network connection, enter credentials and click on Login Actual Result: The error message is always the same. Refer to attached screenshots for the message shown in 4.0 release and also the screenshot for different messages shown in 3.4.2 Studio Expected Result: The error messages should be more informative and based on the error condition",2,test +TISTUD-7331,The run button should have more left padding,"*Details:* Currently, the run button is at the left edge of Appc Studio; see attachment. *Expected:* There should be some left padding so the run button is aligned with the left border of Project Explorer pane.",3,test +TISTUD-7332,"When you click on the run button, the run button should indicate that you clicked on it","*Details:* Currently, if you click on the run button, there is no indication that the run button was clicked; see attachment. *Expected:* There should be an indication when the run button is selected.",5,test +TISTUD-7333,Remove entries related to unsupported platforms from all samples,"h5. Description: Kitchensink and geocoder samples have various entries in tiapp.xml related to unsupported platforms. From KS: {code} false false {code} AND {code} access_shared use_camera read_device_identifying_information access_pimdomain_contacts bbm_connect access_pimdomain_calendars access_pimdomain_messages read_geolocation access_internet access_location_services record_audio access_pimdomain_notebooks access_phone post_notification run_when_backgrounded access_sms_mms {code} From Geocoder {code} false false {code} h5. Steps to reproduce: 1) Import Gecoder or Kitchensink or other samples 2) Examine the tiapp.xml h5. Result: Unsupported platform content h5. Expected Result: No mention of unsupported platfroms",3,test +TISTUD-7337,Install Appc CLI through silent Windows installer,"As part of installation process of Windows silent installer, we need to install Appc CLI stub and package in silent/unattended mode as well in the pre-requisites check.",5,test +TISTUD-7338,Install Appc CLI through unattended Mac installer,Mac unattended installer should also install appc-cli stub and core package as part of its prerequisites check.,5,test +TISTUD-7341,Install Appc CLI package as part of Mac Installer,"Currently we only install Appc CLI stub/installer as part of Mac Installer. Once we install Appc CLI, we need to install Appc CLI core/package as well using the below command. {code} appc use latest {code}",3,test +TISTUD-7345,Move Location of Dashboard and LiveView Icons,right now the position of the Dashboard and LiveView icons in studio is very odd - they should be moved closer to the Run / Target dropdowns in Studio Toolbar. See image example,3,test +TISTUD-7354,Importing Samples into Appcelerator Studio is not changing guid or assigning org,"When importing sample applications either through Studio Dashboard or the Sample Editor, results in an orphaned application not associated to any org. Additionally this is most likely caused by the fact that the GUID is still all '1's ",5,test +TISTUD-7356,Failed to create parts controls message for file in deleted project,"If I delete a project in finder that has files open in Studio, the file has a ""failed to create parts controls"" message. *Steps to reproduce issue*: 1. Create a project in Studio 2. Open several files from that project 3. Close Studio 4. Delete the project in Finder 5. Open Studio *Actual Results*: The files are still open but have the above message and below details in it (see screenshot) *Expected Results* The file is no longer open in Studio as it no longer exists {code} org.eclipse.core.runtime.AssertionFailedException: assertion failed: at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1099) at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:607) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:366) at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:140) at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99) at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:321) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888) at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869) at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120) at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337) at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258) at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104) at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73) at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55) at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:983) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:766) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:737) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:731) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:715) at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1251) at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:66) at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4721) at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:218) at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81) at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59) at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$10.widgetSelected(StackRenderer.java:1035) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3110) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1794) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:283) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) {code}",3,test +TISTUD-7363,Update shows Code Analyzer version of 1.1.1-beta1 and has release notes of 1.1.0,"After installing Appcelerator Studio, build: 4.0.0.201504011425, I get a prompt for updates. In that list is the Code Analyzer which has a version of 1.1.1-beta1 and has release notes for 1.1.0. *Steps to reproduce issue*: 1. Install Appcelerator Studio, build: 4.0.0.201504011425 2. Open Studio 3. Wait for update window to appear or check for Appcelerator updates *Actual Results*: Code Analyzer is listed as version 1.1.1-beta1 and has release notes or 1.1.0 *Expected Results*: Version should be 1.1.1 and have release notes of 1.1.1",3,test +TISTUD-7380,Links on the studio dashboard are not responsive,"h5.Steps To Reproduce: 1. From the studio dashboard try to import samples & projects, create new project & play any videos. h5.Actual Results: 1. Nothing is responsive. No link works. h5.Expected Results: 1. The links on the studio dashboard should be responsive.",5,test +TISTUD-7385,LiveView sees (dot)files as languages,"If starting LiveView with simulator or on device. Both ends in this error Comment, if you need any further information {code} [LiveView] version 1.0.7 [LiveView] File Server Started on Port 8324 [LiveView] Event Server Started on Port 8323 [INFO] : Installing app on device: Sebastian's iPhone [INFO] : App successfully installed on device: Sebastian's iPhone [INFO] : Project built successfully in 1m 45s 157ms Please manually launch the application -- Start application log ----------------------------------------------------- [INFO] : Fantastic Library/4.0.0.0 (0.0.0.96875c9) [LiveView] { [Error: ENOTDIR, open '/Volumes/Data/Users/sebastian/Dropbox/lightapps/Develop/Fantastic Library 4/i18n/.DS_Store/strings.xml'] errno: 27, code: 'ENOTDIR', path: '/Volumes/Data/Users/sebastian/Dropbox/lightapps/Develop/Fantastic Library 4/i18n/.DS_Store/strings.xml' } [ERROR] : Script Error { [ERROR] : column = 225; [ERROR] : line = 567; [ERROR] : message = ""[LiveView] File Server unavailable. Host Unreachable @ 192.168.0.15:8324\n[LiveView] Please ensure your device and computer are on the same network and the port is not blocked.""; [ERROR] : sourceURL = ""file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js""; [ERROR] : stack = ""_getRemoteSource@file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:567:22\n_getSource@file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:586:33\n_compile@file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:632:28\nrequire@file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:502:23\npatch@file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:399:43\nfile:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:676:15\nglobal code@file:///private/var/mobile/Containers/Bundle/Application/9F65876B-19A1-4AEB-A6B3-89949298BFEF/Fantastic%20Library.app/app.js:682:3""; [ERROR] : } {code}",3,test +TISTUD-7387,Dashboard: APIs query sel and unsel behaviors are wrong,"In the dashboard of an arrow project in studio, the sel and unsel in query function behaviors are wrong. h4. Steps to reproduce: 1. Create a new arrow project 2. Run it 3. Select Data->testuser, add column ""user_name"" and create 2 users 4. Select API Docs -> APIs -> testuser and scroll to *GET /api/testuser/query* 5. enter in *sel*, *""user_name""* (include the inverted commas) h4. Expected Result result should contain only ""user_name"" h4. Actual Result result does not contain anything Repeat step 5, but enter in ""unsel"" instead: h4. Expected Result result should contain every other field but ""user_name"" h4. Actual Result result only contains everything If you run the curl command as instructed, the expected results are given. Also see attached screenshot for reference. ",5,test +TISTUD-7408,Import: ACS - Improve UI in Prompting Dialog,"*Details:* If you import a Titanium project with ACS enabled, you will be prompted to change or leave the existing keys. But the choice is not clear. *Steps to reproduce:* # Create a *Titanium* project with ACS enabled; need to use Titanium stack (Titanium Studio: 3.4.1.201410281727, CLI: 3.4.2. SDK: 3.5.1.GA) # Note the ACS keys in the tiapp.xml e.g.: {code} Gy7miwOheiZoKCBAMGon0PJn5Qm4n36D nOdoMY5osVWsliQiIbxGkyQSHL8TtMXi {code} # Next, in Appc Studio, open Studio dashboard, *Import an existing project*, and select *Existing Mobile Project* # You will be prompted to replace keys, but the dialog is confusing.",3,test +TISTUD-7415,"Error using ""Cmd /"" to comment out a line","When using ""Cmd /"" to comment out a line, or block, of code in a controller, the following error occurs. I believe this only started after the update I was prompted to install this morning. {code} [2015-04-16 09:08:46] An error occurred while processing the invoke block for the command Comment Line / Selection in /Applications/Appcelerator Studio/configuration/org.eclipse.osgi/116/0/.cp/bundles/source.ruble/commands/toggle_comment.rb: (NameError) missing class or uppercase package name (`org.eclipse.swt.SWT'), caused by (NameError) cannot load Java class org.eclipse.swt.SWT org.jruby.exceptions.RaiseException: (NameError) missing class or uppercase package name (`org.eclipse.swt.SWT'), caused by (NameError) cannot load Java class org.eclipse.swt.SWT org.jruby.javasupport.JavaUtilities.get_proxy_or_package_under_package(org/jruby/javasupport/JavaUtilities.java:54) Module.method_missing(classpath:/jruby/java/java_package_module_template.rb:14) RUBY.[]=(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/71/0/.cp/framework/ruble/editor.rb:196) org.jruby.RubyProc.call(org/jruby/RubyProc.java:271) RUBY.run(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/117/0/.cp/framework/ruble/ui.rb:249) RUBY.[]=(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/71/0/.cp/framework/ruble/editor.rb:193) RUBY.add(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/116/0/.cp/bundles/source.ruble/lib/comment.rb:233) RUBY.define_command(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/116/0/.cp/bundles/source.ruble/commands/toggle_comment.rb:56) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613) RUBY.define_command(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/116/0/.cp/bundles/source.ruble/commands/toggle_comment.rb:53) org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613) RUBY.define_command(/Applications/Appcelerator Studio/configuration/org.eclipse.osgi/116/0/.cp/bundles/source.ruble/commands/toggle_comment.rb:52) {code}",5,test +TISTUD-7426,Handle ACS key replacement confirmation through studio import project operation,"https://jira.appcelerator.org/browse/CLI-551 Handling the above issue in studio, showing the confirmation dialog to the user to replacing the acs keys based on the user input.",5,test +TISTUD-7428,"Studio launches Mobile Web in browser but returns ""Connection Refused""","Appcelerator Studio no longer launches web browser after Mobile Web build. h1. To reproduce 1. On latest Titanium Studio with 3.5.1.GA, create a Classic Single Window app and run with ""Mobile Web Preview in Browser"" to confirm it opens the browser, displaying the app. 2. On latest Appcelerator Studio with 3.5.1.GA or 4.0.0.Beta3, do the same and confirm it opens the browser, but showing *ERR_CONNECTION_REFUSED* Reported by a user in Q&A: https://community.appcelerator.com/topic/204/localhost-on-mac",5,test +TISTUD-7447,"""Resources not found"" error while creating an android or IOS module","h5.steps to reproduce: 1. Install the mentioned appc studio 4.0.0.201504211201. 2. Create a new android or IOS module project. 3. Fill in all the necessary details & click finish. h5.Actual Results: 1. While the module is getting created we get ""error : resources not found"" but the module is created successfully. Attaching screenshot for reference. h5.Expected Results: 1. We should not get any error while creating a module project.",5,test +TISTUD-7430,Update liveview module,Update studio liveview module with the latest changes.,5,test +TISTUD-7431,"""user profile"" link in ""New Mobile App Project"" wizard directs to wrong URL when signed out on studio dashboard","If the user has signed out on studio dashboard and reloads it, then the ""user profile"" link in ""New Mobile App Project"" wizard takes to a wrong URL 1. Login into studio (the dashboard also shows logged in) 2. Click on ""user profile"" link in the second step of ""New Mobile App Project"" wizard 3. It opens up, in the browser, the manage org webpage on https://platform.appcelerator.com 4. Close the browser window 5. Now in studio, sign out from the dashboard. Reload the dashboard. 6. Again click on ""user profile"" link in the second step of ""New Mobile App Project"" wizard 7. It opens up the url https://appc-studio.appcelerator.com in the browser Expected Result: Even upon sign out, the user profile link should open the https://platform.appcelerator.com and redirect to manage org page upon sign in.",5,test +TISTUD-7432,Dark theme has unreadable white-on-white tabs after upgrade,"During a TeamViewer session with a customer we used the 4.0.0.x 64-bit installer for Mac while Appcelerator Studio 3.4.2 was already installed. It replaced 3.4.2 with no warning. The 3.4.2 Studio had the dark theme enabled and so did the new Studio, but the selected tabs will be white on white instead of black on grey. I could reproduce the issue on my own machine. Not after the initial install of the 4.0.0 Studio, but it did happen after letting Studio update itself.",8,test +TISTUD-7437,"""Sending Analytics Ping"" error when using a pre-4.0 workspace in 4.0 Studio","I opened a pre 4.0 workspace in Studio 4.0 and get the following error popping up every few minutes now. Can't use Studio. {code} An internal error occurred during: ""Sending Analytics Ping ..."". java.lang.NullPointerException {code} I have attached the {{.metadata}} folder, including {{.metadata/.plugins/com.aptana.usage/events}} which [~cwilliams] suggested. Creating a folder with this {{.metadata}} dropped in should reproduce the issue. Creating a new workspace fixes the issue.",3,test +TISTUD-7438,Studio should move to appc commands for module creation and building projects,"h5.Description When Studio creates a module or builds project it is currently using the {{appc ti}} commands, it should move to use {{appc}} commands such as {{appc new}} and {{appc run}} and only use {{appc ti}} where necessary. {code} ""/usr/local/bin/appcelerator"" ""ti"" ""create"" ""--platforms"" ""iphone"" ""--type"" ""module"" ""--id"" ""com.appc.testModule"" ""--sdk"" ""4.0.0.Beta3"" ""--workspace-dir"" ""/Users/eharris/Documents/Appcelerator_Studio_Workspace"" ""--name"" ""testModuleBlah"" ""--verbose"" ""--force"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""--prompt-type"" ""socket-bundle"" ""--prompt-port"" ""49629"" {code} {code} ""/usr/local/bin/appcelerator"" ""ti"" ""build"" ""--platform"" ""ipad"" ""--log-level"" ""trace"" ""--sdk"" ""4.0.0.Beta2"" ""--project-dir"" ""/Users/eharris/Documents/Appcelerator_Studio_Workspace/ProdEnterpriseApp"" ""--target"" ""simulator"" ""--ios-version"" ""8.2"" ""--device-family"" ""universal"" ""--deploy-type"" ""development"" ""--sim-type"" ""ipad"" ""--sim-version"" ""8.2"" ""--device-id"" ""9EF4205F-E350-4767-9CEF-B168C11A52C1"" ""--skip-js-minify"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--prompt-type"" ""socket-bundle"" ""--prompt-port"" ""49629"" {code} h5.Steps To Reproduce 1. Create a module project using Studio 2. Build a project using Studio h5.Actual Result 1. Check the Studio logs {{appc ti create}} will be used 2. Check the Studio logs {{appc ti build}} will be used h5.Expected Result 1. {{appc new}} should be used 2. {{appc run}} should be used",5,test +TISTUD-7440,Studio hangs when cleaning a project if logged out,"When logged out of the CLI, if you clean a project in Studio, Studio will either hang or be unable to perform other actions. *Steps to reproduce issue*: 1. Open Studio 2. Run {{appc logout}} 3. Clean a project in Studio 4. Login and select an org *Actual Results*: Studio hangs while cleaning *Expected Results*: Studio does not hang *Notes*: The project is cleaned, but Studio keeps the cleaning progress bar dialog open. If you ""Run in Background"" the process does not complete, so no further actions (like building) can take place. Cleaning from the CLI works as expected.",5,test +TISTUD-7446,Single Sign On is broken when opening an Arrow Window,"When running an Arrow app within Studio, a new Editor window opens to show the Arrow Admin interface. Unlike the Dashboard tab, this view does not already have the user signed in, and so the User is forced to login to the Appcelerator Platform before getting access to the UI. Additionally the user is also forced to go through 2 factor auth (email or sms) for studio. Expectation: User should not have to login, studio should be able to perform the same check against the CLI for the SSO Url and launch the Arrow window with the user already logged in.",3,test +TISTUD-7449,Update packaged Java version to 1.7u80,"Our current Java version is behind the latest release. We should update the versions to 1.7u80, which is the last public release for 1.7",5,test +TISTUD-7450,Loosen restrictions on Java version being installed via OS X installer,Currently we are quire restrictive about which version of Java we are downloading. We need to loosen that restriction to allow more flexibility of we need to update to a later version.,5,test +TISTUD-7453,Cannot login into studio after logging out from CLI,"After logging out from CLI, the studio does not show login fields on splash screen and opens up studio. After loading studio it shows the interstitial login window which does go off even on entering valid credentials. The issue does not occur if logged out from studio and not from CLI. Steps to Reproduce: 1. From terminal logout using the command ""appc logout"" 2. Now launch studio Actual Result: The splash screen does not show login fields and load studio. Upon load the login window shown does not accept valid credentials and keeps showing.",5,test +TISTUD-7456,"If you publish an Arrow app, the ""Unable to parse URL for publish"" appears","*Details:* -On Windows,- If you publish an Arrow app, the ""Unable to parse URL for publish"" appears. *Note:* * -This issue does not appear on Mac with Appc Studio- * *Workaround:* After you publish the Arrow app from Appc Studio, you can view the published URL with {{appc cloud list }} *Steps to reproduce:* # In Appc Studio, create an Arrow project # Publish the Arrow app # Wait for the AppcStudio to finish publishing Arrow *Actual:* ""Unable to parse URL for publish"" error will appear; see attachment. *Expected:* Should be able to publish an Arrow app from Appc Studio on both Windows and Mac.",5,test +TISTUD-7457,"If you logout from Appc CLI or from the bottom right link, Appc Studio will take you to a non-standard login flow ","*Details:* If you logout of Appc CLI or from Studio's bottom-right link, logging back into Appc Studio takes you to non-standard flow of logging in. *Steps to reproduce:* # Logout of Appc Studio with {{ctrl + q}} or from the bottom-right link # Next, logout of Appc CLI *if* you haven't done so yet # Open Appc Studio *Actual:* Appc Studio will take you to a non-standard login flow i.e. * You will not be prompt to login from the red screen; you will be prompted to login once Appc Studio opens its Project Explorer; see attachments * *Or,* Appc Studio will continually prompt you to login from within Project Explorer *Expected:* Appc Studio should prompt you to login from the red screen.",5,test +TISTUD-7458,Warnings to get SDK info while opening dashboard,"Fokke has noticed a couple of Q&A issues regarding the warnings logged while opening Dashboard: https://community.appcelerator.com/topic/228/error-failed-to-package-application-and/2 https://community.appcelerator.com/topic/179/unable-to-set-property-sdkinfo-of-undefined/7 Though they might not actually impact the functionality, should be good to address them, as the warnings in visible in console to the users. The error: {code} [""Unable to set property 'sdkInfo' of undefined or null reference"",""https://appc-studio.appcelerator.com/"",198] {code} The related line (second last) of code: {code} function onSdkUpdate(sdkEvent){ if(sdkEvent){ var sdkInfo = platforms[sdkEvent.data.sdkName].sdkInfo = sdkEvent.data.sdkInfo; var branding = platforms[sdkEvent.data.sdkName]; {code}",8,test +TISTUD-7459,KitchenSink: Tiapp contains info for blackberry and tizen,"KitchenSink, from master branch, has information in its tiapp.xml for blackberry and tizen. *Steps to reproduce issue*: 1. Import KitchenSink from master: https://github.com/appcelerator/KitchenSink/tree/master 2. Open the tiapp.xml *Actual Results* There is information in the tiapp for blackberry and tizen. *Expected Results* There should not be any reference to unsupported platforms in the tiapp.xml.",2,test +TISTUD-7460,Appc Studio should remember the last org you were logged into,"*Details:* Currently, if you log into Appc Studio (after you have logged out) and select an org, Appc Studio does not remember the last org you were logged into. By default, Appc Studio will select the first org in your list. *Expected:* When you log into Appc Studio (after you have logged out), Appc Studio should remember the last org you were logged into; similar to how Appc CLI remembers which org you were last logged into. *User flow:* # Log out of Appc Studio # Launch and log into Appc Studio # Select an org *Actual:* Appc Studio does not remember the last org you were logged into; see attachment. ",3,test +TISTUD-7461,Project creation fails with NPE when trying to create it at custom location,"The project creation fails when trying to create the project at a custom location i.e. outside the current workspace. Steps to Reproduce: 1. Go to File -> New -> Mobile App Project 2. In the ""New Mobile App Project"" wizard, uncheck the check box for ""Use default location"" 3. Enter a custom location for the project 4. Fill in rest of the details and click on Finish Actual Result: The project creation fails with an error. Refer to attached screenshot Expected Result: Should be able to create project outside workspace",3,test +TISTUD-7462,Blank project created in Studio when offline,"A blank project is created when offline. It should either restrict creation of project or create it with certain message. Steps to Reproduce: 1. With no network connection, try to create a new project in Studio Actual Result: The project gets created with no error but the project is blank",5,test +TISTUD-7463,Appcelerator Studio hang - difficult to repro,"h5. Description: I have seen this occur once before, but the first time I could capture data was recently. I am not completely sure of reproduction steps, but basically during use, Studio ""beach balled"" and hung. The second time it did this, I noticed the memory usage grew as time went on. The attached logs may well be different issues. If so, I will split this out to separate tickets. h5. Steps to reproduce: Unknown, but activities prior to most recent log: 1) Leave Studio open overnight 2) Create new project 3) Attempt to run h5. Result: Studio was hung, with memory footprint increasing, and over 1 GB within a few moments. h5. Expected Result: Studio does not hang",5,test +TISTUD-7466,Arrow project is created with empty directory If we choose custom location in project wizard,"If we choose to create an arrow with custom location, the project is created with an empty directory. Steps: 1. New->Arrow project 2. Project name: ""arrowtest"" and un-check ""Use default location"" and provide path to custom location Example: /Users/kkolipaka/work/eclipse_workspaces/runtime-Titanium-360/arrowtest_diff Here project name and last segment of the path(project directory name) are different. 3. Click finish Project will be created with a name ""arrowtest"" without any content in it. ",3,test +TISTUD-7467,"NullPointerException for ""update UI for index changes"" after importing Movies sample",I imported the movies app via the dashboard and while the wizard was importing got the attached error. Error log attached. I can reproduce this every time.,3,test +TISTUD-7469,Black line in the toolbar of appc studio 4.0.0.201505011217,h5.Steps to reproduce: 1. Install & launch appc 4.0.0.201505011217. 2. Look at the studio tool bar at the top. h5.Actual Results: 1. We see a black line at the lower part of the toolbar which does not looked polished. Attached screenshot for reference. h5.Expected Result: 1. We should not see any black line at the lower part of the toolbar,3,test +TISTUD-7470,Simplify detection of packaged Studio versions,"When testing Studio, it is difficult to tell what build is included in the installers. Viewing http://studio-jenkins.appcelerator.org/job/appcelerator-installer-dmg-mac-release/75/console, you can't tell what version of Appcelerator Studio is included. 3 suggested changes: # Output the version of Studio being packaged in the installer build logs # When building the installer, create a companion file called _version.txt. That file is uploaded to preview.appcelerator.com # On preview.appcelerator.com, add hover text over the installer links to highlight what version is published there (for those who need to know)",8,test +TISTUD-7473,Running a new created project from global run button immediately after creation runs a wrong project,"There are issues with global run button when trying to run a newly created project. Upon creation of new project, the project explorer shows the new project selected however the run button still tries to run the project that it last ran before project creation. Steps to Reproduce: 1. Create a project 'Project 1'. 2. Select the project and run it using the global toolbar 3. Now create another new project 'Project 2'. The project 2 is shown selected in the project explorer (with Grey highlight) 4. Click on the run button in global toolbar Actual Result: The Project 1 is ran instead of Project 2 ",3,test +TISTUD-7474,Finish button in 'Package Module' page not working after running the module project from global toolbar,"Running a module for package using the global toolbar after the module project in project explorer is either not shown selected or shows up with grey background selection opens up the 'Package Module' page but the Finish button is not working Steps to Reproduce: 1. Create a module project 2. When it is shown selected in the project explorer (with blue selection), either click in empty area in project explorer (to remove selection) or in the working area (to show project with grey selection) 3. Click on the run button in global toolbar 4. The 'Package iOS Module' page opens up. With any radio button selection click on the Finish button Actual Result: The Finish button click does not work",3,test +TISTUD-7475,"Mobile Web button shows ""update"" in Studio Dashboard on windows systems","h5. Description: When using the Dashboard in Studio, the ""Appcelerator Studio Prerequisites"" section indicates that mobileweb can be updated. Clicking this opens Android update wizard. Canceling shows this in the console: {code}[""Unable to set property 'sdkInfo' of undefined or null reference"",""https://appc-studio.appcelerator.com/"",198]{code} h5. Steps to reproduce: 1) Launch Studio and open dashboard on a windows system 2) Note the button state on the mobileweb prerequisite h5. Result: The button indicates an upgrade is available, but Android update opens when clicked h5. Expected Result: Button state accurate",5,test +TISTUD-7476,Windows installer: Studio cannot find Java installed by installer due to install location mismatch,"When the Appc Studio windows installer installs Java, it installs it in Program Files(x86). Whereas Studio upon launch tries to look for Java in the jre folder inside the installed Appcelerator Studio folder. Steps to Reproduce: 1. Remove Java from the system 2. Run the windows installer. It prompts for installation of Java as a pre-requisite 3. Once the Java and Appc Studio are installed, try to launch Appcelerator Studio Actual Result: The Appcelerator Studio cannot be launched as it gives an error that it could not find the Java at desired location and in the PATH variable. Refer to attached screenshot The Java got installed inside C:/Program Files (x86)",5,test +TISTUD-7477,Windows Installer: The installer does not install the Appc CLI Core,The windows installer for Appcelerator Studio does not install the Appc CLI core component as part of the pre-requisites. It only installs the Appc CLI NPM component. The core is installed once the installed Studio is launched.,3,test +TISTUD-7478,"On Windows, the toolbar should not have a lot of left padding","*Details:* Currently on Windows, the run button is not aligned with the left border of Project Explorer pane; see attachment. *Note:* This issue does not occur on Appc Studio running on Macs. *Expected:* On Windows, the run button should be aligned with the left border of Project Explorer pane like on Macs.",3,test +TISTUD-7479,"If you enable services on your Titanium app (non-platform), the prompt text is chopped off at the bottom","*Details:* If you enable services on your Titanium app (non-platform), the prompt text to replace your ACS keys is chopped off at the bottom. *Steps to reproduce:* # Download and unzip monkeyTiBob.zip; monkeyTiBob is a Titanium app (non-platform) that has ti.cloud enabled # Next in Appc Studio, open the Dashboard, click on *Import an existing project*, select *Existing Mobile Project*, select monkeyTiBob, and click on *Finish* button # Open the tiapp.xml; wait for *Enable Services* button to appear # Next, click on *Enable Services* button *Actual:* The prompt text to replace your ACS keys is chopped off at the bottom; see chopped_message.png for Mac and see chopped_message2.png for Windows. *Expected:* The prompt text to replace your ACS keys should not be chopped off.",3,test +TISTUD-7482,The four samples on Dashboard do not have option for Appcelerator Platform Services in Import wizard whereas the others do,"The four samples shown on the dashboard i.e. Employee Directory, Movies, Geocoder, RSS Reader do not have the section for Appcelerator Platform Services in Import wizard. Whereas the other remaining samples from the sample view have that section that allows enable or disable of services to the logged in organization at the time of import. Steps To Reproduce: 1. Try to import any of the Employee Directory, Movies, Geocode or RSS Reader sample from the dashboard or the Sample view 2. Now try to import any other sample from the Sample view Actual Result 1. The import wizard doe not show the section for ""Appcelerator Platform Services"" 2. The import wizard shows the section ""Appcelerator Platform Services"" along with Project Name and Location. Expected Result: The behaviour should be consistent across all samples and can have the section for ""Appcelerator Platform Services"" to allow enable or disable of services to the logged in organization at the time of import",8,test +TISTUD-7484,"Dashboard in offline mode:Clicking refresh button from dashboard launches another browser with name""Web Browser""","If studio opened in offline mode i.e. without network connection, dashboard editor shows ""Server currently Unavailable"" and with ""refresh"" button. Clicking on the ""refresh"" button is creating another browser tab with a name ""Web Browser"". Expected: It should refresh the same browser and should not create another browser tab.",5,test +TISTUD-7485,Studio logged in user name shows wrong in status bar,"1. Logout CLI/Studio(appc logout -D) 2. During the studio startup, it will ask for the login credentials. 3. Enter wrong user name and password Example: enter wrong user name ""kkk"" and password 4. Studio again prompt with login dialog since we entered wrong credentials. 5. This time enter correct credentials 6. Studio will login and observe the logged-in user name in status bar, it will show the wrong user name ""kkk"", which I entered for the first time.",5,test +TISTUD-7486,On entering invalid credentials during studio login a second login dialog is shown instead of error message,"While logging into Studio, if the user types wrong credentials in the login fields on the splash screen, then a second dialog for login is shown instead of error message Refer to the attached screenshot. Steps to Reproduce: 1. Launch Appc Studio 2. Enter invalid credentials and click on Login button Actual Result: A dialog pops up with set of login fields. Expected Result: An error message should be shown with the existing login fields on the splash screen",5,test +TISTUD-7488,Error running installer,"When i try to install latest via new installer, i get the error attached. ",5,test +TISTUD-7491,Diagnostic report should contain the Appc CLI core version number,"h5.Description When running a diagnostic report in Studio it does not contain the Appc CLI registry version number, this should be included to help when debugging issues with customers. It contains references to the Appc CLI NPM package as it is a Node module but not the registry package h5.Steps To Reproduce 1. In Studio select Help->Studio->Run Diagnostic Test h5.Actual Result No reference to the Appc CLI registry package is included h5.Expected Result The version number of the Appc CLI registry package should be included",3,test +TISTUD-7493,Appc Studio should be able to properly update Appc CLI after an initial bad Appc CLI install,"*Details:* Currently, if you try to update Appc CLI via Appc Studio and you had a bad install previously (i.e. cancelling the previous update builds), then you will run into this issue: https://community.appcelerator.com/topic/398/appcelerator-studio-updates-error To improve the update process from Windows, Appc Studio should be able to detect {{.installing}} file, delete the file, and update Appc CLI again. *Steps to reproduce:* # Remove the latest Appc CLI build from your machine # Select an older Appc CLI build: {{appc use }} # In Appc Studio, check for updates and accept the new Appc CLI update # As soon as the update wizard starts, cancel the update # Then, check for updates again from Appc Studio *Actual:* Appc Studio will fail to update; see attachment.",5,test +TISTUD-7494,When an app is packaged would be nice to popup a dialog that lets the user know what platform features are being leveraged and which are not,"When an app is packaged would be nice to popup a dialog that lets the user know what platform features are being leveraged and which are not We find that many customers use us for cross device development but don't even know that we have crash, test, analytics, push, ... We need find ways to remind customers what we have and what parts are currently being leveraged. Imagine that when you package an app and we can tell the developer that they have not turned on Analytics and provide a link to Analytics info. This is [~jhaynie]'s idea.",8,test +TISTUD-7495,Studio logs in to wrong organization until restart,"The studio logs into wrong organization whereas the ""appc whomi"" on terminal shows the correct organization that the user logged into. Once the studio is restarted the correct organization is shown. Refer to the attached screenshot. The issue is a regression on the latest build as it did not occur on the previous build of Studio 4.0.0.201505111522 Steps to Reproduce: 1. Launch the studio application 2. On the splash screen when prompted, enter credentials and select the organization. 3. Once studio loads, try to create a new project. 4. Check the ""New Mobile App Project"" wizard for the organization shown Actual Result: The organization shown is not the one selected by the user during sign in at the time of launch of studio. Upon restarting the studio, without signing out, the correct organization is shown. Expected Result: The correct organization should be shown.",5,test +TISTUD-7498,Windows reports failure installing windows core plugin,"STEPS TO REPRODUCE Upon installing Appcelerator Studio on Windows 8, we get an error that says ""Installing Windows Core Plugin"" EXPECTED RESULT - appcelerator studio runs without any errors. ",3,test +TISTUD-7502,Update listing of RSS Reader sample app in Studio to reflect new Alloy version,"The [RSS sample|https://github.com/appcelerator-developer-relations/Sample.RSS] has been [updated to use Alloy|https://github.com/appcelerator-developer-relations/Sample.RSS] and its listing on the dashboard needs an update as well. * Update the data model via appc-studio-server API * Merge PR for updated image: https://github.com/appcelerator/appc-studio-server/pull/19 h1. Current model {code} { ""id"": ""5510cd242194350b7502be19"", ""name"": ""Rss Reader"", ""short_description"": ""A sample Master/Detail app that creates a RSS reader. With it you can pull live RSS feeds from the internet, list them along with thumbnails, then drill down to the article itself."", ""description"": ""A sample Master/Detail app that creates a RSS reader. With it you can pull live RSS feeds from the internet, list them along with thumbnails, then drill down to the article itself."", ""app_id"": ""com.appcelerator.titanium.mobile.samples.rss"", ""tags"": [""Ti.UI.TableView"", ""master-detail"", ""3.5.1.GA""], ""image"": ""rss-sample.png"", ""location"": ""git://github.com/appcelerator-developer-relations/Sample.RSS.git"", ""studio_default"": true, ""created_at"": ""2015-03-24T02:34:12.000Z"", ""updated_at"": ""2015-03-24T02:34:12.000Z"" } {code} h1. Updated model {code} { ""id"": ""5510cd242194350b7502be19"", ""name"": ""RSS Reader"", ""short_description"": ""A sample Master/Detail app that creates a RSS reader. With it you can pull live RSS feeds from the internet, list them and drill down to the article itself."", ""description"": ""A sample Master/Detail app that creates a RSS reader. With it you can pull live RSS feeds from the internet, list them and drill down to the article itself."", ""app_id"": ""com.appcelerator.titanium.mobile.samples.rss"", ""tags"": [""ios"", ""android"", ""mobileweb"", ""alloy"", ""Ti.UI.ListView"", ""Ti.UI.TableView"", ""Ti.UI.WebView"", ""Ti.UI.iOS.NavigationWindow"", ""Ti.UI.iOS.SplitWindow"", ""models"", ""collections"", ""data-binding"", ""master-detail"", ""4.0.0.GA""], ""image"": ""rss-sample.png"", ""location"": ""git://github.com/appcelerator-developer-relations/Sample.RSS.git"", ""studio_default"": true, ""created_at"": ""2015-03-24T02:34:12.000Z"", ""updated_at"": ""2015-06-18T02:34:12.000Z"" } {code} ",5,test +TISTUD-7504,Support switching organizations without needing to logout and in again,"Having worked with Studio for a while now, while being member of multiple organizations, I've found it cumbersome to switch organizations, in particular in Studio. I have to logout by clicking on my name and then re-open studio, login and select the other organization. The prefered solution would be to have a button to switch organizations, which would show a similar popup to the one you get when you login. It would then switch organization without ever closing Studio of requiring you to login again.",8,test +TISTUD-7505,Studio should show active organization,"Studio shows the name of the logged in user on the bottom right, but not the organization. If you are member of multiple organizations this makes it easy to create/import a project in the wrong organization. The only way to find out is to use the CLI ({{appc whoami}}) or open the dropdown on the Studio Dashboard. The prefered UI would be to have the organization name listed with the name. Perhaps clicking the organization name would then allow you to switch organizations as suggested in TISTUD-7504. ",5,test +TISTUD-7508,"When unpublishing an Arrow application, the toast notification displays the app name prefixed with 'P/'","REPRODUCTION: 1. Create a new Arrow application. 2. Publish the Arrow application. 3. Unpublish the Arrow application. RESULTS: When the toast notification appears, the app name is prefixed with 'P/'. EXPECTED RESULTS: App name should appear without the 'P/'.",1,test +TISTUD-7510,Android SDKs detected do not match what is installed and unable to build for android,"h5. Description: After installing Studio, I was prompted to configure android. I could not build to android in this situation, and my list of SDKs did not match what was installed. See screenshots. h5. Steps to reproduce: 1) Install Studio from DMG and launch 2) If you get a dialog to configure, expand the ""settings"" and look at what is installed. 3) If you do not, navigate to Preferences > Studio > Platforms > Android and click the ""install SDKs"" button h5. Result: The list of installed sdks does not match h5. Expected Result: Perfect match between the list of installed sdks and the actual installed sdks",5,test +TISTUD-7511,Studio downloads android TV system image for android 5.1.1 instead of the default mobile ARM image which fails to create the default emulator,"h5. Steps To Reproduce: 1. Make sure you only have android 5.1.1 installed in your android sdk manager. 2. Launch appc studio. 3. Create an app. 4. Run on android emulator. h5. Actual Results: 1. We see that the default emulator is not created. 2. On further digging we found out that when 5.1.1 android sdk is downloaded from studio (note no android sdk were present prior) it does not install the ""ARM EABI v7a System Image"" but installs ""Android TV ARM EABI v7a System Image"". 3. When studio tries to create the default emulator it fails as it looks for mobile image & cannot find it. h5.Expected Result: 1. Studio should download the ""ARM EABI v7a System Image"" . ",8,test +TISTUD-7512,Unexpected setting in ti config causing vague error in studio platform settings,"h5. Description: I have not been able to reproduce the root cause of this, so will write a separate ticket for the ti config setting issue. I noticed I had something odd in my ti config setting for genymotion.executables.vboxmanage: {code} emerrimanMBP:~ eric$ appc ti config Appcelerator Command-Line Interface, version 0.2.285 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. android.emulatorStartTimeout = 180000 android.ndkPath = ""/Users/eric/android-ndk-r8d"" android.sdkPath = ""/Users/eric/Android_SDK"" app.workspace = """" cli.colors = true cli.completion = false cli.failOnWrongSDK = false cli.httpProxyServer = """" cli.ignoreDirs = ""^(\\.svn|_svn|\\.git|\\.hg|\\.?[Cc][Vv][Ss]|\\.bzr|\\$RECYCLE\\.BIN)$"" cli.ignoreFiles = ""^(\\.gitignore|\\.npmignore|\\.cvsignore|\\.DS_Store|\\._.*|[Tt]humbs.db|\\.vspscc|\\.vssscc|\\.sublime-project|\\.sublime-workspace|\\.project|\\.tmproj)$"" cli.logLevel = ""trace"" cli.progressBars = true cli.prompt = true cli.rejectUnauthorized = true cli.width = 100 genymotion.executables.vboxmanage = ""Appcelerator Login required to continue ..."" paths.commands = [] paths.hooks = [""/Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.1.0.1424300841/node_modules/liveview/hook""] paths.modules = [] paths.plugins = [] paths.sdks = [] paths.templates = [] sdk.selected = ""4.0.0.RC4"" user.locale = ""en_US"" {code} While I have no real idea when the setting was made or by what process, it did produce an error in Studio. See screenshots for comparison. The workaround was to remove the setting with: {{appc ti config -r genymotion.executables.vboxmanage}} and the Studio UI returned to a better state. h5. Steps to reproduce: 1) Unsure how I got the setting, but it can be made manually with {{appc ti config enymotion.executables.vboxmanage ""Appcelerator Login required to continue ...""}} 2) Open Studio preferences > Studio > Platforms > Android 3) observe error h5. Result: The error is s bit vague, ""Value must be an existing file"" h5. Expected Result: Clear information on what to do to fix my problem, and which bit of configuration is the problem",5,test +TISTUD-7514,"Ti config for ""genymotion.executables.vboxmanage"" set to ""Appcelerator Login required to continue ...""","h5. Description: Somehow my setting for {{genymotion.executables.vboxmanage}} got set to = ""Appcelerator Login required to continue ..."". I am unsure how or when this happened, but am certain I did not manually set it as such. It looks like a process was running to set this when a prompt to login came up and the process took that as its result and set it. {code}emerrimanMBP:~ eric$ appc ti config Appcelerator Command-Line Interface, version 0.2.285 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. android.emulatorStartTimeout = 180000 android.ndkPath = ""/Users/eric/android-ndk-r8d"" android.sdkPath = ""/Users/eric/Android_SDK"" app.workspace = """" cli.colors = true cli.completion = false cli.failOnWrongSDK = false cli.httpProxyServer = """" cli.ignoreDirs = ""^(\\.svn|_svn|\\.git|\\.hg|\\.?[Cc][Vv][Ss]|\\.bzr|\\$RECYCLE\\.BIN)$"" cli.ignoreFiles = ""^(\\.gitignore|\\.npmignore|\\.cvsignore|\\.DS_Store|\\._.*|[Tt]humbs.db|\\.vspscc|\\.vssscc|\\.sublime-project|\\.sublime-workspace|\\.project|\\.tmproj)$"" cli.logLevel = ""trace"" cli.progressBars = true cli.prompt = true cli.rejectUnauthorized = true cli.width = 100 genymotion.executables.vboxmanage = ""Appcelerator Login required to continue ..."" paths.commands = [] paths.hooks = [""/Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.1.0.1424300841/node_modules/liveview/hook""] paths.modules = [] paths.plugins = [] paths.sdks = [] paths.templates = [] sdk.selected = ""4.0.0.RC4"" user.locale = ""en_US"" {code} h5. Steps to reproduce: 1) Unknown, but would examine whatever process sets this item h5. Result: Prompt set as config option h5. Expected Result: Config option that is not prompt",5,test +TISTUD-7515,%externalize.strings not properly externalized in studio ui,"In the Source > Externalize Strings UI, the string is not properly externalized and shows as ""%externalize.strings.command.name""",3,test +TISTUD-7517,Studio hangs on opening the project files,Studio hangs when opening any of the project files of the newly created project. The issue did not occur on an old workspace I have. For any new workspace the issue occurs on opening any file of the project. The issue also occurred when in a new workspace a project created through CLI was imported. Opening the index.xml file hung the studio. Steps to Reproduce: 1. Select a new workspace 2. Create a new alloy project. Once the project is created the index.xml and tiapp.xml are opened by default. 3. Close the Tiapp.xml 4. Now try to open the Tiapp.xml again Actual Result: Studio hangs. Find attached the log for java stack trace and studio ,8,test +TISTUD-7518,Platform configuration wizard detects android SDK installed even if they are not,"h5. Steps To Reproduce: 1. Remove your android SDK from your system (delete the android-sdk-macosx folder for mac). 2. Launch studio. 3. Go to studio dashboard. 4. You will see android sdk not configured. 5. Click to configure android SDK. 6. The ""Platform Configuration"" wizard will come up. 7. Click on ""settings"" for android. 8. You will see android 5.1.1 SDK is selected. 9. Click on configure. h5. Actual Results: 1. The wizard will configure android SDK in the default location (even though it's not installed) & not download the android SDK. 2. +Workaround:+ De-select & again select android 5.1.1 platform in the ""platform configuration "" wizard for android & click configure, it then gives you the license agreement & downloads the android SDK h5. Expected Results: 1. Studio should not detect android SDK installed & should download if not present.",5,test +TISTUD-7519,Update Home Tab Banner on Ti Studio,"Marketing needs to swap out the OpenX javascript code on Ti Studio home tab to the following js code: {code} {code} ",5,test +TISTUD-7522,"If you update Appc Studio, Appc Studio will not understand Appc CLI 4.0.0-rc","*Details:* Currently, if you update Appc Studio, Studio will try to update Appc CLI to 4.0.0 even though Appc CLI does not exist. This is because Appc Studio cannot recognize 4.0.0-rc. *Steps to reproduce:* # Update Appc Studio on the RC stream *Actual:* Appc Studio will try to update to Appc CLI 4.0.0 even though it does not exist; see attachment. *Expected:* Appc Studio should be able to recognize Appc CLI 4.0.0-rc.",5,test +TISTUD-7523,NPE on studio launch on a new workspace,An exception is shown when a new user launches studio for the first time or launches studio in a new workspace. Refer to the attached screenshot and studio logs. Steps to Reproduce: 1. Launch Studio and while launch mention a new workspace to work with Actual Result: An exception is shown upon studio launch. The exception is not shown if the user restarts the studio.,3,test +TISTUD-7526,Remove samples view,"The samples view in the studio perspectives has been identified for removal. Users should focus on the Samples presented as part of the studio dashboard. The samples view does not appear in the default perspective, but does appear in the ""Extended"" perspective.",3,test +TISTUD-7529,"If you package an Android app from a non-vpc org, then ""VPC Environment"" dropdown list will appear","*Details:* If you package an Android app from a non-vpc org, then the *VPC Environment* dropdown list will appear during Android packaging dialog. *Steps to reproduce:* # Make sure you are logged into a non-vpc org # Create a Titanium or Alloy project # Select the mobile project # Select *Package > Android App Store*, then click the run button *Actual:* The *VPC Environment* dropdown list will appear at the bottom of the dialog; see attachment. *Expected:* The *VPC Environment* dropdown list should not appear unless you are in a VPC enabled org.",5,test +TISTUD-7530,Appc Studio to handle rc/beta versions of Appc core package,"Appc Studio doesn't show an update for Appc Core package @ 4.0.0, if 4.0.0-rc is already installed on the machine.",3,test +TISTUD-7531,Studio hangs when writing a line with an umlaut and a semicolon,h5.Description When writing the following {{console.log('ü)}} and then you follow it up with {{;}} Studio will hang. Following up with logs in a minute h5.Steps To Reproduce 1. Write {{console.log('ü)}} 2. Then follow Javascript best practices and end your line with {{;}} h5.Actual Result Studio will hang h5.Expected Result Studio should not crash with special characters,8,test +TISTUD-7538,Default URL for tiapp.xml valid in wizard but invalid in editor,"The default value for _Company/Personal URL_ field in the new project wizard is {{http://}}. When you remove it to be empty it will tell you it is required, but leaving it to the default does not trigger any errors here. But once the project is created and the Tiapp Editor opens, it will show an error in the XML-view. See the attached screenshots h3. Expected I'd expect the error to be raised in the new project wizard as well. Also, I think this field should not be required and empty by default.",5,test +TISTUD-7546,App Preview Integration in Studio,"With the Installr app integration, we're looking to add a flag in adhoc build distribution flows for uploading to Installr App. Users should be able to flag their build to be uploaded to Installr. When selected they should be able to add a description to their build. Additional options available in the CLI plugin such as emailing existing users in the app or adding emails should also be in the form. CLI plugin located here: https://github.com/jeffbonnes/appc-app-preview-cli-hook",8,test +TISTUD-7547,Install Appcelerator SDK does not list any SDKs,"When I go to _Help > Install Appcelerator SDK.._ and then select _Install from Update Stream:_ the dropdown is empty so I cannot install older SDKs. See attached screenshots. As a side-note, it is confusing that the menu option has _Appcelerator SDK_ and the dialog itself _Titanium SDK_. I would suggest using the latter.",3,test +TISTUD-7548,Login Error has link to 3.x troubleshooting guide,"When you login to Studio and have to enter a authorization code, you have the option to cancel. It will then display an _Login Error_ alert which has a link to a 3.x troubleshooting guide. This link should be updated to the correct 4.x guide. It opens this link: http://go.appcelerator.com/Errors+Logging+In Which redirects to: http://docs.appcelerator.com/titanium/latest/#!/guide/Errors_Logging_In So this can be fixed server-side to lead to: http://docs.appcelerator.com/platform/latest/#!/guide/Errors_Logging_In_to_Studio See screenshots. Related Q&A: https://community.appcelerator.com/topic/500/trying-to-login-to-new-4-studio/5",1,test +TISTUD-7552,Importing an existing Alloy (non-Studio) project does not add Alloy nature,"When you import an Alloy project in Appcelerator Studio that was not a Titanium Studio project, it will not get the Alloy nature. Users who have been using the Titanium CLI will run into this issue when they follow our instructions to migrate their app to the Platform and decide to now use Appcelerator Studio to do so. h3. Reproduce 1. Create a project through the Titanium CLI ({{ti create -t app}}). 2. Initialize it as an Alloy app. ({{alloy new}}). 3. Import the app via Appcelerator Studio. 4. Confirm it does not have the Alloy nature. Reported via Q&A: https://community.appcelerator.com/topic/525/existing-project-imported-into-appcelerator-studio-not-recognized-as-alloy",5,test +TISTUD-7557,New Workflow to set proxy settings on corporate network,"came across these problems: 1) on studio startup, it is hard to be able to enter your proxy settings, which means studio is un usable. It would help to allow shortcut to enter the proxy settings and/or read the OS property settings EXPECTED BEHAVIOR - allow user to enter in proxy settings if behind firewall to get studio to use the connection immediately",5,test +TISTUD-7562,For limited plan billing is not opened via wizard,I created a new account for the free plan and tried an App Store and Ad Hoc build in Studio. When I use the selectors on the top left it opens the Billing page as expected. But when I use the wizards (via the App Explorer view) it doesn't build neither open the Billing page. See the attached movie. It looks like TISTUD-7003 is not fully implemented?,5,test +TISTUD-7563,Replace TC project with AC project,"Placing this in the TISTUD project since it seems this is the place that might require a change or two. We want to reduce confusion between the two projects. Thus, we will be doing the following: # Move all open unresolved tickets from AC to TC # Close TC project # Redirect any references from TC to AC",2,test +TISTUD-7569,The studio login dialog after entering wrong credentials does not close on cancel,h5.Steps To Reproduce: 1. While logging in to studio enter wrong credentials. 2. You will see a login dialog come up. 3. Now click cancel button on the dialog box. h5.Actual Results: 1. The login dialog or studio does not close but the dialog keeps on popping up. 2. The only way to exit studio in this situation is to right click in the dock & close. h5.Expected Results: 1. Studio should close on clicking cancel.,3,test +TISTUD-7570,Code format function does not work well since 4.0.0,h5.Reproduce Step: Code format --> select the section of code and right click -> source -> format. h5.Error Error log attached.,8,test +TISTUD-7578,Show WatchKit section in tiapp editor,Studio should show a WatchKit section in TiApp editor if the app has SDK >= 4.1.0 and is targeted for iphone platform. The section should allow users to add new iOS extension. It should essentially let them point to xcode project to add extensions.,5,test +TISTUD-7579,Users should be able to create new WatchKit extension from Studio,"The WatchKit section in TiApp should allow users to create a new WatchKit extension project. Studio will invoke a CLI command to create a new WatchKit extension xcode project, and then add that extension to tiapp.xml. Will update the details of the CLI command to invoke when user attempts to create a WatchKit extension.",8,test +TISTUD-7580,Parse for targets in WatchKit extension xcode project,"Once user references a WatchKit extension project, Studio should parse the Xcode project of the WatchKit extension to find the targets (such as WatchKit app and WatchKit extension). Then, add these targets to the tiapp editor under /// structure.",8,test +TISTUD-7581,Allow users to set provisioning profiles for each target in extension,"When users sets up a WatchKit extension project, then we would have already help with the workflow to figure out targets of the extension, and now we need to let them to setup provisioning profiles for each target. There are essentially 3 provisioning profiles for each target as mentioned in https://wiki.appcelerator.org/display/pe/iOS+Extensions+and+WatchKit. CLI will read the provisioning profiles from tiapp.xml while launching the app onto device or packaging.",8,test +TISTUD-7583,Launch external display if the Titanium app has WatchKit extension,"If the Titanium app references a WatchKit extension, and if the simulator supports WatchKit, then Studio should pass in an additional argument to Appc CLI run command, in order to launch external display when user launches the app onto iOS simulator. We can find whether a simulator supports WatchKit from {{ti info -t ios}} output.",5,test +TISTUD-7584,Add a preference to avoid launching external display for WatchKit supported apps,"Add a setting in iOS preference page to avoid launching external display for the WatchKit supported Titanium app. The default value should be true, as we want to launch external display by default if the app references WatchKit. We can consider to add a menu item in the iOS launch menus, to let users manage launching WatchKit external display when they launch simulators (similar to Launch Automatically or Run Configuration menu item).",5,test +TISTUD-7591,"Error in ""StudioAnalytics""","Customer report: There is a error pop out after login studio or close a window in IDE. Error screen shot, error detail and log attached. Please help.",5,test +TISTUD-7593,Windows: Error when opening Studio on Windows,"h5.Description When opening Studio the below error is thrown, this appears to be due to the Windows SDK detection {code} !ENTRY org.eclipse.core.jobs 4 2 2015-06-18 16:20:28.962 !MESSAGE An internal error occurred during: ""Computing SDK Info..."". !STACK 0 java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.String at com.appcelerator.titanium.windows.internal.core.launching.Device.(Device.java:30) at com.appcelerator.titanium.windows.core.WindowsSDKLocator$2.map(WindowsSDKLocator.java:247) at com.appcelerator.titanium.windows.core.WindowsSDKLocator$2.map(WindowsSDKLocator.java:1) at com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:432) at com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:466) at com.appcelerator.titanium.windows.core.WindowsSDKLocator.parseTiInfo(WindowsSDKLocator.java:242) at com.appcelerator.titanium.windows.core.WindowsSDKLocator.initialize(WindowsSDKLocator.java:126) at com.appcelerator.titanium.core.mobile.SDKLocator.lazyInitialize(SDKLocator.java:235) at com.appcelerator.titanium.core.mobile.SDKLocator.getInitializationStatus(SDKLocator.java:137) at com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationHelper.getSDKInitializationStatus(MobileSDKConfigurationHelper.java:324) at com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController.refreshSDK(MobileSDKActionController.java:349) at com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:125) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} h5.Steps To Reproduce 1. Install 4.1.0 Studio from http://preview.appcelerator.com/appc-studio/ 2. Open Studio h5.Actual Result The above error is thrown h5.Expected Result Studio should not throw an error when opening",5,test +TISTUD-7595,Login: Studio errors with ECONNREFUSED when building with an invalidated session,"h5.Description When building from Studio if you have an expired or invalidated session when attempting to prompt for login Studio errors out with the below {code} Appcelerator Command-Line Interface, version 4.1.0-1 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. TRACE | __command__ search paths: [ ""/Users/eharris/.appcelerator/install/4.1.0-1/package"", ""/Users/eharris/.appcelerator/install/4.1.0-1/package/node_modules"", ""/Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/MacOS/node_modules"", ""/Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/node_modules"", ""/Applications/Appcelerator Studio/AppceleratorStudio.app/node_modules"", ""/Applications/Appcelerator Studio/node_modules"", ""/Applications/node_modules"", ""/node_modules"", ""/Users/eharris/.appcelerator/.npm/lib/node_modules"" ] DEBUG | [PLUGIN-LOAD] 0ms /Users/eharris/.appcelerator/install/4.1.0-1/package/appc.js DEBUG | [PLUGIN-LOAD] 527ms /Users/eharris/.appcelerator/install/4.1.0-1/package/node_modules/appc-cli-titanium/appc.js DEBUG | [PLUGIN-LOAD] 0ms /Users/eharris/.appcelerator/install/4.1.0-1/package/node_modules/arrow/appc.js log level set to ""trace"" executing command ""run"" set environment to {""registry"":""https://software-preprod.cloud.appctest.com"",""security"":""https://security-preprod.cloud.appctest.com"",""baseurl"":""https://360-preprod.cloud.appctest.com""} checking credentials for existing session Attempting to load session info from config file check if session is invalidated session is invalidated, forcing a login session has expired, forcing a login No session available, attempting interstitial command login... getCredentials() session: {} ERROR | Error: connect ECONNREFUSED at errnoException (net.js:905:11) at Object.afterConnect [as oncomplete] (net.js:896:19) {code} Logs from the log file are attached as econnrefused.txt h5.Steps To Reproduce 1. Open Studio 2. Logout from the CLI 3. Attempt to build h5.Actual Result Studio will error out with an ECONNREFUSED h5.Expected Result Studio should not error out and should prompt with a login dialog",3,test +TISTUD-7597,Tiapp: When saving a tiapp.xml in Studio if a system has non-numeric Android version installed the save fails,"h5.Description When saving a tiapp.xml in Studio if there is a non-numeric Android version present on the system, for example the L preview or the MNC preview then the save will fail with the below if the version is L, if the version is MNC then it will have MNC instead of L {code} Save Failed For input string: ""L"" {code} Full stack trace is attached as saveFailure.txt h5.Steps To Reproduce 1. Ensure you have Android L or Android MNC installed on your system 2. In Studio make a change in a tiapp.xml and save it h5.Actual Result The save will fail with the above error h5.Expected Result The save should not fail",3,test +TISTUD-7598,Failed to publish to MobileIron: No message body writer has been found for response class RuntimeException,The MobileIron plugin is no longer publishing apps correctly. The plugin is failing after the package is built and when it tries to publish to the MobileIron environment attached the error screen shot and log.,5,test +TISTUD-7599,AirWatch plugin is not publishing applications,The AirWatch plugin is no longer publishing apps correctly. The plugin is failing after the package is built and when it tries to publish to the MobileIron environment,5,test +TISTUD-7602,Remove Samples View from Appcelerator Studio,"The Samples view (not those on the Dashboard) lists an out-dated version of the Alloy RSS sample under Alloy (1st screenshot) https://github.com/appcelerator/alloy/tree/master/samples/rss The Dashboard has the updated version: https://github.com/appcelerator-developer-relations/Sample.RSS The Samples view also lists the updated (former classic) version under Classic (2nd screenshot) I'd suggest we remove both RSS samples from the view or even remove the view in full since it has other problems (missing icons) and is missing other samples (Movies, Directory) anyway. If not, then at least the Classic RSS sample should be removed and the Alloy RSS sample updated for the other repo URL.",3,test +TISTUD-7604,Missing Windows Store Certificate in Preferences dialog,"Open the Preferences dialog and navigate to Windows. 1. From the menu, select Window > Preferences to launch the Preferences dialog. 2. Navigate to Studio > Platforms > Windows. RESULTS: The Windows pane is missing the Windows Store Certificate field needed for Windows Store builds. The previous Windows plugin had this field. https://wiki.appcelerator.org/download/attachments/37540095/WindowsPreferences.PNG?api=v2",5,test +TISTUD-7605,Opening a Run Configuration dialog on Windows throws an error,"Run a project once on a Windows Emulator. Open the Run Configurations dialog by selecting the Run Configurations... option from the Launch Target drop-down in the global toolbar. RESULTS: Two error messages appear in the dialogs (see the screenshots), then the Run Configuartions dialog opens with a blank Windows configuration. This is the only information I get from the Studio log file: {noformat} !ENTRY com.aptana.core 1 0 2015-06-22 16:05:13.558 !MESSAGE (Build 4.1.0.201506211738) [INFO] com.aptana.core/debug/shell Running process: Process: ""C:\Users\QE-Tester\AppData\Roaming\npm\appcelerator.CMD"" ""ti"" ""info"" ""-o"" ""json"" ""-t"" ""android,genymotion"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""--prompt-type"" ""socket-bundle"" ""--prompt-port"" ""59138"" ""--username"" ""bhatfield@appcelerator.com"" ""--password"" ""**********"" Working directory: null Environment: {=::=::\, ALLUSERSPROFILE=C:\ProgramData, ANALYTICS_SOURCE=studio, APPC_ENV=preproduction, APPDATA=C:\Users\QE-Tester\AppData\Roaming, COMPUTERNAME=TESTER, ComSpec=C:\Windows\system32\cmd.exe, CommonProgramFiles=C:\Program Files (x86)\Common Files, CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files, CommonProgramW6432=C:\Program Files\Common Files, FP_NO_HOST_CHECK=NO, HOMEDRIVE=C:, HOMEPATH=\Users\QE-Tester, JAVA_HOME=C:/Program Files (x86)/Java/jdk1.7.0_40, LOCALAPPDATA=C:\Users\QE-Tester\AppData\Local, LOGONSERVER=\\TESTER, NUMBER_OF_PROCESSORS=4, OS=Windows_NT, PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC, PROCESSOR_ARCHITECTURE=x86, PROCESSOR_ARCHITEW6432=AMD64, PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel, PROCESSOR_LEVEL=6, PROCESSOR_REVISION=3c03, PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\Intel\, PUBLIC=C:\Users\Public, Path=C:/Program Files (x86)/Java/jdk1.7.0_40\bin;C:/Program Files (x86)/Java/jdk1.7.0_40/bin/../jre/bin/client;C:/Program Files (x86)/Java/jdk1.7.0_40/bin/../jre/bin;C:/Program Files (x86)/Java/jdk1.7.0_40/bin/../jre/lib/i386;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\apache-ant-1.9.4\bin;C:\Program Files (x86)\GnuWin32\bin;C:\apache-ant-1.9.4\apache-ant-1.9.4\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\nodejs\;C:\Program Files (x86)\Java\jdk1.7.0_40\bin;C:\Program Files (x86)\GnuWin32\bin;C:\apache-ant-1.9.4\apache-ant-1.9.4\bin;C:\android-sdk-win;C:\android-sdk-win\platform-tools;C:\android-sdk-win\tools;C:\Program Files (x86)\Git\bin;C:\Users\QE-Tester\AppData\Roaming\npm;C:\Program Files (x86)\Java\jdk1.7.0_80\bin;C:\Users\QE-Tester\Desktop;;C:\Users\QE-Tester\AppData\Roaming\Appcelerator\Appcelerator Studio\plugins\com.appcelerator.titanium.python.win32_1.0.0.1338515509\python, ProgramData=C:\ProgramData, ProgramFiles=C:\Program Files (x86), ProgramFiles(x86)=C:\Program Files (x86), ProgramW6432=C:\Program Files, SESSIONNAME=Console, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=4.1.0.201506211738, SystemDrive=C:, SystemRoot=C:\Windows, TEMP=C:\Users\QE-TES~1\AppData\Local\Temp, TMP=C:\Users\QE-TES~1\AppData\Local\Temp, USERDOMAIN=tester, USERDOMAIN_ROAMINGPROFILE=tester, USERNAME=QE-Tester, USERPROFILE=C:\Users\QE-Tester, VBOX_MSI_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\, VS110COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\, VS120COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\, windir=C:\Windows} !ENTRY com.aptana.editor.common 1 0 2015-06-22 16:05:20.659 !MESSAGE (Build 4.1.0.201506211738) [INFO] com.aptana.editor.common/debug/presentation Reconciling process set for partition limit of 4,000 partitions, background delay of 2,000ms, iteration delay of 500ms, and minimal visible length of 20,000 lines !ENTRY com.aptana.editor.common 1 0 2015-06-22 16:05:20.675 !MESSAGE (Build 4.1.0.201506211738) [INFO] com.aptana.editor.common/debug/presentation Initiating presentation reconciling for region at offset 0, length 3,708 in document of length 3,708 {noformat}",5,test +TISTUD-7606,"For Windows Emulators, Studio displays the UDIDs and not the name of the emulator","In the Launch Target drop-down, Studio lists the emulators using the UDID rather than the name. CLI info output {noformat} 8.1 Emulator 8.1 WVGA 4 inch 512MB UDID 8-1-1 Emulator 8.1 WVGA 4 inch UDID 8-1-2 Emulator 8.1 WXGA 4.5 inch UDID 8-1-3 Emulator 8.1 720P 4.7 inch UDID 8-1-4 Emulator 8.1 1080P 5.5 inch UDID 8-1-5 Emulator 8.1 1080P 6 inch UDID 8-1-6 {noformat}",3,test +TISTUD-7607,Windows SDK preference page doesn't pick up publisher GUID from ti config,"I have a default Windows publisher GUID set up in my ti config using the key ""windows.phone.publisherGuid"". It uses it by default in my ti build commands. But the Studio Windows preference page doesn't pick up that value, I just see a blank text field.",5,test +TISTUD-7608,Shouldn't need to set Windows SDK path in preference page to be configured and see Windows options to run,"I see no options to run an app on Windows phone/store emulator until I set up the SDK path in the Studio > Platforms > Windows preference page. Setting the path is not necessary - the CLI will pick up if the user has their environment configured to use Windows. It's more like iOS in that the path is a well-known location for the SDKs, and we just need to ensure that the CLi can find it and visual studio/etc.",5,test +TISTUD-7611,'iOS/WatchKit Extensions' section in tiapp for projets < 4.1.0,"The 'iOS/WatchKit Extensions' section in the tiapp.xml overview tab exists for projects under SDK 4.1.0. According to linked ticket, this is incorrect. *Steps to reproduce issue*: 1. Create a new project in Studio with SDK < 4.1.0 2. Open the tiapp.xml overview tab *Actual Results* The 'iOS/WatchKit Extensions' section exists *Expected Results* The 'iOS/WatchKit Extensions' section does not exist",8,test +TISTUD-7612,"Windows packaging dialog shows ""NLS missing message""","h5.Description: 1. Create an app for windows platform. 2. Follow the steps to package a window app. h5.Actual Result: 1. The packaging dialog shows ""NLS missing message"". *NOTE* - Attached screenshot for reference. h5.Expected Result: 1. We should not see any ""NLS missing message"" on the packaging dialog. ",2,test +TISTUD-7616,"Studio is not enabling services (Cloud, Test, Performance) no errors","h3. Description I created an application and I tried to enable the services, it failed with no error just analytics got enabled h3. Steps to reproduce * Create a new Alloy Application * Enable services * Analytics got enabled * No other services are enabled Log doesn't show anything, and MATT log has no info h3. Notes This seems to occur when Studio does not ask for login information on startup and prompting breaks.",5,test +TISTUD-7617,Windows: If no publisher GUID is set in preferences then the build will fail,"h5.Description When building for Windows if the publisher GUID is not set in the preference then the build will fail with the {{Launching app on Windows device failed}}, until the user shows the details there is not mention of the reason why the build until details is clicked and then the following is shown {{Invalid Publisher GUID. Please set the value in the Windows platform preference.}}. Rather than failing, the user should be prompted to enter a GUID. h5.Steps To Reproduce 1. Check the Windows preferences to make sure you have no GUID set 2. Attempt to build a project for Windows h5.Actual Result The build fails with the above errors h5.Expected Result The build should not fail and the user should be prompted for a GUID",5,test +TISTUD-7621,Studio hangs when generating Alloy autocomplete list,"Studio hangs whenever generating an autocomplete list when editing an Alloy XML file (not when editing js...) Here's a relevant excerpt from my studio log.... {code} !ENTRY com.aptana.index.core 4 0 2015-06-26 12:42:16.623 !MESSAGE (Build 4.0.1.201506021908) [ERROR] An error occurred while processing the following JSON string {""name"":""focus"",""description"":""

Fired when the view element gains focus.

"",""since"":[],""deprecated"":false,""userAgents"":null,""owningType"":""Titanium.UI.ImageView"",""properties"":[]} !STACK 0 java.lang.NullPointerException com.aptana.js.core.model.EventElement.fromJSON(EventElement.java:73) com.aptana.index.core.IndexReader.populateElement(IndexReader.java:207) com.aptana.index.core.IndexReader.populateElement(IndexReader.java:181) com.aptana.js.internal.core.index.JSIndexReader.createEvent(JSIndexReader.java:78) com.aptana.js.internal.core.index.JSIndexReader$1.map(JSIndexReader.java:219) com.aptana.js.internal.core.index.JSIndexReader$1.map(JSIndexReader.java:1) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:432) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:466) com.aptana.js.internal.core.index.JSIndexReader.getEvents(JSIndexReader.java:215) com.aptana.js.core.index.JSIndexQueryHelper.getEvents(JSIndexQueryHelper.java:388) com.appcelerator.titanium.alloy.core.index.AlloyQueryHelper.getElement(AlloyQueryHelper.java:313) com.appcelerator.titanium.alloy.core.index.AlloyQueryHelper$2.map(AlloyQueryHelper.java:186) com.appcelerator.titanium.alloy.core.index.AlloyQueryHelper$2.map(AlloyQueryHelper.java:1) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:432) com.aptana.core.util.CollectionsUtil.map(CollectionsUtil.java:466) com.appcelerator.titanium.alloy.core.index.AlloyQueryHelper.getElements(AlloyQueryHelper.java:175) com.appcelerator.titanium.alloy.internal.ui.contentassist.AlloyViewContentAssistProcessor.getElements(AlloyViewContentAssistProcessor.java:130) com.aptana.editor.xml.contentassist.XMLContentAssistProcessor.addElementProposals(XMLContentAssistProcessor.java:309) com.aptana.editor.xml.contentassist.XMLContentAssistProcessor.doComputeCompletionProposals(XMLContentAssistProcessor.java:625) com.aptana.editor.common.CommonContentAssistProcessor.computeCompletionProposals(CommonContentAssistProcessor.java:417) com.aptana.editor.common.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:2221) com.aptana.editor.common.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:394) com.aptana.editor.common.contentassist.CompletionProposalPopup.access$7(CompletionProposalPopup.java:388) com.aptana.editor.common.contentassist.CompletionProposalPopup$1.run(CompletionProposalPopup.java:331) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) com.aptana.editor.common.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:325) com.aptana.editor.common.contentassist.ContentAssistant$AutoAssistListener$1.run(ContentAssistant.java:468) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) 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:648) org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) org.eclipse.equinox.launcher.Main.run(Main.java:1465) {code}",5,test +TISTUD-7619,Unable to package from studio for windows exception thrown,h5.Steps To Reproduce; 1. Launch studio. 2. Create an app for windows. 3. Try to package by giving the path for the packaged app. h5.Actual Result: 1. We get exception from studio. (Screenshot attached for reference). h5.Expected Result: 1. Packaging should be successful.,5,test +TISTUD-7622,Windows: Building for Windows Local Machine fails due to change in build process from CLI,"h5.Description The workflow for building a Windows Platform for local machine has changed. The user now has to generate a pfx file, or provide an existing one, which is used to sign the app in order to build. The process if as follows 1. User begins build 2. User is prompted for the pfx file to be used, if the prompt is left blank then a new one will be generated. I believe this is using MakeCert 3. User is prompted to enter passwords for the cert, this using a GUI and is from the MakeCert process 4. User is prompted to import the key, again a GUI and a Windows process 5. Build continues At the moment a Studio build for Windows Local Machine fails with {{\[ERROR] : Missing required option: --ws-cert }} as Studio is passing in --no-prompt which skips the prompting for the above h5.Steps to reproduce 1. Build for Windows Local machine in Studio 2. Build for Windows Local machine from the CLI h5.Actual result 1. The build will fail 2. You will be taken through the process as outlined above h5.Expected result The build should not fail and the process should be similar to the CLI process",13,test +TISTUD-7624,Platform Configuration window does not show download and install option for Windows SDK,"When the Studio does not find the base folder for Windows SDK, the dashboard shows an option to Download the windows sdk. Click on download button opens up the Platform Configuration window which does not have option for Windows SDK Refer to attached screenshot Steps to Reproduce: 1. Remove the Windows SDK from the system. I had removed the folder C:\Program Files (x86)\Microsoft SDKs folder. 2. Open the studio. 3. Check that dashboard. It shows Download button for Windows. 4. Click on Download button Actual Result: The platform configuration window that opens up does not show option for Windows SDK Expected Result: The Windows SDK download and install option should be available.",5,test +TISTUD-7630,Shortcuts for Studio does not taking effect,h6.Issue Description Studio shortcuts like cmd+Shift+F for indentations and cmd+D for deleting current line are not working properly most of the times. Tried out increasing the amount of memory modifying the INI configuration file but that didn't help. Attached the Log file enabling debug level as All. h6.Before {code} --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Xms128m -Xmx1024m -XX:MaxPermSize=256m {code} h6.After {code} --launcher.XXMaxPermSize 1024m --launcher.defaultAction openFile -vmargs -Xms128m -Xmx1024m -XX:MaxPermSize=1024m {code},8,test +TISTUD-7632,On windows node process linger around consuming memory which causes performance degradation,*NOTE* - I encountered this issue 3 times as of now in the past few days while testing for windows platform on windows 8.1 enterprise 64 -bit. h5.Steps To Reproduce: 1. Build a windows app from studio multiple times. 2. Open windows task manager. 3. Observe the node processes. h5.Actual Results: 1. You will see that the node processes created as a result of building apps still linger & are not killed. 2. Some time these end up consuming lot of memory which cause performance degradation of the system. *Attached screenshot for reference* h5.Expected Results: 1. The node process should be killed & should not linger consuming memory. ,5,test +TISTUD-7637,Liveview: --liveview flag is not passed to the CLI when building for Windows Platform,h5.Description When building for Windows Platform from Studio even if liveview is enabled then the --liveview flag is not passed in to the CLI from Studio. Liveview currently does not support Windows Platform TIMOB-19185 however. h5.Steps to reproduce 1. Enable liveview 2. Build an app for Windows Platform 3. Check the logs for the build command h5.Actual result On the command passed to the CLI there will be no --liveview flag h5.Expected result There should be a --liveview flag,2,test +TISTUD-7639,"Clicking on the ""Arrow Builder"" link in the release notes take you to http://www.appcelerator.com/product/","*Details:* Clicking on the ""Arrow Builder"" link in the release notes take you to http://www.appcelerator.com/product/. *Steps to reproduce:* # Revert to an older version of Appc Studio # Go to Help > Check for Appcelerator Updates # Wait for release notes to appear # Click on the ""Arrow Builder"" link *Actual:* The link takes you to http://www.appcelerator.com/product/. *Expected:* The link should take you to http://docs.appcelerator.com/platform/latest/#!/guide/Arrow_Builder_Release_Notes.",3,test +TISTUD-7642,"4.1.0.GA causing An internal error occurred during: ""Loading Platform Contents"". java.lang.NullPointerException","after upgrading to 4.1.0GA i'm getting the following error when opening the tiapp.xml An internal error occurred during: ""Loading Platform Contents"". java.lang.NullPointerException at com.appcelerator.titanium360.internal.core.Titanium360User.getStoredOrganizations(Titanium360User.java:222) at com.appcelerator.titanium360.internal.core.Titanium360User.getOrganizations(Titanium360User.java:185) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.isCurrentUserAuthorized(ThreeSixtyProject.java:594) at com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.get360State(Titanium360TiappContributor.java:534) at com.appcelerator.titanium360.ui.tiapp.Titanium360TiappContributor.updateControlsData(Titanium360TiappContributor.java:406) at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppContributorSection.updateControlsData(TiAppContributorSection.java:100) at com.appcelerator.titanium.ui.ide.tiappEditor.AbstractTiAppSection.refresh(AbstractTiAppSection.java:162) @mikewarnescom throws the following error during the upgrade Error encountered during update An error occurred while uninstalling session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]com.appcelerator.titanium.feature.360.rcp_root 4.0.0.201505202026-867aFEkFGvmRb6X4eY1rvm8ONCXE --> null, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction). Backup of file /Applications/Appcelerator Studio/version.txt failed. File that was copied to backup could not be deleted: /Applications/Appcelerator Studio/version.txt",3,test +TISTUD-7640,Studio intermittently crashes with EXC_BAD_ACCESS,"I have encountered the below crash 3 times in 3 hours of working in Studio. It seems to occur when saving changes in a project file. *Steps to reproduce issue*: 1. Create a project in Studio 2. Work in Studio, creating an app, but build from the CLI *Expected Results*: Studio does not crash *Actual Results*: Studio occasionally crashes *Notes*: I am using El Capitan Beta 3. Crash is: {code} Process: AppceleratorStudio [28422] Path: /Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/MacOS/AppceleratorStudio Identifier: com.appcelerator.appcelerator-studio Version: 4.1.0 (4.1.0.201507071122) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: AppceleratorStudio [28422] User ID: 502 Date/Time: 2015-07-10 12:05:12.584 -0700 OS Version: Mac OS X 10.11 (15A204h) Report Version: 11 Anonymous UUID: C4A8A040-44B1-CEF7-9844-0CAA936F85E5 Sleep/Wake UUID: 0AA9DC93-0173-4E46-B758-9E8C56A04847 Time Awake Since Boot: 45000 seconds Time Since Wake: 15000 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGABRT) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0x8: --> __TEXT 0000000100000000-0000000100004000 [ 16K] r-x/rwx SM=COW /Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/MacOS/AppceleratorStudio Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff8ffe2096 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff937335cd pthread_kill + 90 2 libsystem_c.dylib 0x00007fff928f683b abort + 129 3 libjvm.dylib 0x00000001054fdb93 os::abort(bool) + 25 4 libjvm.dylib 0x0000000105608220 VMError::report_and_die() + 2316 5 libjvm.dylib 0x00000001054ff52d JVM_handle_bsd_signal + 1083 6 libsystem_platform.dylib 0x00007fff93e32eaa _sigtramp + 26 7 com.apple.WebCore 0x00007fff85a45b5a WebCore::PageCache::markPagesForContentsSizeChanged(WebCore::Page&) + 42 8 com.apple.WebCore 0x00007fff84f3093d WebCore::FrameView::setContentsSize(WebCore::IntSize const&) + 221 9 com.apple.WebCore 0x00007fff84f66356 WebCore::FrameView::adjustViewSize() + 150 10 com.apple.WebCore 0x00007fff84f5c9e2 WebCore::FrameView::layout(bool) + 3410 11 com.apple.WebKitLegacy 0x00007fff830e166b -[WebHTMLView layoutToMinimumPageWidth:height:originalPageWidth:originalPageHeight:maximumShrinkRatio:adjustingViewSize:] + 299 12 com.apple.WebKitLegacy 0x00007fff830dacbe -[WebDynamicScrollBarsView(WebInternal) updateScrollers] + 158 13 com.apple.WebCore 0x00007fff85be703d WebCore::ScrollView::platformSetScrollbarModes() + 45 14 com.apple.WebCore 0x00007fff84f24881 WebCore::ScrollView::setScrollbarModes(WebCore::ScrollbarMode, WebCore::ScrollbarMode, bool, bool) + 241 15 com.apple.WebCore 0x00007fff84f5c3fc WebCore::FrameView::layout(bool) + 1900 16 com.apple.WebKitLegacy 0x00007fff830e166b -[WebHTMLView layoutToMinimumPageWidth:height:originalPageWidth:originalPageHeight:maximumShrinkRatio:adjustingViewSize:] + 299 17 com.apple.WebKitLegacy 0x00007fff830db279 -[WebDynamicScrollBarsView(WebInternal) updateScrollers] + 1625 18 com.apple.WebCore 0x00007fff85be703d WebCore::ScrollView::platformSetScrollbarModes() + 45 19 com.apple.WebCore 0x00007fff84f24881 WebCore::ScrollView::setScrollbarModes(WebCore::ScrollbarMode, WebCore::ScrollbarMode, bool, bool) + 241 20 com.apple.WebCore 0x00007fff84f8e190 WebCore::FrameView::~FrameView() + 224 21 com.apple.WebCore 0x00007fff84f8e09e WebCore::FrameView::~FrameView() + 14 22 com.apple.WebCore 0x00007fff850fdb7a WebCore::CachedFrame::clear() + 186 23 com.apple.WebCore 0x00007fff850fd7c8 WebCore::CachedPage::~CachedPage() + 24 24 com.apple.WebCore 0x00007fff85a45988 WebCore::PageCache::prune(WebCore::PruningReason) + 88 25 com.apple.WebCore 0x00007fff84f22794 WebCore::FrameLoader::commitProvisionalLoad() + 292 26 com.apple.WebCore 0x00007fff84fa333f WebCore::DocumentLoader::commitLoad(char const*, int) + 79 27 com.apple.WebCore 0x00007fff84fa1bb4 WebCore::DocumentLoader::continueAfterContentPolicy(WebCore::PolicyAction) + 1492 28 com.apple.WebCore 0x00007fff84f80753 WebCore::DocumentLoader::responseReceived(WebCore::CachedResource*, WebCore::ResourceResponse const&) + 1603 29 com.apple.WebCore 0x00007fff8539101e WebCore::DocumentLoader::handleSubstituteDataLoadNow() + 654 30 com.apple.JavaScriptCore 0x00007fff91f8b483 WTF::timerFired(__CFRunLoopTimer*, void*) + 35 31 com.apple.CoreFoundation 0x00007fff84b35ab4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 32 com.apple.CoreFoundation 0x00007fff84b35743 __CFRunLoopDoTimer + 1075 33 com.apple.CoreFoundation 0x00007fff84bb0eda __CFRunLoopDoTimers + 298 34 com.apple.CoreFoundation 0x00007fff84af0bb1 __CFRunLoopRun + 1841 35 com.apple.CoreFoundation 0x00007fff84af0218 CFRunLoopRunSpecific + 296 36 com.apple.HIToolbox 0x00007fff92567ce9 RunCurrentEventLoopInMode + 235 37 com.apple.HIToolbox 0x00007fff92567a7f ReceiveNextEventCommon + 432 38 com.apple.HIToolbox 0x00007fff925678bf _BlockUntilNextEventMatchingListInModeWithFilter + 71 39 com.apple.AppKit 0x00007fff902d1732 _DPSNextEvent + 927 40 com.apple.AppKit 0x00007fff9069ef74 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 324 41 libswt-pi-cocoa-4427.jnilib 0x000000010f0f1d6a Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSendSuper__Lorg_eclipse_swt_internal_cocoa_objc_1super_2JJJJZ + 122 42 ??? 0x0000000105b48698 0 + 4390684312 43 ??? 0x0000000105b3c175 0 + 4390633845 44 ??? 0x0000000105b3c175 0 + 4390633845 45 ??? 0x0000000105b364e7 0 + 4390610151 46 libjvm.dylib 0x00000001053b9d90 JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 554 47 libjvm.dylib 0x00000001053b9b60 JavaCalls::call(JavaValue*, methodHandle, JavaCallArguments*, Thread*) + 40 48 libjvm.dylib 0x00000001053ed304 jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) + 230 49 libjvm.dylib 0x00000001053e5aec jni_CallStaticLongMethodV + 233 50 libswt-cocoa-4427.jnilib 0x000000010f0b6f92 callback + 1344 51 libswt-cocoa-4427.jnilib 0x000000010f09c525 fn3_6 + 90 52 libswt-pi-cocoa-4427.jnilib 0x000000010f0edbc2 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSend__JJJJJZ + 79 53 ??? 0x0000000105b48698 0 + 4390684312 54 ??? 0x0000000105b3c175 0 + 4390633845 55 ??? 0x0000000105b3c233 0 + 4390634035 56 ??? 0x0000000105b3c350 0 + 4390634320 57 ??? 0x0000000105b3c706 0 + 4390635270 58 ??? 0x0000000105b3c058 0 + 4390633560 59 ??? 0x0000000105b3c058 0 + 4390633560 60 ??? 0x0000000105b3c058 0 + 4390633560 61 ??? 0x0000000105b3c058 0 + 4390633560 62 ??? 0x0000000105b3c058 0 + 4390633560 63 ??? 0x0000000105b3c058 0 + 4390633560 64 ??? 0x0000000105b3c706 0 + 4390635270 65 ??? 0x0000000105b3c058 0 + 4390633560 66 ??? 0x0000000105b3c350 0 + 4390634320 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff8ffe308a kevent_qos + 10 1 libdispatch.dylib 0x00007fff8d35d7f1 _dispatch_mgr_invoke + 251 2 libdispatch.dylib 0x00007fff8d35d445 _dispatch_mgr_thread + 52 Thread 2: 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054dab0d Monitor::wait(bool, long, bool) + 375 6 libjvm.dylib 0x000000010534be6e GCTaskManager::get_task(unsigned int) + 56 7 libjvm.dylib 0x000000010534cd63 GCTaskThread::run() + 349 8 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 9 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 11 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 3: 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054dab0d Monitor::wait(bool, long, bool) + 375 6 libjvm.dylib 0x000000010534be6e GCTaskManager::get_task(unsigned int) + 56 7 libjvm.dylib 0x000000010534cd63 GCTaskThread::run() + 349 8 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 9 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 11 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 4: 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054dab0d Monitor::wait(bool, long, bool) + 375 6 libjvm.dylib 0x000000010534be6e GCTaskManager::get_task(unsigned int) + 56 7 libjvm.dylib 0x000000010534cd63 GCTaskThread::run() + 349 8 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 9 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 11 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054dab0d Monitor::wait(bool, long, bool) + 375 6 libjvm.dylib 0x000000010534be6e GCTaskManager::get_task(unsigned int) + 56 7 libjvm.dylib 0x000000010534cd63 GCTaskThread::run() + 349 8 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 9 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 11 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 6: 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054faddb os::PlatformEvent::park(long long) + 385 3 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 4 libjvm.dylib 0x00000001054dab0d Monitor::wait(bool, long, bool) + 375 5 libjvm.dylib 0x000000010560d8b0 VMThread::loop() + 444 6 libjvm.dylib 0x000000010560d35b VMThread::run() + 121 7 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 8 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 9 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 10 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 7:: Java: Reference Handler 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054f2e57 ObjectMonitor::wait(long long, bool, Thread*) + 757 4 libjvm.dylib 0x00000001055a24a3 ObjectSynchronizer::wait(Handle, long long, Thread*) + 203 5 libjvm.dylib 0x000000010540e0fc JVM_MonitorWait + 156 6 ??? 0x0000000105b48698 0 + 4390684312 7 ??? 0x000000010623200c 0 + 4397932556 Thread 8:: Java: Finalizer 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054f2e57 ObjectMonitor::wait(long long, bool, Thread*) + 757 4 libjvm.dylib 0x00000001055a24a3 ObjectSynchronizer::wait(Handle, long long, Thread*) + 203 5 libjvm.dylib 0x000000010540e0fc JVM_MonitorWait + 156 6 ??? 0x0000000105b48698 0 + 4390684312 7 ??? 0x0000000105ef2388 0 + 4394525576 Thread 9:: Java: Signal Dispatcher 0 libsystem_kernel.dylib 0x00007fff8ffdca02 semaphore_wait_trap + 10 1 libjvm.dylib 0x00000001054fc4a0 check_pending_signals(bool) + 128 2 libjvm.dylib 0x00000001054f8da8 signal_thread_entry(JavaThread*, Thread*) + 57 3 libjvm.dylib 0x00000001055d2b47 JavaThread::thread_main_inner() + 155 4 libjvm.dylib 0x00000001055d424f JavaThread::run() + 419 5 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 6 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 7 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 8 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 10:: Java: C2 CompilerThread0 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054daa74 Monitor::wait(bool, long, bool) + 222 6 libjvm.dylib 0x00000001052a40ab CompileQueue::get() + 153 7 libjvm.dylib 0x00000001052a4c43 CompileBroker::compiler_thread_loop() + 425 8 libjvm.dylib 0x00000001055d2b47 JavaThread::thread_main_inner() + 155 9 libjvm.dylib 0x00000001055d424f JavaThread::run() + 419 10 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 11 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 12 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 13 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 11:: Java: C2 CompilerThread1 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054daa74 Monitor::wait(bool, long, bool) + 222 6 libjvm.dylib 0x00000001052a40ab CompileQueue::get() + 153 7 libjvm.dylib 0x00000001052a4c43 CompileBroker::compiler_thread_loop() + 425 8 libjvm.dylib 0x00000001055d2b47 JavaThread::thread_main_inner() + 155 9 libjvm.dylib 0x00000001055d424f JavaThread::run() + 419 10 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 11 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 12 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 13 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 12:: Java: Service Thread 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054f9e29 os::PlatformEvent::park() + 173 3 libjvm.dylib 0x00000001054da0be ParkCommon(ParkEvent*, long long) + 42 4 libjvm.dylib 0x00000001054da8b0 Monitor::IWait(Thread*, long long) + 160 5 libjvm.dylib 0x00000001054dab0d Monitor::wait(bool, long, bool) + 375 6 libjvm.dylib 0x00000001055521d5 ServiceThread::service_thread_entry(JavaThread*, Thread*) + 109 7 libjvm.dylib 0x00000001055d2b47 JavaThread::thread_main_inner() + 155 8 libjvm.dylib 0x00000001055d424f JavaThread::run() + 419 9 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 10 libsystem_pthread.dylib 0x00007fff93731cc3 _pthread_body + 131 11 libsystem_pthread.dylib 0x00007fff93731c40 _pthread_start + 168 12 libsystem_pthread.dylib 0x00007fff9372eda5 thread_start + 13 Thread 13: 0 libsystem_kernel.dylib 0x00007fff8ffe1f46 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff937321c8 _pthread_cond_wait + 711 2 libjvm.dylib 0x00000001054faddb os::PlatformEvent::park(long long) + 385 3 libjvm.dylib 0x00000001054faf9f os::sleep(Thread*, long long, bool) + 321 4 libjvm.dylib 0x00000001055d3e70 WatcherThread::run() + 134 5 libjvm.dylib 0x00000001054fe1c6 java_start(Thread*) + 294 6 libsystem_pthread.dylib 0x00007fff93731cc3...",5,test +TISTUD-7641,"Regression: Slow due to ""Failed to get the node modules path for package alloy""","After update to Studio 4.1.0, I keep getting the following. Studio becomes slow to respond. Here is the error log: {code} !ENTRY com.appcelerator.titanium.alloy.core 4 0 2015-07-10 15:43:06.426 !MESSAGE (Build 4.1.0.201507071122) [ERROR] Failed to get the node modules path for package 'alloy'. !STACK 1 org.eclipse.core.runtime.CoreException: Failed to get the node modules path for package 'alloy'. com.aptana.js.internal.core.node.NodePackageManager.getModulesPath(NodePackageManager.java:496) com.appcelerator.titanium.alloy.core.AlloyCorePlugin.getAlloyModulesPath(AlloyCorePlugin.java:178) com.appcelerator.titanium.alloy.core.AlloyUtil.getAlloyJscaPath(AlloyUtil.java:183) com.appcelerator.titanium.alloy.core.index.AlloyBuildPathContributor.getBuildPathEntries(AlloyBuildPathContributor.java:37) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:354) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:239) com.aptana.buildpath.core.BuildPathManager.hasBuildPath(BuildPathManager.java:373) com.appcelerator.titanium.core.util.ContentAssistMetadataUtils.getProjectMetadataBuildPath(ContentAssistMetadataUtils.java:143) com.appcelerator.titanium.core.internal.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:93) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:321) com.aptana.js.core.index.JSIndexQueryHelper.getIndices(JSIndexQueryHelper.java:123) com.aptana.js.core.index.JSIndexQueryHelper.(JSIndexQueryHelper.java:98) com.appcelerator.titanium.alloy.core.validators.AlloyViewValidator.getQueryHelper(AlloyViewValidator.java:431) com.appcelerator.titanium.alloy.core.validators.AlloyViewValidator.doBuildFile(AlloyViewValidator.java:224) com.appcelerator.titanium.alloy.core.validators.AlloyViewValidator.buildEnding(AlloyViewValidator.java:132) com.aptana.core.internal.build.LazyBuildParticipant.buildEnding(LazyBuildParticipant.java:67) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:341) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:277) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:235) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.initialReconcile(CommonReconcilingStrategy.java:149) com.aptana.editor.common.text.reconciler.CommonReconciler.initialProcess(CommonReconciler.java:188) org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) !SUBENTRY 1 com.aptana.js.core 4 0 2015-07-10 15:43:06.426 !MESSAGE Failed to get the node modules path for package 'alloy'. {code}",5,test +TISTUD-7780,Launching simulator/emulator creates a new Node.js process without killing the previous one,"Every time i launch the *simulator* (i'm using *Genymotion*), *Appcelerator Studio* recreate the process *NODE* and the process *ADB* (without remove the previous process). Obviously after a while this is a serious problem for the RAM. *Update :* Maybe the problem is *Genymotion* ? *Update 2 :* Now the problem there is also using the iOS simulator (iOS SDK 9.0 , Titanium SDK 5.0.1)",8,test +TISTUD-7652,"If you Refresh Devices, a NullPointerException is thrown","*Details:* If you Refresh Devices from the drop down list, a NullPointerException is thrown. *Note:* This issue *does not occur* with SDK 4.1.0.GA. *Steps to reproduce:* # Create an Alloy project from Appc Studio # In the drop down list, select Refresh Devices; *you do not need to plug in any devices* *Actual:* NullPointerException is thrown; see attachment for dialog and below of the exception from Studio logs: {code} !ENTRY org.eclipse.core.jobs 4 2 2015-07-28 11:15:52.362 !MESSAGE An internal error occurred during: ""Refreshing Devices..."". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.ios.core.IOSSDKLocator.loadSimulators(IOSSDKLocator.java:269) com.appcelerator.titanium.ios.core.IOSSDKLocator.parseTiInfo(IOSSDKLocator.java:191) com.appcelerator.titanium.ios.core.IOSSDKLocator.updateTiInfo(IOSSDKLocator.java:145) com.appcelerator.titanium.ios.core.IOSSDKLocator.refreshDevices(IOSSDKLocator.java:720) com.appcelerator.titanium.internal.ui.launching.DynamicLaunchShortcutManager$4.run(DynamicLaunchShortcutManager.java:273) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} *Expected:* NullPointerException should not be thrown if you refresh devices.",5,test +TISTUD-7653,Can't create modules(Android or IOS) from appc studio 4.1.1.201507141126,*Seeing this issue with:* * Appc CLI 4.1.2 with SDK 4.1.0.GA * Appc CLI 4.1.2 with latest master * Appc CLI 4.2.0-1 with 4.1.0.GA h5.Steps To Reproduce: 1. Using appc studio 4.1.1.201507141126 try to create a module(android or IOS). h5.Actual Results: 1. We can't create a module. 2. In studio logs we get: {code} !ENTRY org.eclipse.ui 4 0 2015-07-28 12:40:33.627 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.ui.ide.wizard.NewMobileModuleProjectCreationPage.validatePlatforms(NewMobileModuleProjectCreationPage.java:431) com.appcelerator.titanium.ui.ide.wizard.NewMobileModuleProjectCreationPage.createControl(NewMobileModuleProjectCreationPage.java:228) org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:178) org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:759) org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:622) org.eclipse.jface.window.Window.create(Window.java:435) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101) org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:95) org.eclipse.jface.action.Action.runWithEvent(Action.java:519) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4199) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4042) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3669) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:483) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) org.eclipse.equinox.launcher.Main.run(Main.java:1465) {code} h5.Expected Results: 1. We should be able to create modules(android & IOS) from appc studio.,3,test +TISTUD-7659,Appcelerator Studio getting crashed while closing Dashboard Window/Tab,h6.Reproduce Step: 1. Open Appcelerator Studio normally. 2. Close dashboard tab in studio. h6.Expect Result: The studio should work well h6.Actual Result: Studio crashes (attached screen shot) Note: here is the [crash log|https://gist.github.com/radamantis/c9088c162e2db91e946e],5,test +TISTUD-7661,Studio login should have option to remember username,Studio login should have option to remember username Some enterprise email addresses are VERY long and we have had this request from a recent prospect,5,test +TISTUD-7663,Installer should check for and deal with 64-bit vs 32-bit JDK version on Windows,Installer should check for and deal with 64-bit vs 32-bit JDK version on Windows See https://wiki.appcelerator.org/display/prd/Installer+Checks for background info This issue did happen recently for an Enterprise evaluation on Windows 8,5,test +TISTUD-7664,Installer should check for and deal with correct JDK version on Windows,"Installer should check for and deal with correct JDK version on Windows See https://wiki.appcelerator.org/display/prd/Installer+Checks for background info Not sure if this has occurred recently, but do recall this from the past",5,test +TISTUD-7665,OS X installer should check for and install correct Node.js version,Installer should check for and deal with correct node version See https://wiki.appcelerator.org/display/prd/Installer+Checks for background Note that it may be possible that user has other software that requires a specific version of node and we require a different version of node so we need to let the user know what we are doing and provide options Not sure that this issue has happened recently but it is one that has occurred in the past,5,test +TISTUD-7666,Studio cannot find android sdk even after studio installed android sdk on Windows,Studio cannot find android sdk even after studio installed android sdk on Windows See https://wiki.appcelerator.org/display/prd/Installer+Checks for background info This issue has occurred recently during Enterprise evaluations,5,test +TISTUD-7673,Studio cannot detect Xcode 7,"*Details:* Latest Appcelerator Studio version (from Release branch) cannot detect Xcode 7 (beta 5). *Note:* Studio can still detect Xcode 6.4. *Steps to reproduce:* # Update your Studio to the latest version from the Release branch: http://studio-jenkins.appcelerator.org/job/appcelerator-rcp-release/lastSuccessfulBuild/artifact/dist/ # After the Studio updates and restarts, launch the Studio dashboard: *Actual:* Studio will show a orange button to update iOS; see dashboard.png attachment. *Expected:* Studio should be able to detect Xcode 7 (beta 5). ",3,test +TISTUD-7677,Attempting to add new watch extension fails with error,"h5. Description: When a project is created and the tiapp.xml editor for watch extension is opened, there is a button labeled ""new"". When this button is clicked there is an error. The log shows no additional info other that what is presented in the dialog. h5. Steps to reproduce: 1) Create a project or use an existing one 2) Open tiapp.xml 3) Click the ""add"" button (green plus) from the tiapp.xml overview 4) Click the ""New"" button h5. Result: Error listed at top of window- ""Error while trying to create extension project [?25h"" h5. Expected Result: A new extension is created",5,test +TISTUD-7678,Integration of Apple WatchOS2 support in studio,Integrate Apple WatchOS2 app creation in studio. {code} appc new --type applewatch --name SGTestWatch --template watchos2 {code},8,test +TISTUD-7682,Update Windows SDK Preference Page to use Windows Publisher ID,"We've had to make a change to some of the config/command line values we use for Windows SDK. Basically before there was a Windows Phone Publisher GUID (-G) that was required. We ended up never actually using that, and it was a holdover from the Win 8 Mobile Web hybrid app stuff. Now that value and config value are optional, not required. It's used to specify the old Windows 8 publisher ID that MS assigned you, in the scenario that you're publishing an ""upgraded"" version of the app for Win 8.1/10. There's now a ""sister"" config value/option called the WIndows Phone product id for the same upgraded 8->8.1 app scenario. It's to specify the old Win 8 app id. see https://github.com/sgtcoolguy/titanium_mobile_windows/blob/master/cli/commands/_build/config/wpProductId.js Again that's optional. I think it's ok to not surface either of these two config/command line options because they'd be used extremely rarely by our customers. (plus one is more global - the Win 8 publisher GUID, while the other is app-specific - the Windows Phone product id). The important change is likely to make the pref page handle showing/editing the new Windows publisher Id config value now (in place of the Windows Phone Publisher GUID we discussed above that it currently surfaces). It's defined for the CLi here: https://github.com/sgtcoolguy/titanium_mobile_windows/blob/master/cli/commands/_build/config/winPublisherId.js It's stored in the ti CLI config key windows.publisherId, and can be specified on the comm,and line with the --win-publisher-id or -I switch. The value is assigned by MS when you sign up for a dev center account, and would be found on your Windows Dev Ceter dashboard at https://dev.windows.com/en-us/Account/Management ",3,test +TISTUD-7683,Should prompt for the name of watch app while creating Watch OS2 app in studio,"While creating a new Apple Watch OS2 project associated to a titanium project through studio, the option to provide a name to the watch app is not available. Steps to Reproduce: 1. In studio, create a new titanium project 2. Go to Tiapp.xml and under the section Apple WatchOS2 App, click on the button create new Actual Result: The watch extensions are created but there is no prompt for watch app name. Currently the watch app get the name as follows ""WatchApp"" Expected Result: There should be a prompt for name for watch app.",3,test +TISTUD-7684,'Create New' button for Apple WatchOS 2 app is shown even though imported project already has watch app extesnions,"When a titanium project with associated Apple Watch app is created in CLI and imported in Studio, the Create New button for watch app is still shown in Tiapp.xml Steps to reproduce: 1. Using CLI, create a titanium project 2. Cd into the project and create a watch app project in it 3. Now in Appc Studio, import the above created project 4. Open the Tiapp.xml Actual Result: The 'Create New' button under Apple WatchOS 2 App section is shown even though the project already has one.",3,test +TISTUD-7689,"Appc studio 5.0.0.201508271032 fails installation due to ""path too long"" error related to liveview","*Note: This is a regression. This issue didn't exist in studio 5.0.0.201508251028.* h5.Steps To Reproduce: 1. Download studio 5.0.0.201508271032 installer for windows. 2. Start the installation process & follow the prompts. h5.Actual Results: 1. During the installation process you get error ""the specified path is too long"". 2. I see that it refers to liveview path & I guess the latest liveview fix caused this issue : https://github.com/appcelerator/titanium_studio/commit/8a60e8d462427d448237149a2ad08377ecc643c0 3. Refer attached screenshot for reference. h5.Expected Result: 1. The installation should not fail & proceed successfully.",3,test +TISTUD-7710,Studio should handle the incompatible cache of ti info output,"When using the 4.1.1 stack, if we update to use SDK 5.0.0, make a project, then move back to SDK 4.1.X, then Studio does not recognize Xcode and we cannot build for iOS sims. *Steps to reproduce issue* 1. Be on the 4.1.1 stack 2. Run {{appc ti sdk select}} and pick a 5.0.0 SDK 3. Restart Studio and make a new mobile project 4. Run {{apc ti sdk select}} and pick a 4.1.1 SDK 5. Restart Studio *Actual Results* Xcode will not be recognized in Studio *Expected Results* Xcode is recognized and you can build/create iOS projects",5,test +TISTUD-7691,Apple Watch App can be created in a project that does not have iOS deployment targets,"An Apple Watch App can be created through trap.xml even for projects that do not have iPhone/iPad as deployment targets. Steps to Reproduce: 1. Create a new titanium project in Appc Studio. Select Android as the only deployment target 2. In the Tiapp.xml, the Apple WatchOS 2 App section is shown even though the target is only Android. 3. Click on Create New button under the section and complete the process. A Apple Watch App is added to the project with extensions and Xcode project. ",3,test +TISTUD-7697,Improve integration of Apple WatchOS2 support in Studio,* Why don't we have an option anymore to link an existing Xcode project? !Screen Shot 2015-09-04 at 14.06.07.png! * The prompt for the name should say _WatchOS2 project name_ and have the name of the Titanium project filled in as default. !Screen Shot 2015-09-04 at 14.07.20.png! * In the above _App Location_ should be _Xcode Path_ just like in the wizard. * Project names with spaces are perfectly fine and work via the CLI. The prompt in Studio should apply the same validation as the CLI. !Screen Shot 2015-09-04 at 14.07.31.png! * Why is the button titled _Configure Provisioning Profiles_ but is the title of the wizard _Configure Targets_? !Screen Shot 2015-09-04 at 15.10.13.png! !Screen Shot 2015-09-04 at 14.08.13.png! * _Watch App XCode Path_ should be _Xcode Path_ (lowercase C and equal to Tiapp Editor). * The wizard suggests that you select the targets here but deselecting doesn't effect the actual listed targets in the {{tiapp.xml}} in anyway. It just determines the choices given in the next step. So the wizard should either remove the unselected targets (and populate this list by reading the available targets in the Xcode project) or it might as well skip this step and show the next step right away for all targets. * The Device provisioning profile list should default to the default development provisioning profile since that will probably be wildcard and what people use for this option. !Screen Shot 2015-09-04 at 14.09.02.png!,8,test +TISTUD-7698,"Beta stream installer from ""preview.appcelerator.com"" & jenkins gives 5.0.0.201508271032 studio","h5.Steps to reproduce: 1. Download the installers from beta stream from ""preview.appcelerator.com"" & jenkins. 2. Completed the studio installation. 3. Check the version of the installed studio. h5.Actual Results: 1. The installed version is 5.0.0.201508271032. NOTE: Updating previous studio from the stream & version in the zip is fine. h5. Expected Results: 1. The installed version should be 4.3.0.201509031836. ",5,test +TISTUD-7699,Unable build sample apps with 9.0 iOS simulators due to app icon size issues,"Unable build sample apps with 9.0 iOS simulators - tried Employee directory and Ti SDK 4.1 Example App. {code} INFO] : Creating app icon set [ERROR] : No suitable app icon that is at least 180x180, unable to create missing icons: [ERROR] : appicon-Small@2x.png - Used for iPhone, iPad - required size: 58x58 (29x29 @2x) [ERROR] : appicon-Small@3x.png - Used for iPhone - required size: 87x87 (29x29 @3x) [ERROR] : appicon-Small-40@2x.png - Used for iPhone, iPad - required size: 80x80 (40x40 @2x) [ERROR] : appicon-Small-40@3x.png - Used for iPhone - required size: 120x120 (40x40 @3x) [ERROR] : appicon-60@2x.png - Used for iPhone - required size: 120x120 (60x60 @2x) [ERROR] : appicon-60@3x.png - Used for iPhone - required size: 180x180 (60x60 @3x) [ERROR] : An error occurred during build after 28s 330ms TRACE | titanium exited with exit code 1 ERROR | Error: ti run exited with error code 1 at ChildProcess. (/Users/kkolipaka/.appcelerator/install/5.0.0-40/package/node_modules/appc-cli-titanium/plugins/run.js:89:66) at ChildProcess.emit (events.js:117:20) at Process.ChildProcess._handle.onexit (child_process.js:820:12) {code}",8,test +TISTUD-7703,Send a flag or environment variable when invoking CLI from studio,"Ideally, we would just set an environment variable for all commands going to CLI before invocation and we can then check in CLI if being called by Studio. This is preferable to me than a command flag since I think it shouldn't be publicly exposed. I would suggest we set the environment variable APPC_STUDIO = 1 before calling any CLI command. We can then use this for CLI-806",3,test +TISTUD-7762,Studio unable to update if OSX (El Capitan) logon using iCloud Account,"When using iCloud account to logon on to OSX (El Capitan) It is not possible to update Appcelerator Studio. When prompted for Password, password is not accepted. Tried changing my user profile to ""Use Separate Password..."" now everything works as expected. ",8,test +TISTUD-7704,[Code refactoring]Consolidate titanium user and titanium360 user implementations in studio,"Currently In the studio codebase we are maintaining titaniumUser and Titanium30User, so as part of this ticket will consolidate the functionality of both. ",13,test +TISTUD-7705,Studio should use the defined range of CLI versions,"If anyone tries to use Studio 4.1.x with CLI/SDK 5.x, then it completely fails to parse ti info output of iOS. It should have defined the version range of compatible CLIs, and if the installed CLI doesn't fall under the range, then it should prompt the user to update Studio or, CLI/SDK accordingly. Similarly case for Studio 4.3.x has the prerequisite of CLI/SDK 5.x ",8,test +TISTUD-7706,"Terminating a running build process will return ""Terminate failed"" dialog","*Details:* If you try to terminate a running build from Studio, a ""Terminate failed"" dialog will appear. *Notes:* * This occurs for both Android and iOS builds. * This issue has occurred on multiple qe machines. *Steps to reproduce:* # Create a mobile project (Titanium or Alloy) in Studio # Next, install the project to device or simulator/emulator # After the app launches, terminate the build (click the red button above the console) *Actual:* ""Terminate failed"" dialog will appear; see single.png attachment. If you click on the red button multiple times, then multiple dialogs will appear; see multiple.png attachment. *Expected:* ""Terminate failed"" dialog should not appear when you try to terminate a build.",3,test +TISTUD-7708,Watchos2 app section is getting disappeared from tiapp editor after creating a new watchos2 app,"Watchos2 app section is getting disappeared from tiapp editor after creating a new watch os2 app through ti app editor. Steps: 1. Open any 4.x sdk selected tiapp.xml editor 2. Switch the sdk version from 4.x to 5.0 (Don't save here!) 3. Click on 'create' from watch os 2 app section. 4. Provide the watch os2 app name 5. watchos2 app will be created successfully in the project but watchos2 app section is disappeared from tiapp editor. To get it back, we have to close the editor and re-open it. Actual: Watchos2 app section is getting disappear after creating a watchos2 app. Expected: Watchos2 app section should not disappear and it should show the app location in tiapp editor. ",5,test +TISTUD-7712,"After you terminate a build process and close Studio, orphaned node processes will linger","*Details:* After you terminate a build process to device or simulator, then close Studio, orphaned node processes will linger. *Steps to reproduce:* # In Studio, create a mobile project # Build the mobile project to either device or simulator # After the app launches, terminate the build process by clicking on the red square # After the build process is killed, close Studio # Then, open Activity Monitor and look for node processes *Actual:* Orphaned node processes will still linger; see attachment. *Expected:* Orphaned node processes should not linger.",5,test +TISTUD-7713,TiApp: Using the tag in tiapp.xml shows an invalid content error,"h5.Description When adding the tag to the tiapp.xml in Studio using the tiapp editor it will be flagged with the below error. {code} Invalid content was found starting with element 'windows'. One of '{sdk-version, deployment-targets, id, name, version, publisher, url, description, copyright, icon, persistent-wifi, prerendered-icon, statusbar-style, statusbar-hidden, fullscreen, navbar-hidden, analytics, guid, iphone, android, ios, mobileweb, tizen, ivi, property, modules, plugins, extensions}' is expected. {code} h5.Steps to reproduce 1. Open a tiapp.xml from a project in Studio 2. Click the tiapp.xml tab to open the editor 3. Add the below {code} com.appc {code} h5.Actual result The tag will be flagged as invalid h5.Expected result The tag should not be flagged as invalid",5,test +TISTUD-7715,TiApp Editor doesn't update when you change ,"When you make a change to the XML under {{}} that change is not reflected in the Overview tap, also not after saving it. You have to really close and re-open the tiapp.xml to see the change. When you make a change to other tags like {{}}, {{}} etc the change is reflected immediately.",5,test +TISTUD-7719,No simulators shown in studio with latest release,"Since the update of studio (and even before the updated XCode 7 had finished downloading - I still had the previous XCode installed), no simulator ""option"" appears in the launch pad area (see graphic below). No amount of reinstalling (done this twice now) is helping. I can confirm that there is indeed a simulator resident at: /Applications/XCode.app/Contents/Developer and then after showing package contents, in: /Platforms/iPhoneSimulator.platform/Developer/SDKs Shows as per the 2nd graphic attached. appc ti info also reports simulators: {code} iOS Simulators 8.4 iPad 2 (ipad) UDID = 671B1D19-7F80-4A54-BEAA-90F56FAAE183 Supports Watch Apps = no iPad Retina (ipad) UDID = 7611D080-36E8-4B72-9ED2-AF5C307F0C50 Supports Watch Apps = no iPad Air (ipad) UDID = A834365B-4833-459D-BCEB-016C9A017886 Supports Watch Apps = no iPhone 4s (iphone) UDID = 34AAD76C-9581-41A7-8B66-BE0F4C96FCDF Supports Watch Apps = no iPhone 5 (iphone) UDID = 35F3FB4A-D5E5-4FF3-8030-EE3D20CAE928 Supports Watch Apps = yes iPhone 5s (iphone) UDID = 58D46170-CAE0-4CC7-AE02-5EF8405A19C0 Supports Watch Apps = yes iPhone 6 Plus (iphone) UDID = 500ACFB8-E0D4-4E2E-9C7C-FBBD2CF63CE3 Supports Watch Apps = yes iPhone 6 (iphone) UDID = 1AC19EEE-8E2E-4E96-ADD8-6307E324A6FE Supports Watch Apps = yes 9.0 iPad 2 (ipad) UDID = 58F9B368-E005-4E25-B9D8-46F9C8641746 Supports Watch Apps = no iPad Retina (ipad) UDID = B64A0D81-8B10-4355-ACA2-CA8964DD0943 Supports Watch Apps = no iPad Air (ipad) UDID = 1C517817-CFC5-4711-9F0A-62C00CDE90B6 Supports Watch Apps = no iPad Air 2 (ipad) UDID = BB83A606-E0EE-4BAE-8074-511159CBABDB Supports Watch Apps = no iPhone 4s (iphone) UDID = 91F430E6-02BC-4B48-BB2E-8EDF8AD3756A Supports Watch Apps = no iPhone 5 (iphone) UDID = 42856DFD-68C4-4423-B9E6-2BCFB9B5FD92 Supports Watch Apps = yes iPhone 5s (iphone) UDID = 519463D7-B47A-4186-9CF2-0FEB4F7DA7F5 Supports Watch Apps = yes iPhone 6 Plus (iphone) UDID = DB90EBEC-EE4A-4DB4-9727-8E4855A242B2 Supports Watch Apps = yes iPhone 6 (iphone) UDID = D6FC99AF-7EF6-4987-917F-E7717762870E Supports Watch Apps = yes iPhone 6s (iphone) UDID = 5FFEB4AF-2557-46FD-AC05-D3889DA04386 Supports Watch Apps = yes iPhone 6s Plus (iphone) UDID = E412D0E2-CBCA-40C9-8622-758663DF802D Supports Watch Apps = yes WatchOS Simulators 2.0 Apple Watch - 38mm (watch) UDID = 12B54138-1724-4D1C-A597-6D4FA53F8644 Apple Watch - 42mm (watch) UDID = 965519F5-F2BD-46E2-A483-FC6456149498 {code} Help! UPDATE **** I've found that if I import a much older Titanium project into studio, THAT project has all simulators available (See third graphic). However, any new project simply doesn't show them. FURTHER UPDATE **** This problem is only apparent on ALLOY projects.",3,test +TISTUD-7717,iOS: Reconnect to the debug session after the app is restarted,"If a user attempts to debug a mobile app, then app initiates a debug connections during its startup. As Studio receives the debug connection request, it initiates the socket connection and receives the debug data. However, if the app is accidentally crashed/terminated on device or simulator, then the user has to re-launch the debug session (which will re-build the app and deploy onto device again). If the app is restarted on the device (or simulator), then it attempts to make a debug connection to Studio, but Studio is no more listening to the debug connection requests. Studio should listen to the debug connection request even though the app is terminated/crashed, so that the user does not need to re-launch debugging the app again.",8,test +TISTUD-7720,watchos2 section disappears if the SDK changes are not saved in tiapp,"Watchos2 app section is getting disappeared from tiapp editor after creating a new watch os2 app through ti app editor. Steps: 1. Open any 4.x sdk selected tiapp.xml editor 2. Switch the sdk version from 4.x to 5.0 (Don't save here!) 3. Click on 'create' from watch os 2 app section. 4. Provide the watch os2 app name 5. watchos2 app will be created successfully in the project but watchos2 app section is disappeared from tiapp editor. To get it back, we have to close the editor and re-open it. Actual: Watchos2 app section is getting disappear after creating a watchos2 app. Expected: Watchos2 app section should not disappear and it should show the app location in tiapp editor. ",5,test +TISTUD-7721,"Allow user to abort ""Appcelerator CLI is currently installing or upgrading""",The only way to resolve _Appcelerator CLI is currently installing or upgrading_ is to let users manually delete the {{~/.appcelerator/.installing}} file. The alert should ask the user if he wishes to abort the current installation process. Related Q&A: https://community.appcelerator.com/topic/3439/can-t-setup-cli-correctly-on-windows-7-x64,5,test +TISTUD-7723,Do NOT limit console output by default,"By default, Studio limits console output to 200,000 characters. This is ridiculous. The builds are more verbose these days and this default makes no sense. I recommend disable limiting console output by default. Otherwise, bump this to something like 1M.",5,test +TISTUD-7725,Studio defaults to Beta Update stream for GA builds,"For GA builds of Studio, the default update stream points to {{Beta}}. Due to that, Studio tries to download SDKs from Beta stream (3.5.x), even though 5.0.0.GA is available in the master stream. - The GA builds of Studio should always points to master stream. - Studio should consider the latest version from stable stream, if its version is higher than the release branch highest version.",5,test +TISTUD-7726,Studio throws NPE while trying to save orgs,"When a new installation of Studio is run on a new workspace, then it ends up throwing NullPointerException while trying to cache a copy of orgs in the workspace.",3,test +TISTUD-7727,Studio: Make Icon in tiapp.xml work,"Starting with Ti SDK 5.0.0.GA, we have a new way to process the app icon on ios, such that we just need to set 1 file, DefaultIcon.png, preferred size of 1024x1024, and the cli will slice the image to the corresponding required sizes for the various device idioms. Studio should update this part on the tiapp.xml GUI such that whichever icon the developer chooses, it will prompt the required dimensions, as well as rename the file as DefaultIcon.png that sits at the root of the project. This should also cater for Android, MobileWeb and Windows once CLI also does the same type of processing on the icon image for these platforms. This icon should also be reflected on the web dashboard.",8,test +TISTUD-7729,Studio should use the defined range of SDK versions,"If anyone tries to use Studio 4.1.x with SDK 5.x, then it completely fails to parse ti info output of iOS. It should have defined the version range of compatible SDK's, and if the installed SDK doesn't fall under the range, then it should prompt the user to update Studio or, SDK accordingly. Similarly case for Studio 4.3.x has the prerequisite of SDK 5.x ",8,test +TISTUD-7730,Alloy: Remove unnecessary CLI call when creating an Alloy project,"h5.Description When creating an Alloy project from Studio it makes two CLI calls, initially it makes an {{appc new}} call to create the project and then {{appc alloy new}} to generate an Alloy project. With the appc CLI it is unnecessary to make the second call and the it actually overwrites the ArrowDB related code injected to the app on project creation by the CLI. {code} !ENTRY com.aptana.core 1 0 2015-09-25 18:05:07.946 !MESSAGE (Build 4.3.1.201509222258) [INFO] com.aptana.core/debug/shell Running process: Process: ""C:\Users\Ewan\AppData\Roaming\npm\appcelerator.CMD"" ""new"" ""--type"" ""titanium"" ""--platforms"" ""android,mobileweb,windows"" ""--id"" ""com.fwan"" ""--name"" ""alloyTwoCalls"" ""--sdk"" ""5.0.1.v20150924103934"" ""--project-dir"" ""F:\Documents\Appcelerator_Studio_Workspace\alloyTwoCalls"" ""--force"" ""--no-services"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""--prompt-type"" ""socket-bundle"" ""--prompt-port"" ""51947"" !ENTRY com.aptana.core 1 0 2015-09-25 18:05:25.370 !MESSAGE (Build 4.3.1.201509222258) [INFO] com.aptana.core/debug/shell Running process: Process: ""C:\Users\Ewan\AppData\Roaming\npm\appcelerator.CMD"" ""alloy"" ""new"" ""--force"" ""F:\Documents\Appcelerator_Studio_Workspace\alloyTwoCalls"" ""default"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""--prompt-type"" ""socket-bundle"" ""--prompt-port"" ""51947"" {code} h5.Steps to reproduce 1. Clear your Studio logs, Help->Studio->View Log File 2. Create an Alloy project 3. Check your Studio logs, Help->Studio->View Log File h5.Actual result There will be an {{appc new}} call and then an {{appc alloy new}} call h5.Expected result Only an {{appc new}} call is needed to create an Alloy project so the {{appc alloy new}} call should not happen",3,test +TISTUD-7731,Unable to build Android Module Project After upgrade to latest 4.3.0,"h6.Reproduce Customer facing this problem. 1. Create a new Mobile Module Project targeting Android. 2. Attempt to Package the module. h6.Expect Result Should build well. h6.Actual Result. 1. Not able to build the module. attached the screen shot. 2. There is a red X error indicator next to the project but nowhere else within the project tree. See the attached screenshots. h6.Note Only happened to customer, I can't reproduce it in my own env. attached ti info output and appc log file as well.",5,test +TISTUD-7732,NullPointerException when trying to Configure SDK,https://community.appcelerator.com/topic/479/nullpointerexception-when-trying-to-configure-sdk NullPointerException is thrown when Xcode 7.0 does not have any watchos 2 simulators. Please find the attachments for iPhone log and studio log,3,test +TISTUD-7740,"Unable to submit a JIRA ticket via Studio as ""versions"" is not defined","# Help > Studio > Submit a ticket... # Log in # Fill out fields # Error reported is: ""Field 'versions' cannot be set""",3,test +TISTUD-7741,"Add prominent display of ""what you like/what can be better"" to solicit feedback","Based on what Microsoft is doing in Outlook, let's add a icon to the toolba to allow people to submit feedback more easily. It can just launch the ""Submit a JIRA ticket"" window.",8,test +TISTUD-7743,Studio hangs in Verifying state during startup,"A community user is on Node 4.0, and reported that Studio is hanging during startup in ""Verifying"" state. When I asked for {{appc whoami --full -o json}} output, it contains {{module loading errors}} along with the json output. Looks Studio is failing to parse the JSON output, and got hung up in the same state. Studio has to fail over the invalid JSON output, and has to recover from that state.",5,test +TISTUD-7800,Creating a controller in a folder doesn't work,"When you right-click on a folder within the ""controllers"" folder, and try to generate a new controller by clicking ""new -> Alloy Controller"" it will not be generated within that folder, but be added to the root ""controllers"" folder, and the generated controller/view/tss files need to be moved to the folder manually. Imo this should be fixed as it is also advised to work with folders within the controllers folder. ",5,test +TISTUD-7746,LiveView via CLI does not work (anymore) until it has been used via Studio after install/update,LiveView is a CLI plugin that lives under Studio and is not hooked into the (Unified) Titanium CLI until it has been run via Studio. Every time the LiveView version changes because you've updated Studio you also have to run it once via Studio to have the hook path updated. The LiveView hook should be moved to the Unified CLI so that it no longer depends on Studio.,8,test +TISTUD-7747,LiveView does not work: Script Error Couldn't find module: localeStrings for architecture: x86_64,"We've had a number of users reporting LiveView does not work anymore on Q&A: https://community.appcelerator.com/topic/3518/error-script-error-couldn-t-find-module-localestrings-for-architecture-x86_64/11 On a freshly installed El Capitan I can now reproduce this as well, every time. LiveView never works. Suspecting NodeJS was involved, I've tried both the version our installers installs (0.10.37), 0.10.40 and 0.12.7 but all with the same result: {code} [INFO] : Launching iOS Simulator [LiveView] version 1.0.8 [LiveView] File Server Started on Port 8324 [LiveView] Event Server Started on Port 8323 [INFO] : Application started [INFO] : LiveView/1.0 (5.0.2.92c2265) [ERROR] : Script Error Couldn't find module: localeStrings for architecture: x86_64 {code} I've done some debugging in https://github.com/appcelerator/liveview/blob/master/build/liveview.js The following I found at [#391|https://github.com/appcelerator/liveview/blob/master/build/liveview.js#L391]: {code} [INFO] : url undefined [INFO] : defaultURL 10.0.1.4 {code} The last is my computer's public IP. The following I've found on [#562|https://github.com/appcelerator/liveview/blob/master/build/liveview.js#L562]: {code} [INFO] : readyState 4 [INFO] : status 0 [INFO] : responseText The operation couldn’t be completed. No such file or directory {code} As pointed out in the Q&A, indeed changing the {{defaultURL}} to {{127.0.0.1}} resolves the issue. *So it seems using the computer's public IP is not working but it's unclear why for some and for me before it does.*",8,test +TISTUD-7754,Windows Installer: Installer should install NodeJS 4.2.2 on a clean machine,Appcelerator Studio Windows Installer should install NodeJS 4.2.2 on a clean machine.,3,test +TISTUD-7755,Installers: Update go.appcelerator.com with the new Node.js version 4.2.2,Update go.appcelerator.com with the new node.js version 4.1.0 *For Windows* Current url: http://go.appcelerator.com/installer_nodejs_windows_10_37.msi New url: Let's use generalized url so that we need not change every time in the installer http://go.appcelerator.com/installer_nodejs_windows.msi *For Mac* URL: http://go.appcelerator.com/installer_nodejs_osx update the existing url to point new node.js 4.1.0 version ,5,test +TISTUD-7756,"During the studio update check, verify minimum required node.js version to 0.12.7","During the studio update check, verify whether system is having minimum required node.js version to 0.12.7. If the minimum required version is not found then show the update site wizard with node 4.1.0 as a prerequisite. ",3,test +TISTUD-7757,Studio wants to update CLI Core version which is already installed but not active,I have CLI Core 5.0.2 and 5.0.1 both installed but 5.0.1 active. Studio will prompt me to install CLI Core 5.0.2. See screenshot. Studio should look if the latest version is installed and let it up to me which version I have active.,5,test +TISTUD-7758,Studio 4.3.1 only has beta Software Site and switching via Studio > Updates doesn't change it,"Installing a brand-new version of Studio via the installer set the update stream to ""Beta"" even if externally it appears you are set to ""stable""",5,test +TISTUD-7759,2000 threads are created in a thread pool after re-launching app multiple times,"I tried to re-launch an app multiple times (with liveview, though it doesn't matter), and Studio was kept running for more than a day. There is a slightly sluggish performance with Studio, and when I captured jstack output of the process, I did notice that there are around 1500-2000 threads created in thread pool. Essentially, for every launch, we are creating 3 threads to read error/output stream and write to input stream. Those threads are not being cleaned up after the launch is terminated. Attached jstack output.",8,test +TISTUD-7763,Integrate error reporting from Appc Studio into analytics server,"If there are any errors occurred in user's environment, then it typically log the error/exceptions into its workspace log file. We don't get to see those kind of exceptions unless user creates a jira ticket with the log file. Appc Studio has to send the error details back to Appc analytics server (need to find out endpoint) using the existing Error Reporting functionality available in Eclipse Mars (4.5). We need to investigate about the integration of Error reporting, and our endpoint to aggregate the data.",8,test +TISTUD-7767,Show Trial mode in Studio UI,Provide an indication in the Studio UI that will let a developer know they are in Trial Mode and ideally how long they have been in trial. Indication could be near the login name in the bottom right hand corner. *Text* Developer Trial [Day NN] (Days are Optional for v1) - Purchase here ,8,test +TISTUD-7766,Trial reminder on Studio Login and Logout,When a user logs in or out of Studio they should be reminded they are in trial along with the expiration. *Text* Thank you for trying the Appcelerator Platform. Just as a reminder while in Trial you are unable to publish applications to any AppStore. Checkout our pricing at https://www.appcelerator.com/pricing or Click here to purchase ,5,test +TISTUD-7769,"On Login splash screen ""Remember my Email Address"" label foreground color looks black on windows and white on mac os","On Login splash screen ""Remember my Email Address"" label foreground color looks black on windows and white on mac os. Ideally it should be white. Looks like Windows os doesn't respect the foreground color for Button/Button with checkbox https://bugs.eclipse.org/bugs/show_bug.cgi?id=23837 http://stackoverflow.com/questions/4747562/how-to-set-swt-button-foreground-color/6704096#6704096 Expected: ""Remember my Email Address"" text name on splash screen should appear in white color in Windows OS. ",5,test +TISTUD-7779,"If you have Node 0.10.X installed, you cannot log into Studio 4.4.0","*Details:* If you have Node 0.10.X installed, you cannot log into Studio 4.4.0. I've updated my Studio via Jenkins branch. *Workaround:* Install Node 0.12.7 and up. *Steps to reproduce:* # Make sure you have Node 0.10.X installed on your machine # Make sure you update your Studio to 4.4.0 # Open Appc Studio and try to log in *Actual:* You will not be able to log into Studio; the log in button will become unresponsive. *Expected:* You should be able to log into Studio 4.4.0 with Node 0.10.X.",5,test +TISTUD-7781,"""Unable to locate the CLI executable.."" error during the studio startup","During the studio startup, studio prompted an error message ""Unable to locate the CLI executable. Please restart Studio or use Help > Check for Appcelerator Studio Updates to install Titanium CLI "" This happens when system does not have appc core setup but having node and npm modules. I can see this only in windows operating system. ",5,test +TISTUD-7782,Improve startup performance by loading orgs in the background,"The Status controller now shows user name along with their active organization in the tooltip. It tries to load organizations and then, show the active org name in the status. Since loading the orgs happens in UI thread, it slows down the startup time of Studio (it spends more time loading in splash screen). For showing username/org in the status bar, we should load orgs in the background thread. So, we should never loads the orgs in the main thread.",5,test +TISTUD-7783,"When you create new project, the App Id field and URL field are in the reverse order","*Details:* When you create a new mobile project in Studio, the URL field is before the App Id field; *this is a regression from Studio 4.3.1*. *Steps to reproduce:* # In Studio, create a new Mobile App Project # Select either the default Alloy project or default Titanium project # Then, click next in the wizard *Actual:* The URL field is before the App Id field; see attachments. *Expected:* The App Id field should be before the URL field.",5,test +TISTUD-7784,Clicking on publish for android packaging opens android studio preferences window,"h5. Steps To Reproduce: 1. Create an app for android. 2. Select packaging option in studio 4.4.0.201510161811. 3. Click the play button. 4. Fill in all the necessary details for packaging like keystore password, distribution location etc. 5. Click publish. h5. Actual Result: 1. After clicking publish the studio android preferences window pops up. h5. Expected Result: 1. Clicking the publish button should package the app.",5,test +TISTUD-7791,Studio prompts for update to incorrect NPM Appc CLI and SDK,"h5. Description: When installing the pre-release version of Studio 4.3.3.201510172433, you are prompted to install the 4.0.1-rc2 version of the Appcelerator CLI NPM package. You are also prompted to install SDK 5.2.0.x. Studio should check for GA, there should be no prompt. h5. Steps to reproduce: 1) Install studio 4.3.3.201510172433 2) Check for appcelerator updates 3) Note versions offered h5. Result: SDK and Appc CLI NPM are presented, but not versions that are needed for the beta release. h5. Expected Result: Neither component offered if on GA version or greater",5,test +TISTUD-7799,"Error connecting to profiler and debugger: Error Domain=NSPOSIXErrorDomain Code=2 ""No such file or directory""","iOS app Debugging/profiling is getting failed with Mac OS El Captain(I am not sure whether it's an OS issue or not, but debugging used to work properly with an earlier version). Below is the error which is thrown. {code} [ERROR] : Error connecting to profiler: Error Domain=NSPOSIXErrorDomain Code=2 ""No such file or directory "" {code} *Steps:* 1. Create an alloy/classic app 2. Run with ""Profile or Debug"" for iOS Simulator *Actual:* App is unable to run either in debugger or profiler mode. And, app is not getting launched in simulator. Please find the console log: {code} Appcelerator Command-Line Interface, version 5.0.3 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. TRACE | __command__ search paths: [ ""/Users/kondalkolipaka/.appcelerator/install/5.0.3/package"", ""/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules"", ""/Users/kondalkolipaka/development/eclipse/Eclipse.app/Contents/MacOS/node_modules"", ""/Users/kondalkolipaka/development/eclipse/Eclipse.app/Contents/node_modules"", ""/Users/kondalkolipaka/development/eclipse/Eclipse.app/node_modules"", ""/Users/kondalkolipaka/development/eclipse/node_modules"", ""/Users/kondalkolipaka/development/node_modules"", ""/Users/kondalkolipaka/node_modules"", ""/Users/node_modules"", ""/node_modules"", ""/Users/kondalkolipaka/.appcelerator/.npm/lib/node_modules"" ] DEBUG | [PLUGIN-LOAD] 0ms /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/appc.js DEBUG | [PLUGIN-LOAD] 573ms /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/appc.js DEBUG | [PLUGIN-LOAD] 1ms /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/arrow/appc.js log level set to ""trace"" executing command ""run"" Preproduction Environment Active set environment to {""registry"":""https://software-preprod.cloud.appctest.com"",""security"":""https://security-preprod.cloud.appctest.com"",""baseurl"":""https://360-preprod.cloud.appctest.com""} checking credentials for existing session Attempting to load session info from config file check if session is invalidated session expiry 1445925862642 false Arrow Cloud config file: /Users/kondalkolipaka/.acs found Arrow Cloud login { mid: 'af31ce68ea17b4a8fff2b7dcdb8fccd67d6bddfe', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise-preprod.appctest.com', username: 'kkolipaka@appcelerator.com', cookie: [ 'connect.sid=s%3A9wNrp1uBdPmXuQaD5bG5qset.iEIHKwr8JT0GWKQzOQYCvsk9FSQ7rzlioEQXP%2Fj5kWw; Path=/; Expires=Wed, 21 Oct 2015 06:04:46 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise-preprod.appctest.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise-preprod.appctest.com Arrow Cloud cookie expiry [ 1445407486000 ] session already loaded in opts.session getCredentials() session: { ""ipaddress"": ""192.168.0.112"", ""username"": ""kkolipaka@appcelerator.com"", ""password"": """", ""session"": """", ""nonce"": """", ""environment"": { ""name"": ""production"", ""isProduction"": true, ""acsBaseUrl"": ""https://preprod-api.cloud.appctest.com"", ""acsAuthBaseUrl"": ""https://dolphin-secure-identity.cloud.appcelerator.com"", ""nodeACSEndpoint"": ""https://admin.cloudapp-enterprise-preprod.appctest.com"" }, ""token"": """", ""fingerprint"": ""af31ce68ea17b4a8fff2b7dcdb8fccd67d6bddfe"", ""fingerprint_description"": ""Mac OSX Serial Number: C02GH2D3DRJC"", ""org_id"": 100000780, ""expiry"": 1445925862642 } loading plugins for command ""run"" run search paths: [ ""/Users/kondalkolipaka/.appcelerator/install/5.0.3/package"", ""/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules"", ""/Users/kondalkolipaka/development/eclipse/Eclipse.app/Contents/MacOS/node_modules"", ""/Users/kondalkolipaka/development/eclipse/Eclipse.app/Contents/node_modules"", ""/Users/kondalkolipaka/development/eclipse/Eclipse.app/node_modules"", ""/Users/kondalkolipaka/development/eclipse/node_modules"", ""/Users/kondalkolipaka/development/node_modules"", ""/Users/kondalkolipaka/node_modules"", ""/Users/node_modules"", ""/node_modules"", ""/Users/kondalkolipaka/.appcelerator/.npm/lib/node_modules"" ] [PLUGIN-LOAD] 0ms /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/appc.js [PLUGIN-LOAD] 414ms /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/appc.js run plugin: /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium [PLUGIN-LOAD] 1ms /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/arrow/appc.js run plugin: /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/arrow plugin ""arrow"" failed its ""when"" function check, skipping... loading plugin ""titanium"" for command ""run"" CLI options via function loading plugin ""titanium"" for command ""run"" CLI options via array Duplicate option ""colors"" for command ""run"", removing... executing command ""run"" with the following plugins: [""titanium""] TRACE | Attempting to load session info from config file TRACE | check if session is invalidated TRACE | session expiry 1445925862642 false TRACE | session already loaded in opts.session DEBUG | Titanium Downloads Last Checked: 1445313325968 TRACE | ""/usr/local/bin/node"" ""/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/node_modules/titanium/bin/titanium"" config -o json-object TRACE | ""/usr/local/bin/node"" ""/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/node_modules/titanium/bin/titanium"" sdk -o json TRACE | checking for titanium, result: { activeSDK: '5.2.0.v20151019184553', defaultInstallLocation: '/Users/kondalkolipaka/Library/Application Support/Titanium', installLocations: [ '/Users/kondalkolipaka/Library/Application Support/Titanium', '/Library/Application Support/Titanium' ], installed: { '5.2.0.v20151019184553': '/Users/kondalkolipaka/Library/Application Support/Titanium/mobilesdk/osx/5.2.0.v20151019184553', '5.0.2.GA': '/Users/kondalkolipaka/Library/Application Support/Titanium/mobilesdk/osx/5.0.2.GA' }, sdks: { '5.2.0.v20151019184553': { name: '5.2.0.v20151019184553', manifest: [Object], path: '/Users/kondalkolipaka/Library/Application Support/Titanium/mobilesdk/osx/5.2.0.v20151019184553' }, '5.0.2.GA': { name: '5.0.2.GA', manifest: [Object], path: '/Users/kondalkolipaka/Library/Application Support/Titanium/mobilesdk/osx/5.0.2.GA' } } } TRACE | /usr/local/bin/node [ '/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/node_modules/titanium/bin/titanium', 'build', '--platform', 'ios', '--log-level', 'trace', '--sdk', '5.2.0.v20151019184553', '--project-dir', '/Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/app5', '--target', 'simulator', '--ios-version', '9.0', '--device-family', 'universal', '--deploy-type', 'development', '--sim-type', 'iphone', '--sim-version', '9.0', '--device-id', '2B5681C9-DB62-4917-AE3E-37B1D79AB4AA', '--profiler-host', '192.168.0.112:58214', '--skip-js-minify', '--no-colors', '--no-progress-bars', '--no-prompt', '--prompt-type', 'socket-bundle', '--prompt-port', '63446', '--username', 'kkolipaka@appcelerator.com', '--password', '[HIDDEN]', '--plugin-paths', '/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules', '--config-file', '/var/folders/9n/xpk1tm596cbctmwyfhcqysfw0000gn/T/build-1445328688793.json', '--no-banner' ] { env: { SHELL: '/bin/bash', TMPDIR: '/var/folders/9n/xpk1tm596cbctmwyfhcqysfw0000gn/T/', SHLVL: '1', JAVA_HOME: '/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home', STUDIO_PRODUCT_ID: 'com.appcelerator.titanium.rcp.product', JAVA_MAIN_CLASS_35192: 'org.eclipse.equinox.launcher.Main', __CF_USER_TEXT_ENCODING: '0x1F5:0x0:0x0', STUDIO_VERSION: '4.4.0.qualifier', PATH: '/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin', ANALYTICS_SOURCE: 'studio', XPC_FLAGS: '0x0', APTANA_VERSION: '4.4.0.qualifier', COMMAND_MODE: 'unix2003', USER: 'kondalkolipaka', PWD: '/Users/kondalkolipaka/development/eclipse/Eclipse.app/Contents/MacOS', APP_ICON_768: '../Resources/Eclipse.icns', HOME: '/Users/kondalkolipaka', STUDIO_NAME: 'Appcelerator Studio', XPC_SERVICE_NAME: 'com.apple.xpc.launchd.oneshot.0x1000000f.eclipse', LOGNAME: 'kondalkolipaka', JAVA_STARTED_ON_FIRST_THREAD_768: '1', Apple_PubSub_Socket_Render: '/private/tmp/com.apple.launchd.zDDbfEmwv2/Render', SSH_AUTH_SOCK: '/private/tmp/com.apple.launchd.OsUway5g8m/Listeners', LANG: 'en_US.UTF-8', JAVA_STARTED_ON_FIRST_THREAD_35192: '1', APPC_NPM_VERSION: '4.2.0', npm_config_cache: '/Users/kondalkolipaka/.appcelerator/.npm', npm_config_prefix: '/Users/kondalkolipaka/.appcelerator/.npm', APPC_INSTALL_DIR: '/Users/kondalkolipaka/.appcelerator/install', APPC_INSTALL_BIN_DIR: '/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/bin/appc', APPC_CONFIG_PROXY: '', NODE_PATH: '/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules:/Users/kondalkolipaka/.appcelerator/cache/node_modules:', APPC_SUPPRESS_PROGRESS: 'true', APPC_REGISTRY_SERVER: 'https://software-preprod.cloud.appctest.com', APPC_SECURITY_SERVER: 'https://security-preprod.cloud.appctest.com', APPC_DASHBOARD_URL: 'https://360-preprod.cloud.appctest.com', APPC_ENV: 'preproduction', APPC_SESSION_TOKEN: 'd6b613747fe4a5ffec203678f4ccf227ae6b7422%20dbJb%2BQGydFVLxzb6jmVRC1yA9r%2FAudNgcYBNW1MceSADHjkkm%2B9zLMzwG7peXGNE%2Fxy5r5Q4Qe2emKKjkobXgAJ13OOojkhmt70Fgfgi2Y4ztv3%2BT%2B2AA3Ej6hpIfEw9%2Bl8EVQMl%2BMkDT3Mwe6fscAfr2qfVMdp7kS%2FEYoNxonmCfJi9694btJNNVt8dUB5R4j3AiaQI%2BJF7BEoo4gZDLRObHw91rzmut5cXwETfE1wRTKqa2OipLWeV%2FGHXrT4z%2FhYMPnqnsa%2FS9x2ddqCzv8WnpWDhiin8VroBVPTYMPg9H1%2FT5WJ%2FjjWGE9YVSELOs28DJ6qg3KO8wG3lAPmzCPtRUt4lNVxWp%2Bv%2BgwXHVFozLlZfHlWhTG7%2BVE%2FvruckbS3%2FgdkmJv%2FpMybddy%2Fteg18I2UzgYhpo4gg1I3ehe9HXVh1UeE4ieofCzo7LsA6HsACYzPm9jwkWyeS0N4i9PEGocWvZU60OuMeIVhHAP2hKe%2FBtT0oqFl%2FIpclutQSwFcHdjrgjLPWYVQ1TB3n%2Fy%2FBImOdSuaIOdCbnKo6RKg7UX7ES2UZWm6mWfbiZrAWTUlHfIB7VRnVtOrQhGgoE1X9JgZEwSvGI0KKt5WTYK7Ps8lZj3P6MdO8GGZ6jjyAzadaTn0Ifn%2BywJeJnMogZs0soU%2BUN88lBnxdtl%2Flfu1za1%2FlLVmcAJitg2iOh2hA6r%2BeR1kPMtbH3agU4XijeWi8mKdn%2FaFEVwszUQjW903A9F0LMEgQOZWHRsM5UIIj7HPQNMxRLVs%2BJOG%2BOoX2HzodWpHR6pC8vbCMSzFn1Ow%3D', APPC_SESSION_SID: 's%3AjYgsQ8hdh5yXnTX8nxy6J8yyv8HRcnMA.jhV1xEQLr3PmHW37yR3hdLwlKgj2NYgrxqQoj9CZzfY', APPC_SESSION_USERNAME: 'kkolipaka@appcelerator.com', APPC_SESSION_ORGID: '100000780', APPC_SESSION_ENV: '{""name"":""production"",""isProduction"":true,""acsBaseUrl"":""https://preprod-api.cloud.appctest.com"",""acsAuthBaseUrl"":""https://dolphin-secure-identity.cloud.appcelerator.com"",""nodeACSEndpoint"":""https://admin.cloudapp-enterprise-preprod.appctest.com""}', APPC_SESSION_ENTITLEMENTS: '{""id"":""54d8e49fce78815d81104cb3"",""name"":""Team"",""partners"":[""acs"",""analytics""],""supportLink"":""http://support2.appcelerator.com/"",""users"":{""min"":1,""max"":-1},""testingDevices"":{""min"":0,""max"":0},""allowProduction"":true,""arrowPublish"":true,""nativeSDK"":false,""insights"":true,""apiRateMonthPerSeat"":10000000,""apiRateMinute"":200,""pushRateMinute"":200,""storageGBRateMonth"":100,""eventRateMonthPerSeat"":2000000,""daysDataRetained"":365,""maxOrganizations"":1,""dateRangeLimit"":365,""dateRangeCustom"":true,""exportMetrics"":true,""exportAcs"":true,""paid"":true,""containerPoints"":0,""containerPointsPerSeat"":9,""_version"":1}', ALLOY_PATH: '/Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/node_modules/alloy/bin/alloy' }, stdio: [ Socket { _connecting: false, _hadError: false, _handle: [Object], _parent: null, _host: null, _readableState: [Object], readable: true, domain: null, _events: [Object], _eventsCount: 4, _maxListeners: undefined, _writableState: [Object], writable: false, allowHalfOpen: false, destroyed: false, bytesRead: 0, _bytesDispatched: 0, _sockname: null, _writev: null, _pendingData: null, _pendingEncoding: '', fd: 0 }, Socket { _connecting: false, _hadError: false, _handle: [Object], _parent: null, _host: null, _readableState: [Object], readable: false, domain: null, _events: [Object], _eventsCount: 3, _maxListeners: undefined, _writableState: [Object], writable: true, allowHalfOpen: false, destroyed: false, bytesRead: 0, _bytesDispatched: 4859, _sockname: null, _writev: null, _pendingData: null, _pendingEncoding: '', _type: 'pipe', fd: 1, _isStdio: true, destroySoon: [Function], destroy: [Function] }, 'pipe' ] } 10/20/2015, 4:11:33 PM Operating System Name = Mac OS X Version = 10.11 Architecture = 64bit # CPUs = 8 Memory = 17179869184 Node.js Node.js Version = 4.1.0 npm Version = 2.14.3 Titanium CLI CLI Version = 5.0.5 Titanium SDK SDK Version = 5.2.0.v20151019184553 SDK Path = /Users/kondalkolipaka/Library/Application Support/Titanium/mobilesdk/osx/5.2.0.v20151019184553 Target Platform = iphone Command /usr/local/bin/node /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/node_modules/titanium/bin/titanium build --platform ios --log-level trace --sdk 5.2.0.v20151019184553 --project-dir /Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/app5 --target simulator --ios-version 9.0 --device-family universal --deploy-type development --sim-type iphone --sim-version 9.0 --device-id 2B5681C9-DB62-4917-AE3E-37B1D79AB4AA --profiler-host 192.168.0.112:58214 --skip-js-minify --no-colors --no-progress-bars --no-prompt --prompt-type socket-bundle --prompt-port 63446 --username kkolipaka@appcelerator.com --password kondal@19519 --plugin-paths /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules --config-file /var/folders/9n/xpk1tm596cbctmwyfhcqysfw0000gn/T/build-1445328688793.json --no-banner [INFO] : Found Titanium plugin id=ti.alloy version=1.0 [INFO] : Deploy type: development [INFO] : Building for target: simulator [INFO] : Building using iOS SDK: 9.0 [INFO] : Building for iOS Simulator: iPhone 6 [INFO] : Building for device family: universal [INFO] : Minimum iOS version: 7.1 [INFO] : Debugging disabled [INFO] : Profiler enabled via profiler host: 192.168.0.112:58214 [INFO] : Set to copy files instead of symlinking [INFO] : Forcing clean build: /Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/app5/build/iphone/build-manifest.json does not exist [INFO] : Initializing the build directory [INFO] : Found Alloy app in /Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/app5/app [INFO] : Executing Alloy compile: /usr/local/bin/node /Users/kondalkolipaka/.appcelerator/install/5.0.3/package/node_modules/appc-cli-titanium/node_modules/alloy/bin/alloy compile /Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/app5/app --config platform=ios,version=0,simtype=none,devicefamily=universal,deploytype=development,target=simulator --no-colors [INFO] : [config.json] config.json unchanged, using cached config.json... [INFO] : ----- MVC GENERATION ----- [INFO] : [global style] loading from cache... [INFO] : [index.xml] view processing... [INFO] : style: ""index.tss"" [INFO] : view: ""index.xml"" [INFO] : controller: ""index.js"" [INFO] : created: ""Resources/iphone/alloy/controllers/index.js"" [INFO] : created: ""Resources/iphone/alloy/styles/index.js"" [INFO] : [INFO] : [INFO] : [app.js] using cached app.js... [INFO] : [INFO] : ----- OPTIMIZING ----- [INFO] : - iphone/alloy.js [INFO] : - iphone/alloy/sync/localStorage.js [INFO] : - iphone/alloy/sync/properties.js [INFO] : - iphone/alloy/sync/sql.js [INFO] : [INFO] : Alloy compiled in 1.26289s [INFO] : Alloy compiler completed successfully [INFO] : Creating Xcode project [INFO] : Creating Entitlements.plist [INFO] : Creating Info.plist [INFO] : Disabling ATS [INFO] : Creating main.m [INFO] : Creating Xcode config files [INFO] : Copying Titanium libraries [INFO] : Copying Titanium iOS files [INFO] : Cleaning Xcode derived data [INFO] : Creating debugger and profiler plists [INFO] : Analyzing Resources directory [INFO] : Analyzing platform files [INFO] : Analyzing module files [INFO] : Analyzing localized launch images [INFO] : Analyzing CommonJS modules [INFO] : Creating asset catalog [INFO] : Creating app icon set [WARN] : Skipping Resources/iphone/appicon-60@2x.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-60@3x.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-76.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-76@2x.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-Small-40.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-Small-40@2x.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-Small.png because app icons must not have an alpha channel [WARN] : Skipping Resources/iphone/appicon-Small@2x.png because app icons must not have an alpha channel [INFO] : Creating launch image set [INFO] : Creating assets image set [INFO] : Processing JavaScript files [INFO] : Writing app properties [INFO] : Writing i18n files [INFO] : Processing Titanium symbols [INFO] : Removing files [INFO] : Invoking xcodebuild [INFO] : Finished building the application in 1m 15s 276ms [INFO] : Launching iOS Simulator [INFO] : Application started [INFO] : app5/1.0 (5.2.0.419c5c2) [ERROR] : Error connecting to profiler: Error Domain=NSPOSIXErrorDomain Code=2 ""No such file or directory"" {code}",5,test +TISTUD-7796,"If you run ""npm ls -g appcelerator"" when a pre-release version is installed, ""npm ERR! code 1"" is returned","*Details:* If you run ""npm ls -g appcelerator"", ""npm ERR! code 1"" is returned. *Note:* * This issue *does not occur* with Node 0.10.38. *Steps to reproduce:* # Make sure you have Node 4.X.X or 0.12.X # Install Appc CLI NPM: {{sudo npm install -g appcelerator@4.2.1-5}}. It HAS to be a pre-release (including a -X in the version #) # Next, run the following command in your ~ path: {{npm ls -g appcelerator}} *Actual:* The following error is returned: {code} WilsonComputer:~ wluu$ npm ls -g appcelerator npm WARN unmet dependency /usr/local/lib/node_modules/gittio/node_modules/update-notifier requires request@'^2.36.0' but will load npm WARN unmet dependency /usr/local/lib/node_modules/gittio/node_modules/request, npm WARN unmet dependency which is version 2.30.0 npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npmconf requires semver@'2' but will load npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver, npm WARN unmet dependency which is version 5.0.3 npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npmconf requires uid-number@'0.0.5' but will load npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/uid-number, npm WARN unmet dependency which is version 0.0.6 npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/read-package-json/node_modules/normalize-package-data requires semver@'2 || 3' but will load npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver, npm WARN unmet dependency which is version 5.0.3 npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client/node_modules/npm-package-arg requires semver@'4' but will load npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver, npm WARN unmet dependency which is version 5.0.3 /usr/local/lib └── (empty) npm ERR! code 1 {code} *Expected:* No error should be returned when you run {{npm ls -g appcelerator}}.",5,test +TISTUD-7853,"WatchOS2: ""Invalid ""--pp-uuid"" value"" Provisioning Profile Error","When importing the sample Apple WatchOS2 app project and running, the following error will occur if the provisioning profile is changed _after_ importing / creating: {code:java} [ERROR] : Invalid ""--pp-uuid"" value ""d69b8a2c-5fd0-4fb2-b86f-abb27aede70f"" For help, run: titanium help build TRACE | titanium exited with exit code 1 ERROR | Error: ti run exited with error code 1 at ChildProcess. (/Users/harrybryant/.appcelerator/install/5.0.4-2/package/node_modules/appc-cli-titanium/plugins/run.js:92:66) at ChildProcess.emit (events.js:110:17) at Process.ChildProcess._handle.onexit (child_process.js:1074:12) TRACE | Sending exit signal to titanium process: 52441 {code} *Steps to Reproduce:* 1. Import Apple WatchOS2 Sample App. 2. Change the Provisioning profile for the Apple Watch & Device in the tiapp.xml, found under ""Configure Provisioning Profiles"" 3. Run the project.",5,test +TISTUD-7801,"In preprod with Node 4.2.1, if you create a mobile app with services enabled, then the tiapp.xml will say ""app is registered with an organization you are not part of""","*Details:* If you are in preprod with Node 4.2.1 and you create a mobile app with services enabled, then the tiapp.xml will say ""app is registered with an organization you are not part of."" *Note:* * Verified the app is created in my org; see same.png attachment * If I create a mobile project from the CLI and import the project into Studio, I get the same bug behavior. * Verified issue is reproducible in preproduction, *not in production.* However, it does take a while to enable services in production. * Issue is *not reproducible with Node 0.12.X and lower.* *Steps to reproduce:* # Make sure your environment is pointing to preproduction # Make sure you have Node 4.2.1 installed # Create a mobile project with services enabled # Once mobile project is enabled, wait for tiapp.xml to load *Actual:* ""app is registered with an organization you are not part of"" message appears in the tiapp.mxl; see bad_error.png. *Expected:* Should be able to create a mobile project from Studio without any issues.",5,test +TISTUD-7804,Cannot open Studio after clean install,"After performing a clean install of Studio, I am unable to open it. The launch is stuck after entering login credentials, on an ""Installing Node"" message. Node was installed with the installer package, so Studio should not need to install it again. *Steps to reproduce issue* 1. Clean your system of any Appcelerator/Node components 2. Install Studio via the installer 3. Launch Studio *Actual Results* Launching Studio gets stuck on an ""Installing Node"" message *Expected Results* Studio is able to launch successfully",8,test +TISTUD-7805,Installers: Update go.appcelerator.com with the new node.js version 0.12.7,Update go.appcelerator.com with the new node.js version 0.12.7 *For Windows* * http://go.appcelerator.com/installer_nodejs_windows * http://go.appcelerator.com/installer_nodejs_windows.msi *For Mac* * URL: http://go.appcelerator.com/installer_nodejs_osx ,5,test +TISTUD-7822,Studio freezes for a while when we open a tiapp.xml file where the project org does not belong to the current logged in user,"Appcelerator Studio freezes for a while when we open a tiapp.xml file where the project organization does not belong to the current logged in user *Reproducible steps:* # Open any project tiapp.xml file which is created with a different org and does not belong to the current logged in user. # Keep doing some activity for next 30 sec(keeping moving mouse cursor for some time to easily reproduce the problem), after some time studio won’t allow you to do and it’s freezes for almost 40 sec.",5,test +TISTUD-7841,Autofill app id based on company url in new project wizard,"Request from [~cwilliams] We've long had an enhancement request related to making this wizard ""smarter"" about fields like this in terms of: * populating the app id default value using reverse of the URL (i.e. http://www.appcelerator.com makes app id start with: ""com.appcelerator."" and when you tab into app id field, you start typing at the end of that.) * Remembering previous values for company URL/app id prefix. It's small, but useful improvement. http://example.org -> org.example. https://www.something.co.uk -> uk.co.something. Like what is typical for java package names ",5,test +TISTUD-7851,Studio: Hangs for a long duration when trying to access remote URL for the first time after launch,"h5. Description: When importing an Existing Mobile Project for the first time after launching Studio, the process takes an abnormally long time, and studio becomes unresponsive. Import times vary between 1:30 - 2 minutes. Any subsequent imports (including different projects to the first) are instant. This occurs during the ""Project Directory"" selection, & before clicking ""Finish"". Closing Studio and relaunching will cause this issue to occur again. I've attached a Jstack log file of the process. *Note:* This issue does not occur 100% of the times tested, But after repeating the above process 4 times, it occurred for 3 of them. h5. Steps to reproduce: 1. Close Studio if already open. 2. Launch Studio. 3. Import Project. 4. Import Existing Mobile Project. 5. Click ""Browse"" and Navigate to a valid mobile project. 6. Issue should occur. 7. Repeat from steps 1 - 5. 8. Issue should not occur. h5. Result: OS loading pinwheel will appear and Studio will become unresponsive for a long duration. h5. Expected Result: Project directory selection for Importing existing mobile projects should be instant. ",5,test +TISTUD-7852,"Studio: During import, there is a typo: ""registring""","h5. Description: While importing an app, I noticed there was a typo in ""registering"". It incorrectly displays ""registring"" in the progress pane as well as in the lower portion of the main Studio window. h5. Steps to reproduce: 1) Import a project that requires registration 2) Open the progress pane 3) Watch the progress pane and the lower portion of the studio window h5. Result: ""Registring"" text appears. h5. Expected Result: ""Registering"" should appear",1,test +TISTUD-7855,Studio: Install Android SDK dialog doesn't resize large enough to hold entries,"h3. Steps to Reproduce Preferences > Studio > Platforms > Android > Install SDKs... h3. Actual Result Loads the list of SDKs on the dialog async, but once they're loaded the listing is both too wide and tall for the containing view, resulting in truncated/missing items. h3. Expected Result View resizes to fit it's content",5,test +TISTUD-7866,"Mac: If you have Node version < 0.12.X, 4.4.0 Studio installer does not install Node version 4.2.2 during installation phase","*Details:* If you have Node version < 0.12.X, 4.4.0 Studio installer does not install Node version 4.2.2 during installation phase. *Steps to reproduce:* # Make sure you have Node version < 0.12.X; I used Node 0.10.38 # Grab Studio installer 4.4.0.201511130407 # Launch Studio installer and go through the wizard *Actual:* Studio installer does not install Node 4.2.2 during installation phase, but installs Node 4.2.2 during launch of Studio. *Expected:* Studio installer should install Node 4.2.2 during installation phase.",5,test +TISTUD-7867,Node is not correctly installed by 4.4.0 windows installer on a win machine with no node,"h5.Steps To Reproduce: *NOTE: Make sure you do not have node & appcelerator studio installed on your win machine.* 1. Download the installer for studio 4.4.0.201511130407. 2. Run the installer. 3. The installer will download the node installer & start the installation. 4. After the node installation observe the error. h5.Actual Results: 1. We see error ""Node.js mandatory prerequisite was not correctly installed"". h5.Expected Results: 1. We should not see any error & the node installation should be successful.",5,test +TISTUD-7869,Error: Node.JS a mandatory pre-requisite was not installed correctly,"While installing Appcelerator- Studio(4.3.3) in Windows 8, 64-bit OS , gives the following error. *Node.JS a mandatory pre-requisite was not installed correctly* ",3,test +TISTUD-7871,"When you update Studio, the admin dialog to enter admin password appears ","*Details:* When you update Studio, the admin dialog to enter admin password appears. *Steps to reproduce:* # Make sure you do not have the latest Studio version # Point Studio to a Stream e.g. [RC Stream|http://preview.appcelerator.com/appcelerator/appc-studio/standalone/update/rc/] # Next, go to Help > Check for Appcelerator Updates # When the update dialog appears, click Next, click the check box to accept license agreement, and click install *Actual:* The admin dialog to enter admin password appears; see attachment. *Expected:* The admin dialog to enter admin password should not appear when you install updates.",5,test +TISTUD-7872,Studio does not find 5.1.0.GA,"Studio 4.3.3 prompted me to update: * Studio 4.4.0 * CLI 4.2.2 * Core 5.1.0 But not SDK 5.1.0 Also after updating Studio and restarting it still didn't. * I'm logged in to production * I have these SDKs installed: 4.1.1.GA, 5.0.1.GA, 5.0.2.GA, 5.1.0.RC, 5.1.0.beta, 5.1.0.v20151116164430, 5.2.0 * {{appc setup}} *does* find SDK 5.1.0 * I'm subscribed to stream {{http://preview.appcelerator.com/appcelerator/appc-studio/standalone/update/stable/}}",3,test +TISTUD-7879,JIRA ticket creation will fail from studio if we select the severity to 'None',JIRA ticket creation will fail from studio if we select the severity to 'None',3,test +TISTUD-7880,Constant error: getSignedInUser() after Studio 4.4.0 upgrade,"h6.Issue Description Client just updated AppC Studio to get 5.1 and now when he tries and do pretty much anything (launch, run in simulator, build, etc) he gets: h6.Error {quote} ""An error has occurred. See error log for more details. com.appcelerator.titanium.core.user.ITitaniumUserManager.getSignedInUser()Lcom/appcelerator/titanium/core/user/ITitaniumUser;"" {quote} h6.Output Command $ du -hs * full output attached. {code} -rw-r--r-- 1 u316184 admin 12K Jul 23 12:48 com.appcelerator.titanium.usage_2.0.0.1426966430.jar -rw-r--r-- 1 u316184 admin 12K May 22 2015 com.appcelerator.titanium.usage_2.0.0.jar -rw-r--r-- 1 u316184 admin 50K Jul 23 12:48 com.aptana.usage_4.0.0.1436893468.jar -rw-r--r-- 1 u316184 admin 50K Nov 23 14:23 com.aptana.usage_4.0.0.1446606882.jar {code}",5,test +TISTUD-7883,Install Titanium SDK - List of SDK's empty,"As shown on the attached image, List of SDK is empty. I'm on a freshly installed Appcelerator studio... This makes it impossible to install older SDK's since: http://builds.appcelerator.com.s3.amazonaws.com/index.html don't include GA builds anymore... ",5,test +TISTUD-7897,Android: App hangs on splash screen if debugger is launched again after the first time,h5.Steps to reproduce: 1. Create an app and set a breakpoint in it. 2. Debug the app on android device. 3. After the app launches do the appropriate thing and make it hit the breakpoint OR just leave the app as is. 4. Do not terminate the debug process from studio. 5. Again launch the debugger without closing the app. 6. Notice after the app launches this time( It sometimes happens on the third debugger run). h5.Actual Results: 1. The app hangs on the splash screen. h5.Expected Results: 1. The app should not hang on the splash screen & should launch fully.,5,test +TISTUD-7899,Remove hardcoded node version 4.2.1 from studio,"Remove hardcoded node version 4.2.1 from studio, rather show it as ""Latest"" in the update wizard. *Reproducible steps:* 1. Make sure you are not on the node version which is supported by studio. Anything lower than 0.12.7(which is min node version supported) 2. Check for Appcelerator updates from Studio through ""Help->Check for Appcelerator Updates"" option 3. Studio will show update wizard with various updates which are available. 4. Look for node version, it shows ""4.2.1"" is the latest version but it installs 0.12.7 when I choose to install. *Expected*: As studio can't identify the latest node version from http://go.appcelerator.com/installer_nodejs_osx link, it's better to show ""Latest"" as a version text and install whatever is available. ",2,test +TISTUD-7900,Invalid proxyServer set after launching Studio,"Appcelerator Studio sets invalid {{proxyServer}} config variable ({{""https://null""}} ) after it forces to update Node.js to 0.12.7 while launching Appcelerator Studio. It happens on both Windows 8.1 and Windows 10. h5. How to reproduce: - Make sure there's no invalid {{proxyServer}} variable set ({{appc config|grep proxyServer}}) - Download latest Appcelerator Studio 4.4.0 - Launch Appc Studio - It launches Node.js 0.12.7 installer - After finished installing Node.js, Studio launches - Appc Studio failed to login & shows error dialog (see attached image) - ( try ({{appc config|grep proxyServer}}) and you'll see ""proxyServer"": ""https://null"" ) ",5,test +TISTUD-7902,Can not dismiss new project dialog and updates message if they are in the screen at the same time,"h2. Description When a user is in the New Project Wizard and the ""Appcelerator Updates Available"" message pops up, the user can not dismiss the updates dialog and can not click to cancel the Wizard because the updates message is at the top, see attached screenshot",5,test +TISTUD-7910,Watch App XCode Path should be Xcode Path (lowercase C).,Watch App XCode Path should be Xcode Path (lowercase C and equal to Tiapp Editor). ,1,test +TISTUD-7911,Remove multiple wizard pages for configuring provisioning profiles ,"Subtask from TISTUD-7697: The wizard suggests that you select the targets here but deselecting doesn't affect the actual listed targets in the tiapp.xml. It just determines the choices given in the next step. So the wizard should either remove the unselected targets (and populate this list by reading the available targets in the Xcode project) or it might as well skip this step and show the next step right away for all targets. It completely make sense and keep everything in one page, as we hardly have 2 targets. ",5,test +TISTUD-7912,Move Studio Login to Background,Currently the Studio Login process is done serially and blocks starting of the environment. We should move this to a parallel process that allows Studio to startup but continues to authenticate in the background. The user should be prompted if there is an issue with credentials authenticating. PJD https://wiki.appcelerator.org/display/prd/PJD+-+Onboarding+Teardown,8,test +TISTUD-7916,Can't login to Jira via Appcelerator Studio if longing have space,"If user wants to submit a ticket (Help -> Studio -> Submit a Ticket...) and tries to login using username which consist white space (i.e. CREATIVE KAIZEN) will get error as on attached picture. It is not caused by bad password/login because in that case error will be different (""Bad credentials) and there is no problem to login with same credentials via webpage.",3,test +TISTUD-7920,Option to link an existing Xcode project?,* Why don't we have an option anymore to link an existing Xcode project? !Screen Shot 2015-09-04 at 14.06.07.png! ,8,test +TISTUD-7939,"WindowsPhone Invalid ""--device-id"" value ""8-1-1"" Error","h6.Issue Description Appcelerator simple project is not building in appcelerator studio, the console log is showing the next error {code} [ERROR] : Invalid ""--device-id"" value ""8-1-1"" For help, run: titanium help build 2015-12-23T17:45:54.023Z | TRACE | titanium exited with exit code 1 2015-12-23T17:45:54.023Z | ERROR | Error: ti run exited with error code 1 at ChildProcess. (C:\Users\rich\.appcelerator\install\5.1.0\package\node_modules\appc-cli-titanium\plugins\run.js:92:66) at ChildProcess.emit (events.js:110:17) at Process.ChildProcess._handle.onexit (child_process.js:1074:12) 2015-12-23T17:45:54.023Z | TRACE | Sending exit signal to titanium process: 5144 {code} h6. Steps to Reproduce # Create a new simple classic project in appcelerator studio # Run for any windows emulator or device **Complete log is attached ** using the command appc ti build -p windows -T wp-emulator -C 8-1-1 works.",5,test +TISTUD-7932,Unable to publish Windows Phone App,"I am trying to publish my App to Windows Store, According to Appcelerator Docs : https://wiki.appcelerator.org/display/guides2/Distributing+Windows+Applications?watchingPage=false&watchingSpace=false&watchingBlogs=false&isAdmin=false&isBlogPost=false Under *Package for Windows Phone Store with Studio*, it says there is an option as *Windows Store* to publish the app, but in my studio this option is not available, I've also tried this on other machines with fresh installations but its not available on that machines too. !scr-1.png|thumbnail! In the manifest when I tried to add Windows Publisher Id under tag it throws error as, ""Invalid content was found starting with element 'windows'. One of '{sdk-version, deployment-targets, id, name, version, publisher, url, description, copyright, icon, persistent-wifi, prerendered-icon, statusbar-style, statusbar-hidden, fullscreen, navbar-hidden, analytics, guid, iphone, android, ios, mobileweb, tizen, ivi, property, modules, plugins, extensions}' is expected"" I have also tried to Publish the app by right clicking the project -> Publish -> Windows Phone Distribution, which opens a new Dialogue Box but there is no option to create a new certificate, as mentioned in the docs. !Scr-2.png|thumbnail! ",2,test +TISTUD-7942,Cannot create Alloy project components via right click menu,"When trying to create an Alloy project component (Controller, Widget, View, etc.) by right clicking the project. The ""OK"" button when entering a name is unresponsive. See attached gif. *Steps to reproduce issue* 1. Create an Alloy project 2. Right-Click the project and select ""New -> Alloy Controller"" 3. Enter a name and click ""OK"" *Expected Results* The Controller is created successfully *Actual Results* The ""OK"" button is unresponsive *Notes* This applies to all project components (Controllers, Migration, Model, Views, Styles, Widget)",3,test +TISTUD-7945,Cache sdk_info.json file for improving performance during startup,"During Studio startup, it tries to pull sdk_info.json file from appc-studio.appcelerator.com in order to validate the SDK and platform (iOS, Android, Windows) versions. If there is a latency to fetch this json file, then Studio performance degrades while validating the platform versions. So, Studio has to keep a cache copy after this file is fetched - and it can use the cache copy during the startup while it tries to update the copy.",5,test +TISTUD-7946,User should be able to set Arrow port in the launch configuration for Studio,"If a customer wants to run an Arrow service on a specific port they have to run the project from the CLI after defining he port in conf/default.js. Running the project from Studio always chooses a random port. *Running from CLI* {code} grep port: conf/default.js port: 8181 appc run | grep port INFO | server started on port 8181 {code} *Console output running the same project from Studio* {code} INFO | Access the Arrow admin at http://127.0.0.1:56503/arrow. This will only be available on your dev environment. To enable in production, set enableAdminInProduction in your config INFO | Access the Arrow API doc at http://127.0.0.1:56503/apidoc INFO | started INFO | server started on port 56503 {code} *Currently run configurations only shows configs for mobile apps*",8,test +TISTUD-7952,iOS: Breakpoints not hit when debugging projects,"When trying to debug an iOS project, I am not seeing any breakpoints hit in Alloy or Classic projects. I see this on devices and simulators *Steps to reproduce issue* 1. Create a new project 2. Add a breakpoint 3. Debug the project *Expected Results* The breakpoints are hit *Actual Results* The breakpoints are not hit and the below appears in the Studio log *Notes* I see this in the Studio log: {code} !ENTRY com.aptana.js.debug.core 1 0 2016-01-12 14:24:48.254 !MESSAGE Extension version: 5.1.2; protocol v2 !ENTRY com.aptana.js.debug.core 4 4 2016-01-12 14:24:48.268 !MESSAGE !STACK 0 java.lang.NullPointerException org.eclipse.core.runtime.Path.fromPortableString(Path.java:103) com.appcelerator.titanium.core.launching.TitaniumAppURIMapper.resolve(TitaniumAppURIMapper.java:71) com.aptana.js.debug.core.internal.model.JSDebugTarget.resolveSourceFile(JSDebugTarget.java:2199) com.aptana.js.debug.core.internal.model.JSDebugTarget.handleScripts(JSDebugTarget.java:730) com.aptana.js.debug.core.internal.model.JSDebugTarget.access$6(JSDebugTarget.java:703) com.aptana.js.debug.core.internal.model.JSDebugTarget$DebugConnectionHandler.handleMessage(JSDebugTarget.java:2355) com.aptana.js.debug.core.internal.model.DebugConnection.handleMessage(DebugConnection.java:228) com.aptana.js.debug.core.internal.model.DebugConnection.access$3(DebugConnection.java:223) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:155) {code}",5,test +TISTUD-7956,Studio does not recognise orgs with CLI 5.2.0,"h5. Description: When launching Studio with CLI version 5.2.0-220, the organisation is not recognised upon project creation, or in the bottom right hand of the Studio. However, the CLI is able to recognise organisations from the terminal. *This issue does not occur when using CLI 5.1.0, and affects production.* h5. Steps to reproduce: 1. Appc use 5.2.0-XXX 2. Launch Studio 3. Observe bottom right hand for organisation. 4. Create mobile app project 5. Observe Appcelerator Platform Services setup. h5. Result: ""Unknown Organisation"" using CLI 5.2.0-220 h5. Expected Result: Studio should recognise organisations using CLI 5.2.0-220",5,test +TISTUD-7957,When creating a new app project the alloy option does not appear ,When creating a new app project the alloy option does not appear. This is a {color:red}regression {color}from 5.1.0 core. *Steps to reproduce:* # From the studio home I selected file > new > mobile app project. *Actual :* The pop-up appears but does not display the option to create an alloy app. (see image) *Expected:* The pop-up appears withe the option for an alloy app. (see image) ,2,test +TISTUD-7960,Add Swift versions of the applewatch templates,"https://github.com/appcelerator/titanium_studio/blob/master/plugins/com.appcelerator.titanium.ios.core/src/com/appcelerator/titanium/ios/core/IOSConstants.java#L85-L93 ( https://github.com/appcelerator/titanium_studio/search?q=APPLEWATCHKIT&type=Code I think it would be best to leave out the --template option so that you let the CLI pick the default for the type, but the problem is that currently that default is still watchos1. With 5.2 it will become watchos2-swift, but we won't drop the Obj-C watchos2 until 6.0. So I think we should check the SDK version of the project and if it's >= 5.2 leave out the option. ",5,test +TISTUD-7961,Avoid force update if studio doesn't find required cli information in the sdk-info.json file,"Avoid force update if studio doesn't find the required cli information in the sdk-info.json file If https://github.com/appcelerator/appc-studio-server/blob/master/web/public/sdk_info.json doesn't have required CLI information, studio is forcing to update everything. *Expected*: Studio shouldn't ask for force update if CLI version info is not defined in the sdk_info.json file.That means, ""Remind me later"" button on the update wizard should be enabled. This is the effect of TISTUD-7705",3,test +TISTUD-7971,Unable to publish arrow app,"h5. Description: Unable to publish arrow app using CLI 5.2.0-233 Able to create and publish arrow app using CLI 5.2.0-233 in 4.4.0GA studio This is a {color:red}regression{color} h5. Steps to reproduce: 1.Create Arrow App 2.Attempt to publish in studio h5. Result: Error is displayed, see attached screenshot h5. Expected Result: Should be able to publish arrow app with no errors, using latest CLI ",3,test +TISTUD-7972,"If you run Test on a non-enabled-service app, then Studio will become unresponsive and crash","*Details:* If you run Test on a non-enabled-service app, then Studio will become unresponsive and crash. *Note:* * This is *not a regression* with current GA stack. *Steps to reproduce.* # In Studio, create a mobile project with services *disabled;* only analytics will be available. # Select on the newly created project and select Test from the drop down list. # Another dialog will appear asking you to enable Test services; select Yes. *Actual:* Studio will become unresponsive and will crash when you force close it; see attachments. *Expected:* Studio should not become unresponsive and crash.",5,test +TISTUD-7974,Org name is hidden below the users email,The org name is hidden below the users email address. *Steps to reproduce:* # Launch Studio # Observe bottom right hand for organisation name . *Actual :* The org name is hidden below the users email address (see image) *Expected:* The full org name is displayed ,3,test +TISTUD-7979,Liveview for the Windows Platform,"h5.Description TIMOB-19185 implemented liveview for the Windows Platform, the version within Studio needs to be updates for this to be distributed. Checking the [hooks/lvhook/js file|https://github.com/appcelerator/titanium_studio/blob/development/plugins/com.appcelerator.titanium.liveview.core/node_modules/liveview/hook/lvhook.js] shows that the current version does not have the Windows Platform changes",3,test +TISTUD-7981,Use appc daemon to request system info,"Appcelerator Studio will no longer need to call {{ti info -t }} a bunch of times each minute. With the appc daemon, Studio can simply connect to the server over a WebSocket and query the system information as well as listen for changes. The appc daemon will ship with the appc cli, so Studio will not need to worry about installing the appc daemon. However, Studio will need to make sure appcd is running before trying to connect to it. If appcd is already running, the start operation immediately returns successfully. Note: appcd isn't guaranteed to be globally installed. You will want to manually invoke it by calling {{node /path/to/appcd start}}. This applies to all platforms: OS X, Linux, and Windows. Studio will need to open a WebSocket to 127.0.0.1 port 1732. Once the socket is open, it will need to send a request using the appcd protocol. It's pretty simple. To kick off a request, Studio needs to send a stringified JSON object containing a {{version}}, {{path}}, {{id}}, and optionally a {{data}} payload. Here's the JavaScript equivalent: {code} socket.send(JSON.stringify({ version: '1.0', path: '/system-info', id: '0' }); {code} The ""version"" must be {{1.0}}. The ""path"" can be {{/system-info}} to get the info for ALL supported platforms (i.e. Android & iOS on OSX, Android & Windows on Windows, Android on Linux). The ""path"" may also contain the specific platform such as {{/system-info/ios}} or even platform specific info such as {{/system-info/ios/devices}}. The ""id"" must be a string containing a unique request id. It can be a sequential number (cast as a string) or a UUID. The purpose of the ""id"" is that a single WebSocket can service multiple simultaneous requests and ""id"" is the only way you can match up the response with the initial request. For example, the appcd client generates a UUID for each request and then registers that UUID with an event emitter so that responses to the request ID are emitted to the code that made the request. Studio can use whatever mechanism it wishes to match responses with requests. The ""data"" payload is optional. It's a JSON object containing additional information. It will allow Studio to specify additional request arguments and filtering options. The response is a stringified JSON object containing an {{id}}, {{data}}, and possibly a {{status}}. If the latest appc cli is not installed, and thus appc daemon is not installed, then Studio should continue to use the {{ti info}} method it does today.",8,test +TISTUD-7982,Windows: Studio should validate the value for Windows Publisher ID before accepting it,"h5.Description Studio should validate the value that it places into the Publisher ID field in Studio->Platforms->Windows, currently it seems that the value has no validation as I have seen {{windows.publisherId not found}} being placed into the field by Studio. For your reference the regex used by the CLI for this value can be found [here|https://github.com/appcelerator/titanium_mobile_windows/blob/master/cli/commands/_build/config/winPublisherId.js#L15] *Workaround* Set your windows.publisherId value to the CLI default {{appc ti config windows.publisherId 00000000-0000-1000-8000-000000000000}} h5.Steps to reproduce 1. Ensure you have no value in your ti config for windows.publisherId {{appc ti config -r windows.publisherId}} 2. Open Studio and check Preferences->Studio->Platforms->Windows h5.Actual result The value {{windows.publisherId not found}} can be placed into the field and when attempting to build it can cause the build to fail h5.Expected result The Publisher ID field should only accept valid input",5,test +TISTUD-7983,Content Assist: Windows Platform is not shown in content assist,h5.Description When using content assist Windows Platform does not show up in the platforms shown in the dialog and Ti.Windows components are not shown. I checked inside the api.jsca and it seems to be showing items listed as being valid for Windows but does not contain Windows specific items. h5.Steps to reproduce 1. In Appc Studio on Windows bring up the content assist dialog by typing {{Ti.}} 2. In Appc Studio on Windows type {{Ti.Windows}} h5.Actual result Nothing is shown h5.Expected result 1. Windows should be shown as a platform 2. Ti.Windows components should be shown,5,test +TISTUD-7987,Dashboard won't open in studio,"h5.Description Clicking the Appcelerator logo no longer loads dashboard in studio. h5.Steps to Reproduce 1.Open studio 2.Click the Appcelerator logo h5.Expected Outcome Dashboard should launch in studio h5.Actual Outcome Studio shows loading bar and says it's opening the page, but page doesn't open",1,test +TISTUD-7991,Creating an Arrow project with invalid characters in studio does not show any warning message.,"Creating an Arrow project with invalid characters in studio does not show any warning messages. This is not a regression. But In the GA the results are slightly different. *Steps to reproduce:* # Create an Arrow project in studio with invalid characters such as spaces. *Actual :* The status bar never moves past 2/3 of the way and stays like that showing no error or warning message. !Arrow Creation Studio.jpg|thumbnail! *Actual GA :* The status bar never moves past 2/3 of the way and stays then shows a warning message as shown in the picture below, and then creates the project. !Arrow Creation Studio GA.jpg|thumbnail! *Expected:* A warning message is displayed as in the CLI. !Arrow Creation CLI.jpg|thumbnail! ",3,test +TISTUD-7997,SDK update to 5.2.0.GA not found when 6.0 nightly is installed,"With 5.1.2.GA, 5.2.0.RC and 6.0.0 nightly installed, Studio update says _Latest Titanium SDK already installed_ and does not install 5.2.0.GA. Renaming the 6.0.0 folder to 6.0.0.CI or the original 6.0.0.v20160110233608 does not fix it. Removing the folder does. I traced it back here, but can't really tell why it thinks 5.2.0.GA is already installed: https://github.com/appcelerator/titanium_studio/blob/bcb31abca5a44bddc7a962319d5b040b4d3610c0/plugins/com.appcelerator.titanium.update.core/src/com/appcelerator/titanium/update/internal/core/TitaniumReleasesUpdater.java#L841-L842 Looking at the code for [getSDKStableInstalledVersion|https://github.com/appcelerator/titanium_studio/blob/bcb31abca5a44bddc7a962319d5b040b4d3610c0/plugins/com.appcelerator.titanium.update.core/src/com/appcelerator/titanium/update/internal/core/TitaniumReleasesUpdater.java#L579] and [SDKReleaseGAFilter|https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.core/src/com/appcelerator/titanium/core/mobile/SDKReleaseGAFilter.java] it should find 5.1.2.GA as my latest SDK. So then something must be wrong with [isHigherThanGA|https://github.com/appcelerator/titanium_studio/blob/bcb31abca5a44bddc7a962319d5b040b4d3610c0/plugins/com.appcelerator.titanium.update.core/src/com/appcelerator/titanium/update/internal/core/TitaniumReleasesUpdater.java#L830] which uses [DescendingStreamAwareVersionComparator|https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.core/src/com/appcelerator/titanium/core/DescendingStreamAwareVersionComparator.java] Logs to help debug the current issue: {code} !ENTRY com.appcelerator.titanium.update.core 1 0 2016-02-23 09:01:13.106 !MESSAGE (Build 4.5.0.201602170821) [INFO] com.appcelerator.titanium.update.core/debug/sdk_update Retrieving the list of Titanium mobilesdk from URL: https://f4df0833a1352ef193633d85356e6e80ffcdcdb7.cloudapp-enterprise.appcelerator.com/api/mobilesdk/releases/25991779-01c4-41a6-a4d3-86107428797b !ENTRY com.appcelerator.titanium.update.core 1 0 2016-02-23 09:01:16.610 !MESSAGE (Build 4.5.0.201602170821) [INFO] com.appcelerator.titanium.update.core/debug/sdk_update Available Titanium mobilesdk: { ""success"": true, ""releases"": [ { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""05645B49-C629-4D8F-93AF-F1CF83200E34"", ""version"": ""3.5.1.GA"", ""os"": ""linux"", ""url"": ""http://api.appcelerator.com/p/v1/release-download?token=v4KZph53"", ""checksum"": ""e9175d2185d9dc38c16a1b6810a257be"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""05645B49-C629-4D8F-93AF-F1CF83200E34"", ""version"": ""3.5.1.GA"", ""os"": ""linux"", ""url"": ""http://api.appcelerator.com/p/v1/release-download?token=h4KZpgK0"", ""checksum"": ""e9175d2185d9dc38c16a1b6810a257be...",5,test +TISTUD-8003,Non-modal dialog for submitting JIRA ticket from the studio,"h3. Please do a non modal dialog box for JIRA ticket. Always i want create a ticket, i can't access or copy past my code in the ticket because modal dialog ",5,test +TISTUD-8002,Studio autocompletes first (private) function that starts with _ when trying to use an underscore function,"When you have a function defined (anywhere) that starts with an underscore like: {code:js} function _bar() { } {code} And then you mean to type {{_.extend()}} Studio will autocomplete {{_}} to {{_bar}} as soon as you type the dot. Expected behaviour is for it to ignore not autocomplete when I deviate from the suggested autocompletions, just like when I type {{_foo}}. See attached video. Discovered by [~falko]: https://github.com/FokkeZB/nl.fokkezb.infiniteScroll/pull/55",8,test +TISTUD-8021,Liveview on Windows Phone 8.1,"According to some other JIRA tickets and the release notes for 5.2.0.GA, Liveview for Windows phone is now fixed. However, I have a windows phone 8.1 project with liveview enabled in appcelerator studio and I don't get any form of automatic code reload. Doesn't seem to work if I use the CLI either. This is the same on an emulator or device. Can I have some information on how to troubleshoot the problem, or maybe an update on the status of this feature? Thanks.",8,test +TISTUD-8009,App Preview for iOS Adhoc builds,"With the Installr app integration, we're looking to add a flag in adhoc build distribution flows for uploading to Installr App. Users should be able to flag their build to be uploaded to Installr. When selected they should be able to add a description to their build. Additional options available in the CLI plugin such as emailing existing users in the app or adding emails should also be in the form. CLI plugin located here: https://github.com/jeffbonnes/appc-app-preview-cli-hook",8,test +TISTUD-8010,App Preview for Android builds,"With the Installr app integration, we're looking to add a flag in adhoc build distribution flows for uploading to Installr App. Users should be able to flag their build to be uploaded to Installr. When selected they should be able to add a description to their build. Additional options available in the CLI plugin such as emailing existing users in the app or adding emails should also be in the form. CLI plugin located here: https://github.com/jeffbonnes/appc-app-preview-cli-hook",8,test +TISTUD-8011,Studio should rely on CLI to find updates ,"With 5.1.2.GA, 5.2.0.RC and 6.0.0 nightly installed, Studio update says _Latest Titanium SDK already installed_ and does not install 5.2.0.GA. Renaming the 6.0.0 folder to 6.0.0.CI or the original 6.0.0.v20160110233608 does not fix it. Removing the folder does. I traced it back here, but can't really tell why it thinks 5.2.0.GA is already installed: https://github.com/appcelerator/titanium_studio/blob/bcb31abca5a44bddc7a962319d5b040b4d3610c0/plugins/com.appcelerator.titanium.update.core/src/com/appcelerator/titanium/update/internal/core/TitaniumReleasesUpdater.java#L841-L842 Looking at the code for [getSDKStableInstalledVersion|https://github.com/appcelerator/titanium_studio/blob/bcb31abca5a44bddc7a962319d5b040b4d3610c0/plugins/com.appcelerator.titanium.update.core/src/com/appcelerator/titanium/update/internal/core/TitaniumReleasesUpdater.java#L579] and [SDKReleaseGAFilter|https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.core/src/com/appcelerator/titanium/core/mobile/SDKReleaseGAFilter.java] it should find 5.1.2.GA as my latest SDK. So then something must be wrong with [isHigherThanGA|https://github.com/appcelerator/titanium_studio/blob/bcb31abca5a44bddc7a962319d5b040b4d3610c0/plugins/com.appcelerator.titanium.update.core/src/com/appcelerator/titanium/update/internal/core/TitaniumReleasesUpdater.java#L830] which uses [DescendingStreamAwareVersionComparator|https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.core/src/com/appcelerator/titanium/core/DescendingStreamAwareVersionComparator.java] Wherever the bug exactly is I think we can simplify and make this a lot more stable: * Don't duplicate this logic (including it's bugs: CLI-705) in CLI and Studio, but let Studio rely on CLI to find updates so we have only one point of failure. * Don't rely on the SDK release version name (for available releases) and folder name (for installed releases) to determine what is available and installed, but use the checksum or timestamp (TIMOB-19541, see {{appc ti sdk list}}) so the logic does not fail if people rename SDK folders (CLI-910). * Don't compare if the latest available release is newer then the latest one installed, but simply check if the latest available release IS installed. This removes all the points of failure in stuff like [DescendingStreamAwareVersionComparator|https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.core/src/com/appcelerator/titanium/core/DescendingStreamAwareVersionComparator.java] Logs to help debug the current issue: {code} !ENTRY com.appcelerator.titanium.update.core 1 0 2016-02-23 09:01:13.106 !MESSAGE (Build 4.5.0.201602170821) [INFO] com.appcelerator.titanium.update.core/debug/sdk_update Retrieving the list of Titanium mobilesdk from URL: https://f4df0833a1352ef193633d85356e6e80ffcdcdb7.cloudapp-enterprise.appcelerator.com/api/mobilesdk/releases/25991779-01c4-41a6-a4d3-86107428797b !ENTRY com.appcelerator.titanium.update.core 1 0 2016-02-23 09:01:16.610 !MESSAGE (Build 4.5.0.201602170821) [INFO] com.appcelerator.titanium.update.core/debug/sdk_update Available Titanium mobilesdk: { ""success"": true, ""releases"": [ { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.2.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.2.0/mobilesdk-5.2.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.2.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.2/mobilesdk-5.1.2.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.1.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.1/mobilesdk-5.1.1.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.1.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.1.0/mobilesdk-5.1.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.2.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.2/mobilesdk-5.0.2.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.1.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.1/mobilesdk-5.0.1.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""5.0.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/5.0.0/mobilesdk-5.0.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.1.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.1/mobilesdk-4.1.1.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.1.0.GA"", ""os"": ""osx"", ""url"": ""http://builds.appcelerator.com/mobile-releases/4.1.0/mobilesdk-4.1.0.GA-osx.zip"", ""checksum"": ""7ff2e2485fbf745950ccc586d28a3483a413cb7e"", ""children"": null }, { ""build_type"": ""64bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""32bit_i386"", ""name"": ""mobilesdk"", ""guid"": ""1C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""linux"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-linux.zip"", ""checksum"": ""db95eff99c6e137bb53c5fb4386380a263844f55"", ""children"": null }, { ""build_type"": ""win32"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""version"": ""4.0.0.GA"", ""os"": ""win32"", ""url"": ""http://builds.appcelerator.com/mobile/4.0.0/mobilesdk-4.0.0.GA-win32.zip"", ""checksum"": ""779bfd4d226ba6d3162a069c50f3650ab42cd504"", ""children"": null }, { ""build_type"": ""10.5_i386"", ""name"": ""mobilesdk"", ""guid"": ""C5A13520-E091-4CEA-BFC3-AE453D23238D"", ""versio...",5,test +TISTUD-8012,"Studio needs to call ""appc run"" / ""ti build"" to build iOS/Android modules","Titanium SDK add support for building Titanium native modules via the CLI a while ago. It is suspected that Studio is still calling {{ant}} for Android modules and {{python build.py}} for iOS modules. These need to be updated to use the CLI. To build Android modules, simply run: {code} appc run --platform android --project-dir /path/to/module/android --build-only - OR - ti build --platform android --project-dir /path/to/module/android --build-only {code} For iOS modules, run: {code} appc run --platform ios --project-dir /path/to/module/iphone --build-only - OR - ti build --platform ios --project-dir /path/to/module/iphone --build-only {code} Things to note: * There should be no notable difference between using the Appc CLI vs Titanium CLI, but I could be wrong. Please advise. * The {{\-\-project\-dir}} must be to the module's platform-specific directory. * {{\-\-build\-only}} is only supported by iOS module build. Android support is coming in Titanium SDK 5.3.0 (TIMOB-20510). * The {{build.py}} has been officially deprecated as of Titanium SDK 5.2.1 and will be removed from new module projects in Titanium SDK 6.0.0, possibly 5.3.0 or 5.4.0. * Refer to TIDOC-2470 for more details.",5,test +TISTUD-8015,"""Missing icon"" in TiApp Editor when using DefaultIcon.png","When using the {{DefaultIcon.png}} in the Appc-Studio, the tiapp.xml shows a validation error (see attachment). When you select the DefaultIcon.png, it copies the Icon to the Resources directory and still fails. We should fix that, it confuses user when using Studio. My approach would be, to disable the whole field if the DefaultIcon.png is located in the project root.",5,test +TISTUD-8018,iOS Debugger: failed to connect. ,"h6. Issue Description The app seems to run fine in the simulator, but the debugger jumps some breakpoints. And approximately five minutes after app startup, user get a popup that says ""iOS debugger on simulator has encountered a problem. Debugger failed to connect. Accept timed out."" This is the error after the popup: {code} !ENTRY com.aptana.js.debug.core 1 0 2016-02-24 23:10:21.776 !MESSAGE Extension version: 4.1.0; protocol v2 !ENTRY com.appcelerator.titanium.ios.core 4 0 2016-02-24 23:15:21.780 !MESSAGE Debugger failed to connect !STACK 0 java.net.SocketTimeoutException: Accept timed out java.net.PlainSocketImpl.socketAccept(Native Method) java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) java.net.ServerSocket.implAccept(ServerSocket.java:545) java.net.ServerSocket.accept(ServerSocket.java:513) com.appcelerator.titanium.ios.core.launching.IOSNodeJSCommandsHelper.connect(IOSNodeJSCommandsHelper.java:491) com.appcelerator.titanium.ios.core.launching.IOSNodeJSCommandsHelper.access$1(IOSNodeJSCommandsHelper.java:488) com.appcelerator.titanium.ios.core.launching.IOSNodeJSCommandsHelper$3.run(IOSNodeJSCommandsHelper.java:464) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} And some other times application is not started. * full timeout log and application not starting log attached. h6. Steps to replicate # Create a new app # Add some breakpoints # Run as Debug # Some breakpoints are not detected # After five minutes the Debug crash # Run again # Application doesn't start ",8,test +TISTUD-8019,Studio: Selecting Two-Tabbed Alloy mobile app project generates a default Alloy project instead,"h5. Description: Selecting a ""two-tabbed"" alloy template during new project wizard instead creates a single-tabbed default alloy project. *This is a regression* h5. Steps to reproduce: 1) Create a new ""mobile app"" project in Studio 2) Select ""Alloy"" and ""Two-tabbed Alloy Application"" 3) Click ""next"" and continue through wizard 4) Examine the project {{index.xml}} at app/views/index.xml h5. Result: The index shows that the default template was used to create the project h5. Expected Result: The two-tabbed template was used to create the project.",5,test +TISTUD-8020,"New android NDK ""r11"" is not detected by appc studio due to missing ""ndk-gdb""","h5.Steps to reproduce: 1. Download the new NDK from here : http://developer.android.com/ndk/downloads/index.html. 2. In studio preferences go to Studio/Android. 3. Set the NDK path to new NDK r11. h5.Actual Results: 1. Studio does not detect the NDK because it can't find ""ndk-gdb"" inside the root NDK folder. 2. Google has removed ""ndk-gdb"" in favour ""ndk-gdb.py"" which is mentioned in the release notes here: http://developer.android.com/ndk/downloads/index.html. h5.Expected Results: 1. Studio should detect the new NDK ""r11"".",5,test +TISTUD-8024,Studio: Debugger Error in iOS ,Hi When you have a watch list and run debugger it crashes it sometimes doesn't let you get to open the app at all. If you are in debug mode and add or remove break points it breaks If you hover over a var or function to see whats it store as a value it breaks. Please fix as soon as possible for next release. Thanks Teli ,8,test +TISTUD-8023,Don't allow to edit organization name in the Splash screen user login prompt ,"Don't allow to edit organization name in the Splash screen org selection prompt during the studio login process. *Steps:* 1. Logout out from studio/CLI 2. Restart the studio 3. Provide login credentials - user name and password 4. Prompt will appear to select the organization name from list of orgs 5. Here, user can edit orgname from the prompt dialog. *Actual: *Studio org selection prompt allowing to edit the org name *Expected:* Org selection combo should be read only - this also applicable \ for auth code selection dialog ",3,test +TISTUD-8025,Windows: Using Windows capabilities with a namespace in a tiapp.xml displays an error,"h5.Description When using the below in the tiapp.xml Studio will not accept it and throw the following error {{The prefix ""m3"" for element ""m3:Capability"" is not bound.}}. {code} {code} *Workaround* Based off TIMOB-20231 the SDK will automatically add these prefixes for you so the workaround is to remove the namespace. However as our [documentation|http://docs.appcelerator.com/platform/latest/#!/guide/tiapp.xml_and_timodule.xml_Reference-section-29004921_tiapp.xmlandtimodule.xmlReference-UserInformationCapability] refers to type of usage we should accept it in Studio. h5.Steps to reproduce 1. Open a tiapp.xml from a project in Studio 2. Click the tiapp.xml tab to open the editor 3. Add the below {code} {code} h5.Actual result Studio will display an error and stop the user from building h5.Expected result The input should be accepted",5,test +TISTUD-8026,Studio can't deal with Genymotion 2.6.0 or later,"Genymotion 2.6.0 changes the location of the player internally in the App Package. We fixed the CLI with TIMOB-20130, but it seems Studio needs a similar fix here: https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.android.ui/src/com/appcelerator/titanium/android/ui/preferences/GenymotionInstallPathFieldEditor.java#L170-L201 But ideally, Studio should just rely on the CLI and not duplicate this logic. Reported on Stack Overflow: http://stackoverflow.com/questions/36136178/an-internal-error-occurred-during-syncing-to-cli-java-lang-nullpointerexc",5,test +TISTUD-8027,Android NDK r11b had moved the NDK-Build file on Windows,Android NDK R11B had moved the NDK-Build file on Windows. *Steps to reproduce:* # Download Android ndk-r11b. # On studio navigate to Window > Preferences > Studio > Platform > Android. # Select android ndk-r11b as the ndk home directory. *Actual :* A problem is detected with the ndk. *Expected:* There are no errors as seen in ndk-r10c.,1,test +TISTUD-8447,Windows: Studio needs to specify the Windows SDK to be used when building to a Windows 10 emulator,"h5.Description When building to a Windows 10 Mobile emulator using the following command {{appc run -p windows -T wp-emulator -C 10-0-6}} currently this will error out with the below until TIMOB-20571 is done as the CLI will use the 8.1 SDKs by default {code} [ERROR] Invalid ""--device-id"" value ""10-0-6"" For help, run: titanium.js help build {code} When building to the a Windows 10 Mobile emulator Studio should also add {{--wp-sdk 10.0}} otherwise the build will fail h5.Steps to reproduce 1. Build to a Windows 10 Emulator using Studio h5.Actual result The build will fail with the below {code} [ERROR] Invalid ""--device-id"" value ""10-0-6"" For help, run: titanium.js help build {code} h5.Expected result The build should not fail",5,test +TISTUD-8448,Integrate App Designer into Appcelerator Studio,* App designer repository and plugins * App Designer plugin is built and published automatically to a certain location. * Appcelerator Studio master pulls in a specified version as part of the packaging step * Appcelerator Studio adds any additional hooks as necessary ,8,test +TISTUD-8450,Appcelerator Studio (new install) stuck on splash screen (message: 'verifying').,"h6. Description Appcelerator studio is not responding. When I open the studio it always shows the message ""verifying"" and getting stuck on this page. *But we can,* - we can login via the CLI (appc login) - We can create application and run via the CLI *Tried this procedure* - we have completely removed node_modules, re-installed nodejs - we have removed .appcelerator, .titnaium folder. - We have reinstalled studio a few times and restarted the machine - We have tried also prior version of studio (v4.3.3, v4.10) - *But the initial error still remains.* *Please see this customer env, org, error and log info* 1. [appc info|http://i.imgur.com/XQTipKQ.jpg] 2. [appc whoami --full -o json|http://i.imgur.com/tNE96HP.png] 3. [Error|http://i.imgur.com/MDM3paG.png] 3. Studio Log {code} !SESSION 2016-04-05 12:48:50.365 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_60 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/mobile/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/mobile/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.net 1 0 2016-04-05 12:48:54.418 !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 {code}",5,test +TISTUD-8451,No console logs displayed when packaging Android & IOS modules with studio 4.6.0.201604041329,h5.Steps to reproduce: 1. Create an android & a IOS module in studio. 2. Package both the module for any of the 3 options. h5.Actual Results: 1. No console logs are seen in the console while the modules are being packaged. 2. This is probably a side effect of moving to use {{appc run}} to build the modules. h5.Expected Results: 1. Console logs should be seen while packaging Android & IOS module. ,3,test +TISTUD-8453,Studio 4.6.0.201604041329 tries to create the samples view but fails with error,"h5.Steps to reproduce: 1. Install studio version 4.6.0.201604041329, make sure you have a previous version of studio installed. (I installed 4.6.0 studio which replaced my 4.5.0 studio). 2. Open studio. h5.Actual Results: 1. After studio open up check the samples view. 2. It will show an error {{Could not create the view:}}. 3. As samples view is removed this might be due to some remnants from the previous studio. h5.Expected Results: 1. We should not see any error.",3,test +TISTUD-8454,Create App designer Jenkins job for building the artifacts,Create App designer build job in jenkins so that it can be used for building the required jars,5,test +TISTUD-8455,An option to set App designer Scratchpad XML editor as a default alloy view editor,"Provide an option to set App designer Scratchpad XML editor as a default alloy view editor. Currently to open an alloy view in the Scratchpad editor, here is the flow: # Right click on the alloy view file # Select ""Open With"" # Select ""Scratchpad XML Editor"" option from the menu. For every file, the user to has to do the same. Instead, provide an option from studio preferences to set App designer scratchpad editor as a default editor for all alloy view files. ",5,test +TISTUD-8457,App designer as part of Studio Installers and 4.6.0 update,"Below scenarios has to be addressed: # Appcelerator Studio 4.6.0 mac and windows installers should also install App designer along with it. # When a user upgrades the Studio 4.5.0 or lower to 4.6.0 Studio, It should also upgrade App designer along with the studio.",5,test +TISTUD-8458,Ran in to a NPE while trying to run Studio,"Here's a bunch of stack traces from my session this morning: {code} !STACK 0 Unexpected character (() at position 0. org.json.simple.parser.Yylex.yylex(Yylex.java:611) org.json.simple.parser.JSONParser.nextToken(JSONParser.java:270) org.json.simple.parser.JSONParser.parse(JSONParser.java:119) org.json.simple.parser.JSONParser.parse(JSONParser.java:82) org.json.simple.parser.JSONParser.parse(JSONParser.java:76) com.appcelerator.titanium.android.core.AndroidSDKLocator.loadTiInfo(AndroidSDKLocator.java:848) com.appcelerator.titanium.android.core.AndroidSDKLocator.updateTiInfo(AndroidSDKLocator.java:226) com.appcelerator.titanium.android.core.AndroidSDKLocator.access$0(AndroidSDKLocator.java:224) com.appcelerator.titanium.android.core.AndroidSDKLocator$1.run(AndroidSDKLocator.java:244) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.jobs 4 2 2016-04-11 10:06:43.547 !MESSAGE An internal error occurred during: ""Configuring SDK"". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.ios.ui.configuration.IOSSDKConfigurer.doConfigure(IOSSDKConfigurer.java:108) com.appcelerator.titanium.ui.mobile.BaseMobilePlatformConfigurer.configure(BaseMobilePlatformConfigurer.java:44) com.appcelerator.titanium.ui.mobile.PlatformsInstallManager$3.run(PlatformsInstallManager.java:171) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.jobs 2 2 2016-04-11 10:06:55.243 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.appcelerator.titanium.android.core.AndroidSDKLocator$1 !SESSION 2016-04-11 10:07:53.414 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_25 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/rickblalock/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/rickblalock/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.net 1 0 2016-04-11 10:07:57.674 !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 com.appcelerator.titanium.rcp 4 0 2016-04-11 10:08:01.493 !MESSAGE (Build 4.5.0.1446607552) [ERROR] Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@39e32ce2; line: 1802, column: 1559] !STACK 0 com.fasterxml.jackson.core.JsonParseException: Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@39e32ce2; line: 1802, column: 1559] com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1486) com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:518) com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:455) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString2(ReaderBasedJsonParser.java:1598) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString(ReaderBasedJsonParser.java:1585) com.fasterxml.jackson.core.json.ReaderBasedJsonParser.getText(ReaderBasedJsonParser.java:233) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:230) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:62) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:14) com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3560) com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2134) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.verifyAppcWhoami(TitaniumSplashHandler.java:1238) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.access$4(TitaniumSplashHandler.java:1215) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler$3.run(TitaniumSplashHandler.java:303) !ENTRY com.appcelerator.titanium.rcp 4 0 2016-04-11 10:08:27.312 !MESSAGE (Build 4.5.0.1446607552) [ERROR] Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@277c8784; line: 1802, column: 1559] !STACK 0 com.fasterxml.jackson.core.JsonParseException: Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@277c8784; line: 1802, column: 1559] com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1486) com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:518) com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:455) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString2(ReaderBasedJsonParser.java:1598) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString(ReaderBasedJsonParser.java:1585) com.fasterxml.jackson.core.json.ReaderBasedJsonParser.getText(ReaderBasedJsonParser.java:233) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:230) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:62) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:14) com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3560) com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2134) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.verifyAppcWhoami(TitaniumSplashHandler.java:1238) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.rebuild(TitaniumSplashHandler.java:1252) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler.access$5(TitaniumSplashHandler.java:1242) com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler$3.run(TitaniumSplashHandler.java:311) !ENTRY com.aptana.scripting 4 0 2016-04-11 10:08:28.600 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Failed to load bundle /Applications/Appcelerator Studio/plugins/com.appcelerator.titanium.core_3.1.2.1455193238/bundles/titanium_mobile.ruble !STACK 0 Can't construct a java object for !ruby/object:Ruble::Bundle; exception=Invalid tag: !ruby/object:Ruble::Bundle in """", line 1, column 5: --- !ruby/object:Ruble::Bundle ^ org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:325) 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:54) Caused by: org.yaml.snakeyaml.error.YAMLException: Invalid tag: !ruby/object:Ruble::Bundle org.yaml.snakeyaml.nodes.Tag.getClassName(Tag.java:108) org.yaml.snakeyaml.constructor.Constructor.getClassForNode(Constructor.java:620) org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.getConstructor(Constructor.java:313) org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:323) ... 9 more !ENTRY com.aptana.js.debug.core 4 0 2016-04-11 10:08:31.586 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Reading {0} fails !STACK 0 java.io.FileNotFoundException: /Users/rickblalock/Library/Application Support/Firefox/Profiles/vq9c71nj.default/prefs.js (No such file or directory) java.io.FileInputStream.open(Native Method) java.io.FileInputStream.(FileInputStream.java:138) com.aptana.js.debug.core.internal.browsers.FirebugUtil.registerEditor(FirebugUtil.java:67) com.aptana.js.debug.ui.JSDebugUIPlugin.registerAsFirebugEditor(JSDebugUIPlugin.java:170) com.aptana.js.debug.ui.JSDebugUIPlugin.start(JSDebugUIPlugin.java:106) org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) java.security.AccessController.doPrivileged(Native Method) org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721) org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936) org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319) org.eclipse.osgi.container.Module.doStart(Module.java:571) org.eclipse.osgi.container.Module.start(Module.java:439) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454) org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531) org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:320) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:395) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) java.lang.ClassLoader.loadClass(ClassLoader.java:357) org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:568) org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:294) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:289) org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition$1.run(LightweightDecoratorDefinition.java:125) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.runtime.Platform.run(Platform.java:867) org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.internalGetDecorator(LightweightDecoratorDefinition.java:120) org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:255) org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:83) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:367) org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:349) org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:372) org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:332) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY com.appcelerator.titanium.core 4 0 2016-04-11 10:08:34.548 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Location to be watched doesn't exist: /Library/Application Support/Titanium/modules !ENTRY com.appcelerator.titanium.core 4 0 2016-04-11 10:08:43.311 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@47b0b491; line: 1802, column: 1559] !STACK 1 org.eclipse.core.runtime.CoreException: Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@47b0b491; line: 1802, column: 1559] com.appcelerator.titanium.core.user.TitaniumUser.doGetOrganizations(TitaniumUser.java:392) com.appcelerator.titanium.core.user.TitaniumUser.getOrganizations(TitaniumUser.java:294) com.appcelerator.titanium.core.user.TitaniumUser.getOrganizationById(TitaniumUser.java:419) com.appcelerator.titanium360.internal.ui.launch.DeveloperAccountListener.isDeveloperAccount(DeveloperAccountListener.java:55) com.appcelerator.titanium360.internal.ui.launch.DeveloperAccountListener.loggedIn(DeveloperAccountListener.java:25) com.appcelerator.titanium.core.user.TitaniumUserManager.addUserListener(TitaniumUserManager.java:628) com.appcelerator.titanium360.ui.Titanium360UIPlugin$1.run(Titanium360UIPlugin.java:65) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@47b0b491; line: 1802, column: 1559] com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1486) com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:518) com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:455) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString2(ReaderBasedJsonParser.java:1598) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString(ReaderBasedJsonParser.java:1585) com.fasterxml.jackson.core.json.ReaderBasedJsonParser.getText(ReaderBasedJsonParser.java:233) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:230) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:62) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:14) com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3560) com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2134) com.appcelerator.titanium.core.user.TitaniumUser.doGetOrganizations(TitaniumUser.java:385) ... 7 more !SUBENTRY 1 com.appcelerator.titanium.core 4 0 2016-04-11 10:08:43.312 !MESSAGE Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@47b0b491; line: 1802, column: 1559] !STACK 0 com.fasterxml.jackson.core.JsonParseException: Unexpected end-of-input: was expecting closing quote for a string value at [Source: java.io.StringReader@47b0b491; line: 1802, column: 1559] com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1486) com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:518) com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:455) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString2(ReaderBasedJsonParser.java:1598) com.fasterxml.jackson.core.json.ReaderBasedJsonParser._finishString(ReaderBasedJsonParser.java:1585) com.fasterxml.jackson.core.json.ReaderBasedJsonParser.getText(ReaderBasedJsonParser.java:233) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:230) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:62) com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:14) com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3560) com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2134) com.appcelerator.titanium.core.user.TitaniumUser.doGetOrganizations(TitaniumUser.java:385) com.appcelerator.titanium.core.user.TitaniumUser.getOrganizations(TitaniumUser.java:294) com.appcelerator.titanium.core.user.TitaniumUser.getOrganizationById(TitaniumUser.java:419) com.appcelerator.titanium360.internal.ui.launch.DeveloperAccountListener.isDeveloperAccount(DeveloperAccountListener.java:55) com.appcelerator.titanium360.internal.ui.launch.DeveloperAccountListener.loggedIn(DeveloperAccountListener.java:25) com.appcelerator.titanium.core.user.TitaniumUserManager.addUserListener(TitaniumUserManager.java:628) com.appcelerator.titanium360.ui.Titanium360UIPlugin$1.run(Titanium360UIPlugin.java:65) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY com.aptana.js.core 4 0 2016-04-11 10:09:09.995 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Failed to determine installed version of package 'appcelerator': null !ENTRY com.appcelerator.titanium.alloy.ui 4 0 2016-04-11 10:09:10.174 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Failed to add Alloy project templates !STACK 1 org.eclipse.core.runtime.CoreException: Cannot find expected binary at /Users/rickblalock/.appcelerator/install/5.2.2/package/node_modules/appc-cli-titanium/node_modules/alloy/bin/alloy. This likely means the install package at /Users/rickblalock/.appcelerator/install/5.2.2/package is invalid for version 5.2.2 [com.appcelerator.install.binary.missing] com.appcelerator.titanium.alloy.internal.core.AlloyManager.getElementsOfType(AlloyManager.java:291) com.appcelerator.titanium.alloy.internal.core.AlloyManager.getTemplates(AlloyManager.java:221) com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.addAlloyTemplates(AlloyTemplateInstaller.java:68) com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:102) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.core 4 1 2016-04-11 10:09:10.174 !MESSAGE Cannot find expected binary at /Users/rickblalock/.appcelerator/install/5.2.2/package/node_modules/appc-cli-titanium/node_modules/alloy/bin/alloy. This likely means the install package at /Users/rickblalock/.appcelerator/install/5.2.2/package is invalid for version 5.2.2 [com.appcelerator.install.binary.missing] !ENTRY com.appcelerator.titanium.alloy.ui 4 0 2016-04-11 10:09:10.349 !MESSAGE (Build 4.5.0.201602170831) [ERROR] Failed to add Alloy project templates !STACK 1 org.eclipse.core.runtime.CoreException: Cannot find expected binary at /Users/rickblalock/.appcelerator/install/5.2.2/package/node_modules/...",3,test +TISTUD-8459,Windows: Remove Windows SDK Home field in preferences,h5.Description Currently Studio has a option to add the path to the Windows SDK location in Preferences->Studio->Platforms->Windows this should be removed for the following reasons # Due to Windows 8.1 and Windows 10 development being supported there are multiple paths for the SDKs and it is not like Android where one location holds mutliple versions of the SDK # The CLI automatically detects these locations through the registry keys # It is confusing for a user to try and set this path and Studio inform them that the detection failed when this is dealt with by the CLI ,3,test +TISTUD-8460,Default Android SDK downloaded by configuration is too old and not supported by Titanium 5.2.2,"When using Studio to download the Android SDK, its downloading 5.0.0 which is no longer supported by Titanium SDK 5.2.2. We should be downloading the latest version of Android SDK by default.",3,test +TISTUD-8461,Replace App designer XML editor by Alloy view editor,"1. Open an alloy view with App designer 'Scratchpad editor' 2. Go to XML section(2nd tab) of the editor 3. Hit 'Ctrl+Space' to see intellisense proposals based on the context 4. Scratchpad XML editor is not showing any intellisense proposals I believe Scratchpad XML editor should exactly work like standard Alloy View XML editor so that users needn't switch between Alloy view editor and Scratchpad editor To do this, studio has to expose Alloy view editor functionality and packages to the VisualUI plugin ",5,test +TISTUD-8462,Sending Analytics Ping error,When launching studio sending analytics ping error appears *Steps to reproduce:* # Use the environment above # Launch studio *Actual :* See image below *Expected:* No error appears ,5,test +TISTUD-8464,"xml views files are in web format, cannot open with studio","h1. Description In an Alloy mobile project, .xml view files can now only be opened in web format, which can't be edited, the right click popup menu is also completely unresponsive, it was found when trying to ""Open With >"". This issue does not occur with .js files within the same project. This issue is confirmed with two systems. h1. Steps to Reproduce 1. Use Appc Studio 4.6.0.201604081249 2. Create an Alloy Project. 3. Navigate to app > views > index.xml 4. Double-click file to Open. 5. Right click, hover over any expandable items in the popup menu. h1. Expected Result File should open in correct format, in Studio. popup menu should show expandable items. h1. Actual Result File is opened in webpage format, outside of Studio. popup menu does not show expandable items.",5,test +TISTUD-8465,Tiapp now opens with the XML editor by default,The Tiapp.xml file has been set by default to now open with the XML Editor instead of the Tiapp Editor. *Steps to reproduce:* # Open or create a new application with the studio specified above. # open the Tiapp.xml file. *Actual :* It is opened with the XML Editor. *Expected:* It is opened by default with the Tiapp Editor. ,3,test +TISTUD-8466,App designer in full screen mode - Showing Properties and Elements on the right side of designer,"App designer in full screen mode - Showing Properties and Elements on the left side of the designer Please find the attached screenshot on the new layout. Will show Properties, Elements and Console on the left side of the designer. !AppDesigner_fullview_layout.png|thumbnail! ",5,test +TISTUD-8467,Studio: Ability to set Windows SDK used to package app,"h5.Description We need to be able to allow a user to set the Windows SDK used to package a Windows Platform app, currently the user is unable to set this in Studio and by default the app will be packaged with 8.1 {code}[TRACE] :  ExpandSDKReferences: Enumerating SDK Reference ""Microsoft.VCLibs, Version=12.0"" from ""C:\Program Files (x86)\Microsoft SDKs\WindowsPhoneApp\v8.1\ExtensionSDKs\Microsoft.VCLibs\12.0\"".{code} h5.Steps to reproduce 1. On a Windows machine select Package->Windows->Windows Phone h5.Actual result You are only able to select the output location, 8.1 SDK is used h5.Expected result User should be able to select a Windows SDK they would like to package an app with",5,test +TISTUD-8469,Studio: Unable to update studio due to dependency issues. ,"When I try to update studio http://studio-jenkins.appcelerator.org/job/appcelerator-rcp-development/lastSuccessfulBuild/artifact/dist/ from version GA to the current jenkins build 4.6.0.201604180847 an error is thrown and the update is unsuccessful. *Steps to reproduce:* # Downloaded the GA of studio # Added AppDesigner from labs using the url: https://preview.appcelerator.com/appcelerator/labs/appdesigner/update/beta/ # Once AppDesigner has been installed I update studio using the development branch: http://studio-jenkins.appcelerator.org/job/appcelerator-rcp-development/lastSuccessfulBuild/artifact/dist/ # This is when I see the error in the image. *Actual :* See image below {code:java} Your original request has been modified. ""Appcelerator Designer"" is already installed, so an update will be performed instead. Cannot complete the install because of a conflicting dependency. Software being installed: Appcelerator Designer 1.0.6 (VisualUIFeature.feature.group 1.0.6) Software currently installed: Appcelerator Studio 4.6.0.201604130502-13042016050308 (com.appcelerator.titanium.rcp.product 4.6.0.201604130502-13042016050308) Only one of the following can be installed at once: Appcelerator Designer 1.0.5.9 (VisualUIFeature.feature.jar 1.0.5.9) Appcelerator Designer 1.0.6 (VisualUIFeature.feature.jar 1.0.6) Cannot satisfy dependency: From: Appcelerator Designer 1.0.5.9 (VisualUIFeature.feature.group 1.0.5.9) To: VisualUIFeature.feature.jar [1.0.5.9] Cannot satisfy dependency: From: Appcelerator Designer 1.0.6 (VisualUIFeature.feature.group 1.0.6) To: VisualUIFeature.feature.jar [1.0.6] Cannot satisfy dependency: From: Appcelerator Studio 4.6.0.201604130502-867nFNNFH1kUeGD5II1bz-HOKIz0 (com.appcelerator.titanium.feature.360.rcp.feature.group 4.6.0.201604130502-867nFNNFH1kUeGD5II1bz-HOKIz0) To: VisualUIFeature.feature.group [1.0.5.9] Cannot satisfy dependency: From: Appcelerator Studio 4.6.0.201604130502-13042016050308 (com.appcelerator.titanium.rcp.product 4.6.0.201604130502-13042016050308) To: com.appcelerator.titanium.feature.360.rcp.feature.group [4.6.0.201604130502-867nFNNFH1kUeGD5II1bz-HOKIz0] {code} *Expected:* Studio is updated.",5,test +TISTUD-8471,"Android: Creating project with just android 6.0 platform installed studio shows a message ""Android development requires [2.3.3,6.0)""","h5.Steps to reproduce: 1. Make sure you have just android 6.0 platform SDK installed.(You can do it using Android SDK manager). 2. Now in studio try to create a new mobile project. 3. On the mobile app project window look at the android deployment targets. h5.Actual Results: 1. You will see a info icon next to android platform & hovering the mouse pointer over it shows message: {{Android development requires [2.3.3,6.0),but you have 6.0, 6.0, 6.0, 6.0, 6.0, 6.0}} 2. Attaching screenshot for reference. h5.Expected Results: 1. You should not see any message & should support project creation etc with just Android 6.0 installed. ",3,test +TISTUD-8472,"Android: Building the app for genymotion emulator gives alert ""The launch requires 2.3.3 SDK or higher""",h5.Steps to reproduce: 1. Create an android app in appcelerator studio. 2. Run it on genymotion emulator. h5.Actual Results: 1. As soon as you click run in studio you will get an alert: {{The launch requires Android 2.3.3 SDK or above. Would you like to update the launch configuration to the required version?}} 2. I already have Android 2.3.3 installed but still see this alert. *NOTE:* This is only seen for the first time a newly created app is run on genymotion emulator. h5.Expected Results: 1. There should be no such alert. ,5,test +TISTUD-8473,Unable to create android module in studio.,"I am unable to select the NDK folder within studio, which means I cannot create a module *Steps to reproduce:* # Download the r11c NDK # In studio navigate to Window > Preferences> Studio > Platforms > Android # Select the path for the NDK *Actual :* An error is returned (see image below) *Expected:* No error is returned and I can create an android module from studio.",5,test +TISTUD-8474,Enable app preview options if appc core is bundled with an app preview hook,"Studio should enable app preview configuration options if appc core is bundled with an app preview hook With CLI-664, app preview hook will be installed in {{/package/hooks/appc-app-preview/}} folder. If it's installed, studio should enable Android app preview and ios app preview options during the build. ",5,test +TISTUD-8475,Unable to build to Windows device,"This is a *regression* from SDK {{5.3.0.v20160421080259}} *Steps to reproduce:* # Create an classic/alloy application # Specify SDK {{5.3.0.v20160428072113}} in the tiapp.xml # Run to Windows 10/8.1 device. *Actual through studio:* {code:java} [ERROR] : Invalid ""--device-id"" value ""0"" For help, run: titanium.js help build {code} *Expected:* The application is built like in the CLI.",5,test +TISTUD-8476,Run targets should show the Windows phone device name rather than udid,"Studio displays Windows phone devices under run targets as their {{UDID}}. It should instead display the device name. This issue is seen only with Windows 10.0 & 8.1 phone devices, and *NOT* Emulators. h2. Steps to Reproduce: 1. Launch Studio (4.6.0.201604290815) 2. Create a new mobile application. 3. Select ""Run"" as the deploy type. 4. Click on Run Targets drop down menu. h2. Actual Result The Windows device is displayed as its UDID. h2. Expected Result The Windows device should be displayed as its name. (i.e: ""Lumia 930 (RM-1045)"")",3,test +TISTUD-8477,Studio should support Github two factor authentication,"Github has introduced two factor authentication, and when turned on for a use Studio is not able to accept the the necessary code for submission. In the case that validation fails as a result of Two Factor Authentication, an additional field should be displayed to accommodate either a 'One Time Password' or a confirmation code. See the below link for details https://developer.github.com/v3/auth/#working-with-two-factor-authentication ",3,test +TISTUD-8481,'App beta' is studio named wrongly as 'App Preview',"h5.Steps to reproduce: 1. Launch studio version mentioned in the environment. 2. Create a project for all platforms. 3. From studio try to package the app for android for app beta & notice what naming studio has for this option. 4. At the end of packaging process before the app is uploaded check the naming there. h5.Actual Results: 1. The current naming is ""App Preview"". 2. In the console logs we see"" {{[INFO] : Uploading app to App Preview}} NOTE: Attached screenshots for reference. h5.Expected Results: 1. The naming should not be ""App Preview"".",1,test +TISTUD-8483,Cannot build for Android,"Studio is unable to build for android. I get the following error: Failed to run dexer: [ERROR] : [ERROR] : Exception in thread ""main"" java.lang.UnsupportedClassVersionError: com/android/dx/command/Main : Unsupported major.minor version 52.0",5,test +TISTUD-8490,App designer: index.xml opened with App designer throws nullpointer exception on closing if studio is installed from installer,"h5.Steps to reproduce: 1. Install appc studio 4.6.0.201605121040 from installer. 2. Launch studio. 3. Create an alloy app. 4. Try top open the index.xml file of the app in app designer. h5.Actual Results: 1. We get an empty tab with no content. 2. Closing the tab gives {{multiple errors have accurred}} dialog with null pointer error. {code} !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-12 15:28:27.045 !MESSAGE Unable to create class 'org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor' from bundle '324' !STACK 0 org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: com/appcelerator/titanium/ui/AppDesignerLaunchValidator org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:62) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888) org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869) org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120) org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337) org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258) org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73) org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55) org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:983) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:766) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:737) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:731) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:715) org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1246) org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:69) org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187) org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) org.eclipse.swt.widgets.Display.syncExec(Display.java:4732) org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:218) org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) 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:81) org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59) 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:488) org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:454) org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:705) org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:392) org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1145) org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3210) org.eclipse.ui.internal.WorkbenchPage.access$23(WorkbenchPage.java:3125) org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3107) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3102) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3066) org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:338) org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:180) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4199) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4042) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3669) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:497) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) org.eclipse.equinox.launcher.Main.run(Main.java:1465) Caused by: java.lang.NoClassDefFoundError: com/appcelerator/titanium/ui/AppDesignerLaunchValidator visualui.editors.ScratchPadEditor.init(ScratchPadEditor.java:239) org.eclipse.ui.internal.EditorReference.initialize(EditorReference.java:390) org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:305) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:497) org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) ... 79 more {code} 2. Tried deleting my {{.appcelerator}} folder & switching to a new workspace, but the issue persists. h5.Expected Results: 1. The index.xml should open as expected in app designer. ",5,test +TISTUD-8491,Android:Reconnect to the debug session after the app is restarted,"If a user attempts to debug a mobile app, then app initiates a debug connections during its startup. As Studio receives the debug connection request, it initiates the socket connection and receives the debug data. However, if the app is accidentally crashed/terminated on device or simulator, then the user has to re-launch the debug session (which will re-build the app and deploy onto device again). If the app is restarted on the device (or simulator), then it attempts to make a debug connection to Studio, but Studio is no more listening to the debug connection requests. Studio should listen to the debug connection request even though the app is terminated/crashed, so that the user does not need to re-launch debugging the app again.",8,test +TISTUD-8492,Enable Hyperloop,"Similar to ""Enable Test Services"", we need another option to ""Enable Hyperloop"". See related ticket for more information. ",8,test +TISTUD-8495,Spelling error on adhoc deployment wizard,"h5. Description: There is a spelling error in the iOS adhoc packaging wizard. It says ""Upload App to App Preivew"" It should say ""Upload App to App Preview"" h5. Steps to reproduce: 1) Launch studio 2) Open iOS-enabled project 3) Set to ""package"" and ""iOS adhoc/enterprise"" 4) Click the go button 5) Examine the wizard contents h5. Result: Spelling error h5. Expected Result: No spelling error",1,test +TISTUD-8506,Cannot unpublish an Arrow app,"*Details:* From Studio, cannot unpublish Arrow app. *Notes:* * This is not a regression. * To workaround this issue, you can unpublish from terminal/cmd: {{appc unpublish}} *Steps to reproduce:* # In Studio, create an Arrow project # Package the Arrow app and wait for the Arrow app to be published # Right-click on the Arrow project and go to Arrow > Unpublish Arrow Service *Actual:* Arrow project is not unpublished; run {{appc cloud list }}. And, here is the Studio logs: {code} !ENTRY com.aptana.core 1 0 2016-05-23 15:53:06.356 !MESSAGE (Build 4.6.0.201605201934) [INFO] com.aptana.core/debug/shell Running process: Process: ""/usr/local/bin/appcelerator"" ""unpublish"" ""monkeyStudArr"" ""--no-colors"" ""--no-progress-bars"" ""--no-prompt"" ""--no-banner"" ""--prompt-type"" ""socket-bundle"" ""--prompt-port"" ""58655"" Working directory: /Users/wluu/Documents/Appcelerator_Studio_Workspace/monkeyStudArr Environment: {ANALYTICS_SOURCE=studio, ANDROID_NDK=/Applications/android-ndk-r11c, ANDROID_SDK=/Applications/android-sdk-macosx, APTANA_VERSION=4.6.0.1455770180, Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.t9xPCRb55D/Render, HOME=/Users/wluu, JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_65.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=wluu, PATH=/Library/Java/JavaVirtualMachines/jdk1.7.0_65.jdk/Contents/Home/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Applications/android-sdk-macosx/tools:/Applications/android-sdk-macosx/platform-tools:/Applications/VMware Fusion.app/Contents/Library/:/Users/wluu/mongodb-osx-x86_64-3.2.3/bin:/usr/local/mysql-5.6.25-osx10.8-x86_64/bin:/Applications/apache-ant-1.9.6/bin:/Users/wluu/Downloads/, PWD=/Users/wluu/Documents/Appcelerator_Studio_Workspace/monkeyStudArr, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.v7TFcIUuWs/Listeners, STUDIO_NAME=Appcelerator Studio, STUDIO_PRODUCT_ID=com.appcelerator.titanium.rcp.product, STUDIO_VERSION=4.6.0.201605201934, TMPDIR=/var/folders/g9/bw6h6yr11t79h_mw4q1r87pm0000gp/T/, USER=wluu, XPC_FLAGS=0x0, XPC_SERVICE_NAME=com.appcelerator.appcelerator-studio.256032, __CF_USER_TEXT_ENCODING=0x1F6:0x0:0x0} !ENTRY com.aptana.core 1 0 2016-05-23 15:53:07.866 !MESSAGE (Build 4.6.0.201605201934) [INFO] com.aptana.core/debug/shell/output Process Output: Unpublishing the application from the Appcelerator Cloud. One moment... 2016-05-23T22:53:07.855Z | ERROR | Invalid URI ""null//null:443monkeyStudArr/login"" {code} *Expected:* Should be able to unpublish Arrow app from Studio.",3,test +TISTUD-8509,Set Node 4.X as minimum supported version,Update the minimum supported version of Node to 4.x. Make sure to check for and update any version checks in the code as well as updating the package.json file.,5,test +TISTUD-8516,"Avoid error notification for ""Unable to retrieve the icon at null for sample Apple WatchOS2""",*Steps:* # Launch Appcelerator Studio # Open dashboard page *Actual:* # Studio error reporting service will prompt a notification dialog to report the error on {{Unable to retrieve the icon at null for sample Apple WatchOS2}} *Expected* We shouldn't get an error notification dialog. ------ STATUS ------ pluginId com.aptana.samples pluginVersion 3.0.0.qualifier code 0 severity 4 message (Build 4.7.0.qualifier) [ERROR] Unable to retrieve the icon at null for sample Apple WatchOS2 fingerprint 543e547c stacktrace {code:java} Exception:org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting at com.aptana.core.logging.IdeLog.log(IdeLog.java:558) at com.aptana.core.logging.IdeLog.log(IdeLog.java:593) at com.aptana.core.logging.IdeLog.logError(IdeLog.java:306) at com.aptana.core.logging.IdeLog.logError(IdeLog.java:280) at com.aptana.core.logging.IdeLog.logError(IdeLog.java:258) at com.aptana.samples.ui.portal.actionController.SamplesActionController.addSample(SamplesActionController.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:103) at com.aptana.portal.ui.dispatch.ActionControllerProxy.invokeAction(ActionControllerProxy.java:77) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:157) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:126) at com.aptana.portal.ui.internal.BrowserWrapper$1.function(BrowserWrapper.java:43) at org.eclipse.swt.browser.WebKit.callJava(WebKit.java:1779) at org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:407) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool(OS.java:-2) at org.eclipse.swt.internal.cocoa.NSRunLoop.runMode(NSRunLoop.java:42) at org.eclipse.swt.widgets.Display.sleep(Display.java:4691) at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopIdle(WorkbenchAdvisor.java:368) at com.appcelerator.titanium.rcp.IDEWorkbenchAdvisor.eventLoopIdle(IDEWorkbenchAdvisor.java:936) at org.eclipse.ui.internal.Workbench$3.eventLoopIdle(Workbench.java:498) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1155) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {code} ------ REPORT ------ name Kondal Kolipaka email kkolipaka@appcelerator.com comment productVersion 4.7.0.qualifier productName Appcelerator Studio javaRuntimeVersion 1.7.0_80-b15 osgiWs cocoa osgiOs MacOSX osgiOsVersion 10.11.1 osgiArch x86_64,2,test +TISTUD-8518,Always run CLI commands with trace level,The info-level log output is insufficient for debugging issues with Titanium builds. Always run CLI commands with trace level output and then filter the output on-the-fly in the console window. This way the log output always has the trace level log output that is useful.,8,test +TISTUD-8519,Support Windows module build from studio,https://wiki.appcelerator.org/display/guides2/Windows+Module+Quick+Start ,8,test +TISTUD-8523,Error reporting: Location to be watched doesn't exist,The following data will be sent: ------ STATUS ------ pluginId com.appcelerator.titanium.core pluginVersion 3.1.2.qualifier code 0 severity 4 message (Build 4.7.0.qualifier) [ERROR] Location to be watched doesn't exist: /Library/Application Support/Titanium/mobilesdk/osx fingerprint 46fef5a3 stacktrace Exception:org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting at com.aptana.core.logging.IdeLog.log(IdeLog.java:558) at com.aptana.core.logging.IdeLog.log(IdeLog.java:593) at com.aptana.core.logging.IdeLog.logError(IdeLog.java:306) at com.aptana.core.logging.IdeLog.logError(IdeLog.java:280) at com.aptana.core.logging.IdeLog.logError(IdeLog.java:258) at com.appcelerator.titanium.core.mobile.SDKLocator.watchLocation(SDKLocator.java:283) at com.appcelerator.titanium.core.mobile.TitaniumMobileSDKLocator.initialize(TitaniumMobileSDKLocator.java:162) at com.appcelerator.titanium.core.mobile.SDKLocator.lazyInitialize(SDKLocator.java:237) at com.appcelerator.titanium.core.mobile.SDKLocator.getAvailable(SDKLocator.java:391) at com.appcelerator.titanium.core.mobile.SDKLocator.findVersion(SDKLocator.java:435) at com.appcelerator.titanium.core.mobile.SDKLocator.findVersion(SDKLocator.java:419) at com.appcelerator.titanium.core.mobile.TitaniumMobileSDKTools.getSDKEntity(TitaniumMobileSDKTools.java:68) at com.appcelerator.titanium.core.mobile.TitaniumMobileSDKTools.getProjectSDK(TitaniumMobileSDKTools.java:49) at com.appcelerator.titanium.mobileweb.core.internal.property.MobileWebPropertyTester.getProjectSDK(MobileWebPropertyTester.java:62) at com.appcelerator.titanium.mobileweb.core.internal.property.MobileWebPropertyTester.test(MobileWebPropertyTester.java:38) at org.eclipse.core.internal.expressions.Property.test(Property.java:58) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:189) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72) at org.eclipse.core.internal.expressions.ReferenceExpression.evaluate(ReferenceExpression.java:70) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256) at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166) at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96) at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188) at org.eclipse.ui.internal.menus.WorkbenchMenuService.populateContributionManager(WorkbenchMenuService.java:326) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:90) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:87) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:87) at org.eclipse.ui.internal.menus.SlaveMenuService.populateContributionManager(SlaveMenuService.java:81) at com.aptana.deploy.internal.ui.DeployPopupContributionItem.fill(DeployPopupContributionItem.java:43) at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:208) at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:780) at org.eclipse.jface.action.MenuManager.update(MenuManager.java:861) at org.eclipse.jface.action.MenuManager.update(MenuManager.java:721) at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:622) at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:423) at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:393) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:352) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:492) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:487) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:519) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4199) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471) at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:806) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(OS.java:-2) at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:278) at org.eclipse.swt.widgets.Display.runPopups(Display.java:4119) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3662) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) ------ REPORT ------ name Kondal Kolipaka email kkolipaka@appcelerator.com comment productVersion 4.7.0.qualifier productName Appcelerator Studio javaRuntimeVersion 1.7.0_80-b15 osgiWs cocoa osgiOs MacOSX osgiOsVersion 10.11.1 osgiArch x86_64 ,3,test +TISTUD-8524,Show Appcelerator Studio version number on startup splash screen,Add version number to Appcelerator studio startup splash screen so that users will know what version they are launching if they have multiple versions of studio.,5,test +TISTUD-8526,Android NDK Version not shown in the studio diagnostic log with android NDK11,*Reproducible Steps:* # Configure android NDK android-ndk-r11c or higher # Run studio Diagnostic Log Test # Verify Android NDK version in the generated log *Actual Result:* Android NDK Version: Unknown/Uninstalled No Android NDK info is shown due to {{RELEASE.TXT}} file is replaced with the {{source.properties}} in the latest android NDK 11 and higher. *Expected Result:* Diagnostic log should show Android NDK info *Here is the studio log.* {code:java} java.io.FileNotFoundException: /Users/kondalkolipaka/Downloads/android-ndk-r11c/RELEASE.TXT (No such file or directory) java.io.FileInputStream.open(Native Method) java.io.FileInputStream.(FileInputStream.java:146) com.appcelerator.titanium.android.internal.core.AndroidDiagnosticLog.getAndroidNDKVersion(AndroidDiagnosticLog.java:75) com.appcelerator.titanium.android.internal.core.AndroidDiagnosticLog.getLog(AndroidDiagnosticLog.java:51) com.aptana.core.internal.diagnostic.DiagnosticManager$LazyDiagnosticLog.getLog(DiagnosticManager.java:166) com.aptana.ui.commands.DiagnosticHandler.getLogContent(DiagnosticHandler.java:66) com.aptana.ui.commands.DiagnosticHandler$1.run(DiagnosticHandler.java:39) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code},3,test +TISTUD-8527,"Norton Security deems Appc Studio unsafe, and Symantec Endpoint Protection think the install is untrustworthy",Symantec quarantine antivirus/Norton software showing Appcelerator Studio as insecure file/threat while downloading the installers. This is happening on Windows 10 64bit system. Please find the screenshot. !antivirus_issue.png|thumbnail! !norton_issue.png|thumbnail!,5,test +TISTUD-8528,Git branch indicator does not properly update,"h3. Steps to Reproduce Create mutliple git branches of your project Make sure they are set upstream to origin switch git branches in terminal/with Git GUI Observe the git branch indicator next to project does not reflect Right click on the project, go to Team, and select Status IDE reports correct branch, still not reflected in branch name h3. Actual Result Git branch name next to project does not change h3. Expected Result Git project name is reflected ",3,test +TISTUD-8529,Update Hyperloop documentation link in the studio,"Need to update the Hyperloop documentation link in the Appcelerator Studio services section Please find the screenshot. !hyperloop.png|thumbnail! When user click on the Details link, will navigate to Hyperloop documentation. Currently, as Hyperloop documentation is not there, we are navigating to http://docs.appcelerator.com",2,test +TISTUD-8530,Windows tag support in timodule.xml,"{code:java} {code} Result: {{windows}} tag is shown as invalid content and error marker is shown on the timodule.xml file. Please find the screenshot below. !windows_tag.png|thumbnail! Expected: Need to support {{windows}} tag in the timodule.xml file ",3,test +TISTUD-8531, MobileWeb Platform is deprecated with Studio 4.7.0/CLI 5.4.0/SDK 5.4.0,"As MobileWeb Platform is deprecated with 4.7.0, show a warning message in # New mobile app project creation wizard, show that ""MobileWeb is deprecated"". # Tiapp.xml file deployment targets This also applicable for creating MobileWeb modules. ",3,test +TISTUD-8532,Turn off Dev Toolbox Console automatic opening on error,"Check this - https://jira.appcelerator.org/browse/TISTUD-7458 During the studio startup, dashboard throws some errors if it is unable to identify sdkInfo path immediately. Let's turn this off as most of the errors printed by Dev Toolbox are irrelevant and invalid - This will help us to quickly turnaround the user experience on studio startup. ",3,test +TISTUD-8533,Studio: Keep showing offline when behind the proxy,"Customer is facing following problem. Behind the proxy, they are able to login to studio, but once the studio lunched. It shows still offline. Like dashboard can't open, build process will stop because of offline. (attached screen shot about this and proxy setting) Can you please advise or any info we need for this problem? ",5,test +TISTUD-8535,Appcelerator studio can't update stuck at “checking for new Appcelerator Updates…”,"From so:http://stackoverflow.com/questions/38216206/appcelerator-studio-cant-update-stuck-at-checking-for-new-appcelerator-updates I'm using Appcelerator studio version 4.5.0 updated in 2016.4.30 But I can't update it recently, it will stuck at ""checking for new Appcelerator Updates..."" and I must close it and reopen it to use continually. There were some timeout errors. [ERROR] com.appcelerator.titanium.update.core/debug/sdk_update Error getting release lists from url 'f4df0833a1352ef193633d85356e6e80ffcdcdb7.cloudapp-enterprise.ap…;",5,test +TISTUD-8536,Support per-platform moduleAPIVersions,"Studio uses the moduleAPIVersion to filter the list of valid modules for a given SDK. With the recent update of V8, we need to bump the moduelAPIVersion for Android, but keep iOS at 2. So we need to support a per-platform moduleAPIVersion in the SDK's manifest.json (and not just a single global version).",5,test +TISTUD-8538,Publishing: Block field input until 'Use Existing' is selected by the user on Windows Phone packaging,"h5.Description When publishing an application for Windows Phone with Windows 10 SDK the user can input an existing certificate location and password to package their app with, these input fields should be locked until the user selects the {{Use Existing}} option similar to the {{Project Name}} field in the MobileWeb packaging options.",3,test +TISTUD-8540,Installation error while opening studio in the offline mode,"*To reproduce:* # Keep node version < 0.1.7 # Launch Appcelerator Studio # During the startup, studio will try to install node and ask for the system root password(mac iCloud password) # Since there is no network connection, studio will unable to verify system root password and after 3 failure attempts, studio will show an empty error message dialog as shown below. !InstallationError_networkissue.png|thumbnail! *Expected*: Studio shouldn't show the empty error dialog, show some error message why it was unable to install it.",3,test +TISTUD-8541,"NPE while checking for ""Install Appcelerator SDK"" from studio help menu",*To reproduce:* # Be in Offline mode # Launch Appcelerator studio # Go to Help Menu in the studio # Click on Install Appcelerator SDK # Select Install from update stream *Actual* NPE has thrown as shown below !SDK_update_error_NPE.png|thumbnail! *Expected:* Show that studio was unable to fetch SDK releases due to network issues. ,3,test +TISTUD-8542,Installing Arrow connectors from Appcelerator Studio,Appcelerator Studio should support installing arrow connectors To identify the list of connectors {code:java} $appc search connector list {code} To install a particular connector {code:java} $appc install connector/appc.azure {code},8,test \ No newline at end of file