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,011 |
TISTUD-6396
|
05/01/2014 18:23:40
|
Create/Modify build job for building online installer
|
We have build jobs for the windows installers for the fat installer. We either need to clone those to create a job for building the thin installer, or we need to modify the existing jobs to generate both.
| 8 |
2,012 |
TISTUD-6397
|
05/01/2014 18:24:19
|
Modify the sync job(s) to push online installer artifacts to same location as "fat" installer
|
If the thin installer is generated as part of a separate job (or even with the normal jobs) we may need to modify our sync scripts to copy over the thin installer files (the MSI and EXE).
| 5 |
2,013 |
TISTUD-6402
|
05/02/2014 19:02:11
|
Error enabling Appcelerator services during app creation
|
When creating the default app, I encountered the error during enabling of appcelerator services. Please, see the attachment. Note: I noticed Environment choice(screenshot), which is not working.
| 3 |
2,014 |
TISTUD-6403
|
05/02/2014 21:05:39
|
Alloy: TSS undefined value should be accepted
|
h5. New Feature description As per https://jira.appcelerator.org/browse/ALOY-822 , undefined is now accepted as a TSS value. For example, {code} '#index': { backgroundColor: '#fff', modal: undefined } {code} is now valid. Studio shouldn't therefore display the Syntax Error warning when undefined is used as a property for TSS styles.
| 5 |
2,015 |
TISTUD-6410
|
05/05/2014 23:03:06
|
BlackBerry: Missing device IP address option
|
When trying to set BB Run configuration in Studio Preferences, there is only option for IP address is Simulator. 3.2.3 Studio has both Simulator and Device.
| 5 |
2,016 |
TISTUD-6419
|
05/07/2014 23:35:11
|
BlackBerry: Cannot build for device from Studio
|
I cannot build default project for device, using Studio. Studio log does not have any output, but "Unhandled event loop exception" attached in log.txt The buid command works in CLI. I am able to launch BB simulator. h5.To reproduce: 1. Create a default project 2. Set IP address and password for BB device in Studio preferences 3. Build for device h5. Unhandled event loop exception
| 3 |
2,017 |
TISTUD-6420
|
05/07/2014 23:51:58
|
Alloy: warnings relative to Custom TSS styles not being used should not be displayed
|
h5. Problem description Studio is displaying warning messages also for CustomTSS conditionals in Styles. See new feature: ALOY-871 h5. Steps to reproduce 1. Create an Alloy project and use the following code: h6. alloy.js {code} Alloy.Globals.someProperty = true; {code} h6. index.xml {code} <Alloy> <Window> <Label id="title1" class="label"/> </Window> </Alloy> {code} h6. index.tss {code} "Window":{ layout:"vertical", backgroundColor:'white', top:20 } /* Class selector applied to labels of class=label */ ".label": { color: 'blue' } /* Component selector applied to all labels, though will be overridden */ "Label":{ top:10, text: "Default label text", font: { fontSize: '14dp' } } /* Custom TSS overrides component and class selectors if someProperty is true */ "Label[if=Alloy.Globals.someProperty]":{ text: "Custom TSS: Alloy.Globals.someProperty==true" } {code} 2. Check styles.tss file Result: Studio is displaying a warning next to CustomTSS style (see screenshot too). Expected results: CustomTSS styles queries should probably be ignored or handled differently.
| 5 |
2,018 |
TISTUD-6424
|
05/08/2014 18:30:28
|
Constant error "Uploading debug symbols" after Packaging for iOS
|
I had an existing project with Appcelertor services enabled. h5. To reproduce 1. Package iOS iTunes Store 2. Package iOS Adhoc/Enterprise h5. Actual result Application packaged and can be installed and run on devices However, there is the error uploading debug symbols (see attached) It happens each time you package the app.
| 5 |
2,019 |
TISTUD-6426
|
05/08/2014 21:52:18
|
NPE while opening update wizard during startup
|
During the startup of Studio, there is an error while showing the Titanium update wizard. java.lang.NullPointerException at java.net.URI$Parser.parse(URI.java:3004) at java.net.URI.<init>(URI.java:577) at java.net.URI.create(URI.java:839) at com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.getReleaseNotesURI(DefaultReleaseNotesProvider.java:77) at com.appcelerator.titanium.update.core.DefaultReleaseNotesProvider.getReleaseNotes(DefaultReleaseNotesProvider.java:88) at com.appcelerator.titanium.update.core.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:131) at com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:456) at com.appcelerator.titanium.update.ui.internal.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:521) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:432) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) at com.appcelerator.titanium.update.ui.internal.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:99)
| 3 |
2,020 |
TISTUD-6427
|
05/08/2014 22:13:11
|
Module Package options are broken in studio 3.3.0.201405011408 , for modules built with 3.3.0 sdk
|
h5. This is a regression. We can see package options for module in 3.2.3 studio created with 3.3.0 sdk. h5.Description: 1. Create a module (any platform) with latest 3.3.0 sdk or mentioned in the description. 2. After its created, try to package it. h5.Actual Results: 1. We do not see any options for packaging modules. All options are greyed out. This is only seen when the module is built with 3.3.0 sdk in studio 3.3.0. If we build a module with 3.2.3 sdk in 3.3.0 studio we can see packaging options. h5.Expected Result: 1. We should see packaging options for modules.
| 5 |
2,021 |
TISTUD-6430
|
05/09/2014 09:33:34
|
Default Titanium Studio Theme not selected on first launch
|
This is not a regression since it occurs on 3.2.3 build also. Default Titanium Studio Theme does not appears to be selected any of the radio button of Light or dark on launching the studio for the first time. However, Titanium Studio UI shows correct radio button selected by default. Note: Once we select any of the radio button either light or dark and on restarting the studio, previously selected theme gets retained. Please refer to the attached screenshot for your reference.
| 5 |
2,022 |
TISTUD-6432
|
05/09/2014 12:00:03
|
Intermittent: Appcelerator Services gets automatically disabled after restarting Studio
|
Test Steps: 1.Create a project with appcelerator services enabled. 2.Observe Tiapp Editor and make sure all the sevices must be enabled. 3.Restart Studio. 4.Reopen Tiapp Editor of the same app created in first step. Actual Result: Appcelerator Services gets automatically disabled on Tiapp Editor after restarting Studio.
| 5 |
2,023 |
TISTUD-6695
|
05/09/2014 14:04:42
|
Remember username (and password) and go directly to login screen on launch
|
I suggest that the first screen a user sees when launching Studio is the login screen. The screen asking about having an account already or not is really only important first time you launch Studio - next time you just want to log in ;-) Next, it would be very nice if Studio could remember the last user id I have entered (and ideally also the password - if I choose). That would make it a lot smoother to log into Studio.
| 1 |
2,024 |
TISTUD-6434
|
05/09/2014 15:56:26
|
Add code coverage to development branch builds (not just nightlies)
|
We currently record code coverage for nightly builds and PHP/Ruby. We should add code coverage to the normal development branch builds: - studio3-core-development - appcelerator-core-development - titanium-core-development
| 3 |
2,025 |
TISTUD-6435
|
05/09/2014 15:57:44
|
Enforce code coverage doesn't drop for normal development builds
|
Once we have code coverage recorded for the three normal builds that run unit tests, we should enforce the coverage never drops like we do for nightlies. This way we can catch if a commit will break the build because of this earlier in the process.
| 2 |
2,026 |
TISTUD-6436
|
05/09/2014 15:58:16
|
Add code coverage to PR builders
|
We should enable tracking code coverage on the PR builders.
| 3 |
2,027 |
TISTUD-6437
|
05/09/2014 15:59:18
|
Enforce that PR builders code coverage doesn't drop or they fail
|
Once the mainline builds and PR builders are recording code coverage results, we should enforce that the PR doesn't pass unless it builds, passes all the tests and doesn't drop coverage from the current level on the target merge branch.
| 5 |
2,028 |
TISTUD-6438
|
05/09/2014 16:30:04
|
Switch to using Findbugs rank over priority
|
Findbugs (and the Jenkins plugin) defaults to using "priority" for sorting issues into high/normal/low. The reality is that "priority" was defined as closer to "confidence level" in the way it's used. With Findbugs 2.0 they introduced "rank" which is the notion of how "scary" a bug is. I'd argue that's a better thing for us to track and determine the high/normal/low values and thresholds to use. The plugin doesn't let you change how the mapping is done, so I looked at the source and it appears to be: 1-4: High 5-9: Normal 10+: Low. (Compare this to Findbugs definition: scariest (rank 1-4), scary (rank 5-9), troubling (rank 10-14), and of concern (rank 15-20).)
| 2 |
2,029 |
TISTUD-6449
|
05/10/2014 04:44:14
|
"Unknow request parameter type" when creating a new OpenShift application
|
1. Install the latest OpenShift Plugin (you will need to install Ruby and PHP first) from http://preview.appcelerator.com/appcelerator/studio/openshift/update/stable-new 2. Create a New PHP or Rack project 3. Get error "Unknow request parameter type integer" I believe this _may_ be fixed by an update to the OpenShift library: https://github.com/openshift/openshift-java-client/pull/71/files
| 5 |
2,030 |
TISTUD-6450
|
05/10/2014 04:46:10
|
Create builder for OpenShift plugin
|
It appears that the OpenShift Jenkins builder is no more. We should re-createdit.
| 3 |
2,031 |
TISTUD-6451
|
05/10/2014 05:32:54
|
Titanium Studio 3.2.3: "can't be opened because it is from an unidentified developer"
|
h5.Description Trying to open Titanium Studio 3.2.3.GA will fail due to a signing issue. A warning will appear telling the user that the software is unidentified and therefore will not be opened h5.Steps To Reproduce 1. Download the following file: http://titanium-studio.s3.amazonaws.com/latest/Titanium_Studio.dmg 2. Attempt to run the application +Make sure that your security settings are set to default in system preferences. It should be set to "App Store and Identified Developers"+ h5.Expected Result A warning to tell the user the risk of opening the software, or open without a prompt. h5.Actual Result Warning states that the user cannot open the file due to the risk Note. You _may_ have already created an exception for Titanium Studio. you have to revoke it: For example: {code} # List the rules sudo spctl --list --type execute 3512[UNLABELED] P0 allow execute [/Applications/Titanium Studio/TitaniumStudio.app] cdhash H"da9cced6cbb48fd8f6837ea67720ebe5a14717fc" or cdhash H"5b0667814e309d89caebefb4f0745755a2b3a63e" # remove the rule in question sudo spctl --remove --rule 3512 {code}
| 5 |
2,032 |
TISTUD-6454
|
05/12/2014 09:24:29
|
Titanium Studio creates recursive folder on startup
|
Titanium Studio creates an deep structured, non-sense folder, see attachment. Titanium Studio has updated the SDK to 3.2.3, but always checks and receives an update notification for sdk 3.2.3, node.acs 1.0.14 and alloy 1.3.1.
| 5 |
2,033 |
TISTUD-6455
|
05/12/2014 15:45:35
|
Move Openshift code out to separate repo
|
We currently have the openshift code in the titanium core repo. It has no dependencies on titanium at all right now (just studio3 core), and it's highly inactive in terms of development. We also don't ship it as part of titanium studio. We should just move it out to it's own repo so it doesn't constantly rebuild when we do checkins related to titanium.
| 5 |
2,034 |
TISTUD-6456
|
05/12/2014 15:47:12
|
Move Testflight out to it's own repo
|
Testflight is a separate feature and one we don't ship in titanium by default. It should be moved out to its own repo so it doesn't constantly rebuild when we check in to titanium core.
| 5 |
2,035 |
TISTUD-6457
|
05/12/2014 15:48:10
|
Move Nukona out to it's own repo
|
Nukona is a separate feature and one we don't ship in titanium by default. It should be moved out to its own repo so it doesn't constantly rebuild when we check in to titanium core. I'm not even sure it does anything right now.
| 5 |
2,036 |
TISTUD-6458
|
05/13/2014 00:54:41
|
Import sample project shows two contributions of enabling Appcelerator Services
|
The samples import wizard now shows two contributions to enable Appcelerator Services. Seems the new extra contribution is coming from NodeJS services contribution.
| 5 |
2,037 |
TISTUD-6490
|
05/15/2014 01:49:52
|
Studio passes older sdk in the build command even though sdk version in tiapp has been changed.
|
h5.Description: 1. Create any app with latest 3.3.0 sdk. 2. Change the sdk in tiapp.xml to any other build. 3. Build & run on device/emulator. h5.Actual Result: 1. In the console logs we see the previous sdk set being user rather than the new one. 2. If you save & run the app again we see that it uses the latest sdk set in the tiapp.xml. 3. E.g If I create an app with latest 3.3.0 sdk , change the sdk to 3.2.3 in tiapp.xml & build it, studio passes the 3.3.0 sdk as below: {code} Process: "/usr/local/bin/titanium" "--no-colors" "--no-progress-bars" "--no-prompt" "build" "--platform" "android" "--log-level" "trace" "--sdk" "3.3.0.v20140514121712" "--target" "emulator" "--android-sdk" "/Users/lokeshchoudhary/Desktop/android-sdk-macosx" "--device-id" "Android_4.4.2" "--skip-js-minify" "--skip-js-minify" {code} h5. Expected Result: 1. Studio should reflect the sdk changes made in the tiapp.xml
| 5 |
2,038 |
TISTUD-6495
|
05/15/2014 02:23:02
|
Debugging doesn't suspend breakpoints with liveview
|
When an app is launched in debug mode along with liveview, then the breakpoints are not suspended either for Alloy app or classic app.
| 8 |
2,039 |
TISTUD-6496
|
05/15/2014 02:32:14
|
Alloy commands in the 'New' menu are not correctly displayed
|
h5. Problem description Alloy command in the 'New' menu are displayed incorrectly. h5. Steps to reproduce Go into a project and right-click on any file in the project. Go to 'New' Result: List of possible options is displayed. Alloy commands are displayed incorrectly - see attached screenshot.
| 3 |
2,040 |
TISTUD-6498
|
05/15/2014 02:39:07
|
Alloy commands in the 'New' menu are not correctly displayed
|
h5. Problem description Alloy command in the 'New' menu are displayed incorrectly. h5. Steps to reproduce Go into a project and right-click on any file in the project. Go to 'New' Result: List of possible options is displayed. Alloy commands are displayed incorrectly - see attached screenshot.
| 3 |
2,041 |
TISTUD-6501
|
05/15/2014 19:35:48
|
Update the release notes with the new format template
|
Doc team is currently working on coming up with the new format templates for displaying the release notes in the update wizard. Currently Studio has their own formatting template, but Doc team is coming up a template that will make the release notes unified and consistent.
| 3 |
2,042 |
TISTUD-6503
|
05/15/2014 22:31:25
|
MobileIron Plugin: Cannot publish to MobileIron after you package for Android Store
|
ENVIRONMENT: Appcelerator Studio, build: 3.3.0.201405121247 Appcelerator Mobile Iron Integration 1.0.0.1396893006-3--59KDJJBAC9 Mac OS X 10.8.5 CLI version 3.3.0-dev Titanium SDK version 3.3.0.v20140512124113 REPRODUCTION: Package an application for the Android App Store. Package an application for MobileIron with an Android target RESULTS: Packaging for MobileIron with an Android target fails with the following alert dialog message: Attribute ATTR_MINIFY is not of type boolean. OTHER INFO: Initially was testing to make sure that packaging for the Android App Store worked. When packaging earlier for MobileIron with an Android target, the command was putting the keystore password in for the alias option. Restarting Studio had no effect, but switching workspaces did.
| 3 |
2,043 |
TISTUD-6504
|
05/16/2014 00:01:49
|
MobileIron Plugin: Fails to upload Android App to Mobile Iron
|
ENVIRONMENT: Appcelerator Studio, build: 3.3.0.201405121247 Appcelerator Mobile Iron Integration 1.0.0.1396893006-3--59KDJJBAC9 Mac OS X 10.8.5 CLI version 3.3.0-dev Titanium SDK version 3.3.0.v20140512124113 REPRODUCTION: Package an application for MobileIron with an Android target RESULTS: Application builds and a package is created, but fails to upload to MobileIron. Studio displays the following alert dialog message: No message body writer has been found for response class RuntimeException.
| 5 |
2,044 |
TISTUD-6505
|
05/16/2014 12:06:41
|
UI difference in Studio for creating Alloy controller, migration, model, view, style and widget
|
This is a regression. Test Steps : 1. Create an alloy project. 2.Select the project and launch File > New > Alloy Controller .Observe the UI. Actual Result : UI difference noticed. Screenshot attached.
| 3 |
2,045 |
TISTUD-6526
|
05/17/2014 00:17:14
|
Geocoder: Android: Alloy sample is crashing after filling an address
|
h5. Problem description Geocoder Alloy sample on Android is crashing when filling in an address. Reproducible only with Alloy 1.4.0 - so is a regression h5. Steps to reproduce 1. From Studio, import the Geocoder sample app. 2. Edit tiapp.xml and remove targetSdkVersion (looged a separate ticket: https://jira.appcelerator.org/browse/ALOY-1020) 3. Run the sample on Android (tested on Google Nexus Galaxy 4.3) 4. Click on the textfield and search for an Address Result: app crashes Crash log: {code} [WARN] : dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x415cf700) [DEBUG] : HTTPClient: The persistent handle is disposed. [ERROR] : Crittercism: java.lang.ClassCastException: ti.map.AnnotationProxy cannot be cast to ti.modules.titanium.map.AnnotationProxy [ERROR] : Crittercism: at ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:273) [ERROR] : Crittercism: at ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:242) [ERROR] : Crittercism: at com.google.android.maps.ItemizedOverlay.populate(ItemizedOverlay.java:309) [ERROR] : Crittercism: at ti.modules.titanium.map.TiMapView$TitaniumOverlay.setAnnotations(TiMapView.java:265) [ERROR] : Crittercism: at ti.modules.titanium.map.TiMapView.doSetAnnotations(TiMapView.java:953) [ERROR] : Crittercism: at ti.modules.titanium.map.TiMapView.doUpdateAnnotations(TiMapView.java:714) [ERROR] : Crittercism: at ti.modules.titanium.map.TiMapView.handleMessage(TiMapView.java:603) [ERROR] : Crittercism: at android.os.Handler.dispatchMessage(Handler.java:95) [ERROR] : Crittercism: at android.os.Looper.loop(Looper.java:137) [ERROR] : Crittercism: at android.app.ActivityThread.main(ActivityThread.java:5103) [ERROR] : Crittercism: at java.lang.reflect.Method.invokeNative(Native Method) [ERROR] : Crittercism: at java.lang.reflect.Method.invoke(Method.java:525) [ERROR] : Crittercism: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737) [ERROR] : Crittercism: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) [ERROR] : Crittercism: at dalvik.system.NativeStart.main(Native Method) [DEBUG] : dalvikvm: GC_CONCURRENT freed 1456K, 9% free 15722K/17216K, paused 3ms+4ms, total 39ms [DEBUG] : dalvikvm: WAIT_FOR_CONCURRENT_GC blocked 21ms [ERROR] : TiApplication: (main) [261349,262305] Sending event: exception on thread: main msg:java.lang.ClassCastException: ti.map.AnnotationProxy cannot be cast to ti.modules.titanium.map.AnnotationProxy; Titanium 3.3.0,2014/05/16 00:25,df56177 [ERROR] : TiApplication: java.lang.ClassCastException: ti.map.AnnotationProxy cannot be cast to ti.modules.titanium.map.AnnotationProxy [ERROR] : TiApplication: at ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:273) [ERROR] : TiApplication: at ti.modules.titanium.map.TiMapView$TitaniumOverlay.createItem(TiMapView.java:242) [ERROR] : TiApplication: at com.google.android.maps.ItemizedOverlay.populate(ItemizedOverlay.java:309) [ERROR] : TiApplication: at ti.modules.titanium.map.TiMapView$TitaniumOverlay.setAnnotations(TiMapView.java:265) [ERROR] : TiApplication: at ti.modules.titanium.map.TiMapView.doSetAnnotations(TiMapView.java:953) [ERROR] : TiApplication: at ti.modules.titanium.map.TiMapView.doUpdateAnnotations(TiMapView.java:714) [ERROR] : TiApplication: at ti.modules.titanium.map.TiMapView.handleMessage(TiMapView.java:603) [ERROR] : TiApplication: at android.os.Handler.dispatchMessage(Handler.java:95) [ERROR] : TiApplication: at android.os.Looper.loop(Looper.java:137) [ERROR] : TiApplication: at android.app.ActivityThread.main(ActivityThread.java:5103) [ERROR] : TiApplication: at java.lang.reflect.Method.invokeNative(Native Method) [ERROR] : TiApplication: at java.lang.reflect.Method.invoke(Method.java:525) [ERROR] : TiApplication: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737) [ERROR] : TiApplication: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) [ERROR] : TiApplication: at dalvik.system.NativeStart.main(Native Method) [INFO] : Process: Sending signal. PID: 8929 SIG: 9 {code} Not reproducible using Alloy version 1.3.1
| 5 |
2,046 |
TISTUD-6507
|
05/17/2014 04:27:04
|
Prompt to update after changing the stream in updates preference
|
If users change the build stream at Preferences > Studio > Updates., then user has to manually select the option from Help > Check for Appcelerator Updates to get the latest build updates. Since we are already accommodating the updating in Studio now, we should prompt to check for updates once user changes the stream.
| 5 |
2,047 |
TISTUD-6508
|
05/19/2014 09:53:20
|
Studio: Shows NullPointerException error on Refresh Devices when Android SDK is not configured
|
Pr-requisite - Android SDK was not configured Steps - 1. Launch Studio 2. Don’t configure Android SDK. Only iOS and Blackberry SDK had shown configured. 3. Create a default classic project from Studio. 4. Select the created project. 5. Select “Refresh Devices” option from shortcut launch menu (See the attached screen shot) Actual Result - Shows NullPointerException error message. See the attached screen shot and log file. Expected Result - Should not show NullPointerException error message while refreshing devices.
| 3 |
2,048 |
TISTUD-6510
|
05/19/2014 10:50:07
|
Android Module packaging to a project is throwing java.lang.reflect.InvocationTargetException
|
This is a regression issue. It didn't happen in 3.2.3 release. Precondition: Add Android NDK in Studio preferences path. Install gperf and make sure its in your path. I have Platform 10 and platform 19 Google API intalled. Test Steps: 1. Create an android module. 2. Package it to a mobile project. Actual Result: Error occurs. Screenshot and logs attached. {code} !MESSAGE Error within Debug UI: !STACK 0 java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275) at org.eclipse.ui.internal.progress.ProgressManager$3.run(ProgressManager.java:960) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:995) at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:970) at org.eclipse.debug.internal.ui.DebugUIPlugin.launchInForeground(DebugUIPlugin.java:1112) at org.eclipse.debug.ui.DebugUITools.launch(DebugUITools.java:759) at com.appcelerator.titanium.ui.module.AbstractModulePackagingWizard.performFinish(AbstractModulePackagingWizard.java:82) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at com.appcelerator.titanium.android.internal.ui.launching.distribution.AndroidModulePackageHandler.execute(AndroidModulePackageHandler.java:34) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at com.appcelerator.titanium.ui.launching.AbstractPackagingLaunchShortcut.launch(AbstractPackagingLaunchShortcut.java:47) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:434) at com.appcelerator.titanium.ui.LaunchAppToolbarContribution$3.widgetSelected(LaunchAppToolbarContribution.java:390) 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.Widget.sendEvent(Widget.java:1057) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) Caused by: java.lang.NullPointerException at com.appcelerator.titanium.android.internal.ui.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:82) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1104) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.NullPointerException at com.appcelerator.titanium.android.internal.ui.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:82) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1104) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code}
| 3 |
2,049 |
TISTUD-6511
|
05/19/2014 10:58:52
|
Node.ACS: NPE while creating new node acs project
|
Getting NPE while creating new node acs project. Refer to attached screenshot and logs. {code} !ENTRY org.eclipse.ui 4 0 2014-05-19 15:03:29.825 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.eclipse.core.runtime.Path.append(Path.java:261) at com.appcelerator.titanium.acs.internal.ui.wizards.NewNodeACSProjectWizard.openIndexFile(NewNodeACSProjectWizard.java:118) at com.aptana.projects.wizards.AbstractNewProjectWizard.createAndRefreshProject(AbstractNewProjectWizard.java:432) at com.aptana.projects.wizards.AbstractNewProjectWizard.performFinish(AbstractNewProjectWizard.java:356) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:98) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: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:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) {code}
| 3 |
2,050 |
TISTUD-6514
|
05/19/2014 20:12:43
|
Allow selecting the base repo and branch for a pull request
|
We allow generating Pull Requests from a forked repo. It currently assumes a lot and I'm bumping against the limitations now. It assumes that the current branch is the "compare" on the current repo. That seems fine to keep. The problem is that we can't change the base, which is hard-coded to be the parent repo (that the fork came off of) and that repo's default branch. At the very least we should allow selecting the base branch. Ideally we'd also allow changing the base repo to any repo in the network of forks.
| 8 |
2,051 |
TISTUD-6516
|
05/19/2014 21:49:03
|
Timeout waiting for uploading debug symbols
|
Debug symbols upload error occurs, when the app first installed onto device, using Studio. h5. To reproduce: 1. I used the default classic app with: app.js {code} var win = Ti.UI.createWindow({ backgroundColor: 'white' }); var label = Ti.UI.createLabel({ text:"who is who "+Ti.Analytics }); win.add(label); win.open(); {code} The error occurs after the app is installed onto device h5. to work around uncheck the box "Enable Appcelerator Services" when creating a New Mobile App Project
| 8 |
2,052 |
TISTUD-6517
|
05/19/2014 22:40:43
|
Appcelerator Services: Test is not being enabled during project creation
|
h5. To reproduce 1. Create the default project, using Studio 2. Enable Appcelerator services h5. Actual result Test Service can be enabled manually only h5. Expected result Appcelerator services should be enabled during project creation
| 8 |
2,053 |
TISTUD-6521
|
05/20/2014 12:02:14
|
Studio: Default modules (com.appcelerator.apm, ti.cloud) are not showing under Modules section in tiapp.xml overview screen after creating the project
|
Steps - 1. Launch Studio 2. Create a default classic project. 3. Observed the Modules section on TiApp Editor Overview screen. Actual Result - No modules are showing under the Modules section. See the attached screen shot and log file. Note - Close the tiapp.xml file and reopen again. Now default modules (com.appcelerator.apm, ti.cloud) are showing under Modules section on TiApp Editor Overview screen Expected Result - Should show the default modules (com.appcelerator.apm, ti.cloud) under Modules section on TiApp Editor Overview screen.
| 5 |
2,054 |
TISTUD-6524
|
05/20/2014 19:13:59
|
ACS version error when creating new a Node.ACS app doesn't make sense
|
Steps: 1. File > New > Node.ACS project. 2. Give project a name and click Create. Results: ACS version error dialog appears (see attached) but the message seems a bit garbled and doesn't make much sense.
| 5 |
2,055 |
TISTUD-6533
|
05/21/2014 21:33:15
|
SDK Release has to extract the entire body release notes
|
Currently Studio depends on the xcode path class 'api-doc' for extracting the release notes content. There is no api-doc tag anymore for SDK release notes, so it should default to entire body contents. If we can't find the content in the expected tag, then we don't apply the template.
| 2 |
2,056 |
TISTUD-6534
|
05/21/2014 21:34:25
|
Studio release has to extract only from guide-container
|
The release notes of Studio should extract the contents from 'guide-container' class div, and then apply the style template.
| 2 |
2,057 |
TISTUD-6535
|
05/21/2014 23:06:13
|
BlackBerry: "Argument cannot be null" error on Run Configuration
|
h5. To reproduce 1. In Studio Project Explorer choose the project and Run configuration 2. Choose Appcelerator BlackBerry Simulator or Appcelerator BlackBerry Application Installer h5. Actual result An error has occurred. Argument cannot be null h5. Expected result To set the desirable configuration and run it
| 3 |
2,058 |
TISTUD-6537
|
05/22/2014 02:43:13
|
AirWatch: Add preference page
|
Add a preference page to allow Add, Edit or Delete the AirWatch publish targets. Though we have the basic infrastructure to create the pref page for publish providers, it might need to provide the table columns, label provider and publish target comparator.
| 8 |
2,059 |
TISTUD-6538
|
05/22/2014 02:45:55
|
AirWatch: Create a register publish provider dialog
|
Create a new register publish target dialog to allow users to input user/pwd/host/alias, similar to existing mobileiron register dialog.
| 5 |
2,060 |
TISTUD-6539
|
05/22/2014 02:48:11
|
AirWatch: Authenticate the given publish target
|
Once the user inputs the credential details in the register dialog, it would have created a publish target based on the credentials. However, we need to authenticate the target based on the user input and return the appropriate error message.
| 5 |
2,061 |
TISTUD-6542
|
05/22/2014 07:43:46
|
Studio: iOS SDK option does not show on Platform Configuration Wizard if Xcode is not installed on system
|
Pre-Requisite - Removed Xcode and Android SDK from System. Steps - 1. Launch Studio 2. Observe the SDK options available on Platform Configuration Wizard. Actual Result - iOS SDK option does not show on Platform Configuration Wizard. Only Android and BlackBerry SDK options are showing. See the attached screen shot. Expected Result - Should show the iOS SDK option on Platform Configuration Wizard. Note - Shows the iOS SDK on Platform Configuration Wizard if using Studio 3.2.3 GA
| 8 |
2,062 |
TISTUD-6543
|
05/22/2014 10:12:51
|
Mobile Web - files are not generated when packaging Mobile Web to new project
|
This is not a regression issue. Steps to reproduce: 1. Package default Titanium project for Mobile Web 2. Select "Create a new project for the Mobile Web app" 3. Open newly created Web project Actual: index.html does not appear in the web project created on packaging. Only 'Connection' appears down the folder hierarchy of the packaged web project. See attached screen shot and log file for more clarification. Expected: The packaged mobile web should contain the index.html in order to preview the app.
| 3 |
2,063 |
TISTUD-6548
|
05/23/2014 00:34:27
|
Studio installer version on Mac displays 3.0 despite being 3.3.0
|
h5.Description Studio displays version 3.0 for all installers of Titanium Studio and Appcelerator Studio. Tested back to Studio 2.1.2 and that also showed version 3.0. h5.Steps To Reproduce 1. Download the installer for Studio 2. Click on the Studio executable h5.Expected Result Should show the correct version number h5.Actual Result Shows version 3.0 +Extra Information+ Checking the executable information (cmd + i) shows the copyright information in the version field. and the actual version is not shown anywhere. Attached screenshots of the Studio executable version and the executable info window. This is not a regression.
| 5 |
2,064 |
TISTUD-6549
|
05/23/2014 07:40:58
|
MobileWeb: Package MobileWeb Project wizard shows "OK" after selecting location path
|
This is a Regression since it does not occur in 3.2.3.GA build. While packaging mobile app project for Mobileweb, text “Package the mobile web application” is replaced by “OK” on selecting the Location path. Steps to Reproduce: 1. Create a default project. 2. Package to Mobile web. Actual Result: Text "Package the mobile web application” is replaced by “OK” on selecting the Location path. Expected Result: Text "Package the mobile web application” should not get change after selecting the location. Refer to the attached screenshots for your reference.
| 3 |
2,065 |
TISTUD-6552
|
05/23/2014 18:26:35
|
Download and index Node.js core modules for user (for version they have)
|
We do support Node/NPM fairly well and can handle module require's decently. But one big hole in our support is that we don't try and force the user to grab the Node.js sources for the version they're using and index those core modules (where we can). This means we can't jump to core modules or give any useful content assist on them.
| 8 |
2,066 |
TISTUD-6556
|
05/28/2014 12:20:03
|
Debugger Exception: No "android-10" or "android-2.3.3" in the Android SDK in the device console log
|
Steps Followed: 1. Create a Titanium project and debug it on a device. Actual Result: The debug process is completed successfully and the breakpoints are also hit. But the device console logs show some Android 2.3.3 dependency error. Note: The same error is observed for profiler also. Also if Android 2.3.3 or API level 10 is installed than this error does not occur. {code} Traceback (most recent call last): File "/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/builder.py", line 2497, in <module> launch_logcat() File "/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/builder.py", line 124, in launch_logcat adb_location = AndroidSDK(android_sdk_location).get_adb() File "/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/androidsdk.py", line 49, in __init__ self.set_api_level(api_level) File "/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/androidsdk.py", line 53, in set_api_level self.find_platform_dir() File "/Users/shreya.chowbey/Library/Application Support/Titanium/mobilesdk/osx/3.3.0.v20140524224144/android/androidsdk.py", line 131, in find_platform_dir raise Exception("No \"%s\" or \"%s\" in the Android SDK" % ('android-%s' % api_level, android_api_levels[api_level])) Exception: No "android-10" or "android-2.3.3" in the Android SDK {code}
| 5 |
2,067 |
TISTUD-6561
|
05/29/2014 17:59:51
|
After building, Studio is still showing 'Launching delegate' in progress
|
h5. Problem description After building an application, it could happen that the app is built and runs fine, but Appc-Studio seems to be still doing something in the background - specifically, ‘Launching delegate’, displaying an ongoing activity in the bottom-right corner, staying stuck at 57%. h5. Steps to reproduce 1. Create an iOS app and build for iOS device Result: app is built and run correctly. However, in the bottom-right corner of Studio, there is an ongoing process (see Screen Shot 2014-05-28). Expected result: Studio should show no ongoing process. 2. Click on the bottom-right progress bar Result: Progress window is displayed, showing details on the ongoing process ("Launching delegate" progress information is shown). See Screen Shot 2014-05-28. Expected result: no ongoing Studio progress should be shown. See the attached screenshots 3. Perform further actions on the app project (build, clean workspace etc...) Result: It is actually possible then to do everything (build, clean workspaces etc…). It seems Studio is not really hang in there, but it shows to stay in the state as shown in the screenshots. So far has been reproduced when building/running an App on iOS device. h5. Additional notes It seems there could be a memory issue too - still not sure if related to this, but at the time of writing and while experiencing the described behavior, checking Activity Monitor, Appc-Studio is using ~400MB of memory which seems to be too much. Investigating.
| 5 |
2,068 |
TISTUD-6574
|
05/29/2014 21:09:39
|
NPE on a project creation when no SDKs are installed
|
When trying to create a default project using Studio, we get java.lang.NullPointerException in the log. No project is being created. {code} java.lang.NullPointerException at com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectCreationPage.validatePlatforms(NewMobileProjectCreationPage.java:281) at com.appcelerator.titanium.ui.ide.wizard.NewMobileProjectCreationPage.createControl(NewMobileProjectCreationPage.java:224) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:432) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) at org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:95) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) {code} To work around check for appcelerator updates and accept required installs.
| 3 |
2,069 |
TISTUD-6576
|
05/29/2014 23:46:58
|
3.3.0 Studio Installer: Studio is installed in the wrong location
|
h5.Description The 3.3.0 Studio installer downloads the temporary files into the AppData folder. After the temp files have been obtained it moves the entire program into the Program Files folder. Once all the files have been moved it attempts to remove the temp files, but fails to remove the root folder in the AppData location, only the files inside it. h5.Steps to Reproduce 1. Download the 3.3.0 Studio offline installer. 2. Install the program. 3. Check your AppData/roaming folder 4. Check your Program Files folder h5.Expected Result Studio should be installed in the AppData folder h5.Actual Result Studio is installed in the Program Files folder, leaving unused files and folders inside the AppData location.
| 5 |
2,070 |
TISTUD-6577
|
05/29/2014 23:53:53
|
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 |
2,071 |
TISTUD-6578
|
05/30/2014 16:22:04
|
Update content assist to support FixedSpace tag
|
Alloy 1.4 adds support for shortcut notation for a fixed space button. <FixedSpace> is a shortcut for <Button systemButton=“Ti.UI.iPhone.SystemButton.FIXED_SPACE>. This is supported on iOS only.
| 5 |
2,072 |
TISTUD-6579
|
05/30/2014 16:24:01
|
Update content assist to support shorthand notation for left and right navigation buttons
|
Alloy 1.4 adds support for horthand notation for left/right navigation buttons (<RightNavButton title=“foo”/> rather than <RightNavButton><Button title=“foo”/></RightNavButton>). This feature is supported on iOS only.
| 5 |
2,073 |
TISTUD-6580
|
05/30/2014 16:29:07
|
Alloy: enable developers to create new widget components
|
Alloy 1.4 adds a new {{alloy generate}} command that can be used to create widget components (controllers, styles). This should be exposed to developers. Currently, a developer can right-click a folder within an Alloy project, choose New, and create a new Alloy component. With this ticket, we'd add the ability to right-click a folder within a widget, and create a new component within that widget.
| 5 |
2,074 |
TISTUD-6581
|
05/30/2014 16:30:54
|
Update content assist to support setting ActionBar properties via the Menu tag
|
Alloy 1.4 adds support for setting Android ActionBar properties (title, subtitle, etc.) as attributes of the <Menu> tag. This change affects Android only.
| 8 |
2,075 |
TISTUD-6582
|
05/30/2014 16:34:14
|
Update content assist to support shorthand notation for keyboard and return key types
|
Alloy 1.4 adds support for using shorthand notation for keyboard and return key types in TextField and TextArea . For example, you can use {{textField.keyboardType=default}} or {{DEFAULT}} (case-insensitive) instead of {{Ti.UI.KEYBOARD_TYPE_DEFAULT}}. This is supported in XML and TSS on all platforms.
| 8 |
2,076 |
TISTUD-6584
|
06/02/2014 11:12:37
|
Importing sample apps from Dashboard or Samples gives intermittent 'Auto-share exception'
|
Importing sample apps from Studio Dashboard or from Samples window intermittently gives 'Auto-share exception'. Although the sample gets imported successfully but there is an exception prompt and also log file shows some exception trace. Please observe the attached screen shot and log file for more clarification. {code} TRY org.eclipse.core.jobs 4 2 2014-06-02 15:21:20.621 !MESSAGE An internal error occurred during: "Auto-share". !STACK 0 java.util.concurrent.RejectedExecutionException at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1774) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:768) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:656) at java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:200) at com.aptana.git.core.model.GitIndex.refresh(GitIndex.java:203) at com.aptana.git.core.model.GitIndex.changedFiles(GitIndex.java:326) at com.aptana.git.core.model.GitIndex.getChangedResources(GitIndex.java:688) at com.aptana.git.core.model.GitRepository.getChangedResources(GitRepository.java:1872) at com.aptana.git.ui.internal.GitLightweightDecorator.repositoryAdded(GitLightweightDecorator.java:379) at com.aptana.git.core.model.GitRepositoryManager.fireRepositoryAddedEvent(GitRepositoryManager.java:227) at com.aptana.git.core.model.GitRepositoryManager.attachExisting(GitRepositoryManager.java:213) at com.aptana.git.core.GitRepositoryProviderType$1.run(GitRepositoryProviderType.java:53) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code}
| 5 |
2,077 |
TISTUD-6696
|
06/03/2014 19:04:40
|
Installing Studio dependencies fails when user has never run sudo before
|
After installing Titanium Studio, it prompts for dependencies like NodeJS, Titanium, Alloy etc. To install these I need to enter my password. Now when I installed Yosemite (clean) I checked the box to login using my AppleID password. If I enter that password in the Studio dialogs it tells me the password is wrong. Only after setting a separate password for my use account I manage to install the dependencies.
| 5 |
2,078 |
TISTUD-6590
|
06/03/2014 20:00:37
|
Clean up login error dialog text/punctuation
|
1. Try to login to Studio with incorrect username/password to make error dialog appear. Result: Second sentence says "click here for more information" Expected: First word should be capitalized, period should complete sentence. "Click <link>here</link> for more information." Or maybe: "Try logging in again, or <link>reset your password</link>." (http://www.w3.org/QA/Tips/noClickHere)
| 2 |
2,079 |
TISTUD-6591
|
06/03/2014 20:29:11
|
Alloy: Update content assist to support leftNavButtons and rightNavButtons arrays
|
Alloy 1.5 will support the new iOS-only properties for a Window object: `rightNavButtons` and `leftNavButtons`. These accept an array of views. This change will affect content assist.
| 8 |
2,080 |
TISTUD-6592
|
06/04/2014 07:21:39
|
Windows: Studio Installer: Studio does not install Jdk and hence fails installation
|
This is regression issue since earlier studio used to get installed with JDK successfully. *Steps To Replicate*: 1. Download *Titanium/Accelerator Studio RC build* 2. Try installing same on clean windows 7 machine. Actual: {color:red} *Some Prerequisite JDK could not be downloaded error appears. Refer screenshot.* {color} Expected: No error should appear. Installation must be successful.
| 5 |
2,081 |
TISTUD-6593
|
06/04/2014 11:53:34
|
Unable to install studio when git is manually installed using context menu option - since git1.8.3
|
When Git is already manually installed on the system, the studio does not recognize the installed git and tries to install the git itself and still fails. This happens when during manual installation of Git, the option for 'Simple Context Menu' (as mentioned in latest docs as well) is chosen instead of 'Advanced Context Menu (git-cheetah plugin)'. Also the issue is only with installation of Git1.8.3 or higher. If the manually installed Git is either Git1.8.2 or lower, or installed using Git-cheetah option, the installer does find the installed Git and hence does not try to install Git again. The overall install of Studio is also Successful. Steps to Reproduce: 1. On a clean machine (or uninstall all previous studio and Git. Ensure no Git folder in C:\Program Files (x86)) 2. Install Git version 1.8.3 or above. During installation process select the option for 'Simple Context Menu'. 3. Once Git is installed, start installing Appcelerator Studio or Titanium Studio. Actual Result: Despite Git being already installed, the installer will download and install Git (Git1.8.4 for Studio 3.2.3 and Git1.9.0 for Studio 3.3.0). After installation of Git, the installer throws an error related to issues in Git installation and quits. Refer to attached screenshots
| 5 |
2,082 |
TISTUD-6594
|
06/05/2014 12:00:28
|
TitaniumStudio: Absurd folder structure for node.acs project
|
*Specific to Titanium Studio.* Two folders with same name as of project is created for node.acs project. This is regression as the folder structure didn't had another folder with same name containing all project files. *Steps To Replicate:* 1. Create a node.acs project using Titanium Studio on Mac machine. 2. Observe the folder structure. [Screenshot attached] Actual: Two folders with project name appears Expected: A single folder containing project files should appear.
| 3 |
2,083 |
TISTUD-6595
|
06/05/2014 12:33:06
|
Theme: Dark Theme from Studio dashboard makes text from tab titles and Project explorer un-Readable
|
The dark theme when selected from studio dashboard makes the expandable/Collapse arrow-icons in project explorer and the inactive tab titles unreadable. *Steps To Reproduce:* 1. On Windows 8 machine, switch to Dark theme from Appc studio dashboard. 2. Observe the UI Actual: Expandable/Collapse arrow-icons in project explorer and the inactive tab titles is not readable in present UI. Expected: UI should be such that, the text is readable. [Please find attached screenshot with unreadable text highlighted in red.]
| 8 |
2,084 |
TISTUD-6597
|
06/05/2014 18:49:58
|
"use strict"; should not reflow immediately after the brace
|
"use strict"; should not reflow immediately after the brace
| 3 |
2,085 |
TISTUD-6598
|
06/05/2014 18:50:17
|
var declarations on newlines should not all be placed on a single line
|
var declarations on newlines should not all be placed on a single line
| 3 |
2,086 |
TISTUD-6599
|
06/05/2014 18:50:35
|
switch statements should not indent cases.
|
switch statements should not indent cases.
| 3 |
2,087 |
TISTUD-6601
|
06/06/2014 16:10:15
|
Update content assist for KeyboardToolbar with TextArea
|
Support for <KeyboardToolbar> with a TextArea has been added in Alloy 1.5. This is an iOS only feature. This likely means that content assist needs to be updated.
| 8 |
2,088 |
TISTUD-6603
|
06/06/2014 18:47:20
|
Pass in proxy details to Titanium CLI login call
|
There is an issue with creating a project for BNSF Railways under their proxy configuration. The project is unable to create as Titanium CLI fails to login. Studio should pass in the proxy credential details to CLI during the login call. The command falls on the similar lines : ti login <username> <password> --config "{cli:{httpProxyServer:’http://IP:PORT'}}"
| 5 |
2,089 |
TISTUD-6604
|
06/07/2014 00:30:14
|
JDK installation fails with message "Wrong Size"
|
h5.NOTE: This steps are done on a clean install of the above mentioned OS. h5.Description: 1. Download the installer for appcelerator studio from RC stream. 2. Start the installation. h5.Actual Result: 1. The installation starts but we get error while downloading jdk in between. (Please refer the screenshot attached for reference). h5.Expected Results: 1. We should not see any errors & the installation should be successful.
| 8 |
2,090 |
TISTUD-6615
|
06/10/2014 08:52:16
|
Studio alloy menu shows Class Names for Alloy Components instead of component name
|
In Appc-Studio 3.3.0, Alloy menu shows class names instead of actual component names. For example: It displays *%alloy.command.controller.label* instead of *Alloy Controller* For more idea about the issue, please refer the attached screenshots. This is a *regression* since it does not occur in Appc-Studio 3.2.3 GA. h5. Steps to reproduce: Install Appcelerator Studio 3.3.0 and create an alloy project. Right click on the project and select on *new*
| 3 |
2,091 |
TISTUD-6616
|
06/10/2014 10:04:39
|
Changes made to iOS/Android Device launch configuration from Run Configuration do not get reflected on app launch
|
This is not a regression issue. Steps Followed: 1. Connect more than one iOS/Android device and try to launch the app on both of them through Run Configuration Window. 2. Go to your Project from Project Context Menu >> Run as >> Run Configuration and select the desired iOSAndroid device lets say Device 1 and than Run the Project. 3. Again for the same Project or any other Project launch it from Run Configuration by making changes and choosing some different configuration say Device 2 or iTunes. Actual Result: The next launch does not reflect the changes made in Run Configuration window before launching the Project and launches the project for the same previous configuration. This scenario is observed for both iOS and Android Device Run Configuration. Note: The Run Shortcut menu from the Global toolbar works fine and respects the launch config selected by user
| 5 |
2,092 |
TISTUD-6618
|
06/10/2014 11:05:41
|
Studio installer does not install mandatory Prerequisite
|
If Git, JDK and Node are not installed in the machine before running the Studio installer, It fails with an error message. The error message is *"X mandatory prerequisite was not correctly installed"* where X could be JDK, NodeJS or Git.... Please refer the attachments for more info. h5. Steps To Reproduce Unistall all the prerequisites from your machine (JDK, Git, Node etc..) Run the Studio 3.3.0.201406061445 installer. h5. Actual Result Installation fails with error message. h5. Expected Result Installer should download and install all the prerequisites.
| 5 |
2,093 |
TISTUD-6625
|
06/11/2014 12:01:42
|
'Clear' button on Setup Proxy Entry popup is missing
|
Test steps: 1. Run Titanium Studio. 2. Provide the Studio workspace path. 3. Select "I already have a user account." in the case of Titanium Studio. 4. Click on "Proxy Setup" link on login splash screen. 5. Enter some value in any fields like host or port. 6. Click on "Clear" button Actual Reult: 1.'Clear' button is missing.Please see attached screenshot. 2.Appcelerator Studio has 'clear' button available.
| 5 |
2,094 |
TISTUD-6626
|
06/11/2014 12:26:52
|
Dashboard: Apps in Marketplace are hovering over each other
|
Go to Dashboard-> MarketPlace-> Featured Components and observe that Apps are hovering over each other due to which they are not readable properly. Please refer to attach screenShot
| 5 |
2,095 |
TISTUD-6635
|
06/12/2014 10:25:44
|
Node ACS: Unable to create new Node.ACS service: Destination directory could not be created
|
Unable to create new Node.ACS services to any of the Classic/Alloy project. Steps to Reproduce: 1. Create new classic project 2. Go to New -> Node.ACS service Actual Result: Unable to create Node.ACS service "There was an error attempting to create a new Node.ACS service Reason: Unable to copy ... to ... because the destination directory could not be created." Expected Result: Node.ACS services should get successfully enabled. Refer to the attached screenshot and console logs for your reference.
| 5 |
2,096 |
TISTUD-6639
|
06/13/2014 12:30:47
|
Generic icon appears for Appcelerator Studio in control panel
|
Control panel must show the icon of Appcelerator studio. Works fine on Windows 7. Works fine for titanium studio on Windows 8.1 *Steps:* 1. Install appcelerator studio +Actual:+ Observe the appcelerator icon in control panel. [refer attachment] +Expected:+ Appcelerator studio icon must appear
| 5 |
2,097 |
TISTUD-6641
|
06/16/2014 12:25:58
|
User operation gets stuck at Preferences window containing invalid values
|
Found this bug when doing clean installtion on windows 8.1 machine with GA components. Steps followed: 1. On Platform Configuration wizard try to configure Blackberry and then cancel the installation. 2. Goto Appcelerator Studio ->Preferences->Studio ->Platforms ->Blackberry 3. Though BB is not configured on my machine, it still shows some invalid default path set in the Preference tab. 4. When I try to click on any other option in the Preference tab, an error pop up message is prompted "The currently displayed page contains invalid values". Actual result: When OK is clicked user is again navigated to the same tab and any other operation gets stuck. User can not navigate to any other tab. Though 'Restore defaults' option clears the path and solves the problem but every time when Blackberry Preferences is opened in the Preference tab same problem occurs. NOTE: Same scenario is observed on every preference window containing invalid values. Please find the attached screenshot for your reference.
| 5 |
2,098 |
TISTUD-6642
|
06/16/2014 21:30:35
|
Appc studio installer showing incomplete studio name
|
h5.Description: 1. Download the appc studio installer mentioned above. 2. Start the installation. 3. Notice the name on the installer h5.Actual Result: 1. The name shows " Appcelerator " & not "Appcelerator Studio". Please refer the attached screenshot for reference. h5.Expected Result: 1. The name should show "Appcelerator Studio".
| 8 |
2,099 |
TISTUD-6644
|
06/17/2014 07:26:54
|
Ubuntu: Organization text cut off when creating Node.ACS project
|
"Create node.acs" project window does not display organisation text clearly. [Refer attachment] *Steps to replicate* 1. Install studio 2. Try creating node.acs project (x) Observe that the window hides "Organization: " text (/) *"Organization: "* text must be clearly visible.
| 8 |
2,100 |
TISTUD-6645
|
06/17/2014 12:11:31
|
Windows: Additional folder created as "Appcelerator, Inc" on running the installer on clean machine
|
On clean installing the Appcelerator studio through installer, it creates additional folder "Appcelerator, Inc" at location "C:\Users\Global\AppData\Roaming" which contains two sub folders as mentioned below, 1-> Appcelerator Studio -> prerequisites 2-> Appcelerator Studio 3.3.0-> 0D804B5 Both these sub folder hierarchy are empty and do not contain any data files. Note: Same scenario is observed while uninstalling the studio, folder still persist under "C:\Users\Global\AppData\Roaming" path. Refer to the attached screenshot for your reference.
| 5 |
2,101 |
TISTUD-6646
|
06/17/2014 21:40:46
|
Studio: Intermittently non-responsive "finish" button in wizard when trying to run on device
|
h5. Description: I encountered a problem when I tried to run on device where the "finish" button in the wizard was unresponsive. This seems to have been caused by an unhanded loop exception. See attached logs. Since this is intermittent, I was unable to determine if a regression or not, but support encountered the same thing on 3.2.3 GA Studio. Please see attached "supportLog" Note, this may be related to building workspace during run on device. h5. Steps to reproduce: 1) Create a new project with Studio 2) Run on iOS device 3) Navigate through the wizard to the last pane 4) Click the "finish" button h5. Result: Nothing happens h5. Expected Result: Build commences
| 5 |
2,102 |
TISTUD-6650
|
06/18/2014 23:56:00
|
Intermittent Error enabling Appcelerator services creating the app with no Appcelerator services
|
I encountered this issue trying to Run the created default app with *no* appcelerator services enabled on BB device. h5. Steps 1. Create the default app with no appcelerator services 2. Run on BB device (I tested BB device) h5. Actual result Error trying to enable appcelerator services h5. Expected result No error I am not sure when the error occurred, after app creation or building it for device.
| 5 |
2,103 |
TISTUD-6654
|
06/19/2014 23:11:52
|
Studio: Large projects (450mb) take a very long time (estimated 90+ minutes) to index
|
h5. Description: While testing a large customer project (450mb on disk) I cleaned all projects. This started a rebuild of the workspace and was indexing for about three minutes when I started a timer. After 45 minutes, I could not wait anymore but the process was less than 50% complete. h5. Steps to reproduce: 1) Use a large project 2) Clean all projects 3) attempt to launch a different project tin iOS simulator h5. Result: Launch of sim delayed until indexing complete h5. Expected Result: Simulator launches
| 8 |
2,104 |
TISTUD-6655
|
06/19/2014 23:37:02
|
Breakpoints disappear after formatting controller file
|
In a controller file of a Alloy project, - Add a new line "Ti.API.info('test')" and select all (using Cmd+A) and format the file (Cmd+Shift+F). - All my breakpoints disappeared. The breakpoints seems to disappear only if there are any formatting changes. Otherwise, they remain as it is.
| 8 |
2,105 |
TISTUD-6656
|
06/20/2014 00:30:01
|
Support breakpoints in alloy.js file
|
In an Alloy project, currently Studio suspends the thread if the breakpoint is only in controller files. If the alloy.js has any breakpoints set, then Studio fails to resolve the breakpoints from the generated (app.js) into original source (alloy.js) file. After ALOY-616 is addressed, I believe it should provide all source maps for JS files including alloy.js file.
| 8 |
2,106 |
TISTUD-6657
|
06/20/2014 17:15:55
|
Appcelerator Studio: Incorrect message on the progress bar after enabling services
|
Incorrect message appears on the progress bar after enabling the services. Steps to Reproduce: 1. Create an application in Appcelerator Studio without enabling the services. 2. Check the Enable Appcelerator Platform Services box. 3. Notice that the progress bar shows "Updating 360 Services" instead of "Appcelerator Services" Note that this happens only if you uncheck "Enabling Appcelerator Platform Services" box and later check it. Please see the attached screenshot. Environment Information: Appcelerator Studio, build: 3.3.0.201406111952, OSX 10.8.5
| 2 |
2,107 |
TISTUD-6662
|
06/25/2014 18:18:50
|
Move to Eclipse 4.4 base for RCP
|
Eclipse 4.4 GA is out! We should be building on top of it.
| 8 |
2,108 |
TISTUD-6663
|
06/25/2014 21:27:37
|
Android Keystore: Escape specials characters used in any of the fields of the keytool wizard
|
h5.Description If special characters (',' or '.' for instance) are used in the keytool wizard then the keystore will fail to generate and an error popup will appear. Showing a warning in the wizard if any special characters are used might prevent users from seeing this error. h5.Steps To Reproduce 1. Publish an Android application and use the wizard to generate a new keystore. 2. In the 'Organization name' field, use a special character (Appcelerator, Inc.) 3. Create the keystore h5.Expected Result Since this is an error with the keytool generator and nothing on Studio's side we should display a warning that specials characters will throw an error. h5.Actual Result Error is thrown with Java exceptions displayed on screen.
| 5 |
2,109 |
TISTUD-6668
|
06/28/2014 01:16:50
|
Reduce the height of modules table in tiapp editor
|
Since there are multiple sections (such as Appcelerator Services, MobWare) after the modules table, the current height of modules table might force the users to scroll down to view those sections, after the project is created. In the default context, there won't be more than 3 modules added when the project is created and we should adjust the height the modules table accordingly. As more modules are being added, the maximum height of the table should be restricted so that the other sections are still accessible easily.
| 3 |
2,110 |
TISTUD-6671
|
06/30/2014 19:40:35
|
Appcelerator Studio license link leads to Titanium Studio license agreement
|
h5.Description Clicking the license link when updating Appcelerator Studio will lead to a web page about Titanium Studio. http://studio.appcelerator.com/license.html h5.Steps To Reproduce 1. Update Appcelerator Studio 2. Click the link in the license box h5.Expected Result Should lead to an Appcelerator Studio license page h5.Actual Result Leads to an Appcelerator Titanium Studio license page
| 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.