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,711 | TISTUD-8966 | 12/18/2017 22:50:42 | iOS Debugger: Not able to resume when debugger stops at first line of code | *Description* Debugger does not stop at set breakpoints on iOS devices *Steps to reproduce* 1. Create default alloy app in Studio. 2. Set a breakpoint at "alert($.label.text);" in the controller. 3. Run debugger. *Actual results* 1. Debugger stops at the splash screen, and unable to "Resume" as buttons are grayed out. *Expected results* 1. User should be allowed to move past the splash screen by clicking "Resume". | 5 |
2,712 | TISTUD-8967 | 12/20/2017 07:31:25 | Eclipse Oxygen: Error while accessing "Axway Appcelerator" item from the import project menu - | Error while accessing "Axway Appcelerator" item from the import project menu. {code:java} !ENTRY org.eclipse.jface 4 2 2017-12-20 14:49:21.950 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 org.eclipse.jface.resource.DeviceResourceException: Unable to create resource URLImageDescriptor(platform:/plugin/org.eclipse.ui.ide/icons/full/etool16/newprj_wiz.gif) at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:182) at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:85) at org.eclipse.jface.resource.LocalResourceManager.allocate(LocalResourceManager.java:69) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:85) at org.eclipse.jface.resource.ResourceManager.get(ResourceManager.java:143) at org.eclipse.ui.model.WorkbenchLabelProvider.getImage(WorkbenchLabelProvider.java:188) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:101) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:146) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:141) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:946) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:117) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1025) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:475) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2159) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:840) at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:817) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:792) at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:595) at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:763) at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1482) at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:880) at org.eclipse.jface.viewers.AbstractTreeViewer$3.treeExpanded(AbstractTreeViewer.java:1494) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) at org.eclipse.swt.widgets.TreeItem.sendExpand(TreeItem.java:1050) at org.eclipse.swt.widgets.Tree.expandItem_expandChildren(Tree.java:1280) at org.eclipse.swt.widgets.Display.windowProc(Display.java:6061) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:228) at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1136) at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2144) at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1128) at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2616) at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2111) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5798) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:228) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2148) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2411) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5862) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5290) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5440) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) at com.aptana.portal.ui.dispatch.actionControllers.CommandHandlerActionController.execute(CommandHandlerActionController.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:103) at com.aptana.portal.ui.dispatch.ActionControllerProxy.invokeAction(ActionControllerProxy.java:77) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:177) at com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:131) at com.aptana.portal.ui.internal.BrowserWrapper$1.function(BrowserWrapper.java:43) at org.eclipse.swt.browser.WebKit.callJava(WebKit.java:1775) at org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:401) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:228) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2148) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2411) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5862) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5290) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5440) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) at org.eclipse.equinox.launcher.Main.run(Main.java:1499) at org.eclipse.equinox.launcher.Main.main(Main.java:1472) {code} | 3 |
2,713 | TISTUD-8971 | 01/03/2018 15:28:50 | Eclipse Oxygen: Issues with menu items | When using eclipse oxygen core for studio following issues are seen in the menus 1. The Commands menu not showing any option 2. Unexpected items in the menus. i) "Open Projects from File System" under File menu | 5 |
2,714 | TISTUD-8976 | 01/04/2018 13:17:14 | Eclipse Oxygen: Issues in Studio Preferences | When using eclipse oxygen core for studio following issues seen in Preferences: 1. Need to remove General->Tracing, General->UI Responsiveness Monitor 2. Studio>Formatter. Text for TSS is not proper. Check screenshot 3. Error Reporting option shown under General. It should be under Studio. | 5 |
2,715 | TISTUD-8978 | 01/08/2018 07:00:31 | Eclipse Oxygen: Issues with project import | When using eclipse oxygen core for studio following issues seen during import: 1. File > Import. errors are shown. Check screenshot1. Also check screenshot2 for missing icon in import window Also attached are the error logs. | 5 |
2,716 | TISTUD-8979 | 01/09/2018 03:54:38 | Eclipse Oxygen: Error during step into or step over during debug | When using eclipse oxygen core for studio an error is shown during debug when a breakpoint is hit and we click on Step Into or Step over buttons. Check the attached screenshot and logs. | 5 |
2,717 | TISTUD-8983 | 01/09/2018 15:52:51 | Studio: Cannot package iOS module projects | Developers cannot package native iOS modules (probably Android as well) modules from Studio. I tried importing https://github.com/hansemannn/titanium-firebase-core to Studio (both with reference to the root of the project and the ios/ directory). Outcome: - Root of the module: Studio does not detect the module-sub-directories, does not offer package options - "ios" sub-directory: The "Package" option is shown, but Studio errors with "Cannot find /ios/ios/manifest" error. | 5 |
2,718 | TISTUD-8986 | 01/16/2018 00:12:13 | Can not deploy to iOS Simulator, no devices listed | iOS simulators are listed in Appcelerator Studio but when I go to build against a simulator I get the error message below [ERROR] : Invalid "--device-id" value "5CF408BF-0CB1-4386-9639-08389788EDDA" Available iOS Simulators: For help, run: titanium.js help build Running on command line appc run -p ios --device-id Appcelerator Command-Line Interface, version 7.0.1 Copyright (c) 2014-2018, Appcelerator, Inc. All Rights Reserved. [ERROR] Invalid "--device-id" value "" Available iOS Simulators: For help, run: titanium.js help build | 3 |
2,719 | TISTUD-8984 | 01/16/2018 09:24:59 | Eclipse-oxygen-2: Exceptions while creating Mobile Project while in debug perspective | When we move to eclipse oxygen-2 or later, we might have to address the issues logged in attached document [^Exceptions_while_CreatingProject_eclipse472_debugPerspective.rtf] Basically, these issues are not related to Studio code, rather issues caused by AbstractTreeViewer.java (within eclipse community). We shall closely watch those changes in community commits and adopt to or get latest changes. | 5 |
2,720 | TISTUD-8985 | 01/17/2018 09:33:20 | Eclipse Oxygen: UI Issues in the Windows OS | When using eclipse oxygen core for studio following UI Issues are seen. Refer to attached screenshot as well. Point 1 & 2 below occur only on windows. Point 3 & 4 can be seen on both windows and Mac. The same code base and screen resolution does not show these UI issues when ran with Eclipse Luna. 1. The Run and Device drop down are shown truncated 2. The logged in User, feedback button and change organization button at the bottom right are not shown 3. When no tab is open then a small black line is shown in the editor area near the left and right edge 4. Extra white border of each view. It gives a feeling of extra lines in the gap between views. | 1 |
2,721 | TISTUD-8987 | 01/23/2018 19:11:06 | Windows: Studio Debugging is not working on windows 10 | Hello, Studio Debugging is not working on windows 10 when trying to debug for Android emulator as well as the device. We are attaching the Studio Diagnostic log and *appc ti setup check* log in the attachment file. *Working Environment Details:* {code}Operating System Name = Microsoft Windows 10 Pro Version = 10.0.16299 Architecture = 64bit # CPUs = 8 Memory = 17132167168 Node.js Node.js Version = 8.9.4 npm Version = 5.6.0 Titanium CLI CLI Version = 5.0.14 Titanium SDK SDK Version = 7.0.1.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\7.0.1.GA Target Platform = android {code} This issue happens to a specific user. Thanks | 8 |
2,722 | TISTUD-8991 | 01/25/2018 22:28:11 | Studio: Eclipse Upgrade from Oxygen to Eclipse 4.9(2018-09) | This epic will track all the items required to enable support for later versions of the core | 8 |
2,723 | TISTUD-8997 | 01/30/2018 02:22:54 | Eclipse Oxygen: The Run and Device drop down are shown truncated in Windows OS | The Run and Device drop down are shown truncated | 5 |
2,724 | TISTUD-9004 | 02/06/2018 09:44:15 | How do I switch back to previous studio version | Appcelerator Studio update 5 is crap. I must to switch back to previous version so I can help my customers. | 2 |
2,725 | TISTUD-9005 | 02/07/2018 04:50:09 | Studio Stuck at Workspace Launcher | Studio suddenly stop working, every time open it, will stuck at workspace launcher. (Like attached screenshot). Cannot edit or click anything on the dialog. Try the following steps, but did not help 1. Force to quit studio. 2. Restart the system. 3. Remove the studio package from Application, and re-install it from latest installer. 4. Remove the old workspace. All the changes is I recently updated JDK to version 1.8.0_161. But I tried to revert it back. Still seeing same issue. Run "appc info" and "appc setup check". All works well. (attached) Please advice. | 3 |
2,726 | TISTUD-9006 | 02/07/2018 06:58:43 | The "full_uninstall.txt" file in the Appcelerator folder is outdated | The "full_uninstall.txt" file in the Appcelerator folder is outdated {code:java} Uninstalling/Re-installing Axway Appcelerator Studio ====================================================================================== If you need to fully uninstall and reinstall Axway Appcelerator Studio, you can follow the "Uninstalling Studio" steps here: http://go.appcelerator.com/apupdate and then re-download and install again as before. {code} | 3 |
2,727 | TISTUD-9011 | 02/13/2018 10:00:24 | Unable to build iOS Project | h3. Steps to Reproduce 1. Update TiSDK to 7.0.2.GA 2. Update CLA to 7.0.2.GA h3. Actual Result - Unable to build for iOS project as well as unable to Select XCode from preferences>studio>Platform>iOS. - Certificates and Provisional not listing in Preferences. - Can't build for distribution or development for iOS. h3. Expected Result Able to Build for iOS Profile. | 1 |
2,728 | TISTUD-9013 | 02/15/2018 18:56:55 | Windows: Unable to run the Studio on windows 10 | Hello, The customer has several Windows 10 PCs that are not able to run Appcelerator Studio. After installing all components, when they try to start Studio it gives an error: “An error has occurred. See the log file.” Attaching the log file and also attaching the output of the “appc ti check setup” command and screenshot. Thanks | 5 |
2,729 | TISTUD-9015 | 02/20/2018 08:32:13 | Windows Installer: The installer for 5.1 builds has the flag to set required java version to 1.8 | Appcelerator Studio installed on windows has vmargs flag -Dosgi.requiredJavaVersion=1.8 already set by default. Hence the studio does not work if the system has only Java 9 which is supposed to be supported in this build. | 3 |
2,730 | TISTUD-9016 | 02/20/2018 08:36:23 | The installer installs JDK1.8.0_131 even if JDK 1.9 is already installed | On both Mac and Windows OS, the Appcelerator Studio installer prompts for missing JDK even though JDK 1.9 is already installed. Hence it downloads and installs JDK 1.8 during installation. | 8 |
2,731 | TISTUD-9017 | 02/20/2018 09:52:01 | Install Java 1.8.162 with the Studio 5.1.0 installers | Install Java 1.8.162 with the Studio 5.1.0 installers(Windows and macOS) Installer links: http://go.appcelerator.com/installer_jdk_mac http://go.appcelerator.com/installer_jdk_windows http://go.appcelerator.com/installer_jdk_windows_x64 (new link for supporting 64-bit JDK for Windows) | 5 |
2,732 | TISTUD-9019 | 02/22/2018 10:45:49 | Updating JRuby plugins to support Java 9 | As we are not unable to load default ruble templates with the Java 9 - we need to update the JRuby jar to the latest and update relevant code to support Java 9 | 13 |
2,733 | TISTUD-9022 | 03/01/2018 20:08:02 | iOS Debugger: Devices will not connect | When trying to debug on iOS, the debugger will not connect to devices. Simulators are working as expected. *Steps to reproduce issue* 1. Create a new project (alloy) 2. Add a break point to the index.js file 3. Debug the app for an iOS device *Expected Results* The debugger connects to the device and the break point is hit *Actual Results* The debugger does not connect to the device | 5 |
2,734 | TISTUD-9023 | 03/06/2018 08:35:08 | Android device connected but I can not get Studio to show a device at all | https://jira.appcelerator.org/browse/TISTUD-7054 From [~dlewis23] "I am also having this issue with SDK 7.0.2. appc ti info shows my Android device connected but I can not get Studio to show a device at all. Nothing I do fixes the problem to get a device to show." | 5 |
2,735 | TISTUD-9029 | 03/09/2018 08:41:24 | Button colors not proper on login screen on windows OS | With Studio 5.1.0, both 32 bit and 64 bit version, the color of the buttons on the login screen are not proper. See the attached screenshot "LoginScreen_Issue_5.1.png". The color of the buttons also makes it difficult to read text on the button. Also attached is the screenshot for Studio 5.0 for comparison. Check "LoginScreen_5.0.png" | 3 |
2,736 | TISTUD-9031 | 03/09/2018 15:57:20 | Studio installs outdated hyperloop plugin | I installed Studio on a clean machine today. Studio installed CLI/Java/Node and after that was done Studio also wanted to install SDK 7.0.2.GA and Hyperloop. Turns out, this is plugin version 1.2.8. As it no longer comes in plugin form, hyperloop installation should be removed. *Expected behaviour* Studio should not install Hyperloop plugin | 3 |
2,737 | TISTUD-9032 | 03/12/2018 09:43:26 | Selecting a readonly directory leads to an irrecoverable situation | I tried opening a workspace that another user created on my mac. The permission was not set correctly and it was put as readonly. When that happens you get to a state where you cannot change the workspace again. If the user is not in the condition to change the directory they selected then it will be impossible to recover from this situation. See attachment for error. *Expected result* Instead, an error should pop up as it does now, and then the workspace selector should pop up again. (note: I've selected to never ask me again on startup) | 1 |
2,738 | TISTUD-9036 | 03/14/2018 06:39:02 | Null Pointer Exception shown on studio launch with a new workspace | Null Pointer Exception is shown upon studio launch when a new workspace is selected. Steps to Reproduce: 1. Select a new workspace and open studio 2. When studio gets launched an exception is shown. Check the screenshot and logs. 3. Close studio and launch again with same workspace. No exception this time. {code} !ENTRY org.eclipse.ui 4 4 2018-03-14 11:45:19.475 !MESSAGE An internal error has occurred. !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ui.LaunchAppToolbarContribution$8.runInUIThread(LaunchAppToolbarContribution.java:546) at org.eclipse.ui.progress.UIJob.lambda$0(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4034) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3701) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) at org.eclipse.equinox.launcher.Main.run(Main.java:1499) {code} | 8 |
2,739 | TISTUD-9040 | 03/20/2018 07:45:40 | Remove profiler related code/plugins from studio | Remove Appcelerator profiler related code/plugins from studio | 8 |
2,740 | TISTUD-9043 | 03/22/2018 03:58:35 | Appc Studio Installer crashes during install process if only JDK 9 is installed | When system has only JDK 9 installed then the installer crashes during the installation process. Following issue is reported in crash log {code} *** Terminating app due to uncaught exception 'NSRangeException', reason: '-[NSTaggedPointerString substringWithRange:]: Range {4, 6} out of bounds; string length 9' terminating with uncaught exception of type NSException abort() called {code} | 5 |
2,741 | TISTUD-9046 | 03/26/2018 16:55:26 | Ramdom crashes | h3. The new axway appcelertor studio IDE keeps crashing randomly. This was way more stable in the past. | 1 |
2,742 | TISTUD-9047 | 03/27/2018 23:05:00 | Appc studio 5.1.0.201803260453 gives "Terminal is not functional" on clicking terminal tab | h5.Steps to reproduce: 1. Open appc studio 5.1.0.201803260453. 2. Click on the terminal tab next to console tab. h5. Actual result: 1. We get the message below: {code} This Terminal Emulator is not functional because no 'bash' shell could be found. Please correct the problem and restart the IDE. {code} h5.Expected result: 1. Bash terminal should open inside studio. | 5 |
2,743 | TISTUD-9049 | 03/29/2018 14:34:33 | Unable to view application source when debugging Android project on Windows | h5.Description When debugging an Android app on Windows, I'm unable to see the source, the below error is thrown in the logs, and a tab that looks like the attached image is shown. This occurs for me on 2 different Windows machines with 2 different Android devices. It happens for Alloy or classic apps. The functionality of debugging works, i.e I can step through code, see variables, I can even see the internal JS code of the SDK (kroll.js, events.js etc.), I just cant see any of the apps js code. Following https://wiki.appcelerator.org/display/guides2/Debugging+Android+Apps+with+3rd-party+Tools to debug through chrome works fine and i see the source code {code} !ENTRY org.eclipse.debug.core 4 125 2018-03-29 14:28:30.815 !MESSAGE Error logged from Debug Core: !STACK 0 java.lang.IllegalArgumentException: Path must include project and resource name: /app.js at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137) at org.eclipse.core.internal.resources.Container.getFile(Container.java:208) at com.aptana.debug.core.sourcelookup.LocalFileSourceContainer.findSourceElements(LocalFileSourceContainer.java:45) at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.findSourceElements(CompositeSourceContainer.java:81) at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.findSourceElements(CompositeSourceContainer.java:48) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupParticipant.findSourceElements(AbstractSourceLookupParticipant.java:70) at com.aptana.debug.core.sourcelookup.RemoteContentSourceLookupParticipant.findSourceElements(RemoteContentSourceLookupParticipant.java:27) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector$SourceLookupQuery.run(AbstractSourceLookupDirector.java:142) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.doSourceLookup(AbstractSourceLookupDirector.java:505) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.getSourceElement(AbstractSourceLookupDirector.java:785) at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.lookup(SourceLookupFacility.java:343) at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$SourceLookupJob.run(SourceLookupFacility.java:738) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} h5.Steps to reproduce 1. Debug an app for Android, making sure to place a breakpoint and that the device is unlocked h5.Actual When the breakpoint is hit the source is not shown, but debugging is functional, i.e I can step through the code and view variables in the context h5.Expected Source should be shown | 3 |
2,744 | TISTUD-9056 | 04/05/2018 09:23:56 | Java 10 support for studio | Track all the studio issues related to Java 10 with this epic Java 10 GA (a.k.a. 18.3) was released on 20 March 2018 and eclipse added the support for Java 10 with the 4.7.3a RC2 build https://projects.eclipse.org/projects/eclipse/releases/4.7.3a | 1 |
2,745 | TISTUD-9060 | 04/13/2018 18:07:50 | Android: Available software sites are not pre populated to select for download JDT tools | h5.Steps to reproduce: 1. File -> New -> Mobile module project. 2. You will be presented with New mobile module project dialog. 3. When you try to select android it will ask you to install JDT tools. 4. Go to Help -> Install new software & click on manage. 5. The Available software sites dialog will open up. h5.Actual results: 1. There are no pre populated sites there to select from to install JDT tools. 2. We used to pre populate this with studio 5.0.0. h5.Expected results: 1. The available software sites should be pre populated so that the user can select it to install the JDT tools. *NOTE :* The link to the guide where studio points the user for installation of JDT tools should be updated as well. | 5 |
2,746 | TISTUD-9062 | 04/17/2018 04:26:55 | Android: Packaging android modules shows error mark next to project even though no error. | h5.Steps to reproduce: 1. Create an android module using studio. 2. Notice you might have a warning icon next to your module project. 3. Package the module using any of the 3 options. h5.Actual result: 1. Packaging is successful but we see a error icon next to our project. 2. I tried to find which file has the error but I don't see any files with the error icon on them. 3. Also, tried to change the java compliance preference in workspace settings but I still see it. NOTE : Attached screenshot where you see an error icon but none of the file or folder has an error icon. h5.Expected results: 1. Studio should not show wrong error icon or if there is an error show an error icon next to the file which has the error. | 1 |
2,747 | TISTUD-9063 | 04/17/2018 05:24:42 | Update http://go.appcelerator.com/installer_git_windows.exe link to Git-2.16.2 32 bit version | Update http://go.appcelerator.com/installer_git_windows.exe with the Git-2.16.2 32 bit version. This will address the project import issue we were having from the studio dashboard. Please refer this TISTUD-9053 Two things we need to do here for GA # 5.1.0 RC builds are having temporary git link which are pointing to 2.16.2 which need to be replaced with the standard appc link http://go.appcelerator.com/installer_git_windows.exe # Update http://go.appcelerator.com/installer_git_windows.exe link with the Git-2.16.2 32 bit version. Currently, it's pointing to 0.18.x | 3 |
2,748 | TISTUD-9067 | 04/18/2018 06:03:15 | Studio: Failed to debug on android device from Studio. | *Issue Overview:* The studio debugger shows error when I try to debug on android device. It happens for existing project as well as for the new project. *Reproduction:* Create a new project. Try to debug on android device It shows error. *Expected:* The debugger should work *Actual:* Studio debugger does not work. | 5 |
2,749 | TISTUD-9159 | 05/02/2018 10:09:36 | iOS Debug: Not able to debug on iOS Simulator version 11.3 | Debug not successful on iOS simulator v11.3. The breakpoints are not hit. Debug of same application worked for iOS simulator v11.0, v10.3 The results are same irrespective of different SDK and CLI versions. Steps to Reproduce: 1. Create a default alloy project 2. In index.js, add some breakpoints 3. Debug on any iOS simulator of version 11.3 Actual Result: Breakpoints not hit. The project builds and launches successfully on the simulator. | 8 |
2,750 | TISTUD-9074 | 05/03/2018 21:20:17 | Studio unable to load provisioning profiles after SDK/CLI upgrade | After upgrading CLI & TiSDK to latest versions (7.0.3 & 7.1.1.GA) studio throws an error when going to preferences > studio > platforms > ios Crash log attached User quote: {code} my xcode sdk home is "not specified" and no certs or provisioning profiles load...it was all working fine earlier and now nothing loads. {code} Tried: - {{appc appcd restart}} while studio running - closing studio, running command above, restarting studio - restarting mac and launching studio after | 5 |
2,751 | TISTUD-9079 | 05/14/2018 18:45:52 | Images in the project have a webpage icon & when opened opens in studio's internal web browser | h5.Steps to reproduce: 1. Expand any existing or newly created project in studio. 2. Look at the icon for the image files in the project. h5.Actual results: 1. We see a webpage icon & double clicking it & opening, opens the image in studio's internal web browser. h5.Expected results: 1. The image file should open in default image preview application of the machine OS. | 2 |
2,752 | TISTUD-9085 | 06/08/2018 17:44:51 | Update to liveview 1.2.2 to support babel transpilation | h5.Description We shipped a bugfix for liveview to fix an issue with babel transpilation in TIMOB-25790. It would be good if we could ship those fixes in Studio 5.1.0. Testing steps can be found in TIMOB-25790, the version is 1.2.2 I will endeavour to provide the PR myself so assigning to myself | 5 |
2,753 | TISTUD-9086 | 06/11/2018 11:57:12 | Support ES6 by transpiling to ES5 via new tiapp.xml "transpile" property | Add transpile identifier to the tiapp.xm schemal file so that it won't show the error on the tiapp.xml when it's used Steps to reproduce: 1. Enable transpilation by adding the <transpile>true</transpile> flag to your tiapp.xml 2. tiapp.xml shows the error on the *transpile* keyword as it's not recognised as a valid identifier | 3 |
2,754 | TISTUD-9089 | 06/25/2018 11:57:09 | Studio is not picking up newly downloaded iOS certificates | When downloading new iOS distribution certificates, studio doesn't pick them up automatically. The refresh button does nothing either. The only way to get these certificates showing up in studio is to restart studio. Restarting daemon doesn't resolve it either. (Daemon actually list the certificates already when studio does not) | 5 |
2,755 | TISTUD-9092 | 06/27/2018 04:26:42 | Error occurred during "Getting Diagnostic Logs" | !MESSAGE An internal error occurred during: "Getting Diagnostic Logs". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.ios.internal.core.IOSDiagnosticLog.getLog(IOSDiagnosticLog.java:28) at com.aptana.core.internal.diagnostic.DiagnosticManager$LazyDiagnosticLog.getLog(DiagnosticManager.java:166) at com.aptana.ui.commands.DiagnosticHandler.getLogContent(DiagnosticHandler.java:66) at com.aptana.ui.commands.DiagnosticHandler$1.run(DiagnosticHandler.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) | 3 |
2,756 | TISTUD-9093 | 06/27/2018 18:47:01 | Windows: Studio says it requires Windows 8.1 SDK | Support for Windows 8.1 was dropped in SDK 7.0.0 but studio still requires it *Steps to reproduce* # Remove Windows 8.1 SDK in the visual studio installer # Open restart studio *Error* !win8.PNG|thumbnail! *Expected* Studio should not require Windows SDK 8.1 | 3 |
2,757 | TISTUD-9094 | 06/27/2018 22:15:28 | Windows: Unable to create a mobile project with Java 10.0.1 | I am unable to create a mobile application with the new java version *Test steps* # Uninstall other versions of JAVA on your machine # Download JDK 10.0.1 [Here|http://www.oracle.com/technetwork/java/javase/downloads/jdk10-downloads-4416644.html] # Set JAVA_HOME in your enviroment variables # Set it in the cli just for safe measure {{appc ti config java.home "C:\Program Files\Java\jdk-10.0.1"}} # Install studio # Right click > new > Mobile App Project *Expected* I am able to create an application *Actual* No popup is shown to create an application {color:red}*I have attached a gif of my results and the log is [here |https://gist.github.com/longton95/927deabeb2dbe1afb874adfc1f18a6a9]*{color} | 5 |
2,758 | TISTUD-9101 | 07/13/2018 00:42:43 | Install android 8.1 by default in the appcelerator studio | Install android 8.1 by default in the appcelerator studio | 5 |
2,759 | TISTUD-9105 | 07/24/2018 10:28:49 | Run configurations not updated when Xcode is updated | When updating Xcode (these days done automatically by macOS), Xcode also updates the iOS Simulators. In case of one of our community members, this now results in a state where Studio is unusable, because Studio attempts to use the old Simulator (11.3), although only 11.4 is available. Error: {code} 2018-07-24T09:13:38.690Z | DEBUG | Titanium Downloads Last Checked: 1532354784142 2018-07-24T09:13:38.738Z | TRACE | No project alloy hook; skipping update to 1.0.0 [ERROR] : Invalid “--ios-version” value “11.3" Accepted values: 11.4 [ERROR] : Invalid “--device-id” value “9BED048B-F072-4ADA-95CB-4F8664D592FD” 12.0 Available iOS Simulators: 12.0 {code} It should: - validate and refresh the run configurations if necessary (Xcode change) - select the {{xcode-select}} selected Xcode-version by default (cc [~eharris]) | 1 |
2,760 | TISTUD-9106 | 07/27/2018 07:56:07 | iOS Debugger: Studio will not stop at breakpoint in Alloy project | h6.Reproduce 1. Create a new Alloy project. 2. Add breakpoint to line 2 and 5 in index.js file 3. Choose debug from dropdown list 4. Exceute the app with debug model. h6.Actual Result App will not stop at neither of the breakpoints on iOS simulator. You can click the label without stop. h6.Expect Result App should stop at line 2 and line 5 as breakpoints h6.Note On Android platform, the above test works well as expect. h6.Env Detail Studio IDE: 5.0.0.201712081732 Ti SDK: 7.2.0.GA AppC CLI: 7.0.4 Java Version: "1.8.0_131" Node Version: 8.9.1 | 5 |
2,761 | TISTUD-9108 | 08/01/2018 05:47:37 | Update preview.appcelerator.com/appc-studio with the 64-bit Windows builds | Update preview.appcelerator.com/appc-studio with the 64-bit Windows builds | 5 |
2,762 | TISTUD-9110 | 08/16/2018 09:52:14 | Using Debugger breakpoint is not working on studio 5.1.0(alloy and classic) | Tested the issue using breakpoints. Using Debugger, breakpoint is not working on studio 5.1.0.201808080937(alloy and classic). *Test Envioroment:* {code} Axway Appcelerator Studio, build: 5.1.0.201808080937 Appcelerator Command-Line Interface, version 7.0.4 Operating System Name = Mac OS X Version = 10.13.6 Architecture = 64bit CPUs = 4 Memory = 8589934592 Node.js Node.js Version = 8.9.1 npm Version = 5.5.1 Titanium CLI CLI Version = 5.1.1 Titanium SDK SDK Version = 7.2.0.GA iOS SDK: 11.4, iOS Simulator: iPhone X {code} *Test code:* ////////////////// *Alloy:* /////////// *index.js* {code} function doClick(e) { alert($.label.text);// breakpoint is added on this } $.index.open(); {code} *index.xml* {code} <Alloy> <Window class="container"> <Label id="label" onClick="doClick">Hello, World</Label> </Window> </Alloy> {code} *Classic:* {code} var win = Ti.UI.createWindow({ title: "Testing debug", backgroundColor: '#fff' }); // Create a Label. var aLabel = Ti.UI.createLabel({ text : 'test', color : 'red', font : {fontSize:20}, textAlign : 'center' }); // Add to the parent view. win.add(aLabel); aLabel.addEventListener("click",function(e){ Ti.API.info("Debugging started"); alert("Debugging started");// breakpoint is added on this line }); win.open(); {code} *Test steps:* 1. Create a project(alloy and classic). 2. There is a label on window and has an alert option upon clicking on it. Set a breakpoint on this alert. 3. Debug it on a simulator and observe that alert is fired on clickevent. *Test Output:* Screen shots are attached above for alloy and classic project both. *Expected output:* Alert should not be fired as breakpoint is set on that. | 3 |
2,763 | TISTUD-9111 | 08/17/2018 07:24:24 | Error reporting: History service is not (yet) available | Studio crash logs are considerably larger. One crash log is 190 KB. Here is the reported crash log which is related to History service is not (yet) available from AERI Plugin [^crash_report.txt] | 3 |
2,764 | TISTUD-9142 | 08/20/2018 13:55:58 | LiveView: Newline character is displayed when using liveview | Community credit to [~cmoss] for locating the problem On both iOS and Android, when running an app with liveview translations with a newline character are displayed. When running without liveview the newline is displayed, and the newline character is hidden. See attached screenshots for iOS and Android strings.xml {code:xml} <string name="Test">Test\nTest</string> {code} index.xml {code:xml} <Label id="myLabel"></Label> {code} index.tss: {code} "#myLabel": { color: "#000000", text: L("Test") } {code} Problem occurs also in xml: {code:xml} <Label>L("Test")</Label> {code} Problem doesn't occur when using the textid property. | 3 |
2,765 | TISTUD-9113 | 08/23/2018 10:27:40 | Studio's method for picking up release notes needs updating | Once again, the release notes in Studio are broken. People joked about it on Slack and it's pretty bad to know that these basics even still cause issues. Please fix this. | 3 |
2,766 | TISTUD-9115 | 08/29/2018 20:03:36 | Studio 6.0 GA: Update Node.js version distributed by Studio | I believe the version Studio distributes is v8.9.1 or something. We have a npm dependencies that uses a new ES2018 feature (dotAll & lookbehind regex support) and so the minimum required version will be Node.js v8.10.0. The latest LTS release is v8.11.4 and it's the version that we test, so please update Studio's installer to install Node.js v8.11.4. | 13 |
2,767 | TISTUD-9116 | 08/30/2018 06:41:44 | Error reporting: CollapseAll icon is missing in the General -> Keys preferences in the studio | CollapseAll icon is missing in the General -> Keys preferences in the studio {code:java} STACK 0 org.eclipse.jface.resource.DeviceResourceException: Unable to create resource URLImageDescriptor(platform:/plugin/org.eclipse.ui.ide/icons/full/elcl16/collapseall.gif) at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:182) at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:85) at org.eclipse.jface.resource.LocalResourceManager.allocate(LocalResourceManager.java:69) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:85) at org.eclipse.jface.resource.ResourceManager.createImage(ResourceManager.java:172) at org.eclipse.ui.internal.keys.NewKeysPreferencePage$BindingElementLabelProvider.getColumnImage(NewKeysPreferencePage.java:408) at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:67) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:141) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:946) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:117) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1025) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:475) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2159) at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2713) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1894) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:668) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1870) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1827) at org.eclipse.jface.viewers.StructuredViewer.lambda$3(StructuredViewer.java:1531) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1447) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:354) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1408) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1531) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:535) at org.eclipse.ui.dialogs.FilteredTree$NotifyingTreeViewer.refresh(FilteredTree.java:1214) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1492) at org.eclipse.ui.dialogs.FilteredTree$NotifyingTreeViewer.refresh(FilteredTree.java:1202) at org.eclipse.ui.dialogs.FilteredTree$1.runInUIThread(FilteredTree.java:511) at org.eclipse.ui.progress.UIJob.lambda$0(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4034) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3701) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:196) at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.runCommand(CocoaUIHandler.java:647) at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.access$5(CocoaUIHandler.java:634) at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler$3.widgetSelected(CocoaUIHandler.java:506) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4258) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4082) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) at org.eclipse.equinox.launcher.Main.run(Main.java:1499) at org.eclipse.equinox.launcher.Main.main(Main.java:1472) {code} | 3 |
2,768 | TISTUD-9117 | 08/30/2018 11:48:48 | Fixing major error reporting issues on 5.1.0 | *Issue 1:* https://github.com/aptana/studio3/files/2332007/crashreport_UTFDataformat.txt Due to this, the huge amount of JS code(converted character data) dumping into the crash reports and hence increasing the crash file size *Issue 2:* Avoid HIDDEN.HIDDEN calls in the crash reports for beaver plugin {code:java} "ts":"2018-08-08T13:15:29Z","source":"app-track","sid":"d747349b-92c5-4551-9c33-fd003d588379","platform":"Windows10","osver":"10.0.0","mid":"0cbf27f813e196f27c706e11f6aa4461","id":"c1c6f814-6eb2-4aef-8014-1d1c2fb1d249","guid":"936afc9e-28ed-4618-88b8-f6e6e3869b09","event":"crash.studio","data":{"stack":"Exception:HIDDEN: Cannot recover from the syntax error\\n\\t at HIDDEN.HIDDEN(HIDDEN:-1)\\n\\t at com.aptana.js.core.parsing.JSParser.recoverFromError(JSParser.java:493)\\n\\t at HI {code} | 5 |
2,769 | TISTUD-9118 | 09/04/2018 08:16:05 | Failed to add Alloy project templates when there is a new Appc CLI core update | {code:java} !MESSAGE (Build 5.2.0.qualifier) [ERROR] Failed to add Alloy project templates !STACK 0 java.lang.IllegalStateException: unknown char 'A'(65) in |||A new update (7.0.6) is available... Download with appc use 7.0.6 [ { "name": "default", "label": "Default Alloy Project", "Description": "Basic \"Hello, World!\" application using the Alloy MVC framework.", "icon": "app.png" }, { "name": "two_tabbed", "label": "Two-tabbed Alloy Application", "Description": "Titanium's traditional two-tabbed application created using the Alloy MVC framework.", "icon": "app.png" } ] at com.aptana.jetty.util.epl.ajax.JSON.handleUnknown(JSON.java:910) at com.aptana.jetty.util.epl.ajax.JSON.parse(JSON.java:898) at com.aptana.jetty.util.epl.ajax.JSON.parse(JSON.java:724) at com.aptana.jetty.util.epl.ajax.JSON.parse(JSON.java:180) at com.appcelerator.titanium.alloy.internal.core.AlloyManager.getElementsOfType(AlloyManager.java:296) at com.appcelerator.titanium.alloy.internal.core.AlloyManager.getTemplates(AlloyManager.java:221) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.addAlloyTemplates(AlloyTemplateInstaller.java:68) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:102) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) (Build 5.2.0.qualifier) [ERROR] Failed to add Alloy project templates java.lang.IllegalStateException: unknown char 'A'(65) in |||A new update (7.0.6) is available... Download with appc use 7.0.6 [ { "name": "default", "label": "Default Alloy Project", "Description": "Basic \"Hello, World!\" application using the Alloy MVC framework.", "icon": "app.png" }, { "name": "two_tabbed", "label": "Two-tabbed Alloy Application", "Description": "Titanium's traditional two-tabbed application created using the Alloy MVC framework.", "icon": "app.png" } ] at com.aptana.jetty.util.epl.ajax.JSON.handleUnknown(JSON.java:910) at com.aptana.jetty.util.epl.ajax.JSON.parse(JSON.java:898) at com.aptana.jetty.util.epl.ajax.JSON.parse(JSON.java:724) at com.aptana.jetty.util.epl.ajax.JSON.parse(JSON.java:180) at com.appcelerator.titanium.alloy.internal.core.AlloyManager.getElementsOfType(AlloyManager.java:296) at com.appcelerator.titanium.alloy.internal.core.AlloyManager.getTemplates(AlloyManager.java:221) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.addAlloyTemplates(AlloyTemplateInstaller.java:68) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:102) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} | 3 |
2,770 | TISTUD-9123 | 09/11/2018 10:18:34 | Issues with the re-engineered session management | Issue1: When the session is invalid, then upon trying to create a project the error report shows the following error first: {code} !ENTRY org.eclipse.core.resources 4 368 2018-09-11 17:10:49.271 !MESSAGE Resource '/test123' does not exist. {code} In Studio the appropriate alert message is shown regarding session being invalid. However as soon as we close the alert message a NPE message is shown. {code} !ENTRY com.aptana.projects 2 0 2018-09-11 17:11:36.802 !MESSAGE Internal error: null !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.registerApp(NodeAppcCLI.java:804) at com.appcelerator.titanium360.ui.wizard.Titanium360ProjectWizardContributor.performWizardFinish(Titanium360ProjectWizardContributor.java:135) at com.aptana.projects.wizards.ProjectWizardContributionManager.performProjectFinish(ProjectWizardContributionManager.java:246) at com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:262) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262) at com.aptana.projects.wizards.AbstractNewProjectWizard.doCreateProject(AbstractNewProjectWizard.java:323) at com.aptana.projects.wizards.AbstractNewProjectWizard$2.run(AbstractNewProjectWizard.java:376) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) {code} Issue 2: On Windows OS, when the session gets invalid and the user clicks on the username in status bar then there are two pop ups shown. One for login with fields to enter username and password credentials and the second prompt for select Org. The select Org prompt should not be shown till username and password have been entered and submitted. Check screenshot !LoginIssue.png|thumbnail! | 3 |
2,771 | TISTUD-9125 | 09/12/2018 07:45:52 | Error reporting: Deleting a closed project thrown an exception | While deleting a closed project, error reporting prompt appeared with an exception. *To reproduce:* # Close a project # Delete a closed project # Error reporting prompt appeared with an exception Please find the exception below {code:java} The following data will be sent: ------ STATUS ------ pluginId com.aptana.usage pluginVersion 4.0.0.qualifier code 0 severity 4 message (Build 5.1.0.201809100526) [ERROR] Project 'CSS' is not open. fingerprint 2f4238ba stacktrace Exception:org.eclipse.core.internal.resources.ResourceException: Project 'CSS' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144) at org.eclipse.core.internal.resources.Project.getDescription(Project.java:389) at com.aptana.usage.internal.SendPingJob$1.resourceChanged(SendPingJob.java:189) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:265) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:369) at org.eclipse.core.internal.resources.Resource.broadcastPreDeleteEvent(Resource.java:1836) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:745) at org.eclipse.core.internal.resources.Project.delete(Project.java:318) at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:155) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:280) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:280) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:257) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:305) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:96) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:216) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:86) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) ------ STATUS ------ pluginId org.eclipse.core.resources pluginVersion 3.12.0.v20170417-1558 code 372 severity 4 message Project 'CSS' is not open. [detached from CoreException of Status '(Build 5.1.0.201809100526) [ERROR] Project 'CSS' is not open.' by Error Reporting] fingerprint 00000000 stacktrace ------ REPORT ------ name Kondal Kolipaka email [email protected] comment productVersion 5.1.0.201809100526 productName Appcelerator Studio javaRuntimeVersion 1.8.0_144-b01 osgiWs cocoa osgiOs MacOSX osgiOsVersion 10.13.4 osgiArch x86_64 {code} | 3 |
2,772 | TISTUD-9129 | 09/28/2018 05:40:34 | Cannot launch studio with JDK 11 | Cannot launch studio with JDK 11. Upon launch an error is shown. Below is the error log {code} !SESSION 2018-09-28 10:02:10.883 ----------------------------------------------- eclipse.buildId=unknown java.version=11 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_SG Framework arguments: -keyring /Users/ssekhri/.eclipse_keyring Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/ssekhri/.eclipse_keyring !ENTRY org.eclipse.core.net 1 0 2018-09-28 10:02:15.418 !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.osgi 4 0 2018-09-28 10:02:15.507 !MESSAGE Application error !STACK 1 org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:410) at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318) at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:491) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:505) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:204) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:614) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) at org.eclipse.equinox.launcher.Main.run(Main.java:1499) Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124) at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399) ... 22 more Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.100.v20170421-1418 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ... 24 more !ENTRY org.eclipse.e4.ui.workbench 4 0 2018-09-28 10:02:15.512 !MESSAGE FrameworkEvent ERROR !STACK 0 java.lang.NoClassDefFoundError: javax/annotation/PreDestroy at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:450) at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:156) at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78) at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111) at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74) at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:178) at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:99) at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:141) at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:168) at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) at org.eclipse.osgi.container.Module.doStop(Module.java:634) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.100.v20170421-1418 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ... 21 more !ENTRY org.eclipse.core.jobs 4 2 2018-09-28 10:02:15.901 !MESSAGE An internal error occurred during: "Checking signedIn user". !STACK 0 java.lang.NullPointerException at org.eclipse.core.internal.runtime.InternalPlatform.getOS(InternalPlatform.java:395) at org.eclipse.core.runtime.Platform.getOS(Platform.java:1126) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.getCLIPath(NodeAppcCLI.java:170) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.isInstalled(NodeAppcCLI.java:599) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.isAppcCoreInstalled(NodeAppcCLI.java:815) at com.appcelerator.titanium.core.user.TitaniumUserManager.hasSignedInUser(TitaniumUserManager.java:517) at com.appcelerator.titanium.core.user.TitaniumUserManager$6.run(TitaniumUserManager.java:637) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} | 8 |
2,773 | TISTUD-9138 | 10/10/2018 14:28:18 | Support 'source-maps' property in tiapp.xml | At the moment when the {{tiapp.xml}} includes 'source-maps' (https://jira.appcelerator.org/browse/TIMOB-26333) studio shows an error. Steps to reproduce: 1. Enable source-maps by adding the <source-maps>true</source-maps> flag to your tiapp.xml 2. tiapp.xml shows the error on the source-maps keyword | 2 |
2,774 | TISTUD-9148 | 10/31/2018 15:47:12 | Update the Node.js installer links to the latest LTS 10.13 | Update the Appcelerator Node.js installer links to 10.13 (ideally with or before our SDK 8.0.0 coupled release) http://go.appcelerator.com/installer_nodejs_osx http://go.appcelerator.com/installer_nodejs_windows.msi | 3 |
2,775 | TISTUD-9149 | 10/31/2018 16:56:39 | Update studio to new IOS module zip path to match with SDK changes | h5. Description: 1. SDK now looks for packaged IOS module zip at a new location in the module project here: {code} https://github.com/appcelerator/titanium_mobile/blob/d7f9d09336a45e0fae2461286692982f84ad98e8/iphone/cli/commands/_buildModule.js#L611 {code} 2. Studio 5.1.1 throws error while trying to packaging: {code} Unable to locate generated zip file at /Users/kmahalingam/Documents/Appcelerator_Studio_Workspace/hh/com.appc.hh-iphone-1.0.0.zip {code} 3. Studio needs to be updated to look for the module in the new path as well as old path for backward compatibility. h5. Expected result: 1. Studio does not throw error while packaging IOS module. | 1 |
2,776 | TISTUD-9151 | 11/08/2018 01:20:30 | Fixing JSStyle Validator issues with Graal | Following test cases need to be addressed with ES6 changes com.aptana.js.internal.core.build.JSStyleValidatorTest.testTabsDontMessUpOffset com.aptana.js.internal.core.build.JSStyleValidatorTest.testBadAssignmentA1 com.aptana.js.internal.core.build.JSStyleValidatorTest.testBadAssignmentA5 com.aptana.js.internal.core.build.JSStyleValidatorTest.testStatementBlock1 com.aptana.js.internal.core.build.JSStyleValidatorTest.testStatementBlock2 com.aptana.js.internal.core.build.JSStyleValidatorTest.testWeirdProgram1 com.aptana.js.internal.core.build.JSStyleValidatorTest.testWeirdProgram2 com.aptana.js.internal.core.build.JSStyleValidatorTest.testWeirdProgram3 com.aptana.js.internal.core.build.JSStyleValidatorTest.testUseArray3 com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock1 com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock2 com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock3 com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock4 com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock5 com.aptana.js.internal.core.build.JSStyleValidatorTest.testMoveInvocation2 com.aptana.js.internal.core.build.JSStyleValidatorTest.testUnreachableAB1 com.aptana.js.internal.core.build.JSStyleValidatorTest.testUnreachableAB2 com.aptana.js.internal.core.build.JSStyleValidatorTest.testUnreachableAB3 com.aptana.js.internal.core.build.JSStyleValidatorTest.testStatementBlockOK2 com.aptana.js.internal.core.build.JSStyleValidatorTest.testMissingA1 c | 5 |
2,777 | TISTUD-9155 | 11/19/2018 08:05:28 | Studio 6.0 GA: Install Java 11 with Studio 6.0 installers | Install Java 11(LTS) with the Studio 6.0 installers(Windows and macOS) Installer links: http://go.appcelerator.com/installer_jdk_mac http://go.appcelerator.com/installer_jdk_windows http://go.appcelerator.com/installer_jdk_windows_x64 | 5 |
2,778 | TISTUD-9156 | 11/26/2018 15:41:33 | Studio 6.0 RC: Update Studio 6.0 with the JDK 11 temporary links for macOS and Win64 | For Studio 6.0 RC, we need to update the installers with the Java 11 temporary links. Since Java 10 and 11 won't support 64-bit JDK installers will update only Studio Windows 64bit and macOS installers. | 5 |
2,779 | TISTUD-9166 | 01/31/2019 22:17:22 | iOS Debug: The iOS debug breaks on few anonymous files before app launches | Debug of alloy or classic app on iOS device or iOS simulator breaks few times on anonymous files before the app launch or the user added breakpoint. This happens with 8.0.0.X SDK builds and the issue is not seen when the app is built with 7.5.0.GA Steps to Reproduce: 1. Create an alloy or classic app 2. Set a breakpoint in a js file in the created app project 3. Debug on iOS simulator or device Actual Result: The debug process breaks at few anonymous files before the app launch and before it hits the user added breakpoint. Check the screenshots as well from studio showing the debug stack Expected Result: The debug process should break at the user added breakpoint | 8 |
2,780 | TISTUD-9168 | 05/09/2019 22:55:21 | Debugger: Debug on Android fails with exception during app launch on device | When trying to debug a titanium project on Android device it fails with an exception at the time of app launch. Steps to Reproduce: 1. Create a titanium project 2. Select to debug on Android device Actual Result: The project builds and installs on device successfully. When the debugger tries to launch the app on the device it fails with exception as below: {code} !MESSAGE An internal error occurred during: "Launching Android Device - debug_test". !STACK 0 java.lang.NullPointerException at com.axway.inspector.protocol.Inspector.sendCommandAsync(Inspector.java:240) at com.axway.inspector.protocol.Inspector.sendCommandAsync(Inspector.java:231) at com.axway.inspector.debugger.Debugger.enable(Debugger.java:67) at com.axway.inspector.model.InspectorDebugTarget.setupSession(InspectorDebugTarget.java:848) at com.appcelerator.titanium.android.debug.core.inspector.V8InspectorDebugTarget.setupSession(V8InspectorDebugTarget.java:33) at com.axway.inspector.model.InspectorDebugTarget.init(InspectorDebugTarget.java:832) at com.appcelerator.titanium.android.ui.launching.device.AndroidDebugOnDeviceLaunchConfigurationDelegate.connectInspectorBasedDebugger(AndroidDebugOnDeviceLaunchConfigurationDelegate.java:267) at com.appcelerator.titanium.android.ui.launching.device.AndroidDebugOnDeviceLaunchConfigurationDelegate.connect(AndroidDebugOnDeviceLaunchConfigurationDelegate.java:211) at com.appcelerator.titanium.android.ui.launching.device.AndroidDebugOnDeviceLaunchConfigurationDelegate.launch(AndroidDebugOnDeviceLaunchConfigurationDelegate.java:119) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:862) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:720) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1029) at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1243) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) {code} Expected Result: The debugger should work on Android device | 0 |
2,781 | TISTUD-9170 | 05/10/2019 19:27:58 | Debugger: Exception in variable view due to empty labels for few variables | Exceptions are shown when expanding a variable to view its child key-values. The exception gets generated when a blank row/rows are shown in the variable view. On iOS this issue doesn't really occur but was seen when during debug a source file was opened showing Source not found. On Android it is easily reproducible for few variables like when we expand the variables Ti or Titanium or Tabgroup or Win Steps to Reproduce: 1. Create a default classic titanium project 2. Add a breakpoint to tabGroup.open() 3. Debug on Android device/emulator 4. When the debug thread gets suspended on the brekapoint, check the variables view and expand the variable tabgroup Actual Result: Blank rows are shown upon expansion. Also exceptions are shown. Following are the studio logs: {code} !ENTRY org.eclipse.core.jobs 4 2 2019-05-10 10:53:32.864 !MESSAGE An internal error occurred during: "Label Job". !STACK 0 java.lang.NullPointerException at com.axway.inspector.model.InspectorVariablePreview.getValue(InspectorVariablePreview.java:77) at org.eclipse.debug.internal.ui.model.elements.VariableLabelProvider.getLabel(VariableLabelProvider.java:95) at org.eclipse.debug.internal.ui.model.elements.ElementLabelProvider.getLabel(ElementLabelProvider.java:315) at org.eclipse.debug.internal.ui.model.elements.ElementLabelProvider.retrieveLabel(ElementLabelProvider.java:218) at org.eclipse.debug.internal.ui.model.elements.ElementLabelProvider$LabelUpdater.run(ElementLabelProvider.java:165) at org.eclipse.debug.internal.ui.model.elements.ElementLabelProvider$LabelJob.run(ElementLabelProvider.java:74) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) !ENTRY org.eclipse.core.jobs 4 2 2019-05-10 10:53:32.865 !MESSAGE An internal error occurred during: "has children update". !STACK 0 java.lang.NullPointerException at com.axway.inspector.model.InspectorVariablePreview.getValue(InspectorVariablePreview.java:77) at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.hasChildren(VariableContentProvider.java:65) at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.updateHasChildren(ElementContentProvider.java:229) at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$3.run(ElementContentProvider.java:206) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} | 8 |
2,782 | TISTUD-9178 | 06/07/2019 14:53:04 | Support inline source mapping | We currently support source maps written to external files. However, we've started to move towards inlining source maps for the transpile phase. We should support reading in and using the inlined source maps on the generated JS files. | 8 |
2,783 | TISTUD-9190 | 08/15/2019 19:13:03 | iOS:Running iOS app on same simulator multiple times throws error and exits with code 165 | *Steps to Reproduce:* 1.Create a classic app 2.Run on iOS simulator 3.Rerun on same simulator again *Actual:* throws error and exits [INFO] : Launching iOS Simulator [TRACE] : [ioslib] Selected iOS Simulator: iPhone 6 [TRACE] : [ioslib] UDID = 2A09648F-A541-4DD5-9E06-3B6087C54CB3 [TRACE] : [ioslib] iOS = 12.2 [TRACE] : [ioslib] Autoselected Xcode: 10.3 [TRACE] : [ioslib] Checking if the simulator /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator is already running [TRACE] : [ioslib] Simulator is not running [TRACE] : [ioslib] Tailing iPhone 6 Simulator system log: /Users/kmahalingam/Library/Logs/CoreSimulator/2A09648F-A541-4DD5-9E06-3B6087C54CB3/system.log [ERROR] : An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=165): Unable to shutdown device in current state: Shutdown *Expected:* App should launch fine *Notes:* *It is happening only on studio not on command line | 5 |
2,784 | TISTUD-9201 | 11/18/2019 16:38:26 | iOS Simulator stopped working after completing app building in Axway Appcelerator Studio Version: 5.1.4.201909061933 | After updating Axway Appcelerator Studio to Version: 5.1.4.201909061933, customer facing an issue. The issue is, whenever client starts an iOS simulator from appcelerator studio for app building, it starts. After completing app building, if client stopped/quitted the application from app building, it killed the iOS simulator as well. It also happened from appcelerator CLI. He downgraded from Xcode 11.2.1 to Xcode 11.1, but it didn't change the situation. *Attachments*: 1. appc ti info 2. trace log from app building | 0 |
2,785 | TISTUD-9204 | 12/17/2019 01:11:14 | Android: Module packaging disabled in studio for module created with SDK supporting gradle | h5.Steps to reproduce: 1. Create an android module with SDK 9.0.0 which has the gradle fixes. 2. Try to package the module. h5.Actual results: 1. Module package options are disabled for the module. h5.Expected results: 1. Module packaging options should be enabled & functional. | 8 |
2,786 | TISTUD-9207 | 02/19/2020 18:50:51 | Remove API Builder capabilities | h5.Description API Builder v3 is being retired, and will be removed from Appc CLI 8. We should also remove these CLI-1385 | 3 |
2,787 | TISTUD-9208 | 03/02/2020 15:57:25 | Fix Mac Installer signing: need new key/cert pair | This is currently breaking builds of the Mac Installer, as the private key/cert pair are now expired. | 8 |
2,788 | TISTUD-9209 | 03/02/2020 20:33:52 | Fix Windows Installer signing: SignTool Error: The specified timestamp server either could not be reached or returned an invalid response. | This is currently breaking builds of the Windows Installer. The old timestamp URL/server has been de-commissioned and the new URL I tried doesn't seem to be working either. | 8 |
2,789 | TISTUD-9211 | 03/13/2020 21:06:05 | Issues with version number and About page in RC build | The latest RC build for 6.0.0 studio has following issues: 1. The splash screen does not show the version number. Instead it shows a placeholder ${qualifiedVersion} Similarly the diagnostic logs show the placeholder instead of exact value. 2. The "About Axway Appcelerator Studio" page does not open. It shows the following error {code} !ENTRY org.eclipse.e4.ui.workbench 4 0 2020-03-13 14:05:26.415 !MESSAGE Command 'org.eclipse.ui.help.aboutAction' failed !STACK 0 org.eclipse.core.commands.ExecutionException: Error executing 'org.eclipse.ui.help.aboutAction': java.lang.IllegalArgumentException: This method is not available in MessageFormat objects that use alphanumeric argument names. at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:170) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:498) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:195) at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.runCommand(CocoaUIHandler.java:424) at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.access$1(CocoaUIHandler.java:410) at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler$2.widgetSelected(CocoaUIHandler.java:284) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4406) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1512) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1535) at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1585) at org.eclipse.swt.widgets.MenuItem.sendSelection(MenuItem.java:595) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5838) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:5284) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5716) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:97) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3804) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:633) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:126) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:660) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) at org.eclipse.equinox.launcher.Main.run(Main.java:1468) Caused by: org.eclipse.e4.core.di.InjectionException: java.lang.IllegalArgumentException: This method is not available in MessageFormat objects that use alphanumeric argument names. at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156) ... 42 more Caused by: java.lang.IllegalArgumentException: This method is not available in MessageFormat objects that use alphanumeric argument names. at com.ibm.icu.text.MessageFormat.format(MessageFormat.java:2170) at com.ibm.icu.text.MessageFormat.format(MessageFormat.java:2156) at com.ibm.icu.text.MessageFormat.format(MessageFormat.java:1089) at java.base/java.text.Format.format(Format.java:158) at com.ibm.icu.text.MessageFormat.format(MessageFormat.java:1028) at org.eclipse.ui.internal.ProductProperties.getAboutText(ProductProperties.java:278) at org.eclipse.ui.internal.dialogs.AboutDialog.createDialogArea(AboutDialog.java:196) at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:767) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1094) at org.eclipse.jface.window.Window.open(Window.java:788) at org.eclipse.ui.internal.about.AboutHandler.execute(AboutHandler.java:31) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:95) at jdk.internal.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58) ... 46 more {code} | 3 |
2,790 | TISTUD-9212 | 03/24/2020 13:17:51 | [Windows] Syntax highlighting is not present | When creating/opening an application in APPC studio, no syntax highlighting can be seen (e.g tiapp.xml or JS files). +*Steps to reproduce:*+ # Download an APPC studio build in this case a GA candidate (https://jenkins.appcelerator.org/job/appcelerator-studio/job/titanium_studio/job/master/155) # Run the installer # Create a new work space # Create an Alloy or Titanium application # Check the Tiapp.xml and JS files *+Actual result+* No syntax formatting is seen *+Expected result+* Syntax formatting should be seen | 8 |
2,791 | TISTUD-9213 | 03/24/2020 14:11:41 | [Windows] When checking windows processes, APPC Studio process shows as Java | Once APPC studio is running and the user checks running processes, APPC studio is shown as JAVA platform. *Test Steps:* # Download an APPC studio build in this case a GA candidate (https://jenkins.appcelerator.org/job/appcelerator-studio/job/titanium_studio/job/master/155) # Run the installer # Create a new work space # Press {{CTRL + ALT + DELETE}} # Select Task manager # Look for the Appcelerator studio process *+Actual result:+* (APPC Studio: 6.0.0.202003181504) Running process is seen as: !image-2020-03-24-14-08-57-530.png|thumbnail! *+Expected result:+* (APPC Studio: 5.1.4.201909061933) Running process should be seen as: !image-2020-03-24-14-09-54-698.png|thumbnail! | 8 |
2,792 | TISTUD-9215 | 04/16/2020 16:03:03 | iOS: Debugging on 13.4 Simulators shows a 'Debug child count update' error | When debugging using iOS 13.4 simulators the following error is shown (not seen using iOS 13.1 Sims). !Screenshot 2020-04-16 at 15.54.56.png|thumbnail! *Test Steps:* # Download Appc studio 6.0.0 (e.g. from https://preview.appcelerator.com/appc-studio/) # Download the latest SDK from 9_0_X (In this case 9.0.1.v20200415143120) # Make sure you have iOS13.4 sims installed (will require XCode 11.4) # Create an alloy application # Set breakpoints in the {{index.js}} (line 2 and 5 for example) # Debug to 13.4 Simulator # Try {{step in}} or click on {{hello world}} *Expected result* Application should debug without any issues *Actual result* Above error is shown | 8 |
2,793 | TISTUD-9219 | 05/12/2020 02:15:14 | With latest RC build all open projects are rebuilt on every studio launch | This is a regression with latest RC. The issue did not happen on older version of 6.0 RC build. Every time studio is launched then all the loaded and open projects are rebuilt. | 5 |
0 | XD-7 | 04/12/2013 06:43:52 | Tuple data structure | The tuple data structure should be backward compatible in functionality for use in spring batch. Porting over FieldSet tests in spring batch to use the tuple data structure is one way help ensure that compatibility. | 1 |
1 | XD-10 | 04/12/2013 06:44:56 | Reactor based http ingestion | When there is support for boostrapping a http server in the reactor project, and inbound SI adapter and associated XD source module should be created. | 5 |
2 | XD-22 | 04/16/2013 11:20:36 | Create Module base abstractions | A module groups together a collection of spring configuration files. | 0 |
3 | XD-24 | 04/16/2013 11:23:51 | Create pipes and filters DSL for ingestion | Initial simple handcoded implementation for straight through pipe and filter model, e.g. a | b | c | 2 |
4 | XD-28 | 04/17/2013 08:48:08 | Create simple gague service | A gauge just stores a number. Implementations for in-memory and redis. | 1 |
5 | XD-29 | 04/17/2013 08:49:15 | Create rich gauge service | A rich gauge stores a number and also rmd, min, max. Implementations for in-memory and redis. | 5 |
6 | XD-30 | 04/17/2013 08:50:13 | Create a simple counter service | A simple counters can increment/decrement a number. Implementations for in-memory and redis. | 1 |
7 | XD-31 | 04/17/2013 08:51:18 | Create field-value counters | A field-value counter is useful for bar chart graphs, Strings on x-axis and count on y-axis. Maps well to zset in redis. Implementations for in-memory and redis. | 5 |
8 | XD-32 | 04/17/2013 11:22:10 | Create base Channel Registry abstraction | Define the ChannelRegistry interface. | 0 |
9 | XD-33 | 04/17/2013 11:24:06 | Implement LocalChannelRegistry | This should be usable within a single JVM process. Lives within shared application context of the process. | 0 |
10 | XD-37 | 04/22/2013 09:48:16 | Gradle based multi-project build | multi project build. - look to Spring Framework for source of starting point. | 2 |
11 | XD-43 | 05/06/2013 07:35:36 | Metric repositories should support Spring Data CrudRepository interface | This provides common CRUD behavior and a shared interface that can be useful in testing scenarios. | 5 |
12 | XD-44 | 05/06/2013 07:39:10 | Redis based repositories should use a NamingStrategy class to calculate the name of the key to use for persistence | RedisCounterRepository and RedisGaugeRepository have duplicated code that needs to be factored out into a one place. One such duplication is the determination of the key name to use for persistence. This should be abstracted out into a strategy helper class. | 1 |
13 | XD-45 | 05/06/2013 07:44:41 | Remove the expiry of keys in Redis based repositories | There is duplicated code in Redis based repositories that related to expiry behavior, move into a common shared helper class and/or base class. | 1 |
14 | XD-50 | 05/07/2013 08:37:05 | Add tap support to DIRT | syntax: {code} tap @ somechannel --key=value | somecounter {code} | 2 |
15 | XD-53 | 05/08/2013 14:07:47 | Design and document desired high level DSL for configuring data processing in XD | Start to explore how the DSL can cover both advanced (non-linear) spring integration flows as well as spring batch jobs. | 13 |
16 | XD-54 | 05/08/2013 14:17:42 | XD Metrics backed Message Counter | A Spring Integration based @ServiceActivator that counts the number of messages using the Spring XD metrics support | 1 |
Subsets and Splits