id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
2,111 |
TISTUD-6674
|
07/01/2014 22:52:47
|
Content Assist: Documentation link in Content assist opens invalid URL
|
h5.Description Content-Assist has a link that will lead the developer to the documentation site. The link currently leads the user to: {code}http://127.0.0.1:58701/help/nftopic/com.aptana.documentation/html/reference/api/Titanium.UI.html?visibility=basic#Titanium.UI.createTabGroup{code} h5.Steps To Reproduce 1. Create a classic project in Studio 2. Click on the first Titanium.UI.createTabGroup() 3. 'Press F2 to focus', this will bring up a little icon underneath the Content-Assist window. 4. Click on the icon h5.Expected Result Should link the developer to the documentation site. h5.Actual Result Opens a blank page.
| 5 |
2,112 |
TISTUD-6677
|
07/02/2014 18:20:49
|
Windows: Additional folder created as "Appcelerator Studio 3.3.0" on running the installer on clean machine
|
On clean installing the Appcelerator studio through installer, it creates additional folder "C:\Users\Global\AppData\Roaming\Appcelerator Studio 3.3.0" which contains an empty "0D804B5" folder. The actual installation of the product is in "C:\Users\Global\AppData\Roaming\Appcelerator Studio"
| 5 |
2,113 |
TISTUD-6680
|
07/03/2014 10:02:16
|
Android: Platform Configuration Window does not show the latest Android updates
|
Steps followed 1. On a clean machine, when Studio is launched Platform Configuration Window is prompted. 2. In the Android Platform section click on Settings and observe the available versions displayed for configuration. Actual Result: The latest Android L(API 20 L,preview) and Android W (API 20) are not displayed in the Platform Configuration Window and only till Android 4.4.2 are available. Expected result: The latest available versions of Android should also be displayed on Platform Configuration Window for users to configure it. Please refer the attached screen shot for more clarification.
| 8 |
2,114 |
TISTUD-6681
|
07/03/2014 11:21:52
|
Android is not detected on Studio Dashboard if only Android L (5.0) is installed
|
Steps Followed: 1. Install only the latest Android L or W (API 20) and do not install any other Android version previous to this. Actual Result: 1. The installation completes successfully but Android is not detected on Studio Dashboard. 2. Android is detected in Studio >> Preferences>> Platform >> Android Configuration window and path is successfully detected. Also the default emulator gets created for API L 3. Projects can be successfully build and launched. Expected Result: Android should be successfully detected on Studio dashboard as it is detected from Preference window and also available for launching an app. Please observe the attached screen shot for more clarification
| 5 |
2,115 |
TISTUD-6685
|
07/04/2014 12:30:18
|
Studio: Studio does not recognize the previous Titanium installation directory after upgrading 3.2.3 to 3.3.0
|
After upgrading the 3.2.3 Studio with 3.3.0, studio is unable to recognize the previous (<=3.2.3) titanium installation directory C:\Users\Global\AppData\Roaming\Titanium. Steps to Reproduce: Upgrade Appcelerator Studio from 3.2.3 GA -> 3.3.0 1. Configured all the GA components (Studio, SDK, CLI, Alloy & CP) on the system. 2. Created a classic and alloy project. Everything is working fine. 3. Studio shows the default Titanium installation path - C:\Users\Global\AppData\Roaming\Titanium 4. Verified that the location (C:\Users\Global\AppData\Roaming\Titanium) contains three folders - mobilesdk, modules & plugins 5. Note that as per bug TISTUD-6337, the default Titanium path in 3.2.3 is C:\Users\Global\AppData\Roaming\Titanium and 3.3.0 is C:\ProgramData\Titanium 6. Now upgrade the Appcelerator Studio from 3.2.3 to 3.3.0. 7. Once the upgrade completes, studio asks to restart. Restarted the Studio. {color:red}*Actual Result:*{color} As soon as we get the Dashboard, Studio shows the Appcelerator Update dialog box which contains the SDK 3.2.3 GA and two more studio plugins {color:green}*Expected Result:*{color} Studio should recognize the existing titanium installation directory and should not prompt for Appcelerator update dialog box. Note: After upgrading the Studio with 3.3.0, the default Titanium path is C:\ProgramData\Titanium that's why studio is unable to recognize the previous (<=3.2.3) titanium installation directory C:\Users\Global\AppData\Roaming\Titanium.
| 5 |
2,116 |
TISTUD-6686
|
07/04/2014 14:44:11
|
Windows: The installer is not able to install GIT from our URL
|
h2. Problem When trying to install on Windows, Git is required but can't be downloaded by the installer, thus install fails. Git is actually installed and works from the command line. h2. Logs {code:lang=none} Detecting JDK Version Comparing version 1.7 to 1.7 results in 0 JDK Version detection complete - result = C:\Program Files (x86)\Java\jdk1.7.0_40 Detecting Git Version Git Version detection complete - result = No Git Found About to download Git from http://go.aptana.com/installer_git_windows Download result = Access Forbidden (403) {code} h4. Extra info The URL in the installer uses http://go.aptana.com/installer_git_windows that is redirect to: https://msysgit.googlecode.com/files/Git-1.8.4-preview20130916.exe that is showing a 403.
| 2 |
2,117 |
TISTUD-6689
|
07/07/2014 21:31:06
|
Support AndroidView in addition to View as child of AlertDialog
|
While the API name is AndroidView, Alloy expects child views of AlertDialog to be created with the View tag. It throws an error that Ti.UI.createAndroidView is not a valid method name if you use AndroidView. While it's okay to support View as a shorthand, we should also support AndroidView as a tag. Reference: http://developer.appcelerator.com/question/163125/cannot-getset-textfield-value-in-alloy#answer-275881 Test case attached with commented-out working code that uses View.
| 5 |
2,118 |
TISTUD-6691
|
07/08/2014 00:50:33
|
command/quick fix to extract a string to i18n files
|
We should allow a user to select a string and extract ti out to i18n XML files in their titanium projects, much like the Eclipse PDE support for extracting strings in Java files.
| 13 |
2,119 |
TISTUD-6692
|
07/08/2014 00:51:20
|
Add hyperlink detector to jump from i18n translation keys in Alloy View XML attributes to their definition in strings.xml files
|
We should be able to navigate the user from usage of a translation key/string to it's definition in an i18n file.
| 8 |
2,120 |
TISTUD-6693
|
07/08/2014 00:52:09
|
Add hyperlink detector to jump from string keys in i18n files to usage in view files
|
We should be able to navigate the user from definition of a translation key/string in an i18n file to it's usage(s) in alloy views and in JS code.
| 8 |
2,121 |
TISTUD-6694
|
07/08/2014 00:53:11
|
content assist to suggest strings inside L() calls in Alloy view XML from the available keys in i18n files
|
We should be able to offer up proposals for i18n strings (as the argument) inside L() and Ti.Locale.getString calls. https://wiki.appcelerator.org/display/guides2/Internationalization
| 8 |
2,122 |
TISTUD-6701
|
07/09/2014 15:50:38
|
Update content assist for <ActionBar> tag
|
Alloy has added the new <ActionBar> tag with ALOY-994. Studio's content assist should support this new tag. The tag is valid on Android only.
| 5 |
2,123 |
TISTUD-6702
|
07/09/2014 20:33:10
|
Allow updates from secure locations
|
In the near future we will have a need to store items coming through Studio's update system in secure locations, ones requiring some sort of authentication to download. Specifically this is planned for the Mobware (AMW) project. Ideally this will likely involve Studio querying for a list of updates, getting the listing, finding the URL for an update (all as usual so far), then hitting that URL with the user's Appcelerator login credentials through Studio's APIs in order to pull down the secured download. Same exact process, just passing credentials with the actual download request.
| 8 |
2,124 |
TISTUD-6706
|
07/11/2014 19:53:58
|
"Null" username when logging out Studio and cancel the process
|
Somehow my username became "Null" when I tried to log out and canceled the process. Please, check the screenshot. {code} !ENTRY com.appcelerator.titanium.ios.ui 4 0 2014-07-11 11:18:53.771 !MESSAGE No signed in user !STACK 1 org.eclipse.core.runtime.CoreException: No signed in user at com.appcelerator.titanium.core.internal.cli.NodeTitaniumCLI.run(NodeTitaniumCLI.java:177) at com.appcelerator.titanium.core.internal.cli.NodeTitaniumCLI.packageProject(NodeTitaniumCLI.java:559) at com.appcelerator.titanium.ios.core.launching.IOSNodeJSCommandsHelper.packageProject(IOSNodeJSCommandsHelper.java:542) at com.appcelerator.titanium.ios.internal.ui.launching.packaging.IOSPackagerLaunchConfigurationDelegate$1.run(IOSPackagerLaunchConfigurationDelegate.java:86) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 com.appcelerator.titanium.core 4 0 2014-07-11 11:18:53.772 !MESSAGE No signed in user {code}
| 1 |
2,125 |
TISTUD-6708
|
07/11/2014 20:32:58
|
Installing Android 4.1.2 through Studio Wizard installs too many build tools
|
I chose to install Android 4.1.2 (the default) for a clean install. The installed items look incorrect to me. Notably it installed a large number of build tools revisions. Additionally, it looks like it installed the system images twice each, once under system-images and again under system-images/default. I'm assuming the latter is incorrect.
| 5 |
2,126 |
TISTUD-6709
|
07/11/2014 20:51:19
|
NPE when install wizard advanced config for Android is shown
|
This doesn't appear to actually impact usage. AndroidSDKComposite throws an NPE at line 269. This is likely due to trying to parse Android L as a version number.
| 3 |
2,127 |
TISTUD-8596
|
07/12/2014 09:05:06
|
CLI:Platform specific folders are not created under resources when additional deployment targets are selected from tiapp.xml
|
Creating a project for a specific deployment target and then later changing the deployment target at the xml tab of the tiapp.xml and not at the overview tab does not create the necessary folders in the resources folder of the project This is not a regression as it also occurs in 3.2.3GA Steps to reproduce: 1. Create a project for only one of the deployment targets 2. Check the boxes for one more deployment target in the overview section of the tiapp.xml, save and refresh 3. In the tiapp.xml, at the deployment target allow for the other deployment targets by changing the value to true, save and refresh Expected Results: 1. Creates a project with only the platform folder for the selected deployment target under the resources folder of the project 2. Folders for the additional deployment targets selected will be included under the resources folder of the project 3. The checkboxes at the overview section is checked and the folders for the additional deployment targets selected should be created under the resources folder of the project Actual results: 1. Creates a project with only the platform folder for the selected deployment target under the resources folder of the project 2. Folders for the additional deployment targets selected will be included under the resources folder of the project 3. The checkboxes at the overview section is checked but the folders for the additional deployment targets selected are not created under the resources folder of the project
| 3 |
2,128 |
TISTUD-6711
|
07/12/2014 21:06:29
|
Studio: Theme resets with every update
|
h3. Steps to Reproduce update studio h3. Actual Result theme changes back to white background h3. Expected Result remember my theme
| 5 |
2,129 |
TISTUD-6712
|
07/14/2014 18:26:59
|
Force overwrite of modules folder on SDK installation
|
We have a number of issues with module installation whereby during the development process we change the contents of a module but hold the version the same. While this is not ideal, until we come up with a proper solution for it, we at least need to overwrite the module contents to make sure users get the latest version.
| 8 |
2,130 |
TISTUD-6721
|
07/15/2014 22:28:27
|
Pull out CoffeeScript plugins into Aptana Studio
|
Since Titanium or Appcelerator Studio does not have explicit dependency on CoffeeScript plugins, they need to be pulled out from the RCP applications and a new update site should be made available to install the CoffeeScript plugins on top of RCP.
| 5 |
2,131 |
TISTUD-6722
|
07/16/2014 00:48:29
|
Android: Module cannot be packaged on Windows
|
I was verifying the fix of TISTUD-6510 and encountered an inability to package an Android module. I cannot verify if it is a regression. h5. To reproduce 1. Create a module 2. Package it h5. Actual result {code} Executing build.xml... C:\ProgramData\Application Data\Titanium\mobilesdk\win32\3.3.0.v20140711123603\module\android\build.xml:326: The following error occurred while executing this line: C:\ProgramData\Application Data\Titanium\mobilesdk\win32\3.3.0.v20140711123603\module\android\build.xml:281: exec returned: 2 {code} NPE logs Intermittently in Studio log file. {code} java.lang.NullPointerException at com.appcelerator.titanium.android.ui.launching.AndroidLaunchConfigurationUIUtil.createMobileModulePackagerLaunchConfiguration(AndroidLaunchConfigurationUIUtil.java:169) at com.appcelerator.titanium.android.internal.ui.launching.distribution.PackageAndroidModuleWizard.generateLaunchConfig(PackageAndroidModuleWizard.java:28) at com.appcelerator.titanium.ui.module.AbstractModulePackagingWizard.generateLaunchConfiguration(AbstractModulePackagingWizard.java:115) at com.appcelerator.titanium.ui.module.AbstractModulePackagingWizard.performFinish(AbstractModulePackagingWizard.java:81) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) {code} h5. Expected result Module Packaging Successfully
| 8 |
2,132 |
TISTUD-6726
|
07/17/2014 16:03:28
|
Studio: Alloy TSS doesn't understand bitwise operator
|
If you use bitwise in a TSS file, studio flags it as an error: {code} <Alloy> <Window id="win"/> </Alloy> {code} {code} "#win[platform=android]": { windowSoftInputMode: Ti.UI.Android.SOFT_INPUT_STATE_HIDDEN | Ti.UI.Android.SOFT_INPUT_ADJUST_PAN } {code} The app compiles and runs properly, it's just a lint issue. Per ALOY-750 this is supported.
| 5 |
2,133 |
TISTUD-6733
|
07/18/2014 20:05:27
|
Studio global run toolbar looks bad on Windows with larger font size
|
I saw a developer's screen during a Webex where the global toolbar looked wrong with his increased OS font size. The arrows were too small compared to the other toolbar dropdown arrows, and the text was cut off.
| 8 |
2,134 |
TISTUD-6735
|
07/21/2014 19:07:56
|
Provide useful content assist against mobware commonjs SDKs/modules
|
Looking at Tony's screencast, Studio was less than helpful in terms of CA once trying to require the module and exposing the methods/apis. We need to investigate why it's failing to be useful here!
| 8 |
2,135 |
TISTUD-6736
|
07/21/2014 19:32:18
|
Suggest content assist for string arguments to require function call
|
We don't offer any content assist for the argument to a require call. We have a similar idea for CA on src attributes in HTML where we provide possibilities based on the files in the filesystem. We should offer a similar approach to suggest base filenames for files relative to the current file, titanium modules by id, etc.
| 5 |
2,136 |
TISTUD-6737
|
07/21/2014 21:53:30
|
Replace 32-bit version of Studio with 64-bit version
|
I believe we can stop creating a 32-bit version of Studio (and only do a 64-bit version) http://support.apple.com/kb/ht5444 I think we could actually get rid of it now, but it’s inconvenient to do so for a minor release: http://www.everymac.com/mac-answers/os-x-mountain-lion-faq/macs-compatible-incompatible-with-os-x-mountain-lion.html
| 8 |
2,137 |
TISTUD-6739
|
07/22/2014 02:19:06
|
Liveview should not validate the hooks on startup
|
The liveview hooks are now being validate for every launch, so there is no need to validate the liveview hooks during the startup again.
| 2 |
2,138 |
TISTUD-6744
|
07/23/2014 01:24:09
|
Breakpoints not hit on Mac OS X
|
Breakpoints are not hit on Mac OS X. First they were hit, then I've used the "Remove all breakpoints" option and added some new breakpoints around. From that moment the debugger doesn't stop at any breakpoint. Tried restarting Aptana Studio, the iOS simulator and the whole system.
| 8 |
2,139 |
TISTUD-6742
|
07/24/2014 18:10:47
|
Allow downloading and installing modules accessed with basic auth
|
We now can pass in auth for a given URL to our download manager (see TISTUD-6702). We need to break apart the utility method for installing modules to download and install separately and allow for passing in the auth in the download portion so for Mobware we can pass along auth to download the SDK zips.
| 8 |
2,140 |
TISTUD-6753
|
07/25/2014 02:33:00
|
Unable to do updates and installs
|
h3. Steps to Reproduce When attempting to do updates and installs, the wrong user name is being used. The user name field cannot be changed. It is defaulting to 'tfreeman'. It should be Freeman, Tom. h3. Actual Result No updates or installs are happening. h3. Expected Result Updates and installs should be happening
| 5 |
2,141 |
TISTUD-6745
|
07/25/2014 18:40:11
|
Windows: No shortcut added to Windows Start Menu
|
h4. Problem Description When you install Titanium Studio (as of the installer from the developers page on July 25th, 2014), you won't be getting an entry in the start menu in windows 7 professional. h4. Extra info Almost all enterprise customers use Windows. And most of them still uses Windows 7 Professional.
| 5 |
2,142 |
TISTUD-6883
|
07/28/2014 10:08:48
|
Titanium updates are not installed when node is available, but npm is not available
|
h3. Steps to Reproduce When updating the Titanium, node and Restart Titanium but no changes. h3. Actual Result I get an error 'Problem Occured' message Text : 'Installing Titanium updates' has encountered a problem. Error encountered during update Error encountered during update NPM is not installed. NPM is not installed. NPM is not installed. h3. Expected Result Log Error : !ENTRY com.aptana.core 4 1 2014-07-28 10:51:11.288 !MESSAGE sudo: a password is required !ENTRY com.appcelerator.titanium.update.core 4 4 2014-07-28 10:51:14.468 !MESSAGE Error encountered during update !SUBENTRY 1 com.aptana.js.core 4 0 2014-07-28 10:51:14.468 !MESSAGE NPM is not installed. !SUBENTRY 1 com.aptana.js.core 4 0 2014-07-28 10:51:14.468 !MESSAGE NPM is not installed. !SUBENTRY 1 com.aptana.js.core 4 0 2014-07-28 10:51:14.468 !MESSAGE NPM is not installed.
| 5 |
2,143 |
TISTUD-6749
|
07/28/2014 14:52:09
|
Titanium's require resolver logic isn't getting applied to Alloy projects and files underneath app folder
|
The TitaniumRequireResolver which knows to look at modules when resolving a require call for index/CA purposes isn't getting "applied" for Alloy projects and files underneath the app folder. It explicitly looks for the titanium mobile nature and files underneath Resources. We need to also "turn it on" for files under the app folder hierarchy.
| 3 |
2,144 |
TISTUD-6755
|
07/30/2014 00:31:16
|
Appcelerator Studio: Run configurations display incorrectly
|
h5.Description All run configuration categories have Appcelerator at the start (example, Appcelerator iOS Device or Appcelerator Mobile Web Preview). However Android starts with Titanium (example, Titanium Android Device) Also each platform has Device and Simulator/Emulator configurations, however BlackBerry has 'Application Installer' and 'Simulator'.
| 2 |
2,145 |
TISTUD-6759
|
08/01/2014 18:38:53
|
Studio should prompt for new node.js version updates
|
Studio currently prompts to install Node.JS only if it is not installed on the system. However, if the old version (like 0.8.x) of Node.JS is already installed on the system, then it does not prompt to update to the minimum required version (currently it is 0.10.13).
| 5 |
2,146 |
TISTUD-6772
|
08/06/2014 22:25:34
|
Errors occurring when editing TiApp.xml
|
h5. Problem description Appcelerator Studio is displaying an error popup multiple times when editing TiApp.xml. Error popup appears again every time is being dismissed. h5. Steps to reproduce 1. Create a new project in Studio 2. Edit Tiapp.xml Result: error popup is displayed. See the screenshot and the attached log file for additional informations 3. Click on 'Ok' button Result: error popup is dismissed and immediately displayed again. Is basically not possible not dismiss the error.
| 5 |
2,147 |
TISTUD-6776
|
08/07/2014 16:39:00
|
Show XCode6 iOS simulators categorized on SDK
|
In XCode6, the list of simulators are different from the traditional way. It has simulators as iPhone 4s, iPhone 5, iPhone 6, iPad Retina etc for each iOS version. In case if the XCode supports 3 iOS versions, then it will show almost 23 simulators. Having them to show all 23 simulators in one list will be confusing to the user. So, we need to categorize (through multi level menu) the simulators based on the version, similar to Simulator device menu.
| 8 |
2,148 |
TISTUD-6778
|
08/08/2014 02:03:16
|
Show full username instead of user id in sudo password prompt
|
The Sudo password prompt (before it install npm updates) currently shows the logged in userId and the dialog does not mimic the Mac password prompt dialog. Also, a lot of users are confused whether they need to input the system password, or Appcelerator password or the network password. If the password prompt mimics closer to Mac native dialog by showing the userName, it will eliminate the confusion and fewer users will run into invalid password issues.
| 5 |
2,149 |
TISTUD-6833
|
08/12/2014 10:39:58
|
Android modules are not recognized as Java projects
|
h3. Summary As of the release of Titanium (& Studio) 3.3.0, old Android modules project had to be recreated (the structure having changed, the new build scripts wouldn't build an project created previously). However, new projects, even though they "build" through the script, are not proper Java projects anymore and can not be worked on via Titanium Studio. Even when imported in ADT they are pure "text" projects and no autocompletion or syntax validation is available anymore. h3. How to reproduce Having properly installed the following SDKS : Android 4.4.2, Android 4.1.2, Android 2.3.3 And having the NDK installed and properly configured in studio. From an empty workspace, when you create a new Android module (in the example named bob, with id com.bob), everything seems to work fine, no errors are displayed during the creation and you now get a structure where source files are in android/src/com/bob folder : !AndroidModuleBug.png! The Java files no longer appear as part of a *package*. There are *no jar* dependencies shown. It's not even a *proper Java project* anymore. I have removed a ";" in the screenshot to show that the *syntax validation* didn't pick it up. When using *autocomplete*, you get the following message (cf. screenshot) "This compilation unit is not on the build path of a Java project". When removing the fake syntax error, the module packages fine, however it can no longer be worked on properly : no proper Java editing, have to "guess" all the fields. I have reinstalled Titanium Studio from scratch to make sure it was not related to a problem in the update mechanism. This is a complete nightmare for me since I have no longer the capability of editing my Android modules on my projects.
| 5 |
2,150 |
TISTUD-6786
|
08/14/2014 19:25:40
|
Studio installs of global npm packages modifies permissions of .npm folder
|
h2. problem When I install a node.js module globally via Studio updates (titanium cli for example), it changes the permissions of my .npm folder such that I can no longer do npm installs of any kind without {{sudo}}. Essentially the folder and all files contained within get {{chown}}'ed to {{root}}. This is detailed in this post: https://coderwall.com/p/dxmfpg. The difference between this situation and that link is that this still occurs even if I already have a .npm folder. h2. reproduce # Open Appc Studio # request Appcelerator updates, making sure that it will include titanium cli (rollback your globally installed titanium module if need be) # Install the titanium cli update # attempt to do {{npm install commander}} any where at the CLI (it could be any module on npm) # you should get error like the following {code} npm ERR! Error: EACCES, mkdir '/Users/tlukasavage/.npm/commander/2.3.0' npm ERR! { [Error: EACCES, mkdir '/Users/tlukasavage/.npm/commander/2.3.0'] npm ERR! errno: 3, npm ERR! code: 'EACCES', npm ERR! path: '/Users/tlukasavage/.npm/commander/2.3.0' } npm ERR! npm ERR! Please try running this command again as root/Administrator. npm ERR! System Darwin 13.3.0 npm ERR! command "node" "/usr/local/bin/npm" "install" "commander" npm ERR! cwd /Users/tlukasavage npm ERR! node -v v0.10.29 npm ERR! npm -v 1.4.14 npm ERR! path /Users/tlukasavage/.npm/commander/2.3.0 npm ERR! code EACCES npm ERR! errno 3 npm ERR! stack Error: EACCES, mkdir '/Users/tlukasavage/.npm/commander/2.3.0' npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /Users/tlukasavage/npm-debug.log npm ERR! not ok code 0 {code} To workaround this issue, you can do the following: {{sudo chown -R USERNAME ~/.npm}} After which you can do npm installs again without sudo
| 5 |
2,151 |
TISTUD-6806
|
08/18/2014 21:32:18
|
Update content assist for Picker to reflect new data-binding support
|
Add data-binding attribute to Picker element.
| 5 |
2,152 |
TISTUD-6810
|
08/20/2014 12:07:38
|
Studio:Update Label inside Preference screen appears as "%update.preference.name"
|
Update Label inside Preference screen appears as "%update.preference.name". Click on Preferences>Studio> The first option (Automatic Updates) appears as "%update.preference.name" Please refer to screenshot attached.
| 3 |
2,153 |
TISTUD-6811
|
08/20/2014 19:34:06
|
Failure to build project onto device with error: An internal error occurred during: "Saving packaging preferences".
|
When trying to build an imported from https://github.com/appcelerator/titanium_mobile_tests_internal project for a iOS device, I encountered the following: An internal error occurred during: "Saving packaging preferences". {code} Titanium Command-Line Interface, CLI version 3.4.0-dev, Titanium SDK version 3.4.0.v20140819094113 Copyright (c) 2012-2014, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ For help, run: titanium help build [ERROR] : Invalid "--keychain" value "System Defaults" {code} h5. To reproduce 1. Open Appcelerator Studio 2. Import any project from https://github.com/appcelerator/titanium_mobile_tests_internal 3. Run> your device h5. Actual result Please, refer to the attachments h5. Expected result No errors, success, installing an app on to the device The Work Around Run>Configuration>Appcelerator IOS device Please, notice iOS device is showing as iTunes sync (screenshots)
| 5 |
2,154 |
TISTUD-6815
|
08/21/2014 21:43:12
|
Studio does not recognize installed npm packages if there are unmet dependencies with npm
|
When I look for updates in 3.3.0 Appcelerator Studio, it did not recognize any installed npm packags and prompted to force install all of those npm updates. Studio runs npm ls <package> command to figure out the installed location and if there any errors in the output, then we fails to parse out the warnings/errors from the output. When I ran the below command, I realized that 'jake' npm package has certain issues with dependencies on the machine. {code} $ "/usr/local/bin/node" "/usr/local/bin/npm" "ls" "alloy" "--color" "false" "-g" npm WARN unmet dependency /usr/local/lib/node_modules/jake/node_modules/filelist requires minimatch@'^0.3.0' but will load npm WARN unmet dependency /usr/local/lib/node_modules/jake/node_modules/minimatch, npm WARN unmet dependency which is version 0.2.14 /usr/local/lib └── [email protected] (git://github.com/appcelerator/alloy.git#23da3c86415437cafec5a4f7385ecb52455893b8) {code}
| 5 |
2,155 |
TISTUD-6817
|
08/22/2014 00:16:47
|
MobileIron and AirWatch publish options are disabled for non-iOS apps
|
REPRODUCTION: 1. In the project's tiapp.xml file, unselect iPhone and iPad. 2. Right-click on the project and select Publish > MobileIron > Publish... or Publish > AirWatch > Publish... (if visible) RESULTS: The AirWatch and MobileIron publish wizards do not appear or the options for MobileIron and AirWatch may not appear in the right-context menu. WORKAROUND: Select either iPhone or iPad in the tiapp.xml file.
| 5 |
2,156 |
TISTUD-6820
|
08/22/2014 09:25:56
|
Studio Dashboard and Platform configuration wizards conflicts for Android SDK setup status
|
Studio Dashboard shows Android SDK is not installed, while platform configuration wizard shows that Android SDK is properly installed. So, It *does not allows further installation into the same location.* Possible Reason for this problem is: If the Android SDK set up fails in middle of installation, it leaves some partial SDK files into the specified destination folder. It causes the problem in Android SDK detection process of Studio. This is *not a regression* since it happens in Studio 3.3.0 as well. h5. Steps to Reproduce 1. Delete your Android SDK installation. 2. Start installation from Studio Dashboard 3. After installation starts, disconnect your network for some time. 4. Installation will fail and leave some files into specified location. 5. If you try to set up Android SDK into the same location, this scenario will happen. Expected Result: Android SDK installation should succeed. We could clean the folder if the installation fails before completion.
| 8 |
2,157 |
TISTUD-6822
|
08/22/2014 11:16:27
|
Studio: Clearing invalid proxy setup still does not allow login to studio
|
Clearing invalid proxy login, still does not allow the user to login to the studio and shows a message that the server is unreachable. This is not a regression as it also happens in Appcelerator studio 3.3.0 Steps to reproduce: 1. Click proxy set up 2. Enter the following in the proxy setup host: !@# port:8080 3. Click ok 4. Enter your credentials and login to studio 5.Clear the proxy settings 6. Login to the studio Actual Result: 4. "Login server is currently unreachable" message is displayed 5. "Login server is currently unreachable" message is displayed Expected Result: 5. Studio should be able to login The studio is only able to login when it is launched the next time.
| 3 |
2,158 |
TISTUD-6824
|
08/22/2014 14:14:00
|
Default to 64-bit Mac build inside installer
|
Since we plan to phase out the 32-bit builds of Studio, we should move the installer/DMG to include the 64-bit build.
| 5 |
2,159 |
TISTUD-6834
|
08/26/2014 18:13:18
|
Add F3 command to jump from string keys in i18n files to usage
|
Add a command with F3 binding to jump to references/usage of translation keys in other files in a Titanium Mobile project. This is simply a matter of defining a command with binding and handler, and then reusing some of the same implementation we have for the hyperlink detector.
| 3 |
2,160 |
TISTUD-6835
|
08/26/2014 18:15:04
|
Add F3 command to jump from i18n translation keys in Alloy view XML to definition in strings.xml file
|
Add a command with F3 binding to jump to the definition of translation keys in the strings.xml file(s) in a Titanium Mobile project. This is simply a matter of defining a command with binding and handler, and then reusing some of the same implementation we have for the hyperlink detector from TISTUD-6692
| 3 |
2,161 |
TISTUD-6836
|
08/26/2014 18:17:11
|
Index translation key references in TSS files
|
We need to start indexing the usage of translation keys in Alloy TSS files so we can support F3/hyperlinks for navigating the relationship with their definitions in strings.xml files. See https://github.com/FokkeZB/ti-i18n/tree/master/test/source
| 5 |
2,162 |
TISTUD-6837
|
08/26/2014 18:18:14
|
Index translation key references in Titanium Mobile JS files
|
We need to start indexing the usage of translation keys in JS files so we can support F3/hyperlinks for navigating the relationship with their definitions in strings.xml files. See https://github.com/FokkeZB/ti-i18n/tree/master/test/source
| 8 |
2,163 |
TISTUD-6838
|
08/26/2014 18:31:53
|
Add hyperlink detector to jump from i18n translation keys in JS code to definition in strings.xml file
|
Add a hyperlink detector to navigate from keys in JS to strings.xml definition.
| 8 |
2,164 |
TISTUD-6839
|
08/26/2014 18:32:41
|
Add hyperlink detector to jump from i18n translation keys in TSS code to definition in strings.xml file
|
Add a hyperlink detector to navigate from keys in TSS to strings.xml definition.
| 5 |
2,165 |
TISTUD-6840
|
08/26/2014 18:33:12
|
Add F3 command to jump from i18n translation keys in TSS code to definition in strings.xml file
|
Add a hyperlink detector to navigate from keys in TSS to strings.xml definition.
| 3 |
2,166 |
TISTUD-6841
|
08/26/2014 18:33:22
|
Add F3 command to jump from i18n translation keys in JS code to definition in strings.xml file
|
Add a hyperlink detector to navigate from keys in JS to strings.xml definition.
| 3 |
2,167 |
TISTUD-6845
|
08/28/2014 11:20:09
|
Studio: Unable to create Node.ACS project on Windows
|
When a node.acs project under the organization: qe_test_org_prod studio, it starts creating the project and then when it is more than half way in creating the necessary folder, it hangs. However, node.acs project is successfully created under Appcelerator,Inc organization. Steps to reproduce: 1. Go to File > New > Node.ACS Project 2. Enter Project Name and select organization as qe_test_org_prod 3. Click Finish Actual Result: Starts creating the project and then when it is more than half way in creating the necessary folder, it hangs. When the red square beside the progress bar is clicked it stops but the 'new node.acs project wizard' cannot be closed. Studio then becomes unresponsive and it has to be forcefully quit. Expected Result: Node.ACS project must be successfully created.
| 5 |
2,168 |
TISTUD-6847
|
08/29/2014 00:05:19
|
Support detection of i18n translation keys in Alloy View XML text nodes and id attributes
|
We should be able to navigate the user from usage of a translation key/string to it's definition in an i18n file. This extends the previous functionality from TISTUD-6692: If you hold down Cmd and hover the mouse over the titleid attribute for first label, or L() macro on second label, They are not turning into hyperlinks. {code} <Label titleid="welcome_message3"></Label> <Label>L('welcome_message4')</Label> {code}
| 5 |
2,169 |
TISTUD-6851
|
08/29/2014 19:36:31
|
iOS: Xcode6-beta6 - Cannot install to iOS device 7.X or launch simulator 7.X
|
*Details:* Cannot build to iOS devices or simulators with Xcode 6-beta6. *Steps to reproduce:* 0. Make sure your machine has Xcode 6-beta6 and your CLI only points to that Xcode version 1. Create a Titanium project 2. Install to either device or simulator *Actual:* Cannot build to device or simulator; see attachments for null pointer exception. *Expected:* Should be able to build to device or simulator with Xcode 6-beta6.
| 3 |
2,170 |
TISTUD-6855
|
09/01/2014 09:20:26
|
Studio: Tool tip does not disappear when changing tab
|
When creating a new mobile app project, the VPC environment is not selected and the users are prompted to select one on the tiapp.xml page when the project is created. This tool tip does not disappear when the window is changed. Look at attachment. Steps to reproduce: 1. Create a sample mobile app project with service enabled. 2. When the 'Please select the VPC environment' tool tip appears immediately switch to another window(e.g.: chrome/safari) and the mouse should not go over the tiapp.xml page while switching to another window. 3. Go to the tiapp.xml and remove the following line to disable performance service: <property name="com-appcelerator-apm-id" type="string">54044046f36ad34fda0000c0</property> 4. Switch to the tiapp overview page and click on the enable services button 5. Switch to another window e.g. safari/chrome Actual Result: 2.Tool tip for selecting the VPC environment does not disappear. 3. Removes the performance services 4. Performance Service is enabled and 'Please choose a VPC environment name' tool tip appears 5. 'Please choose a VPC environment name' tool tip still shows up. Expected Result: 2.Tool tip for selecting the VPC environment should disappear. 3. Removes the performance services 4. Performance Service is enabled and 'Please choose a VPC environment name' tool tip appears 5. 'Please choose a VPC environment name' tool tip should disappear.
| 5 |
2,171 |
TISTUD-6856
|
09/01/2014 09:26:14
|
Error on opening Preferences > Studio > Platforms > iOS. "Invalid values"
|
An error is shown when the iOS screen under preferences is opened. The same worked earlier but now the issue is shown in 3.3.0 Studio as well. Steps to Reproduce: 1. In Appcelerator Studio, go to Preferences > Studio > Platforms > iOS Actual: An error is shown. Refer to attached screenshot and logs.
| 5 |
2,172 |
TISTUD-6857
|
09/01/2014 09:54:52
|
Studio: Error displayed at the top of tiapp.xml page only refreshes after re-opening it
|
When a new mobile app project is created (both alloy and classic) the VPC environment is not selected and hence the cloud service is not enabled displaying a red cross beside it at the Appcelerator Platform Service section in the tiapp.xml. However, there is no error message displayed at the top of the tiapp overview page until it is reopened(see attachment) Steps to reproduce: 1.Create a sample mobile app project and observe the tiapp overview page 2. Close the tiapp.xml and reopen it. 3. Select the VPC environment and save. 4. Close and reopen tiapp.xml. Actual Result: 1. The total no of error is not displayed at the top of the tiapp overview page and there is no red cross near the VPC environment. 2. '1 error detected' at the top of the tiapp overview page and the red cross beside the VPC environment appear. 3. Cloud service enabled but '1 error detected' at the top of the tiapp overview page and the red cross beside the VPC environment are still shown 4. No error message displayed Expected Result: '1 error detected' at the top of the tiapp overview page and the red cross beside the VPC environment appear in both step 1 and 2. 3. Cloud service is enabled and no error message should be displayed on the tiapp overview page. 4. No error message displayed.
| 5 |
2,173 |
TISTUD-6859
|
09/01/2014 10:42:35
|
iOS Simulator: Run As shows multiple iOS simulator with same name, when multiple versions of iOS simulator on system
|
When we have multiple versions of iOS simulator on the system, for example downloaded and setup simulator version 7.0 and/or 7.1 along with default version 8.0 in Xcode 6, then the context menu for Run As in studio shows multiple options of same simulator. Steps to Reproduce: 1. Download multiple versions of iOS Simulator. 2. In AppC Studio, create a new project. 3. In the project explorer, right click on the project and go to Run As. Actual Result: The Run As menu shows multiple iOS Simulator with same name. Refer to attached screenshot. Expected: Either the simulators should be grouped by their versions. Same as the Run option in the toolbar. Or the version number should be shown against each simulator, same as in Device Profile drop down in Run configuration for iOS Simulator
| 5 |
2,174 |
TISTUD-6860
|
09/01/2014 11:21:58
|
Studio: Switching default titanium studio theme in the dashboard leaves behind black background in some views
|
Switching between the light and dark theme does not change the theme properly Steps to reproduce: 1. Launch appcelerator studio and open dashboard 2. Click on the get started tab and choose 'Light' as the default titanium studio theme 3. Switch to 'dark' as the default titanium studio theme 4. Switch to 'light' default titanium studio theme Actual Result: 1. Studio launches and dashboard opens without any error 2. Light theme applied entirely 3. Dark theme applied entirely 4. Light theme applied but with dark background for the outline and 'Studio Console' is highlighted in black (see attachment) Expected Result: 1. Studio launches and dashboard opens without any error 2. Light theme applied entirely 3. Dark theme applied entirely 4. Light theme applied entirely leaving behind dark background from the previous dark theme
| 5 |
2,175 |
TISTUD-6865
|
09/02/2014 07:55:01
|
Studio: VPC Environment field cannot be selected in package configuration
|
The package configuration for a mobile app has two VPC environment selection field: one under settings and another under build. The VPC environment under settings is enabled but the user is unable to open the drop down to select an environment while the one under build section allows the user to select the environment. Steps to reproduce: 1. Create a sample mobile app for android 2. Publish it to android app store 3. Open package configuration and open the configuration for the newly created project Actual Result: 3. VPC environment under settings is enabled but the drop down menu does not open up. See attachment Expected Result: 3. There should only be one VPC environment field either under build or under settings. Or if there needs to be two, the drop down menu should be able to open for the user to select an option.
| 5 |
2,176 |
TISTUD-6866
|
09/02/2014 09:10:16
|
Studio is opening in offline mode without prompting login splash after we change the password from dashboard
|
Studio is opening in offline mode without launching login splash screen if we change the password in dashboard.appcelerator.com before launching the studio. h5. Steps To Reproduce 1. Close your studio if opened 2. Go to [Dashboard|https://dashboard.appcelerator.com/] and change your password. 3. Launch your studio again h5. Actual Result Studio launches in offline mode. Please see the attachment for more info. h5. Expected Result Studio should launch *login splash* for signing in again. It would be better if we can give a warning as *Your password is changed recently but you are launching with older password*. Facebook uses this kind of warning message and it's really useful for users.
| 5 |
2,177 |
TISTUD-6872
|
09/03/2014 06:34:55
|
Breakpoints are not hitting for Android device in OSX
|
Breakpoints are not hitting on Android device for Classic Apps. This is a *regression*. h5. Steps To Reproduce 1. Create a mobile app project 2. Insert a breakpoint at a valid location in app.js file. 3. Call Debug. h5. Expected results Project debugs without error.
| 5 |
2,178 |
TISTUD-6878
|
09/04/2014 06:35:32
|
Studio Dashboard and Preferences window conflicts for Xcode setup status
|
(!) This is a *regression* since Studio 3.3.0 dashboard is updated correctly when it is refreshed. h5. Steps To Reproduce 1. Open the studio 2. Delete the Xcode.app 3. Refresh the studio dashboard ( It will not update iOS SDK status) 4. Open Preferences Window 5. Click *Refresh Button* on iOS platform configuration section (Preferences > Studio > Platforms > iOS ). This will update preferences window 6. Close the Preference window 7. Again Refresh Studio dashboard. h5. Actual Result Studio Dashboard is *not updated* to reflect the Preferences Window status h5. Expected Result Studio Dashboard should be updated to reflect the same status as in Preferences window *Note:* Same scenario will occur if we install Xcode on the machine while the studio is opened. h5. Attachments BeforRestartingStudio.png: Xcode is deleted but studio is not yet restarted After_Restarting_studio.png : Studio is restarted Screen Shot 2014-09-04 at 12.59.13 PM.png : Xcode is installed but studio is not yet restarted studio_log3.4.0.txt : Studio log file at this scenario h5. Workaround Restart the studio. Then Studio dashboard will be updated.
| 5 |
2,179 |
TISTUD-6885
|
09/05/2014 10:39:22
|
Multiline Search: Selecting 'Search selection' using the gear icon does not activate the feature in the search bar
|
When selecting the search selection from the settings in the multiline search bar, it does not enable the feature in the search bar. This seems to also happen in appcelerator studio 3.3.0 Steps to reproduce: 1. Open a javascript file (e.g., app.js). 2. Activate the search toolbar (command + f on osx, control + f on windows). 3. Press the gear icon (Show Find Bar Options). See Results. 4. Select 'Search Selection' Actual Result: The search selection icon in the search bar is not enabled. Expected result: There must be a tick sign beside the search selection option in the drop down menu and the search selection icon in the search bar must be enabled.
| 5 |
2,180 |
TISTUD-6886
|
09/05/2014 11:19:06
|
Studio: Values entered in the module creation wizard is not reflected in the manifest file
|
While creating a mobile module project, the values entered in the wizard for manifest file are not reflected in the manifest file generated when the project is created. This is not a regression as it happens with Studio, CLI and SDK in 3.3.0 Steps to reproduce: 1. Create a Module Project and enter values for version, author, description to be populated in the manifest file. Actual Result: The following is generated in the manifest file under build folder with version as always 1.0.0 and the description is always the name of the app. The author name version: 1.0.0 apiversion: 2 description: androidmodule1 author: Your Name license: Specify your license copyright: Copyright (c) 2014 by Your Company Expected Result: Values entered during module creation such as version, author, description must be reflected in the manifest file generated.
| 5 |
2,181 |
TISTUD-6889
|
09/05/2014 18:37:05
|
Update Studio Release Notes link
|
In order to display "Studio Release Notes" instead of "Titanium Studio Release Notes", the name to the web page had to change. The new link will be: http://docs.appcelerator.com/titanium/latest/?print=/guide/Studio_Release_Notes
| 2 |
2,182 |
TISTUD-6896
|
09/08/2014 22:42:13
|
Importing Alloy project and changing Titanium SDK in tiapp.xml causes the Global Toolbar to become inactive
|
h5. To reproduce 1. Import an existing Alloy project(in my case it was fromgit/titanium_mobile_tests_internal/FeatureTest/Orientation/TIMOB-16177 Alloy) 2. Change Titanium SDK to the latest(?) one and save changes. h5. Actual result Inactive Global Toolbar (screenshot) Note: The user can Run As > Run configuration when right click on the project.
| 5 |
2,183 |
TISTUD-6897
|
09/08/2014 23:56:46
|
Studio: With Xcode 5.1.1 set in xcode-select, Studio build command sends device ID
|
h5. Description: When in an environment with both Xcode 6.0 (beta 7) and Xcode 5.1.1, I tried to configure to run for SDK 3.3.0 targeting Xcode 5.1.1 and iOS 7.1. The build would begin and hang. Looking at the Studio output, the command sent includes the device ID. Using the command in terminal also would not allow a build, until the device ID was removed. {code} Process: "/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "build" "--platform" "iphone" "--log-level" "trace" "--sdk" "3.3.0.GA" "--project-dir" "/Users/eric/Documents/Appcelerator_Studio_Workspace/serendipityTest" "--target" "simulator" "--ios-version" "7.1" "--device-family" "universal" "--sim-version" "6.1" "--deploy-type" "development" "--sim-type" "iphone" "--device-id" "160BB50F-CB46-4E01-A767-7F77D70806A9" "--skip-js-minify" "--skip-js-minify" {code} h5. Steps to reproduce: 1) Install Xcode 5.1.1 and Xcode 6 beta 7 in environment listed above 2) Set xcode-select to use 5.1.1 3) Create a project with SDK 3.3.0 set in tiapp.xml 4) Attempt to build for iOS 7.1, any supported simulator h5. Result: Build begins but does not proceed h5. Expected Result: Build continues, completes without errors.
| 5 |
2,184 |
TISTUD-6898
|
09/09/2014 01:28:57
|
Studio: Option to build for iOS8 sim is available when on Xcode5 and 3.3.0 SDK
|
h5.Description When Xcode5 is selected and 3.3.0.GA SDK is selected in the tiapp.xml I still see an option to build to an iOS8 simulator in the menus. h5.Steps To Reproduce 1. In a projects tiapp.xml change the SDK version to 3.3.0.GA and in the terminal use the following command with your path to Xcode5 to switch to Xcode5 {code} sudo xcode-select -s *path to Xcode5* {code} 2. Go to build to an iOS simulator. h5.Actual Result You should see the same as the attached screenshot. h5.Expected Result There should only be iOS 7.1.
| 3 |
2,185 |
TISTUD-6900
|
09/09/2014 16:13:43
|
Avoid installing test and performance services based on membership plan
|
The membership plans are associated with organization rather than with the user. So, if the user is part of multiple organizations, then we need to determine whether they have access to Test/Performance services by looking at the membership plans of all their organizations. If any of the membership plan is eligible for Test/Performance services, then we should allow them to install or update these services.
| 5 |
2,186 |
TISTUD-6901
|
09/09/2014 16:17:51
|
Associate Organization with Plan
|
The membership plans are associated with the organization. So when Studio receives information about organization, it contains the details of membership plan name/id associated with that organization. So, the organization model should parse and store the details of the membership plan, as all the services can query for the plan and figure out enabling the services.
| 3 |
2,187 |
TISTUD-6902
|
09/09/2014 21:49:24
|
Enable Test and Performance services based on project's organization's plan
|
The 360 Appcelerator Services can be enabled while creating projects or from TiApp. In either of those situations, we need to verify for the organization membership plan and only then let the Test and Performance services to enable if the membership plan has privileges.
| 5 |
2,188 |
TISTUD-6904
|
09/10/2014 10:25:55
|
Code Processor: Code Processor is not working if there is no Android SDK installed
|
Code Processor is not working If I don't have Android SDK set up on my machine. (!) This is *not a regression* since issue is there in 3.3.0 GA as well. h5. Steps To Reproduce 1. Remove the Android SDK path from your Studio Preferences (Studio should not detect any Android SDK from your machine) 2. Create a project 3. Run code Analyze for any platform (iPhone or Mobileweb) h5. Actual Result Code Processor fails with an error message. Please see the *attachment.* Following log entry is observed in Studio log file {code} !ENTRY com.appcelerator.titanium.codeprocessor.core 4 0 2014-09-10 17:24:12.097 !MESSAGE [ERROR] : No valid Android SDK targets found. [ERROR] : Please download an Android SDK target API level 14 or newer from the Android SDK Manager and try again. {code} h5. Expected Result It should generate proper html report.
| 5 |
2,189 |
TISTUD-6907
|
09/10/2014 11:20:33
|
Platform Configuration window shows incorrect version after installation of Android SDK
|
Platform configuration shows a wrong android version after finishing of Android SDK installation. (!) This is *not a regression* since issue is there in Studio 3.3.0 as well. h5. Steps To Reproduce 1. Remove the Android SDK from your machine 2. Open studio dashboard and on Android SDK link 3. Click on *Install or Update Android SDK* button 4. Click the settings and select an android SDK version ( I selected Android 4.1.2 in 3.4.0 Studio and Android 2.3.3 in 3.3.0 Studio) 5. Configure the Android h5. Actual Result It reports as a wrong version of Android is installed. (When I install 4.1.2, It says as 4.2.2 is installed. ) Please see the attachment for more info. h5. Expected Result It should say the correct version of Android SDK as installed. *Note:* Whatever version of Android is installed, It says the same message for me. But In another machine, It says as *Latest version installed: 2.3.3*.
| 5 |
2,190 |
TISTUD-6910
|
09/10/2014 21:58:09
|
Investigate why Native proxy provider isn't being used by default on Windows
|
We're getting killed with customer issues getting the proxy set up. The easiest fix for this is to bypass auth and then just set the proxy provider to "native" and restart. But we should already be using the native provider by default. Why isn't that working? Is it just not getting loaded? We need to figure that out and fix it.
| 8 |
2,191 |
TISTUD-6911
|
09/11/2014 01:53:59
|
iOS: Simulator - Incorrect simulator OS version appears in the drop down list with project created with SDK 3.3.0.GA
|
*Details:* With Xcode 5.1.1, if you create a project with SDK 3.3.0.GA (selected in tiapp.xml), but latest 3.4.0 SDK selected in CLI, then the incorrect iOS simulator version appears in the device drop down list. *Steps to reproduce:* 1. Make sure your CLI has the latest SDK selected: e.g. {{ti sdk select 3.4.0.v20140909222515}} 2. Make sure your CLI *only* recognize Xcode 5.1.1 3. Next, create a Titanium project with target SDK 3.3.0.GA 4. At the device drop down list, select any simulator *Actual:* Next to the simulator device name, "(v5.1)" appears; see actual.png attachment. *Expected:* The correct simulator OS should appear next to the simulator device name; see expected.png
| 3 |
2,192 |
TISTUD-6915
|
09/11/2014 15:44:07
|
java.lang.ClassCastException: org.json.simple.JSONObject cannot be cast to org.json.simple.JSONArray
|
From http://www.appcelerator.com/blog/2014/09/titanium-sdk-3-4-0-beta-for-ios-8-now-available/#div-comment-71550 We’ve been running Java 8 with it since 8 was released. We’ve heard mention that we need specific versions like 6 or 7 installed by various parties before, but traditionally that was because of Android limitations. There is instead likely a `ti info` bug like TISTUD-6909 but on the iOS side. Somehow the CLI is giving us different JSON values than we’ve traditionally received (i.e. Numbers where they used to be strings, objects where they used to be arrays). We couldn’t reproduce it locally for 6909, but were able to test and fix based on the user’s ti info output. In this case, we are guessing we used to get an array and now get an object, but without the output we don’t know where. Please run: {code} titanium info -t ios -o json {code} So we can generate a test case for it, and fix it.
| 3 |
2,193 |
TISTUD-6917
|
09/11/2014 22:05:04
|
Launching iOS simulator ignores the SDK version built into the simulator definition
|
I'm trying to debug an an 8.0 simulator by selecting one from the global toolbar. When I try to launch, it gives me: {code} Titanium Command-Line Interface, CLI version 3.4.0-rc2, Titanium SDK version 3.4.0.v20140829184521 Copyright (c) 2012-2014, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ Accepted values: [ERROR] : Invalid "--ios-version" value "7.1" 8.0 For help, run: titanium help build {code} We passed on 7.1 to the CLI, but the simulator is 8.0 explicitly. The offending code is in IOSNodeJSCommandsHelper#build. We grab the ios version and sim version from the launch config, and I don't think those use the values from the simulator/device. Later down in the code we grab the device id and get the simulator/device object, but don't use that object's stored version for either value.
| 5 |
2,194 |
TISTUD-6918
|
09/12/2014 06:22:56
|
Studio doesn't install all the components in one attempt If it installs Node
|
Studio doesn't install all components in one attempt if It needs to install node. We need to check for Appcelerator updates 2nd time to install remaining components. Same behavior is observed in 3.3.0 GA as well. I found some NPEs in Studio Log. Please refer attachment *studio_log3.4.0.txt* for more info. h5. Steps to Reproduce 1. Unistall node, npm, and npm packages from your machine {code} sudo npm uninstall npm -g sudo rm /usr/local/bin/node sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.* {code} 2. Open the Studio and check for Appcelerator Updates (It will show all the components to be installed. Please see attachment *First_Update.png* for more info) 3. Install the components. 4. Check in CLI for installation (for eg: node -v, npm -v, ti -v, alloy -v) h5. Actual Result Only Node and NPM are installed. Alloy, Titanium and ACS are not installed. If you check for Appc-Updates again, you can see the result as in attachment *Second_Update.png*. h5. Expected Result All components should be installed at one attempt. h5. Another Consecutive scenario triggered by this issue When I try to check updates second time (see attachment *Second_Update.png*), Studio 3.4.0 RC fails with following error log. There was no explicit error dialogs. {code} !ENTRY com.aptana.core 4 1 2014-09-12 13:06:10.363 !MESSAGE sudo: a password is required {code} It didn't allow me to install alloy and CLI components from studio. But I tried the same thing in Studio 3.3.0, It *succeeded in second attempt.* (!) So this part could be *regression*.
| 5 |
2,195 |
TISTUD-6920
|
09/12/2014 08:54:50
|
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.
| 5 |
2,196 |
TISTUD-6924
|
09/12/2014 14:35:50
|
NPE in IOSSDKLocator with cached v1 ti info output
|
I'm getting an NPE in my dev environment. IOSSDKLocator is loading a cached copy of ti info output, and apparently it's really old (using v1 detect output). We get an NPE on line 188 with this input.
| 3 |
2,197 |
TISTUD-6930
|
09/15/2014 16:04:46
|
Content Assist: Alloy: Show Object instance methods for $
|
The content assist does not shown Object instance methods for $ in controller files. This is a regression as the issue does not occur in studio 3.3.0 Steps to Reproduce: 1. Create an Alloy project 2. Copy the below xml code in index.xml {code} <Alloy> <TabGroup id='tabgroup'> <Tab id='tab1'> <Window class="container"> <View id='view'> <Label id="label">Hello, World</Label> <Button id="button" onClick="doClick">Click</Button> </View> </Window> </Tab> </TabGroup> </Alloy> {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 |
2,198 |
TISTUD-6931
|
09/15/2014 16:38:45
|
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 |
2,199 |
TISTUD-6933
|
09/16/2014 06:25:25
|
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: at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:253) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327) at com.aptana.projects.wizards.AbstractNewProjectWizard.doCreateProject(AbstractNewProjectWizard.java:321) at com.aptana.projects.wizards.AbstractNewProjectWizard$2.run(AbstractNewProjectWizard.java:374) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: java.lang.NullPointerException at com.appcelerator.titanium.core.internal.cli.NodeTitaniumSDKCommandsHandler.createModuleProject(NodeTitaniumSDKCommandsHandler.java:222) at com.appcelerator.titanium.ui.ide.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:254) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:300) at 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 at com.appcelerator.titanium.core.internal.cli.NodeTitaniumSDKCommandsHandler.createModuleProject(NodeTitaniumSDKCommandsHandler.java:222) at com.appcelerator.titanium.ui.ide.wizard.NewMobileModuleProjectWizard.finalizeProjectCreation(NewMobileModuleProjectWizard.java:254) at com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:300) at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:249) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327) at com.aptana.projects.wizards.AbstractNewProjectWizard.doCreateProject(AbstractNewProjectWizard.java:321) at com.aptana.projects.wizards.AbstractNewProjectWizard$2.run(AbstractNewProjectWizard.java:374) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code}
| 5 |
2,200 |
TISTUD-6938
|
09/17/2014 00:49:25
|
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 |
2,201 |
TISTUD-6940
|
09/17/2014 18:52:07
|
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 |
2,202 |
TISTUD-6941
|
09/18/2014 10:44:49
|
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 |
2,203 |
TISTUD-6944
|
09/22/2014 04:49:52
|
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 |
2,204 |
TISTUD-6949
|
09/23/2014 21:21:10
|
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 |
2,205 |
TISTUD-6954
|
09/25/2014 01:22:14
|
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 [email protected] installed on their machine, the even though the update stream references to RC stream, Studio does not prompt for [email protected] release.
| 5 |
2,206 |
TISTUD-6957
|
09/25/2014 19:27:54
|
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 |
2,207 |
TISTUD-6961
|
09/26/2014 19:16:10
|
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 at org.jruby.util.OSEnvironment.getAsMapOfRubyStrings(OSEnvironment.java:90) at org.jruby.util.OSEnvironment.getSystemPropertiesMap(OSEnvironment.java:75) at org.jruby.RubyGlobal.defineGlobalEnvConstants(RubyGlobal.java:393) at org.jruby.RubyGlobal.createGlobals(RubyGlobal.java:358) at org.jruby.Ruby.init(Ruby.java:1078) at org.jruby.Ruby.newInstance(Ruby.java:186) at org.jruby.embed.internal.SingletonLocalContextProvider.getRuntime(SingletonLocalContextProvider.java:95) at org.jruby.embed.internal.EmbedRubyRuntimeAdapterImpl.runParser(EmbedRubyRuntimeAdapterImpl.java:166) at org.jruby.embed.internal.EmbedRubyRuntimeAdapterImpl.parse(EmbedRubyRuntimeAdapterImpl.java:93) at org.jruby.embed.ScriptingContainer.parse(ScriptingContainer.java:1163) at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1223) at com.aptana.scripting.ScriptingEngine.getInitializedScriptingContainer(ScriptingEngine.java:292) at com.aptana.scripting.model.ScriptLoadJob.run(ScriptLoadJob.java:76) at com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:144) at com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:180) at com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:274) at com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:243) at com.aptana.scripting.model.BundleManager.loadScript(BundleManager.java:2032) at com.aptana.scripting.model.BundleManager$BundleLoadJob.run(BundleManager.java:129) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 5 |
2,208 |
TISTUD-6965
|
09/29/2014 20:10:27
|
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 |
2,209 |
TISTUD-6968
|
09/30/2014 23:45:46
|
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 |
2,210 |
TISTUD-6972
|
10/02/2014 20:24:35
|
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.