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
|
|---|---|---|---|---|---|
459 | APSTUD-7630 | 12/19/2012 02:49:54 | Aptana Eclipse plug-in fails to download | Aptana fails ot install the Eclipse plugin. I tried several methods. Market place, direct download, update site, etc. Using the given direct download, * http://www.aptana.com/products/studio3/download Crashes Juno during the download with a zip file error. ---------[ zip error ]--------- java.util.zip.ZipException: zip file is empty at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(Unknown Source) at java.util.zip.ZipFile.<init>(Unknown Source) at org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.basicLoadManifest(BundlesAction.java:576) at org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.loadManifest(BundlesAction.java:562) at org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.createBundleDescription(BundlesAction.java:555) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.processBundle(RepositoryListener.java:141) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.process(RepositoryListener.java:136) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.added(RepositoryListener.java:117) at org.eclipse.equinox.internal.p2.extensionlocation.BundlePoolFilteredListener.added(BundlePoolFilteredListener.java:42) at org.eclipse.equinox.internal.p2.extensionlocation.SiteListener.added(SiteListener.java:336) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.processFile(DirectoryWatcher.java:197) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.scanDirectories(DirectoryWatcher.java:160) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:108) at org.eclipse.equinox.internal.p2.extensionlocation.SiteListener.synchronizeRepositories(SiteListener.java:111) at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationMetadataRepository.ensureInitialized(ExtensionLocationMetadataRepository.java:66) at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationMetadataRepository.getProperties(ExtensionLocationMetadataRepository.java:194) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.addRepository(AbstractRepositoryManager.java:127) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:657) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.loadMetadataRepository(Activator.java:99) at org.eclipse.equinox.internal.p2.reconciler.dropins.PlatformXmlListener.synchronizeConfiguration(PlatformXmlListener.java:227) at org.eclipse.equinox.internal.p2.reconciler.dropins.PlatformXmlListener.stopPoll(PlatformXmlListener.java:133) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.stopPoll(DirectoryWatcher.java:171) at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:109) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.watchConfiguration(Activator.java:511) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:174) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) ---------[ ]--------- | 2 |
460 | APSTUD-7634 | 12/20/2012 02:12:05 | PHP $var not being highlighted inside double quotes | The PHP syntax highlighting used to work before the last update (I belive I was previously using 3.0.4) inside of double quotes: <?php $string = "hello $name" ;?> The $name used to get fully highlighted, now it only highlights the $. This can make it a lot more difficult to review the code, and see when a variable is being used vs normal string chars. EDIT: I am using version 3.3.1.201212171919 | 5 |
461 | APSTUD-7636 | 12/20/2012 06:58:08 | Cannot show preview (embedded WebKit browser) | h3. Steps to Reproduce 1. Update to Aptana 3.3.1. 2. Open HTML page. 3. Press button 'Show Preview Editor' h3. Actual Result New tab header is created (clicking on this tab has no effect). Error record is appended to log file: 'java.lang.NoClassDefFoundError: Could not initialize class cef.CEFJNI' h3. Expected Result Preview should be opened exactly as in previous versions of Aptana. Preview worked without errors in Aptana 3.2.X before updating to 3.3.1. | 5 |
462 | APSTUD-7638 | 12/20/2012 07:10:15 | When submitting ticket from Aptana it skips some fields | h3. Steps to Reproduce 1. Create ticket from Aptana. 2. Select severity. 3. Attach log file. 4. Press OK. 5. Check created ticket in web browser (on jira.appcelerator.org). h3. Actual Result No attachments will be created. h3. Expected Result Log file should be attached. | 8 |
463 | APSTUD-7662 | 01/03/2013 09:24:59 | Aptana Studio 3 crashes on attempted preview/render | h3. Steps to Reproduce Have tested and retested what is causing this: The addition of a textarea element to a HTML file. File has previously been successfully previewed many times. Tested adding the textarea with a combination (none, all, some) of the rows, cols and name attributes just in case it was expecting something that wasn't there: no difference. The inclusion of the textarea element causes Aptana to crash on preview attempt. While I wasn't able to include a screenshot I did attach the various error logs I could assemble: aptana diagnostic, aptana log file (cleared then reproduced error) and system error report on crash (Mac OS X 10.6.8) h3. Actual Result Aptana Studio 3 crashes about a second after pressing the preview button. h3. Expected Result Expected successful preview/render. | 3 |
464 | APSTUD-7686 | 01/14/2013 13:40:35 | NullPointerException when trying to get a UserAgent for JS code assist | An exception occasionally happens when performing a code assist on a JS file: {code} Exception in thread "Aptana: ContentAssistant.assist_delay_timer_name" org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:196) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4613) at com.aptana.editor.common.contentassist.ContentAssistant$AutoAssistListener.showAssist(ContentAssistant.java:456) at com.aptana.editor.common.contentassist.ContentAssistant$AutoAssistListener.run(ContentAssistant.java:311) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.NullPointerException at com.aptana.core.internal.UserAgentManager.getUserAgentById(UserAgentManager.java:162) at com.aptana.editor.common.contentassist.UserAgentManager.getUserAgentById(UserAgentManager.java:368) at com.aptana.editor.common.contentassist.UserAgentManager.getUserAgentsByID(UserAgentManager.java:355) at com.aptana.editor.common.contentassist.UserAgentManager.getActiveUserAgents(UserAgentManager.java:208) at com.aptana.editor.common.contentassist.UserAgentManager.getUserAgentImages(UserAgentManager.java:309) at com.aptana.editor.js.contentassist.JSContentAssistProcessor.addProposal(JSContentAssistProcessor.java:360) at com.aptana.editor.js.contentassist.JSContentAssistProcessor.addKeywords(JSContentAssistProcessor.java:179) at com.aptana.editor.js.contentassist.JSContentAssistProcessor.doComputeCompletionProposals(JSContentAssistProcessor.java:738) at com.aptana.editor.common.CommonContentAssistProcessor.computeCompletionProposals(CommonContentAssistProcessor.java:417) at com.aptana.editor.common.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:2221) at com.aptana.editor.common.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:394) at com.aptana.editor.common.contentassist.CompletionProposalPopup.access$7(CompletionProposalPopup.java:388) at com.aptana.editor.common.contentassist.CompletionProposalPopup$1.run(CompletionProposalPopup.java:331) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.aptana.editor.common.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:325) at com.aptana.editor.common.contentassist.ContentAssistant$AutoAssistListener$1.run(ContentAssistant.java:468) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} | 5 |
465 | APSTUD-7825 | 04/18/2013 23:42:28 | Show Preview Window now loads FLUSH RIGHT only | h3. Steps to Reproduce load an HTML document and click on the Show Preview WIndow button from the toolbar. I just was upgraded to Aptana Studio 3 v. 3.4. Prior to this, the rendered HTML was always FLUSH left in the viewing screen. Info: Host OS: Mac OS X OS Version: 10.6.8 OS Arch: x86 JRE Version: 1.6.0_31 JRE Vendor: Apple Inc. JRE Home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Aptana Studio 3 Version: 3.4.0.201304151603 Install Directory: file:/Applications/Aptana Studio 3/ Workspace Directory: file:/Users/teacher/Desktop/Aptana Studio 3 Workspace/ VM Arguments: -Xms40m -Xmx512m -Declipse.p2.unsignedPolicy=allow -Declipse.log.size.max=10000 -Declipse.log.backup.max=5 -Xdock:icon=../Resources/aptana.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=256m -Djava.class.path=/Applications/Aptana Studio 3/AptanaStudio3.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar Language: en_US Node.JS Version: Not installed NPM Path: Not installed h3. Actual Result HTML loads FLUSH RIGHT ... see attached screen shot. h3. Expected Result LEFT JUSTIFICATION on the preview. | 8 |
466 | APSTUD-8026 | 10/29/2013 21:57:35 | Update PyDev to 3.0.0 | The latest version Fabio has pushed on http://pydev.org is 3.0.0 , and we should include it in Aptana Studio. The source is on https://github.com/fabioz/Pydev. | 8 |
467 | APSTUD-8061 | 12/11/2013 14:18:59 | Javascript format shorthand modulo | // crashes: res['angle'] %= (2 * Math.PI); // works: res['angle'] = res['angle'] % (2 * Math.PI); | 3 |
468 | APSTUD-8079 | 12/27/2013 19:56:18 | PyDev no longer installed after update | h3. Steps to Reproduce Updated Aptana Studio 3 to new version. Note: Trying to install Pydev using the instructions here: http://download.appcelerator.com/aptana/studio3/pydev/update/stable/ gives the message that 'pydev is already installed'. But Pydev functionality is still not available, and the Preferences menu does not list Pydev. Reverting to Aptana Studio v3.4.1 restores the Pydev functionality. h3. Actual Result Afterward update of Aptana Studio 3, Pydev isn't installed and can't be reinstalled. h3. Expected Result Should be seamless, with no steps needed to reinstall Pydev or make sure it isn't clobbered by update. | 8 |
469 | APSTUD-8217 | 06/05/2014 14:04:25 | Windows: Aptana Studio Installer: Studio does not install JRE and hence fails installation | This is regression issue since earlier studio used to get installed with JRE successfully. *Steps To Replicate*: 1. Download *Aptana Studio RC build* 2. Try installing same on clean windows 7 machine. Actual: {color:red} *Some Prerequisite JRE could not be downloaded error appears. Refer screenshot.* {color} Expected: No error should appear. Installation must be successful. | 5 |
470 | APSTUD-8257 | 08/01/2014 10:42:59 | Can't access connections row from Project Explorer | h3. Steps to Reproduce Create a project and open the Project Explorer window h3. Actual Result Don't show the connections row h3. Expected Result Be able to connect to remote servers via connections | 5 |
471 | APSTUD-8259 | 08/01/2014 18:42:29 | Aptana Studio 3 Crashes on Startup after Updating | I just installed an update for Aptana Studio and once I did, it would no longer open but would crash while loading, during the splash screen. I then updated my Java version and reinstalled Aptana Studio but still had the same problem. I am on Mac OS X 10.9.4. As suggested, I ran it from the terminal and here is the output: {code} tgmac$ /Applications/Aptana\ Studio\ 3/AptanaStudio3.app/Contents/MacOS/AptanaStudio3 !SESSION 2014-08-01 13:21:32.345 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_65 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/thangrove/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/thangrove/.eclipse_keyring -consoleLog -showlocation !ENTRY org.eclipse.core.resources 2 10035 2014-08-01 13:21:43.412 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.core.net 1 0 2014-08-01 13:22:02.129 !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.ui.workbench 4 2 2014-08-01 13:22:04.129 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". !STACK 0 java.lang.NullPointerException at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:671) at com.aptana.scripting.ui.ScriptingUIPlugin.getImageDescriptor(ScriptingUIPlugin.java:71) at com.aptana.scripting.ui.ScriptingConsole.<init>(ScriptingConsole.java:68) at com.aptana.scripting.ui.ScriptingConsole.getInstance(ScriptingConsole.java:42) at com.aptana.scripting.ui.ScriptingConsoleStartup.earlyStartup(ScriptingConsoleStartup.java:25) at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2555) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !ENTRY org.eclipse.ui 4 4 2014-08-01 13:22:04.186 !MESSAGE Unhandled Exception !ENTRY com.aptana.scripting.ui 4 0 2014-08-01 13:22:04.186 !MESSAGE Unable to execute early startup code for an extension !STACK 0 java.lang.NullPointerException at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:671) at com.aptana.scripting.ui.ScriptingUIPlugin.getImageDescriptor(ScriptingUIPlugin.java:71) at com.aptana.scripting.ui.ScriptingConsole.<init>(ScriptingConsole.java:68) at com.aptana.scripting.ui.ScriptingConsole.getInstance(ScriptingConsole.java:42) at com.aptana.scripting.ui.ScriptingConsoleStartup.earlyStartup(ScriptingConsoleStartup.java:25) at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2555) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) ***WARNING: Display must be created on main thread due to Cocoa restrictions. !ENTRY org.eclipse.core.jobs 4 2 2014-08-01 13:22:04.861 !MESSAGE An internal error occurred during: "Start Ruble bundle manager". !STACK 0 java.lang.NullPointerException at com.aptana.filewatcher.FileWatcherPlugin.log(FileWatcherPlugin.java:71) at com.aptana.filewatcher.FileWatcherPlugin.log(FileWatcherPlugin.java:66) at com.aptana.filewatcher.FileWatcher.instance(FileWatcher.java:51) at com.aptana.filewatcher.FileWatcher.addWatch(FileWatcher.java:71) at com.aptana.filewatcher.FileWatcher.addWatch(FileWatcher.java:65) at com.aptana.scripting.internal.model.BundleMonitor.beginMonitoring(BundleMonitor.java:123) at com.aptana.scripting.ScriptingActivator$1.run(ScriptingActivator.java:114) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !ENTRY org.eclipse.ui 4 0 2014-08-01 13:22:04.895 !MESSAGE Error occurred during status handling !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Display.error(Display.java:1076) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:833) at org.eclipse.swt.widgets.Display.create(Display.java:816) at org.eclipse.swt.graphics.Device.<init>(Device.java:130) at org.eclipse.swt.widgets.Display.<init>(Display.java:707) at org.eclipse.swt.widgets.Display.<init>(Display.java:698) at org.eclipse.swt.widgets.Display.getDefault(Display.java:1396) at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:67) at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:108) at com.aptana.rcp.IDEWorkbenchAdvisor$5.handle(IDEWorkbenchAdvisor.java:839) at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189) at org.eclipse.ui.internal.progress.ProgressManager$2.done(ProgressManager.java:467) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:96) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) !ENTRY org.eclipse.core.jobs 4 2 2014-08-01 13:22:04.899 !MESSAGE An internal error occurred during: "Start Ruble bundle manager". !STACK 0 java.lang.NullPointerException at com.aptana.filewatcher.FileWatcherPlugin.log(FileWatcherPlugin.java:71) at com.aptana.filewatcher.FileWatcherPlugin.log(FileWatcherPlugin.java:66) at com.aptana.filewatcher.FileWatcher.instance(FileWatcher.java:51) at com.aptana.filewatcher.FileWatcher.addWatch(FileWatcher.java:71) at com.aptana.filewatcher.FileWatcher.addWatch(FileWatcher.java:65) at com.aptana.scripting.internal.model.BundleMonitor.beginMonitoring(BundleMonitor.java:123) at com.aptana.scripting.ScriptingActivator$1.run(ScriptingActivator.java:114) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !ENTRY org.eclipse.core.jobs 2 2 2014-08-01 13:22:05.222 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.scripting.model.BundleManager$BundleLoadJob Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.scripting.model.BundleManager$BundleLoadJob !ENTRY org.eclipse.core.jobs 2 2 2014-08-01 13:22:05.223 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.Workbench$55 Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.Workbench$55 !ENTRY org.eclipse.core.jobs 2 2 2014-08-01 13:22:05.223 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.scripting.model.BundleManager$BundleLoadJob Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.scripting.model.BundleManager$BundleLoadJob !ENTRY org.eclipse.ui 4 4 2014-08-01 13:22:05.361 !MESSAGE Unhandled Exception !ENTRY org.eclipse.equinox.p2.ui.sdk.scheduler 4 0 2014-08-01 13:22:05.362 !MESSAGE Unable to execute early startup code for an extension !STACK 1 org.eclipse.core.runtime.CoreException: Plug-in "org.eclipse.equinox.p2.ui.sdk.scheduler" was unable to instantiate class "org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler". at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:282) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:278) at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:117) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2555) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: java.lang.NullPointerException at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.<init>(AutomaticUpdateScheduler.java:73) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:357) at java.lang.Class.newInstance(Class.java:310) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) ... 11 more !SUBENTRY 1 org.eclipse.equinox.registry 4 1 2014-08-01 13:22:05.363 !MESSAGE Plug-in "org.eclipse.equinox.p2.ui.sdk.scheduler" was unable to instantiate class "org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler". !STACK 0 java.lang.NullPointerException at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.<init>(AutomaticUpdateScheduler.java:73) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:357) at java.lang.Class.newInstance(Class.java:310) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:282) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:278) at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:117) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2555) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) ***WARNING: Display must be created on main thread due to Cocoa restrictions. !ENTRY org.eclipse.core.jobs 4 2 2014-08-01 13:22:05.376 !MESSAGE An internal error occurred during: "Loading bundle: /Applications/Aptana Studio 3/configuration/org.eclipse.osgi/bundles/90/1/.cp/bundles/capistrano.ruble". !STACK 0 java.lang.LinkageError: Error reading class bytes: org.jruby.Ruby at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:558) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:492) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:465) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:464) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.jruby.RubyInstanceConfig.<init>(RubyInstanceConfig.java:400) at org.jruby.embed.internal.AbstractLocalContextProvider.<init>(AbstractLocalContextProvider.java:42) at org.jruby.embed.internal.SingletonLocalContextProvider.<init>(SingletonLocalContextProvider.java:88) at org.jruby.embed.ScriptingContainer.getProviderInstance(ScriptingContainer.java:243) at org.jruby.embed.ScriptingContainer.<init>(ScriptingContainer.java:221) at org.jruby.embed.ScriptingContainer.<init>(ScriptingContainer.java:207) at com.aptana.scripting.ScriptingEngine.createScriptingContainer(ScriptingEngine.java:74) at com.aptana.scripting.ScriptingEngine.getScriptingContainer(ScriptingEngine.java:230) at com.aptana.scripting.ScriptingEngine.getInitializedScriptingContainer(ScriptingEngine.java:289) at com.aptana.scripting.model.ScriptLoadJob.run(ScriptLoadJob.java:76) at com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:144) at com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:180) at com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:274) at com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:243) at com.aptana.scripting.model.BundleManager.loadScript(BundleManager.java:2032) at com.aptana.scripting.model.BundleManager$BundleLoadJob.run(BundleManager.java:129) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: java.util.zip.ZipException: ZipFile closed at java.util.zip.ZipFile.ensureOpenOrZipException(ZipFile.java:427) at java.util.zip.ZipFile.access$1100(ZipFile.java:31) at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:459) at java.util.zip.ZipFile$1.fill(ZipFile.java:244) at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleEntry$ZipBundleEntryInputStream.read(ZipBundleEntry.java:157) at org.eclipse.osgi.internal.baseadaptor.AdaptorUtil.getBytes(AdaptorUtil.java:247) at org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes(BundleEntry.java:96) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:554) ... 26 more !ENTRY org.eclipse.ui 4 0 2014-08-01 13:22:05.377 !MESSAGE Error occurred during status handling !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Display.error(Display.java:1076) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:833) at org.eclipse.swt.widgets.Display.create(Display.java:816) at org.eclipse.swt.graphics.Device.<init>(Device.java:130) at org.eclipse.swt.widgets.Display.<init>(Display.java:707) at org.eclipse.swt.widgets.Display.<init>(Display.java:698) at org.eclipse.swt.widgets.Display.getDefault(Display.java:1396) at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:67) at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:108) at com.aptana.rcp.IDEWorkbenchAdvisor$5.handle(IDEWorkbenchAdvisor.java:839) at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189) at org.eclipse.ui.internal.progress.ProgressManager$2.done(ProgressManager.java:467) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:96) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) ***WARNING: Display must be created on main thread due to Cocoa restrictions. !ENTRY org.eclipse.core.jobs 4 2 2014-08-01 13:22:05.379 !MESSAGE An internal error occurred during: "Loading bundle: /Applications/Aptana Studio 3/configuration/org.eclipse.osgi/bundles/46/1/.cp/bundles/php.ruble". !STACK 0 java.lang.LinkageError: org/jruby/Ruby at org.jruby.RubyInstanceConfig.<init>(RubyInstanceConfig.java:400) at org.jruby.embed.internal.AbstractLocalContextProvider.<init>(AbstractLocalContextProvider.java:42) at org.jruby.embed.internal.SingletonLocalContextProvider.<init>(SingletonLocalContextProvider.java:88) at org.jruby.embed.ScriptingContainer.getProviderInstance(ScriptingContainer.java:243) at org.jruby.embed.ScriptingContainer.<init>(ScriptingContainer.java:221) at org.jruby.embed.ScriptingContainer.<init>(ScriptingContainer.java:207) at com.aptana.scripting.ScriptingEngine.createScriptingContainer(ScriptingEngine.java:74) at com.aptana.scripting.ScriptingEngine.getScriptingContainer(ScriptingEngine.java:230) at com.aptana.scripting.ScriptingEngine.getInitializedScriptingContainer(ScriptingEngine.java:289) at com.aptana.scripting.model.ScriptLoadJob.run(ScriptLoadJob.java:76) at com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:144) at com.aptana.scripting.model.AbstractScriptRunner.run(AbstractScriptRunner.java:180) at com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:274) at com.aptana.scripting.ScriptingEngine.runScript(ScriptingEngine.java:243) at com.aptana.scripting.model.BundleManager.loadScript(BundleManager.java:2032) at com.aptana.scripting.model.BundleManager$BundleLoadJob.run(BundleManager.java:129) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !ENTRY org.eclipse.ui 4 0 2014-08-01 13:22:05.379 !MESSAGE Error occurred during status handling !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.SWT.error(SWT.java:4283) at org.eclipse.swt.widgets.Display.error(Display.java:1076) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:833) at org.eclipse.swt.widgets.Display.create(Display.java:816) at org.eclipse.swt.graphics.Device.<init>(Device.java:130) at org.eclipse.swt.widgets.Display.<init>(Display.java:707) at org.eclipse.swt.widgets.Display.<init>(Display.java:698) at org.eclipse.swt.widgets.Display.getDefault(Display.java:1396) at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:67) at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:108) at com.aptana.rcp.IDEWorkbenchAdvisor$5.handle(IDEWorkbenchAdvisor.java:839) at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189) at org.eclipse.ui.internal.progress.ProgressManager$2.done(ProgressManager.java:467) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:96) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) {code} Thanks in advance. | 3 |
472 | APSTUD-8264 | 08/04/2014 21:16:51 | After upgrade to 3.6 switching workspaces requires forcequit | This has happened every time I needed to switch workspaces. Aptana closes like usual, but never opens up the new workspace. In fact, related perhaps, Aptana does not actually close when I quit either. The only way I can use Aptana again is by force closing through the Mac OS force close interface. It will then open and ask my which workspace I want. I have about 6 workspaces I switch between frequently. Prior to the upgrade I did not have any problems switching spaces. Also noticed that the "connections" node is missing as is the App Explorer tab. Developing js, html, css and php (no python, no mobile apps, no mysql). Thanks and let me know what other information might be helpful to you. Brian | 5 |
473 | APSTUD-8406 | 06/10/2015 09:13:31 | Aptana Fails to launch on OS X El Capitan (10.11) | Java SE 6 is no longer supported in OS X El Capitan and there will be no further support added for it, this in turn stops Aptana from starting, i have tried installing the SDK for 8+ and it still doesn't work | 1 |
474 | APSTUD-8462 | 03/24/2016 17:50:54 | alsabbat | pizzakambaden | 100 |
475 | APSTUD-8518 | 01/04/2018 19:00:02 | Aptana Studio: Start Page Unavailable | The Aptana studio is not displayed and an error is shown. h3. Steps to reproduce: # Open Aptana studio # Navigate to Help > Aptana > Show Aptana Studio Start Page h3. Actual !startPageUnavailable.PNG|thumbnail! When refresh is clicked: {noformat} {"event":"error","eventType":"Unknown Controller","data":{"errorDetails":"Unknown controller: portal.browser"}} {noformat} h3. Expected No error | 5 |
0 | CLI-903 | 07/21/2014 20:09:25 | Investigate locking down NPM dependencies | When deploying NPM modules, even if we specify exact versions in our package.json file, those dependencies could be less strict in what they choose to use. The end result is that every install of our NPM modules could be different, leading to difficult-to-reporduce bugs. One solution is to use tools like shrink-wrap or lockdown: https://www.npmjs.org/doc/cli/npm-shrinkwrap.html https://www.npmjs.org/package/lockdown Some goals: * People can use NPM install from the NPMJS repo like before * They only get the exact set of direct and indirect dependencies we've tested There is a concern (as noted in APPTS-1879) that a dependency could be unpublished from NPM. It's unclear how prevalent that is, but it is a possibility. If we instead decided to host a version of our nodules external to NPMJS, then we'd need to make sure we removed them from the main repo to avoid confusion. | 13 |
1 | CLI-649 | 03/21/2015 22:38:27 | Android build tool warning directs user to run "ti config" | h5. Description: I was warned in console of a potential compatibility issue with my build tools. This warned told me to set with "ti config". This should be updated to reflect new tools. {code}[WARN] : [WARN] : Android Build Tools 22 are too new and may or may not work with Titanium. [WARN] : If you encounter problems, select a supported version with: [WARN] : ti config android.buildTools.selectedVersion ##.##.## [WARN] : where ##.##.## is a version in /Users/eric/Android_SDK/build-tools that is <=21.x{code} h5. Steps to reproduce: 1) Install Android build tools 22 2) Create an android project in studio or CLI and run on emulator or device h5. Result: The console warning appears with references to "ti config" h5. Expected Result: The warning should say "appc ti config" | 5 |
2 | CLI-517 | 04/03/2015 15:10:54 | Add "appc test" command | I would like not to use any NPM commands when using Arrow as I feel it is confusing to jump between the two. Add `appc test` which passes through to `npm test` | 5 |
3 | CLI-531 | 04/08/2015 00:28:39 | appc unpublish should support "--project-dir" | h5. Description: While closing a related ticket, I tried {{appc run}}, {{appc publish}}, and {{appc unpublish}} from outside the project directory. {{appc unpublish --project-dir}} does not work. An error is shown like: {code}emerrimanMBP:~ eric$ appc unpublish --project-dir ~/arrowsCarbon/ Appcelerator Command-Line Interface, version 0.2.230 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. ERROR | No component found or specified for unpublish {code} h5. Steps to reproduce: 1) Create or use an Arrow project, publish the app 2) From outside the directory, run {{appc unpublish --project-dir <your directory here>}} h5. Result: The app does not unpublish, {{appc unpublish}} help does not show support for {{--project-dir}} h5. Expected Result: Unpublish support for {{--project-dir}} | 5 |
4 | CLI-615 | 04/14/2015 01:20:50 | Unable to run 'appc setup' on io.js | appc won't setup on io.js {code} appc setup [17:18:00] Finding latest version ...0.2.242 ✓ Version 0.2.242 already installed. ? Do you plan on developing Titanium apps? Yes Checking your environment... You have the latest Titanium SDK release 4.0.0.Beta2 ERROR | titanium exited with 1 exit code {code} | 5 |
5 | CLI-561 | 04/17/2015 08:22:41 | Automatically prompt for new login when session is invalid | Every now and then I get the error we see reported in the Q&A a lot as well: {code} ERROR | invalid session {code} Logging out (I using {{-D}} to be sure) and in again fixes it. I think the UX would be better if don't spit out an error but inform the user the session as expired and he needs to login again. Then under the hood logout, clean up whatever we can and present the login again. {code} ≫ appc new Appcelerator Command-Line Interface, version 0.2.247 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. ? What type of project are you creating? Native App ? Which SDK would you like to use? Titanium SDK (JavaScript) ? What's the project name? bully ? What's your application id (example: com.myapp)? nl.fokkezb ERROR | invalid session (~/dev/tests) ≫ appc logout -D Appcelerator Command-Line Interface, version 0.2.247 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. logged out (~/dev/tests) ≫ appc login Appcelerator Command-Line Interface, version 0.2.247 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ********* ? Into which organization would you like to login? Appcelerator, Inc This computer must be authorized before you can complete your login. ? Confirm with authorization code to Email or Phone/SMS? SMS to +31624105142 An authorization code was sent to your phone at +31624105142 ? Please enter the code you received: 1086 This computer is now authorized: Mac OSX Serial Number: C02MP05QFH05 You can deauthorize this computer by logging out with appc logout Generating Developer Certificate and Private/Public Keys... [email protected] logged into organization Appcelerator, Inc [14301] (~/dev/tests) ≫ appc new Appcelerator Command-Line Interface, version 0.2.247 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. ? What type of project are you creating? Native App ? Which SDK would you like to use? Titanium SDK (JavaScript) ? What's the project name? bully ? What's your application id (example: com.myapp)? nl.fokkezb ? Please provide your password for enabling Test service: ********* *** new completed. *** {code} | 3 |
6 | CLI-563 | 04/17/2015 18:34:58 | Alert users when attempting to run an app that belongs to a different org than they are currently logged in as | if the current user is logged in under Org A and tries to run an app created under Org B that fails. The error message is cryptic: {code} [ERROR] : Application not registered. titanium exited with exit code 100 {code} That's fine if the user has no rights to Org B, we shouldn't give any details about it. But if the user _is_ a member of the other org that the app belongs to, we should give more details about why we can't run this app. Specifically we should tell them they are logged in under Org A, the app is part of Org B and that they need to logout and back in under Org B to run it. | 0 |
7 | CLI-570 | 04/21/2015 10:40:26 | Titanium always does full rebuild, forced by encryptJS | When building a Titanium app for iOS Simulator, it always forces a rebuild because *JavaScript files need to be re-encrypted*. This even happens when you set deploy type to development. It does however *NOT* happen when you skip {{appc run}} and use {{ti build}} directly. This issue makes rebuilds take a lot longer then needed. h1. To reproduce 1. Create a project. 2. Run the project via AppC ({{appc run -p ios}}) once for an initial build. 3. Run the project via AppC again ({{appc run -p ios}}) and confirm it says: {{Forcing rebuild: JavaScript files need to be re-encrypted}} and later {{Forcing rebuild: ApplicationDefaults.m has changed since last build}}. 4. Run the project via AppC with development deployType ({{appc run -p ios -D development}}) once for a new build with changed deployType. 5. Run the project via AppC with development deployType ({{appc run -p ios -D development}}) again and confirm it says the same. 6. Run the project via Ti ({{ti build -p ios}}) once to generate a new build. 7. Run the project via Ti ({{ti build -p ios}}) again to confirm that this time it does not force a rebuild. Found by this user: https://community.appcelerator.com/topic/203/appcelerator-forcing-a-rebuild-for-javascript-re-encryption | 8 |
8 | CLI-571 | 04/21/2015 20:04:12 | Appc ti -v returns Appc CLI version | When I run {{appc ti -v}} I get the output of {{appc -v}}. *Steps to reproduce issue*: 1. Run {{appc ti -v}} *Actual Results*: Same output as {{appc -v}} *Expected Results*: Output should show the local Titanium CLI version. | 1 |
9 | CLI-573 | 04/22/2015 08:39:14 | Random "Cannot find module" errors when updating via "appc use latest" | Every now and then people get {{Cannot find module}} errors during {{appc use latest}} and sometimes with {{appc run}}. * https://community.appcelerator.com/topic/123/the-login-server-returned-an-error/19 * https://community.appcelerator.com/topic/150/can-not-login-to-appcelerator-studio/5 * https://community.appcelerator.com/topic/219/error-cannot-find-module-after-update-0-2-255 * https://community.appcelerator.com/topic/185/error-cannot-find-module-arrow/2 (slightly different, during appc run) | 0 |
10 | CLI-574 | 04/22/2015 09:12:55 | Login validation error message not passed through prompt from CLI | Please refer to Studio ticket. https://jira.appcelerator.org/browse/TISTUD-7325 Studio is listening to CLI through socket communication through request and response protocol model. In case of Sign-in, If user is not provided any credentials and entered Ok, will get the proper error message from CLI. The response looks like below. {"type":"error","message":"validate error: you must enter a value for the Appcelerator ID","question":[{"type":"input","name":"username","message":"Appcelerator ID:"},{"type":"password","name":"password","message":"Password:"}]} If user provided wrong credentials, then CLI is not returning the error message from the server. Response looks like below. {"type":"question","question":[{"type":"input","name":"username","message":"Appcelerator ID:"},{"type":"password","name":"password","message":"Password:"}]} Expected: CLI should send error message, so that same will be passed back to the studio user, they can able to see what went wrong. | 3 |
11 | CLI-577 | 04/22/2015 17:53:45 | Need to add proxy logic to underlying appc process such as acs | same as we're using here https://github.com/appcelerator/appc-cli/blob/c0f602a2992ee27fbe8c7a1328eedec422f912a7/lib/constants.js#L200 this code above should reference APPC_CONFIG_PROXY env and this code should be refactored https://github.com/appcelerator/appc-cli/blob/7a134ba6a50624ea9046b1d7578547b8760b21ee/lib/commands/login.js#L511 we need the front-end and the appc cli to both respect the proxy. | 5 |
12 | CLI-579 | 04/22/2015 19:57:43 | Errors updating Core CLI when Studio is open | When trying to update the Core CLI from terminal (via {{appc use latest}} or {{appc setup}}) I get errors when Studio is open. *Steps to reproduce issue* 1. Open Studio 2. Run {{appc use latest}} (do not already have the latest version installed) ----------------------- 3. Delete the latest folder from {{~/.appcelerator/install}} 4. Close Studio 5. Run {{appc use latest}} *Actual Results* 2. Install of latest version fails 5. Install succeeds *Expected Results* Installs of latest version succeed *Notes* This makes it very difficult to install CLI updates from inside Studio. I tested this many times. 10/10 installs succeeded with Studio closed, 10/10 installs failed with Studio open. | 5 |
13 | CLI-585 | 04/22/2015 21:49:07 | Can not login in Appcelerator Studio | Can not login to Appcelerator Studio, I'm receiving the error: ERROR | Required body parameter: userAgent missing | 3 |
14 | CLI-582 | 04/23/2015 08:10:51 | CLI prompts for login twice when --env option is given in the command | The cli prompts twice for login when --env option is given during appc new or appc run command. However, if username and password are provided as part of the command then it prompts twice for organization even if a valid --org-id is also passed in the command Steps to Reproduce: 1. Run the command "appc new --env preproduction" Actual Result: The user is forced to enter username, password and organization selection two times. {code} ssekhri-MBP:testing ssekhri$ appc whoami Appcelerator Command-Line Interface, version 0.2.261 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. [email protected] in organization qe_test_org_preprod_team (100001710) ssekhri-MBP:testing ssekhri$ appc new --env preproduction Appcelerator Command-Line Interface, version 0.2.261 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ****** ? Into which organization would you like to login? qe_test_org_preprod_team Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ****** ? Into which organization would you like to login? qe_test_org_preprod_team ? What type of project are you creating? (Use arrow keys) ❯ Native App Arrow App Titanium Module {code} | 2 |
15 | CLI-586 | 04/23/2015 19:08:04 | Clean up appc new arguments | Clean up the undefined arguments passed to titanium during app creation. This could cause problems. {code} args [ 'create', '-t', 'app', '--platforms', 'all', '--no-banner', '--no-prompt', '--workspace-dir', '/Users/gmathews/github/appc', undefined, true, '--log-level', 'info', undefined, true, undefined, 'app', undefined, 'titanium', undefined, 'titanium', '--name', 'testApp', '--id', 'com.test', '--project-dir', '/Users/gmathews/github/appc/testApp', '--url', 'unspecified' ] {code} | 3 |
16 | CLI-588 | 04/24/2015 01:48:27 | Rebuilding an application for Android emulator fails | h5.Description When rebuilding an application for Android emulator using 0.2.269 the build exits with the following {code} [INFO] Generating i18n files [INFO] Generating /Users/eharris/Documents/sambotWorkspace/android/build/android/res/values/theme.xml TRACE | titanium exited with exit code 0 {code} Full logs are attached as fullOutput.txt *If I set encryptJS to true [here|https://github.com/appcelerator/appc-cli-titanium/blob/master/hook/titanium.js#L147] then the build has no problems.* h5.Steps To Reproduce 1. Create a new application using {{appc new}} 2. Build the application for Android using {{appc run -p android -T emulator}} 3. Rebuild the application for Android using {{appc run -p android -T emulator}} h5.Actual Result The build will fail with the output above h5.Expected Result The build should pass | 3 |
17 | CLI-591 | 04/24/2015 22:20:00 | Build to an iOS device and then an iOS simulator fails | h5.Description When building an iOS app, if you build the app for device and then build the device for simulator the build for simulator will fail with the following error {code: title=error 1} [DEBUG] [ioslib] [ios-sim] [DEBUG] Session could not be started: Error Domain=NSPOSIXErrorDomain Code=22 "Installation Failed" UserInfo=0x7f916347ea40 {NSLocalizedDescription=Installation Failed, NSLocalizedRecoverySuggestion=An error occurred while preparing the app for installation (no bundle identifier was found at the expected path)} [DEBUG] [ioslib] [ios-sim] Exited with code: 1 [ERROR] Project failed to build after 7s 726ms [ERROR] An error occurred running the iOS Simulator (ios-sim exit code 1) {code} If I attempt to then clean the project and run again it fails with the following {code: title=error 2} [DEBUG] Setting Info.plist CFBundleVersion to 1.0 [DEBUG] Setting Info.plist CFBundleShortVersionString to 1.0 TRACE | titanium exited with exit code 0 {code} From what I see, if I wait the full time required for the rebuild (1 hour) then it seems to work fine. Setting [this line|https://github.com/appcelerator/appc-cli-titanium/blob/master/hook/titanium.js#L146] to be true makes the build work everytime! The fix for CLI-588 *does not fix this issue* h5.Steps To Reproduce 1. Create a new application using {{appc new}} 2. Run the app on simulator using {{appc run -p ios -T simulator}} 3. Run the app on device using {{appc run -p ios -T device}} 4. Run the app on simulator using {{appc run -p ios -T simulator}} 5. Clean the app {{appc ti clean}} 6. Run the app on simulator using {{appc run -p ios -T simulator}} h5.Actual Result 2. App will be built successfully 3. App will be built successfully 4. App will not be built successfully (see error 1) 6. App will not be built successfully (see error 2) h5.Expected Result App should be successfully every time | 2 |
18 | CLI-604 | 04/29/2015 13:01:20 | ENOTEMPTY error when creating titanium project | Run the following command the first time, the project files are created in */Users/feonsua/work/sandbox1/sandbox2/sandbox3* Run the command again, a classic project is created under */Users/feonsua/work/sandbox1/sandbox2/app1*, which is one directory up than what was being specified. Then the process is terminated with an error message. {code} Feons-MacBook-Pro:~ feonsua$ appc new --type titanium --name app1 --id com.test --project-dir /Users/feonsua/work/sandbox1/sandbox2/sandbox3 --force Appcelerator Command-Line Interface, version 0.2.273 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. ERROR | ENOTEMPTY, directory not empty '/Users/feonsua/work/sandbox1/sandbox2/app1' {code} This happens when the --project-dir specified is different from the project name. | 3 |
19 | CLI-605 | 04/30/2015 05:35:05 | Attempt to retry when registry is not available | For the appcelerator front-end (apps-install) need to retry when registry is unavailable. Will try up to 10 times with each iteration waiting 500 x N (where N= is retry count) | 5 |
20 | CLI-606 | 04/30/2015 07:26:39 | "appc -v" should show both the NPM and active version | When we're debugging user problems we ask them to make sure they're on the latest version of the appcelerator NPM package. But the only way to check is: {code} $ npm list -g --depth 0 appcelerator {code} We should include both the NPM and active version with {{appc -v}}. {code} $ appc -v npm: 0.3.51 cli: 0.2.273 {code} Q&A: https://community.appcelerator.com/topic/285/appc-setup-causing-error-with-exit-code-1/2 | 5 |
21 | CLI-607 | 04/30/2015 20:16:05 | Creating a project with an invalid session errors out after logging in | h5.Description After a session has been invalidated due to logging in on a different machine when creating a new project the CLI will prompt you to login again and authorize your hardware. After logging in the project creation fails with the below. {code} ERROR | Error at Request._callback (/Users/eharris/.appcelerator/install/0.2.274/package/node_modules/appc-cli-titanium/plugins/new.js:305:23) at Request.self.callback (/Users/eharris/.appcelerator/install/0.2.274/package/node_modules/request/request.js:368:22) at Request.emit (events.js:98:17) at Request.<anonymous> (/Users/eharris/.appcelerator/install/0.2.274/package/node_modules/request/request.js:1219:14) at Request.emit (events.js:117:20) at IncomingMessage.<anonymous> (/Users/eharris/.appcelerator/install/0.2.274/package/node_modules/request/request.js:1167:12) at IncomingMessage.emit (events.js:117:20) at _stream_readable.js:944:16 at process._tickCallback (node.js:448:13) {code} Just before this error when running with -l trace the following is output, it appears that the session that the CLI is using in not a valid session. {code} sending app post { method: 'post', json: { session: 'a9adbc3a5dea29d6a17823ad6a6ceb215ca50cae sa1eZdG82mfMMvDxYxpD4WPbTNpTT6X+p+J4YqfKjNyPXmd1KgNgAmXZvO/SmyFxarxxKT359VcElJm4YR1RhTAQTQrHEehfRFbtWCqyiU0QnGRyK7LnB/+eC0vAD+EpnnCaQ8WWOdLXisvrh77+jqwr+mEuwL2NIQMRoiGxR3E0eeiBpawTFHmI5Xl8Rebn5PRovXCqThbKmoMeg7wTO0rHIdzNY9M9+ju5HXLUID2v+kCUWHVB3aF9hsJeP/Ph/1eV4jLSte5jsJmrRUsXBhMcXBe9YVjQ3Il+9WHYN7DxQ/1tTAT5a1Ym18DO1hc0SCjiH3Fwoc5GrAiAo1RlWvepNpM5dU1w5HapoT0o1N9m9P/tRdi7s4LQJvS1x2lA1t2birl2lM1KrGkFiuDd8N17eLsSRaV2fC3pC1+0oo4+9QpNrY+XzsMYhhhll2LGN8sbLY1T2zCtqMrzgabE0O2Q8/8aR/v8Ct9gBnVr/PpkgwX/SW27rfHaHEsRdhA7IFlf63vPsD2zkuRLsuOY4xPIG0mhrZoPxUIqfukqzP9R3DoR/TebediC+FdAu2I0rAzorPn89WsaxujxRM5JMec1x3aqw/EJX7v3jZn86W4dtDxsqkqdRu0qziK5hCRZ+1DnjUTh1Uq9SPwjZTH+BkWH2Gc6KDLHvQHka3QNprvq5eYS2GXUSu8sYzl5xaOmXOO820ksTPFBqWclTbg0uwLj5HgCn3Ck01u/XFKyNkThBXTv//InHE6wJR+ypjMrxG0zyqwRW/DlvBHztmzlABpwXGaP0BYVRide0hnoZ2o=', tiapp: '<?xml version="1.0" encoding="UTF-8"?><ti:app xmlns:ti="http://ti.appcelerator.org">\r\n\t<id>com.appc.testApp123</id>\r\n\t<name>testApp123</name>\r\n\t<version>1.0</version>\r\n\t<publisher>not specified</publisher>\r\n\t<url>unspecified</url>\r\n\t<description/>\r\n\t<copyright>not specified</copyright>\r\n\t<icon>appicon.png</icon>\r\n\t<fullscreen>false</fullscreen>\r\n\t<navbar-hidden>false</navbar-hidden>\r\n\t<analytics>true</analytics>\r\n\t<guid>2760f5af-3b92-451b-94e6-4c21d1088da6</guid>\r\n\t<property name="ti.ui.defaultunit" type="string">dp</property>\r\n\t<ios>\r\n\t\t<plist>\r\n\t\t\t<dict>\r\n\t\t\t\t<key>UISupportedInterfaceOrientations~iphone</key>\r\n\t\t\t\t<array>\r\n\t\t\t\t\t<string>UIInterfaceOrientationPortrait</string>\r\n\t\t\t\t</array>\r\n\t\t\t\t<key>UISupportedInterfaceOrientations~ipad</key>\r\n\t\t\t\t<array>\r\n\t\t\t\t\t<string>UIInterfaceOrientationPortrait</string>\r\n\t\t\t\t\t<string>UIInterfaceOrientationPortraitUpsideDown</string>\r\n\t\t\t\t\t<string>UIInterfaceOrientationLandscapeLeft</string>\r\n\t\t\t\t\t<string>UIInterfaceOrientationLandscapeRight</string>\r\n\t\t\t\t</array>\r\n\t\t\t\t<key>UIRequiresPersistentWiFi</key>\r\n\t\t\t\t<false/>\r\n\t\t\t\t<key>UIPrerenderedIcon</key>\r\n\t\t\t\t<false/>\r\n\t\t\t\t<key>UIStatusBarHidden</key>\r\n\t\t\t\t<false/>\r\n\t\t\t\t<key>UIStatusBarStyle</key>\r\n\t\t\t\t<string>UIStatusBarStyleDefault</string>\r\n\t\t\t</dict>\r\n\t\t</plist>\r\n\t</ios>\r\n\t<android xmlns:android="http://schemas.android.com/apk/res/android">\r\n\t</android>\r\n\t<mobileweb>\r\n\t\t<precache>\r\n\t\t</precache>\r\n\t\t<splash>\r\n\t\t\t<enabled>true</enabled>\r\n\t\t\t<inline-css-images>true</inline-css-images>\r\n\t\t</splash>\r\n\t\t<theme>default</theme>\r\n\t</mobileweb>\r\n\t<modules>\r\n\t</modules>\r\n\t<deployment-targets>\r\n\t\t<target device="android">true</target>\r\n\t\t<target device="ipad">true</target>\r\n\t\t<target device="iphone">true</target>\r\n\t\t<target device="mobileweb">true</target>\r\n\t</deployment-targets>\r\n\t<sdk-version>4.0.0.v20150430090209</sdk-version>\r\n<plugins><plugin version="1.0">ti.alloy</plugin>\n</plugins>\n</ti:app>' }, gzip: true, url: 'https://de7a3ab4b12bf1d3d4b7fde7f306c11bc2b98f67.cloudapp-enterprise-preprod.appctest.com/app' } app post response { success: false, error: 'invalid session', code: 'com.appcelerator.security.invalid.session' } done with plugin [Error] {code} Full output is attached as fullOuput.txt *When running {{appc new}} after this failure it does not fail* h5.Steps To Reproduce 1. Login on machine Y {{appc login}} 2. Login on machine X {{appc login}} 3. Create an app on machine X {{appc new}} 4. Create an app on machine Y {{appc new}} 5. Login when prompted h5.Actual Result The project creation will error out with the above h5.Expected Result The project creation should be successful | 1 |
22 | CLI-609 | 05/02/2015 00:48:12 | Improve password masking for appc-logger | see https://github.com/appcelerator/appc-cli/pull/145 | 1 |
23 | CLI-610 | 05/02/2015 00:51:45 | Device authorization code is referred to with two different terms when authorizing hardware | h5.Description When authorizing a new machine you will be prompted with the following {code} ? Confirm with authorization code to Email or Phone/SMS? SMS to <notMyPhoneNumber> {code} And then when selecting how you would like to receive the code you will be prompted with the following {code} An authorization code was sent to your phone at <notMyPhoneNumber> ? Please enter the activation code you received via your phone at <notMyPhoneNumber>: <notAuthCode> {code} The code should only be referred to as an authorization code, or an activation code. Preferably an authorization code as that is what it is h5.Steps To Reproduce 1. Logout of your machine with {{appc logout -D}} 2. Login with {{appc login}} 3. Run through the prompts h5.Actual Result The device auth code will be referred to using two different terminologies h5.Expected Result The device auth code should only be referred to using one terminology | 1 |
24 | CLI-611 | 05/02/2015 00:59:50 | Auth code is always required on login after session is invalidated | h5. Description Whenever a user logs in on a machine after having a session invalidated, an auth code will be required when logging in. For example: # Log in to CLI on machine 1 using auth code {code} $ appc login Appcelerator Command-Line Interface, version 0.2.275 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Your session has expired. Please log in again Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ********* ? Into which organization would you like to login? qe_test_org_preprod_team This computer must be authorized before you can complete your login. ? Confirm with authorization code to Email or Phone/SMS? Email to [email protected] An authorization code was sent to your email at [email protected] ? Please enter the activation code you received via your email at [email protected]: 4867 This computer is now authorized: Mac OSX Serial Number: C02HX4TMDV35 You can deauthorize this computer by logging out with appc logout Generating Developer Certificate and Private/Public Keys... [email protected] in organization qe_test_org_preprod_team (100001710) {code} # Log in to CLI on machine 2 using auth code {code} $ appc login Appcelerator Command-Line Interface, version 0.2.275 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ********* ? Into which organization would you like to login? qe_test_org_preprod_team This computer must be authorized before you can complete your login. ? Confirm with authorization code to Email or Phone/SMS? Email to [email protected] An authorization code was sent to your email at [email protected] ? Please enter the activation code you received via your email at [email protected]: 8897 This computer is now authorized: Mac OSX Serial Number: C07JM0CMDY3J You can deauthorize this computer by logging out with appc logout Generating Developer Certificate and Private/Public Keys... [email protected] logged into organization qe_test_org_preprod_team [100001710] {code} # Attempt to use CLI on machine 1, session will be expired but an auth code will also be requested again {code} $ appc whoami -f Appcelerator Command-Line Interface, version 0.2.275 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Your session has expired. Please log in again Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ********* ? Into which organization would you like to login? qe_test_org_preprod_team This computer must be authorized before you can complete your login. ? Confirm with authorization code to Email or Phone/SMS? Email to [email protected] An authorization code was sent to your email at [email protected] ? Please enter the activation code you received via your email at [email protected]: 4867 This computer is now authorized: Mac OSX Serial Number: C02HX4TMDV35 You can deauthorize this computer by logging out with appc logout Generating Developer Certificate and Private/Public Keys... [email protected] in organization qe_test_org_preprod_team (100001710) {code} h5. Actual behaviour A user needs to enter an auth code every time they log in to the CLI after their session is invalidated h5. Expected behaviour A user will only need to enter an auth code the first time they log in from a machine | 1 |
25 | CLI-612 | 05/02/2015 02:35:14 | Support logging in to VPC environment | When one or more VPC environments are configured for an organization, need to allow the user to be able to select the environment to log in. Currently, logs into the production Node.ACS / ACS environment instead of one provided. | 1 |
26 | CLI-613 | 05/05/2015 01:24:31 | If you create an Arrow project with an existing name, then "ERROR | { errcode: 230, statusCode: 400 }" is returned | *Details:* If you create an Arrow project with an existing name, then "ERROR \| \{ errcode: 230, statusCode: 400 \}" is returned. *Note:* * This is a *regression* since this does not occur with Appc CLI 0.2.276; released in the wild * This is *not a cloud issue* since this bug is reproducible if you point Appc CLI 0.2.279 to production *Steps to reproduce:* # Run {{appc new}} # Select *Arrow App* # Specify an Arrow project name that already existed *Actual:* "ERROR \| \{ errcode: 230, statusCode: 400 \}" message is returned. *Expected:* "ERROR | App <APP_NAME> already exists." message should appear instead. | 1 |
27 | CLI-614 | 05/05/2015 17:44:11 | Console logs incorrectly that setting org to undefined | There is an org in the session. Unsure if this means the /user/organizations call to 360 is empty. I'm not able to duplicate with any of my accounts. If this is an empty orgs payload from 360 causing it, is there a way to drum up the actual URL and response? Impersonating this user and hitting the endpoint in platform.appc yields the expected org (below). {code} login returned undefined { username: '[email protected]', org_id: 100005581, org_name: 'Float Mobile Learning', session: 'add0a3752b53ce2245414c687235c1733c9c92e2 aQPrCSXmOcQ8yB+6LG3140UF1ZFU+srQp4bloc1k/0R9nXZGOmcJDpWJXbI+RO2yIT8NER5UOKtRBwEJgZnfj3J47Odt5lzXTgZ2IgkYHs3HR31P6DZ4rfnIvePzdIbF2mok7PVWAwAJeodgMAiS2pNXnd8D/LseTTzOVEfRkkH5mbS+qwOYERRbq3NIRGynmgs9ASdd1hTiem7cqrZOW7NrMvF9SnemJTjwBkz4If3cbauLDfo6A1Y8urtZlZzHMWNIARcn7GGGdyyExwR6IJ7Gc5OU8pCGwFna7y/h0b+6Fwse+deu78nqj2GMaYAtHPpLU6r8TkGoIzxNTUQl9Ye6i/C9mjIwathRkz4+Wg7QZVdam/uQ5CpySlV8pN8KxYzZMJTeclg+r2CcXoc9w/sKoIlKSXAmsBolqZZc9Fv7EETstalsw7NT2ZsMZfz+HXZJctlI0tEkW5bJhxY+cgUqfJFeKKDQiOk9Qb4a17o4Tm6xhUqBW1twU6xBCyRARX2Dxc8UTn6rQrTHZbm46GQgP+kx15dUKcb5+HlGKogZFCaqb9k2eTo8tuLgPfiNo+MwR8/+NTL5/SXbPfcnyZGbN+SP4WP9EXZV6U5yNzjpN4ODIl4wGyesvggBYqIGFCjN7DdBd/g2satWrTYkoldnSmgvt0OhEMPwsWkQ0BABCYj/Vt1dgPEr9eTVP5BXvkQAsa14t4qIwt6Yxfp5i1L2xwsLW5elV9Sk5jS+vs8TYnhgyby+JXqNDwpU1UyI4KKYGWgiO9yimP7ACOviiDi/nuxFdi3lCWZXrakPtWI=', expiry: 1430855827351, firstname: 'Daniel', lastname: 'Pfeiffer', sid: 's:9bSE6kWvXGnRkCLzS7d-uXCgMCLMw2ak.PzB5B7jLItVL9dm+Tv3hhAm9bN2UeAWGy1kly5/Z49g', dashboard: 'https://platform.appcelerator.com', soastaUrl: 'https://appctest-2.appcelerator.com/concerto', entitlements: { id: '54d8e47cce78815d81104cb1', name: 'Developer', partners: [ 'acs', 'analytics' ], supportLink: 'https://community.appcelerator.com', users: { min: 1, max: 1 }, testingDevices: { min: 0, max: 0 }, allowProduction: false, arrowPublish: true, nativeSDK: false, insights: false, apiRateMonthPerSeat: 100000, apiRateMinute: 10, pushRateMinute: 10, storageGBRateMonth: 1, eventRateMonthPerSeat: 100000, daysDataRetained: 7, maxOrganizations: 1, dateRangeLimit: 7, dateRangeCustom: true, exportMetrics: false, exportAcs: false, paid: false, containerPointsPerSeat: 1 } } response from login { username: '[email protected]', org_id: 100005581, org_name: 'Float Mobile Learning', session: 'add0a3752b53ce2245414c687235c1733c9c92e2 aQPrCSXmOcQ8yB+6LG3140UF1ZFU+srQp4bloc1k/0R9nXZGOmcJDpWJXbI+RO2yIT8NER5UOKtRBwEJgZnfj3J47Odt5lzXTgZ2IgkYHs3HR31P6DZ4rfnIvePzdIbF2mok7PVWAwAJeodgMAiS2pNXnd8D/LseTTzOVEfRkkH5mbS+qwOYERRbq3NIRGynmgs9ASdd1hTiem7cqrZOW7NrMvF9SnemJTjwBkz4If3cbauLDfo6A1Y8urtZlZzHMWNIARcn7GGGdyyExwR6IJ7Gc5OU8pCGwFna7y/h0b+6Fwse+deu78nqj2GMaYAtHPpLU6r8TkGoIzxNTUQl9Ye6i/C9mjIwathRkz4+Wg7QZVdam/uQ5CpySlV8pN8KxYzZMJTeclg+r2CcXoc9w/sKoIlKSXAmsBolqZZc9Fv7EETstalsw7NT2ZsMZfz+HXZJctlI0tEkW5bJhxY+cgUqfJFeKKDQiOk9Qb4a17o4Tm6xhUqBW1twU6xBCyRARX2Dxc8UTn6rQrTHZbm46GQgP+kx15dUKcb5+HlGKogZFCaqb9k2eTo8tuLgPfiNo+MwR8/+NTL5/SXbPfcnyZGbN+SP4WP9EXZV6U5yNzjpN4ODIl4wGyesvggBYqIGFCjN7DdBd/g2satWrTYkoldnSmgvt0OhEMPwsWkQ0BABCYj/Vt1dgPEr9eTVP5BXvkQAsa14t4qIwt6Yxfp5i1L2xwsLW5elV9Sk5jS+vs8TYnhgyby+JXqNDwpU1UyI4KKYGWgiO9yimP7ACOviiDi/nuxFdi3lCWZXrakPtWI=', expiry: 1430855827351, firstname: 'Daniel', lastname: 'Pfeiffer', sid: 's:9bSE6kWvXGnRkCLzS7d-uXCgMCLMw2ak.PzB5B7jLItVL9dm+Tv3hhAm9bN2UeAWGy1kly5/Z49g', dashboard: 'https://platform.appcelerator.com', soastaUrl: 'https://appctest-2.appcelerator.com/concerto', entitlements: { id: '54d8e47cce78815d81104cb1', name: 'Developer', partners: [ 'acs', 'analytics' ], supportLink: 'https://community.appcelerator.com', users: { min: 1, max: 1 }, testingDevices: { min: 0, max: 0 }, allowProduction: false, arrowPublish: true, nativeSDK: false, insights: false, apiRateMonthPerSeat: 100000, apiRateMinute: 10, pushRateMinute: 10, storageGBRateMonth: 1, eventRateMonthPerSeat: 100000, daysDataRetained: 7, maxOrganizations: 1, dateRangeLimit: 7, dateRangeCustom: true, exportMetrics: false, exportAcs: false, paid: false, containerPointsPerSeat: 1 } } saving config { author: 'Daniel Pfeiffer', dashboard: 'https://platform.appcelerator.com', environmentName: 'production', username: '[email protected]', org_id: 100005581, org_name: 'Float Mobile Learning', session: 'add0a3752b53ce2245414c687235c1733c9c92e2 aQPrCSXmOcQ8yB+6LG3140UF1ZFU+srQp4bloc1k/0R9nXZGOmcJDpWJXbI+RO2yIT8NER5UOKtRBwEJgZnfj3J47Odt5lzXTgZ2IgkYHs3HR31P6DZ4rfnIvePzdIbF2mok7PVWAwAJeodgMAiS2pNXnd8D/LseTTzOVEfRkkH5mbS+qwOYERRbq3NIRGynmgs9ASdd1hTiem7cqrZOW7NrMvF9SnemJTjwBkz4If3cbauLDfo6A1Y8urtZlZzHMWNIARcn7GGGdyyExwR6IJ7Gc5OU8pCGwFna7y/h0b+6Fwse+deu78nqj2GMaYAtHPpLU6r8TkGoIzxNTUQl9Ye6i/C9mjIwathRkz4+Wg7QZVdam/uQ5CpySlV8pN8KxYzZMJTeclg+r2CcXoc9w/sKoIlKSXAmsBolqZZc9Fv7EETstalsw7NT2ZsMZfz+HXZJctlI0tEkW5bJhxY+cgUqfJFeKKDQiOk9Qb4a17o4Tm6xhUqBW1twU6xBCyRARX2Dxc8UTn6rQrTHZbm46GQgP+kx15dUKcb5+HlGKogZFCaqb9k2eTo8tuLgPfiNo+MwR8/+NTL5/SXbPfcnyZGbN+SP4WP9EXZV6U5yNzjpN4ODIl4wGyesvggBYqIGFCjN7DdBd/g2satWrTYkoldnSmgvt0OhEMPwsWkQ0BABCYj/Vt1dgPEr9eTVP5BXvkQAsa14t4qIwt6Yxfp5i1L2xwsLW5elV9Sk5jS+vs8TYnhgyby+JXqNDwpU1UyI4KKYGWgiO9yimP7ACOviiDi/nuxFdi3lCWZXrakPtWI=', expiry: 1430855827351, firstname: 'Daniel', lastname: 'Pfeiffer', sid: 's:9bSE6kWvXGnRkCLzS7d-uXCgMCLMw2ak.PzB5B7jLItVL9dm+Tv3hhAm9bN2UeAWGy1kly5/Z49g', soastaUrl: 'https://appctest-2.appcelerator.com/concerto', entitlements: { id: '54d8e47cce78815d81104cb1', name: 'Developer', partners: [ 'acs', 'analytics' ], supportLink: 'https://community.appcelerator.com', users: { min: 1, max: 1 }, testingDevices: { min: 0, max: 0 }, allowProduction: false, arrowPublish: true, nativeSDK: false, insights: false, apiRateMonthPerSeat: 100000, apiRateMinute: 10, pushRateMinute: 10, storageGBRateMonth: 1, eventRateMonthPerSeat: 100000, daysDataRetained: 7, maxOrganizations: 1, dateRangeLimit: 7, dateRangeCustom: true, exportMetrics: false, exportAcs: false, paid: false, containerPointsPerSeat: 1 } } loading org list... setting org: undefined "/usr/local/bin/node" "/Users/dpfeiffer/.appcelerator/install/0.2.276/package/node_modules/arrow/node_modules/acs/bin/acs" login --no-banner --host https://admin.cloudapp-enterprise.appcelerator.com "[email protected]" "**********" | ERROR | Error: [ERROR] Invalid Appcelerator 360 Login Credentials. Check your username and password and try again. at /Users/dpfeiffer/.appcelerator/install/0.2.276/package/lib/commands/login.js:243:21 at ChildProcess.exithandler (child_process.js:652:7) at ChildProcess.emit (events.js:98:17) at maybeClose (child_process.js:756:16) at Socket.<anonymous> (child_process.js:969:11) at Socket.emit (events.js:95:17) at Pipe.close (net.js:465:12) dpfeiffer:~ dpfeiffer$ {code} user/organizations response: {code} { success: true, result: [ { org_id: 100005581, name: "Float Mobile Learning", _id: "55305d4b1874fb8761bb7f8c", guid: "a0b31d6f-e0d9-40eb-b9da-dee92c685873", user_count: 1, current_users_role: "admin", is_node_acs_admin: true, created: "2015-04-17T01:09:31.925Z", reseller: false, active: true, parent_org_guid: "null", package: "free", envs: [ { _id: "production", name: "production", isProduction: true, acsBaseUrl: "https://api.cloud.appcelerator.com", acsAuthBaseUrl: "https://secure-identity.cloud.appcelerator.com", nodeACSEndpoint: "https://admin.cloudapp-enterprise.appcelerator.com" }, { _id: "development", name: "development", isProduction: false, acsBaseUrl: "https://api.cloud.appcelerator.com", acsAuthBaseUrl: "https://secure-identity.cloud.appcelerator.com", nodeACSEndpoint: "https://admin.cloudapp-enterprise.appcelerator.com" } ] } ] } {code} | 3 |
28 | CLI-616 | 05/07/2015 01:24:14 | Building to android with SDK 3.5.1.GA fails when using appc cli 0.2.280 | h6. This might be related to the encryption fix which went in CLI 2.8.0 : CLI-608 h5.Steps To Reproduce: 1. Make sure appc ali 0.2.280 is installed. 2. Build an app for android device/emulator with sdk 3.5.1.GA. h5.Actual Results: 1. The build fails with errors: {code} [INFO] : Building Java source files: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/javac "-J-Xmx256M" "-encoding" "utf8" "-bootclasspath" "/Users/lokeshchoudhary/Desktop/android-sdk-macosx/platforms/android-21/android.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/kroll-v8.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-analytics.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/aps-analytics.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-android.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/jaxen-1.1.1.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/ti-commons-codec-1.3.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/kroll-common.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/titanium.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-app.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-ui.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/nineoldandroids-appc-2.4.0.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-filesystem.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-media.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-appcompat.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/android-support-v4.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/android-support-v7-appcompat.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-locale.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-network.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/thirdparty.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-xml.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/modules/titanium-platform.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/modules/android/com.appcelerator.apm/1.1.1/crittercism.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/modules/android/com.appcelerator.apm/1.1.1/lib/classes.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/kroll-apt.jar:/Users/lokeshchoudhary/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA/android/lib/titanium-verify.jar:R.class:ApplicationStylesheet.class:AssetCryptImpl.class:TestappActivity.class:TestappAppInfo.class:TestappApplication.class" "-d" "/Users/lokeshchoudhary/Desktop/workspaces/new_workspace/testapp/build/android/bin/classes" "-proc:none" "-target" "1.6" "-source" "1.6" "@/Users/lokeshchoudhary/Desktop/workspaces/new_workspace/testapp/build/android/java-sources.txt" [ERROR] : Failed to compile Java source files: [ERROR] : [ERROR] : /Users/lokeshchoudhary/Desktop/workspaces/new_workspace/testapp/build/android/gen/com/app/testapp/AssetCryptImpl.java:44: error: cannot find symbol [ERROR] : Range range = assets.get(path); [ERROR] : ^ [ERROR] : symbol: variable assets [ERROR] : location: class AssetCryptImpl [ERROR] : /Users/lokeshchoudhary/Desktop/workspaces/new_workspace/testapp/build/android/gen/com/app/testapp/AssetCryptImpl.java:48: error: cannot find symbol [ERROR] : return new String(filterDataInRange(assetsBytes, range.offset, range.length)); [ERROR] : ^ [ERROR] : symbol: variable assetsBytes [ERROR] : location: class AssetCryptImpl [ERROR] : Note: /Users/lokeshchoudhary/Desktop/workspaces/new_workspace/testapp/build/android/gen/com/app/testapp/AssetCryptImpl.java uses unchecked or unsafe operations. [ERROR] : Note: Recompile with -Xlint:unchecked for details. [ERROR] : 2 errors titanium exited with exit code 1 [ERROR] Application Installer abnormal process termination. Process exit value was 1 {code} 2. Same app when built with SDK 3.5.1.GA & appc cli 0.2.279 builds successfully. 3. Same app when built with latest 4.0.0 & appc cli 0.2.280 builds successfully. h5.Expected Results: 1. The build should take place successfully with no errors. | 8 |
29 | CLI-621 | 05/07/2015 21:56:41 | Running appc ti build -h fails with: 'Cannot read property 'properties' of undefined' | h5.Description When running the command {{appc ti build --help}} or {{appc ti build -h}} the command errors out with the following error {code} Ewans-MacBook-Pro:testing eharris$ appc ti build --help Appcelerator Command-Line Interface, version 0.2.280 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:185 throw e; ^ TypeError: Cannot read property 'properties' of undefined at cli.addHook.post (/Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/hook/titanium.js:69:30) at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/hook.js:235:13 at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:551:21 at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:227:13 at iterate (/Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:134:13) at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:145:25 at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:229:17 at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:556:34 at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/hook.js:243:8 at /Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:551:21 --------------------------------------------- at Object.run (/Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/node-appc/lib/subprocess.js:59:8) at find (/Users/eharris/.appcelerator/install/0.2.280/package/node_modules/appc-cli-titanium/node_modules/node-appc/lib/subprocess.js:96:14) at q.process (/Users/eharris/.appcelerator/install/0.2.280/package/node_modules/async/lib/async.js:809:21) at processImmediate (timers.js:354:15) {code} When running with -l trace I see that the following parameters are passed in to the Titanium CLI {{ARGS: [ 'build', '-h', '-e', '-l', '-p', '-l', 'trace' ]}} or {{ARGS: [ 'build', '-h', '-l', 'trace' ]}} The above Running the command with Titanium [email protected] works with no issues. Running the command with 0.2.276(prod latest) and 0.2.279(last preprod version) work with no issues so this is a *regression*. h5.Steps To Reproduce 1. From the command line run {{appc ti build -h}} h5.Actual Result The command errors out with the above h5.Expected Result The command should print a useful help section | 1 |
30 | CLI-622 | 05/10/2015 14:41:25 | Wrapped `appc ti module --output json` should not show banner | The {{appc ti module -o json}} command shows the banner, where it shouldn't. h1. Reproduce * Run {{ti module -o json}} for the correct output * Run {{appc ti module -o json}} for the incorrect (with banner) output {code} ≫ appc ti module -o json Appcelerator Command-Line Interface, version 0.2.282 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. { "global": { "android": { {code} h1. Related code https://github.com/appcelerator/appc-cli/blob/a86886e6636c132eb4daa90551c40066c251994b/bin/appc#L86-L89 h1. Suggested solution If {{\-o}} and {{--output}} is the current standard for setting the output on any of the bundled CLI's, we should keep this standard and change the code to: {code} var pos; if (((pos = args.indexOf('-o')) !== -1 || (pos = args.indexOf('--output') !== -1)) && args[pos + 1] === 'json') { program.banner = false; } {code} | 3 |
31 | CLI-624 | 05/12/2015 01:37:23 | Platform-SDK: Logout request is incorrect | Calling AppC.Auth.Logout() results in an error in the callback. This is due to an incorrect 'post' rather than a 'get' to the dahsboard /auth/logout endpoint | 5 |
32 | CLI-626 | 05/12/2015 17:11:52 | Offline packaging is successful for Android & IOS with CLI 0.2.282 | h6.This is a regression. I don't see this issue with appc cli 0.2.276 h5.Steps to reproduce: 1. Install appc CLI 0.2.282. 2. Create an app for android and ios platforms. 3. Go offline. 4. Package the app for both android & ios. h5.Actual Results: 1. We can package successfully. h5.Expected Results: 1. We should not be able to package as we are offline & production builds should fail. | 8 |
33 | CLI-628 | 05/12/2015 18:27:00 | Improve Offline with Remote Verbiage | Improve the verbiage when the device is offline, and the app is built with remote security policy. | 5 |
34 | CLI-634 | 05/14/2015 19:13:44 | Setup does not find latest 4.0.0.RC4 | When I run {{appc setup}} the CLI does not find 4.0.0.RC4 while Studio does (see screenshot). Running the command with trace shows it does find 4.0.0.RC4 listed in the releases but somehow it thinks the installed 4.0.0.RC3 is the newest. Running {{appc ti sdk -r}} also lists 4.0.0.RC4. Trace log: https://gist.github.com/FokkeZB/27e1c31a9d1808ebcb61#file-console-log-L46 | 8 |
35 | CLI-635 | 05/14/2015 19:45:20 | If you create an Arrow project when the cloud is unstable, then a misleading error message is returned | *Details:* If you create an Arrow project when the cloud is unstable, then a misleading error message is return: bq. Unable to register the new app with Appcelerator Platform either due to limited connectivity or other unexpected problem. Please retry later using the command 'appc new --import --project-dir /path/to/project' { \[Error: Resource Not Found\] The {{appc new --import}} command is specific for importing Titanium mobile projects into the platform. *Steps to reproduce:* # In terminal, run {{appc new}} when the cloud is unstable # Select *Arrow app* # And finish the steps of creating an Arrow project *Actual:* When the cloud is unstable, the following error message is returned: {code} WilsonComputer:~ wluu$ appc new Appcelerator Command-Line Interface, version 0.2.285 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ******* ? Into which organization would you like to login? qe_test_org_preprod_enterprise ? What type of project are you creating? Arrow App ? What's the project name? monkey788 Unable to register the new app with Appcelerator Platform either due to limited connectivity or other unexpected problem. Please retry later using the command 'appc new --import --project-dir /path/to/project' { [Error: Resource Not Found] success: false, description: 'Resource Not Found', code: 404, internalCode: undefined } *** new completed. *** WilsonComputer:~ wluu$ {code} *Expected:* Instead of {{appc new --import}}, the messaging should be: bq. Please retry later using the command 'appc new'. | 5 |
36 | CLI-636 | 05/14/2015 21:05:51 | appc -v returns undefined for NPM version | h5.Description When running appc -v the NPM version is returned as undefined. This is because it relies on [this pull|https://github.com/appcelerator/appc-install/pull/17] for the NPM package which has not been published yet {code} NPM: undefined CLI: 0.2.286 {code} h5.Steps To Reproduce 1. Using Appc CLI version 0.2.286 run appc -v h5.Actual Result Undefined is returned for the NPM version h5.Expected Result The NPM version should be returned and if not available undefined should not be shwon | 1 |
37 | CLI-641 | 05/15/2015 15:14:16 | Support switching organizations directly without logging (out and) in | After working with the new CLI and Studio for a while, and being member of multiple organizations I've found it very cumbersome to switch between them. On the website is a matter of selecting a different organization in the dropdown, but in Studio or CLI there is no such option. For CLI, you have to run {{appc login}} or {{appc login -o <id>}} if you know the ID by hart. In both cases, you need to enter your username and password again. The preferred solution would be to be able to do: {code} $ appc org switch Appcelerator Command-Line Interface, version 0.2.285 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. ? To which organization would you like to switch? (Use arrow keys) ❯ Appcelerator, Inc Fokke Zandbergen [email protected] switched to organization Appcelerator, Inc [14301] {code} | 8 |
38 | CLI-643 | 05/15/2015 22:32:07 | Appc ti -v should not print out a banner | h5.Description When running the command {{appc ti -v}} the command prints the below {code} Appcelerator Command-Line Interface, version 0.2.287 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. 4.0.0-beta8 {code} Every other version command does not print out a banner so the titanium banner should match the existing behavior for the other commands. h5.Steps To Reproduce 1. Run {{appc ti -v}} h5.Actual Result A banner is printed out h5.Expected Result A banner should not be printed out | 2 |
39 | CLI-654 | 05/19/2015 20:06:40 | ETIMEDOUT is returned when you publish an Arrow app | *Details:* Occasionally, if you publish an Arrow app, ETIMEDOUT is returned. *Steps to reproduce:* # Create an Arrow project on Windows # Publish the Arrow project: {{DEBUG=* appc publish -l trace}} *Actual:* ETIMEDOUT is returned: {code} sending {"method":"post","url":"https://admin.cloudapp-enterprise.appcelerator.com:443/publish/monkeyWiseEric/1.0.0/0?orgid=100000675","headers":{"Cookie":"connect.sid=s%3A HDSzlSzrQINttzZbig0er6Wj.T%2FuwhEXemXPHFlsBg9leqsuI900dfn32h%2BQtxv9uPsc","User-Agent":"Appcelerator/1.0.72 (Windows 6.2.9200 x64) Version/1.1.1 Safari/0.0.0 appcelerator/4 .0.0-rc","Accept":"text/json, application/json","Content-Type":"application/octet-stream","Content-Length":"231889","Content-Disposition":"attachment;filename=arrowcloud-pu blish-monkeyWiseEric-1.0.0.tgz","X-Content-Checksum":"88c79ca492e0193debe5e22fcf947b26"},"gzip":true,"timeout":120000} Deploying application ... receiving err={"code":"ETIMEDOUT"}, body=undefined ERROR | Error: ETIMEDOUT at null._onTimeout (C:\Users\QE\.appcelerator\install\4.0.0-rc\package\node_modules\request\request.js:973:15) at Timer.listOnTimeout [as ontimeout] (timers.js:112:15) {code} *Expected:* Appc CLI should be able to handle ETIMEDOUT. | 1 |
40 | CLI-655 | 05/19/2015 23:13:09 | Implement 'appc info' command | We should implement an {{appc info}} command to display the following: - Active Appcelerator NPM package version - Active CLI version - Active Titanium SDK version - Studio version (if possible) As suggested [here|https://jira.appcelerator.org/browse/CLI-606?focusedCommentId=352954&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-352954] | 5 |
41 | CLI-658 | 05/20/2015 22:02:40 | Encryption fails on Windows when using 64-bit Java | h5.Description When building a project for device on Windows if the machine is using 64-bit Java then the encryption stage will fail with the following {code} ERROR] Failed to encrypt JavaScript files [ERROR] This application cannot be built with the Titanium open source SDK because it is an Appcelerator Platform registered application. Please use t he Appcelerator Platform CLI tools or Appcelerator Studio to build this application. ERROR | ti run exited with error code 1 {code} Switching back to 32-bit Java works. *Titanium CLI works fine with 64-bit Java* h5.Steps To Reproduce 1. On a Windows machine check your Java using {{appc ti info -t jdk}} If you see Program Files (x86) run the following command {{set JAVA_HOME=<64-bit Path}} 2. Create a project using {{appc new}} or use an existing one 3. Build the project using {{appc run -p android -T device --build-only -l trace}} h5.Actual Result The build will fail with the above error h5.Expected Result The encryption should pass, build should not fail | 5 |
42 | CLI-664 | 05/22/2015 16:01:02 | App Preview CLI hook integration | There already is a Ti CLI hook available for App Preview. Since we're doing this integration, it probably makes sense to ship this with the Ti CLI | 3 |
43 | CLI-665 | 05/22/2015 17:22:52 | "appc new" asks for login without prompting for it | I tried to create a new (Arrow) project and the CLI told me I needed to login first, but without prompting for the login like it used to do, it just exited. {code} (~/dev/tests) ≫ appc new Appcelerator Command-Line Interface, version 4.0.0 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. ? What type of project are you creating? Arrow App ? What's the project name? test ERROR | Please login first! (~/dev/tests) {code} h3. Expected I'd expected it to prompt for the login directly. | 0 |
44 | CLI-667 | 05/26/2015 19:53:31 | Creating an arrow project when logged out fails to register the app | h5.Description *Checking on platform.appcelerator.com shows that the app is actually created* When creating an arrow project if your session has expired or you are logged out you will be prompted to log in and then carry on with the creation of the project. When the app is created the following is printed out {code} Unable to register the new app with Appcelerator Platform either due to limited connectivity or other unexpected problem. Please retry later using the command 'appc new --import --project-dir /path/to/project' { [Error: Resource Not Found] success: false, description: 'Resource Not Found', code: 404, internalCode: undefined } {code} Full logs are attached as arrowOutput.txt h5.Steps To Reproduce 1. Logout of the appc cli using {{appc logout}} 2. Create a new project using {{appc new}} 3. Enter your credentials 4. Select an arrow project and input a name h5.Actual Result When the project creation has finished the above message will be printed out h5.Expected Result The app should be created successfully | 8 |
45 | CLI-670 | 05/28/2015 14:32:42 | Proxy Server settings not carried through properly | .appcelerator/appc-cli.json is a file that is created on macs. When users need a proxy server on a corporate network, they need to enter the proxy server in studio and the CLI. Here are the problems I uncovered with regards to the CLI operation. 1) It looks like the values on both are different, proxy differs from proxyServer. 2) Also, not all parts of the CLI, especially when using Arrow are using the proxy server settings. Especially on "appc new", "appc login", etc.. all need to ensure they are carrying over the proxy server settings. 3) We should allow the ability to do a "appc config set proxyServer" setting without having it to try to auto - update. Otherwise, it will keep failing as it does not have the ability to work outside a network. 4) Also, some of the services like appc new are doing the up to 10 tries to try to get the source. If it's using the wrong proxy server settings, it will lock a user out. FINAL THOUGTS FOR RESOLUTION - We had to edit the .appcelerator/appc-cli.json to have the right syntax to finally get it to work right. - the titianium-connection-test -p proxy server usage seemed to be great to work. Maybe we need to incorporate a proxy server test to make sure the syntax is right after a user enters it. | 0 |
46 | CLI-676 | 06/02/2015 00:30:17 | CLI needs better support to handle proxy servers | We need better support to handle proxy servers inside the Unified CLI. Here are some observations to make from being onsite with Comerica recently: # if AppC Studio has already defined a proxy, can the CLI just use this setting? Studio will put a "proxy" server setting in the {{<HOME>/.appcelerator/appc-cli.json file}}. When you first install the CLI, there is no way to insert a proxyServer settings (it always tries to update without checking if a proxy required to get outside). The only workaround was to hack this file and all a proxyServer setting. # When both are finally defined ( the proxy for studio + proxy for CLI ), the syntax for both seem to be different. We had to modify to figure out which one worked. The titanium-connection-test proxy flag seemed to work great. Maybe we can mirror some of the capability. # We need to ensure that if the proxy is defined, then it should follow through all the CLI commands. Found that some commands may not have passthrough to use the proxy server if it is set. EXPECTED RESULTS # Provide an command or option to set the proxy server for CLI before the CLI tries to do "appc use latest" or run any initial commands ( as they might not work without a proxy server ). Maybe the CLI can look for a proxy server to be set through studio and use that as well. # CLI use the proxy server prior to running any request for external resource if the proxy server is set. | 5 |
47 | CLI-679 | 06/02/2015 01:29:53 | Build: Update, Package and Deploy the dependencies | Unified CLI has a lot of dependencies/modules, and if a few of those modules are updated, then there is a chance that we are missing to include those updated modules in new version of appc-cli. When we attempt to publish a new version of appc-cli, the proposal is - - We know a list of dependencies (appc-cli-titanium, arrow, appc-platform-sdk...) - Look for any code changes (in git) after the latest tag, or any changes after the recent version of appc-cli published date. - For each modified dependent module, -- Update the version -- Publish the npm package -- Tag a release in the specified branch (4_0_X or 4_1_X) - Change the package.json of appc-cli with all of the modified module versions. - Publish appc-cli. - Tag appc-cli version in the github with the release name. | 8 |
48 | CLI-680 | 06/03/2015 19:17:49 | Set proxy details without downloading CLI core package | For customers behind proxy server, they are able to download Appc CLI npm package, but not able to download CLI Core. When they attempt to set the proxy server details using {{appc config set proxyServer <value>}} command, it is attempting to download CLI core before saving the config. We should let users set the config without downloading CLI Core. | 8 |
49 | CLI-682 | 06/04/2015 22:50:57 | Running appc ti commands fail with Error: Cannot find module './commands/config' | h5.Description When running appc ti command it fails with the following {code} Ewans-MacBook-Pro:Appcelerator_Studio_Workspace eharris$ appc ti Appcelerator Command-Line Interface, version 4.0.2-rc Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Error: Cannot find module './commands/config' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at getDefaultEnvironment (/Users/eharris/.appcelerator/install/4.0.2-rc/package/lib/constants.js:174:15) at Object.setEnvironment (/Users/eharris/.appcelerator/install/4.0.2-rc/package/lib/constants.js:226:11) at Object.<anonymous> (/Users/eharris/.appcelerator/install/4.0.2-rc/package/bin/appc-ti:72:26) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) {code} h5.Steps To Reproduce 1. Run appc ti h5.Actual Result The error above is printed out h5.Expected Result The command should not fail | 3 |
50 | CLI-683 | 06/04/2015 22:58:39 | Appc commands fail with no return output | h5.Description When running {{appc run}} the command is returning and failing with no output, see below {code} Ewans-MacBook-Pro:Appcelerator_Studio_Workspace eharris$ appc new -l trace Appcelerator Command-Line Interface, version 4.0.2-rc Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. __command__ search paths: [ "/Users/eharris/.appcelerator/install/4.0.2-rc/package", "/Users/eharris/.appcelerator/install/4.0.2-rc/package/node_modules", "/Users/eharris/Documents/Appcelerator_Studio_Workspace/modules", "/Users/eharris/Documents/Appcelerator_Studio_Workspace/node_modules", "/Users/eharris/Documents/node_modules", "/Users/eharris/node_modules", "/Users/node_modules", "/node_modules", "/Users/eharris/.appcelerator/.npm/lib/node_modules" ] [PLUGIN-LOAD] 0ms /Users/eharris/.appcelerator/install/4.0.2-rc/package/appc.js [PLUGIN-LOAD] 494ms /Users/eharris/.appcelerator/install/4.0.2-rc/package/node_modules/appc-cli-titanium/appc.js [PLUGIN-LOAD] 0ms /Users/eharris/.appcelerator/install/4.0.2-rc/package/node_modules/arrow/appc.js {code} h5.Steps To Reproduce 1. Run {{appc run}} h5.Actual Result The command returns with no output h5.Expected Result The commands should run as expected | 3 |
51 | CLI-687 | 06/08/2015 22:39:26 | appc new should handle the Alloy --testapp option | The Alloy CLI exposed a new option in version 1.7.0 to copy the test application source when a new project is created. See linked ticket. It would be nice if the Appc CLI can accept this option when creating a new project. Right now, you have to create a new classic project, then run the Alloy new command. So instead of running these commands: {noformat} appc new -t titanium --classic -i com.appc.picker -n AlloyPicker cd AlloyPicker appc alloy new --testapp ui/picker {noformat} A developer can just run this command: {noformat} appc new -t titanium -i com.appc.picker -n AlloyPicker --testapp ui/picker {noformat} | 5 |
52 | CLI-691 | 06/11/2015 05:08:22 | using invalid connector on appc install returns error | I typed in the wrong connector and i get a registry error like it's down. However, its because the registry api is correctly returning 404. our logic for handling down registry is not handling correctly. need to fix this. repro with DEBUG=* appc install connector/appc.mongodb | 3 |
53 | CLI-692 | 06/11/2015 17:20:30 | Directory permission error | Looks like this API is not passing the right args on a directory permission issue. {code} Internal failure. Unexpected usage of internal command. Please report error code: com.appcelerator.install.preflight.directory.ownership(invalid args) to Appcelerator Support with the following stack trace:Error at createErrorMessage (/usr/local/lib/node_modules/appcelerator/lib/error.js:117:179) at Object.exports.createError (/usr/local/lib/node_modules/appcelerator/lib/error.js:140:35) at Object.checkDirectory (/usr/local/lib/node_modules/appcelerator/lib/util.js:642:21) at preflight (/usr/local/lib/node_modules/appcelerator/lib/install.js:69:19) at start (/usr/local/lib/node_modules/appcelerator/lib/install.js:252:2) at Object.install (/usr/local/lib/node_modules/appcelerator/lib/install.js:299:2) at main (/usr/local/lib/node_modules/appcelerator/bin/appc:262:7) at Object.<anonymous> (/usr/local/lib/node_modules/appcelerator/bin/appc:282:1) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) {code} | 1 |
54 | CLI-699 | 06/16/2015 23:17:54 | Add banner for trial accounts | Add a lightweight CLI banner for Developer trial account. | 1 |
55 | CLI-700 | 06/18/2015 18:25:15 | If I am an indie user then the CLI should not download Soasta and APM | h5.Description When creating a project is Soasta and APM are not on my system then the CLI will download them for me, however if I have an indie or team plan then these should not download as I am unable to use them on these plans. h5.Steps To Reproduce 1. Remove APM and Soasta from your Titanium folder 2. Sign in to an indie account 3. Create a project h5.Actual Result Soasta and APM is downloaded for indie and team plans h5.Expected Result Soasta and APM should not be downloaded on plans that don't have it | 5 |
56 | CLI-703 | 06/25/2015 21:23:56 | When creating an app on prod the process errors with cannot call method 'indexOf' undefined | h5.Description *This is a regression as when using 4.0.2, project creation has no issues* When creating a project on production and using the latest CLI in preprod, project creation fails with the below {code} ERROR | TypeError: Cannot call method 'indexOf' of undefined at appc.async.series.appc.async.parallel.supportedPlatforms (C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\appc-cli-titani um\plugins\new.js:359:57) at C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:607:21 at C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:246:17 at iterate (C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:146:13) at C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:157:25 at C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:248:21 at C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:612:34 at async.waterfall.async.each.platformsToUpdate (C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\appc-cli-titanium\plugins\u til.js:625:11) at fn (C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:638:34) at Object._onImmediate (C:\Users\Windo_000\.appcelerator\install\4.1.0-3\package\node_modules\async\lib\async.js:554:34) {code} [This is the line|https://github.com/appcelerator/appc-cli-titanium/blob/master/plugins/new.js#L358] that is failing out h5.Steps To Reproduce 1. Using the latest appc cli create a project on prod using {{appc new}} h5.Actual Result The project creation fails h5.Expected Result Project creation should not fail | 5 |
57 | CLI-705 | 06/26/2015 12:04:19 | Setup does not install latest GA if a newer beta/RC/nightly is active | If you don't have the latest GA but you are running a newer beta/RC/nightly then {{appc setup}} will not install the latest GA for you and wrongly state that the newer beta/RC/nightly is the latest release: {code} $ appc setup Finding latest version ...4.0.2 ✓ Version 4.0.2 already installed. ? Do you plan on developing Titanium apps? Yes Checking your environment... You have the latest Titanium SDK release 4.1.0.v20150516202834 appc setup complete! {code} h2. Expected I'd expect the setup to install the newest GA and just not activate it if the current activated version is newer. It should say what version it is downloading (currently it's not) and reassure the user that his newer version will remain active: {code} $ appc setup Finding latest version ...4.0.2 ✓ Version 4.0.2 already installed. ? Do you plan on developing Titanium apps? Yes Checking your environment... A new release of the Titanium SDK is available, will download 4.0.0. Please not that your active version remains 4.1.0.v20150516202834 appc setup complete! {code} Related Q&A: https://community.appcelerator.com/topic/377/4-0-0-rc3-now-available/11 | 0 |
58 | CLI-706 | 06/26/2015 12:42:34 | Entitlements should be refreshed before failing over a limit | The following scenario has been causing confusion to several customers. The workaround if often simple, but by the time they or we figure it out, they already have a negative experience with a very crucial and sensitive step in our funnel.. paying us (or claiming their free Indie seat). h2. Current situation # User tries to build for ad-hoc or store. # Studio/CLI says they can't and directs them to billing. # User claims pays or claims his free Indie/Pro/Team seat. # User tries to build for ad-hoc or store again. # Studio/CLI still says they can't. # User gets frustrated and jumps on the Q&A or email. # We loose valuable support time to figure it out. h2. Workaround The workaround is for the user to logout and then in again, triggering their locally stored entitlements to be refreshed. h2. Solution Whenever the CLI/Studio would now abort because of a limitation in the entitlements, it should first refresh the entitlements and check again. Only then it should fail if the entitlements still don't allow the user to do what he wanted. Related Q&A: * https://community.appcelerator.com/topic/145/unable-to-package-ios-application-in-new-appcelerator-studio * https://community.appcelerator.com/topic/487/issue-with-my-account-need-appcelerator-billing-help * https://community.appcelerator.com/topic/145/unable-to-package-ios-application-in-new-appcelerator-studio * https://community.appcelerator.com/topic/699/unable-to-publish-android | 3 |
59 | CLI-708 | 06/26/2015 20:01:34 | Login token flag is not removed | *Details:* When you login with the token flag, "token missing in API definition" error is returned. *This flag should be removed since it is not supported anymore.* Snippet from the Arrow flow: {quote} JeffH this is not a github token. this is a security server token. i don’t think it’s fully supported anymore and we shoudl probably remove it until it is. we don’t support github login tokens {quote} *Steps to reproduce:* # In terminal, login with the token flag: {{appc login --username <EMAIL> --password <PASSWORD> -t <RANDOM_STUFF>}} *Actual:* {{Error: body parameters: token missing in API definition}} error is returned: {code} WilsonComputer:~ wluu$ DEBUG=* appc login --username [email protected] --password bnorhwe -t f2e3003619b67949be01f85b23a1c92a005cec1b -l trace appc:bin install bin is '/Users/wluu/.appcelerator/install/4.1.0-3/package/bin/appc' +0ms appc:bin main subcommand login +3ms appc:run run with env={"DEBUG":"*","TERM_PROGRAM":"Apple_Terminal","SHELL":"/bin/bash","TERM":"xterm-256color","TMPDIR":"/var/folders/g9/bw6h6yr11t79h_mw4q1r87pm0000gp/T/","Apple_PubSub_Socket_Render":"/private/tmp/com.apple.launchd.Y7RzG9OKmY/Render","TERM_PROGRAM_VERSION":"343.7","TERM_SESSION_ID":"63C09CC1-B073-462E-988B-EB3D646667A1","USER":"wluu","SSH_AUTH_SOCK":"/private/tmp/com.apple.launchd.7hwuWSXue4/Listeners","__CF_USER_TEXT_ENCODING":"0x1F6:0x0:0x0","PATH":"/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Applications/android-sdk-macosx/tools:/Applications/android-sdk-macosx/platform-tools:/Applications/VMware Fusion.app/Contents/Library/:/Users/wluu/mongodb-osx-x86_64-2.6.7/bin:/usr/local/mysql-5.6.25-osx10.8-x86_64/bin","PWD":"/Users/wluu","LANG":"en_US.UTF-8","XPC_FLAGS":"0x0","XPC_SERVICE_NAME":"0","SHLVL":"1","HOME":"/Users/wluu","LOGNAME":"wluu","_":"/usr/local/bin/appc","APPC_NPM_VERSION":"4.1.0-1","npm_config_cache":"/Users/wluu/.appcelerator/.npm","npm_config_prefix":"/Users/wluu/.appcelerator/.npm","APPC_INSTALL_DIR":"/Users/wluu/.appcelerator/install","APPC_INSTALL_BIN_DIR":"/Users/wluu/.appcelerator/install/4.1.0-3/package/bin/appc","APPC_CONFIG_PROXY":"","NODE_PATH":"/Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules:/Users/wluu/.appcelerator/cache/node_modules:"}, args=[ '/Users/wluu/.appcelerator/install/4.1.0-3/package/bin/appc', 'login', '--username', '[email protected]', '--password', 'bnorhwe', '-t', 'f2e3003619b67949be01f85b23a1c92a005cec1b', '-l', 'trace' ] +0ms Appcelerator Command-Line Interface, version 4.1.0-3 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. appc:sdk set production to https://platform.appcelerator.com +0ms __command__ search paths: [ "/Users/wluu/.appcelerator/install/4.1.0-3/package", "/Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules", "/Users/wluu/node_modules", "/Users/node_modules", "/node_modules", "/Users/wluu/.appcelerator/.npm/lib/node_modules" ] [PLUGIN-LOAD] 0ms /Users/wluu/.appcelerator/install/4.1.0-3/package/appc.js appc:sdk set production to https://platform.appcelerator.com +0ms [PLUGIN-LOAD] 447ms /Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules/appc-cli-titanium/appc.js [PLUGIN-LOAD] 0ms /Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules/arrow/appc.js appc:sdk set production to https://platform.appcelerator.com +0ms log level set to "trace" executing command "login" appc:sdk set preproduction to https://360-preprod.cloud.appctest.com +403ms set environment to {"registry":"https://software-preprod.cloud.appctest.com","security":"https://security-preprod.cloud.appctest.com","baseurl":"https://360-preprod.cloud.appctest.com"} noPlugins set for command "login" executing command "login" with no plugins arrow:sdk sending request to https://software-preprod.cloud.appctest.com/api/login arrow:sdk response received err=null, body={ message: 'body parameters: token missing in API definition', code: 400, success: false, 'request-id': 'abfe10d0-f61b-48ed-ba2c-cdada5ad9ba6' }, status code=400 registry result 400 application/json false undefined true 1 registry returned { message: 'body parameters: token missing in API definition', code: 400, success: false, 'request-id': 'abfe10d0-f61b-48ed-ba2c-cdada5ad9ba6' } login returned { [Error: body parameters: token missing in API definition] code: 400 } { message: 'body parameters: token missing in API definition', code: 400, success: false, 'request-id': 'abfe10d0-f61b-48ed-ba2c-cdada5ad9ba6' } ERROR | Error: body parameters: token missing in API definition at Request._callback (/Users/wluu/.appcelerator/install/4.1.0-3/package/lib/appc-registry-server-sdk/index.js:975:13) at Request.self.callback (/Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules/request/request.js:197:22) at Request.emit (events.js:98:17) at Request.<anonymous> (/Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules/request/request.js:1050:14) at Request.emit (events.js:117:20) at IncomingMessage.<anonymous> (/Users/wluu/.appcelerator/install/4.1.0-3/package/node_modules/request/request.js:996:12) at IncomingMessage.emit (events.js:117:20) at _stream_readable.js:944:16 at process._tickCallback (node.js:448:13) {code} *Expected:* Token flag should be removed since it is not supported anymore. | 1 |
60 | CLI-709 | 06/27/2015 00:20:14 | Android classic app crashes on launch with java.lang.IllegalArgumentException due to CLI injected code related to ACS | h5.Steps To Reproduce: 1. Create a classic android app from studio or appc CLI. 2. Build it to an android device/emulator. h5.Actual Results: 1. The app crashes at the splash screen with error: {code} [ERROR] : KrollProxy: (KrollRuntimeThread) [189,189] Error creating proxy [ERROR] : KrollProxy: java.lang.IllegalArgumentException: Invalid argument passed to securityManager property. Does not conform to SecurityManagerProtocol [ERROR] : KrollProxy: at ti.modules.titanium.network.HTTPClientProxy.handleCreationDict(HTTPClientProxy.java:73) [ERROR] : KrollProxy: at org.appcelerator.kroll.KrollProxy.handleCreationArgs(KrollProxy.java:227) [ERROR] : KrollProxy: at org.appcelerator.kroll.KrollProxy.setupProxy(KrollProxy.java:135) [ERROR] : KrollProxy: at org.appcelerator.kroll.KrollProxy.createProxy(KrollProxy.java:143) [ERROR] : KrollProxy: at org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModule(Native Method) [ERROR] : KrollProxy: at org.appcelerator.kroll.runtime.v8.V8Runtime.doRunModule(V8Runtime.java:177) [ERROR] : KrollProxy: at org.appcelerator.kroll.KrollRuntime.handleMessage(KrollRuntime.java:299) [ERROR] : KrollProxy: at org.appcelerator.kroll.runtime.v8.V8Runtime.handleMessage(V8Runtime.java:203) [ERROR] : KrollProxy: at android.os.Handler.dispatchMessage(Handler.java:98) [ERROR] : KrollProxy: at android.os.Looper.loop(Looper.java:135) [ERROR] : KrollProxy: at org.appcelerator.kroll.KrollRuntime$KrollRuntimeThread.run(KrollRuntime.java:112) [INFO] : art: art/runtime/check_jni.cc:65] JNI DETECTED ERROR IN APPLICATION: obj == null [INFO] : art: art/runtime/check_jni.cc:65] in call to CallVoidMethodA [INFO] : art: art/runtime/check_jni.cc:65] from void org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModule(java.lang.String, java.lang.String, org.appcelerator.kroll.KrollProxySupport) [INFO] : art: art/runtime/check_jni.cc:65] "KrollRuntimeThread" prio=5 tid=13 Runnable [INFO] : art: art/runtime/check_jni.cc:65] | group="main" sCount=0 dsCount=0 obj=0x12e22c40 self=0xac3a1000 [INFO] : art: art/runtime/check_jni.cc:65] | sysTid=6687 nice=0 cgrp=apps sched=0/0 handle=0xac395d80 [INFO] : art: art/runtime/check_jni.cc:65] | state=R schedstat=( 202113649 48744684 191 ) utm=18 stm=2 core=2 HZ=100 [INFO] : art: art/runtime/check_jni.cc:65] | stack=0xafafa000-0xafafc000 stackSize=1052KB [INFO] : art: art/runtime/check_jni.cc:65] | held mutexes= "mutator lock"(shared held) [INFO] : art: art/runtime/check_jni.cc:65] native: #00 pc 00004c58 /system/lib/libbacktrace_libc++.so (UnwindCurrent::Unwind(unsigned int, ucontext*)+23) [INFO] : art: art/runtime/check_jni.cc:65] native: #01 pc 000034c1 /system/lib/libbacktrace_libc++.so (Backtrace::Unwind(unsigned int, ucontext*)+8) [INFO] : art: art/runtime/check_jni.cc:65] native: #02 pc 002526c5 /system/lib/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::mirror::ArtMethod*)+84) [INFO] : art: art/runtime/check_jni.cc:65] native: #03 pc 002361a3 /system/lib/libart.so (art::Thread::Dump(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) const+162) [INFO] : art: art/runtime/check_jni.cc:65] native: #04 pc 000b1215 /system/lib/libart.so (art::JniAbort(char const*, char const*)+620) [INFO] : art: art/runtime/check_jni.cc:65] native: #05 pc 000b1945 /system/lib/libart.so (art::JniAbortF(char const*, char const*, ...)+68) [INFO] : art: art/runtime/check_jni.cc:65] native: #06 pc 001b2b83 /system/lib/libart.so (art::JNI::CallVoidMethodA(_JNIEnv*, _jobject*, _jmethodID*, jvalue*)+614) [INFO] : art: art/runtime/check_jni.cc:65] native: #07 pc 00085f47 /data/app/com.app.test1c-1/lib/arm/libkroll-v8.so (_JNIEnv::CallVoidMethodA(_jobject*, _jmethodID*, jvalue*)+8) [INFO] : art: art/runtime/check_jni.cc:65] native: #08 pc 000dce53 /data/app/com.app.test1c-1/lib/arm/libkroll-v8.so (titanium::network::HTTPClientProxy::open(v8::Arguments const&)+246) [INFO] : art: art/runtime/check_jni.cc:65] native: #09 pc 0014dfbc /data/app/com.app.test1c-1/lib/arm/libkroll-v8.so (???) [INFO] : art: art/runtime/check_jni.cc:65] at org.appcelerator.kroll.runtime.v8.V8Runtime.nativeRunModule(Native method) [INFO] : art: art/runtime/check_jni.cc:65] at org.appcelerator.kroll.runtime.v8.V8Runtime.doRunModule(V8Runtime.java:177) [INFO] : art: art/runtime/check_jni.cc:65] at org.appcelerator.kroll.KrollRuntime.handleMessage(KrollRuntime.java:299) [INFO] : art: art/runtime/check_jni.cc:65] at org.appcelerator.kroll.runtime.v8.V8Runtime.handleMessage(V8Runtime.java:203) [INFO] : art: art/runtime/check_jni.cc:65] at android.os.Handler.dispatchMessage(Handler.java:98) [INFO] : art: art/runtime/check_jni.cc:65] at android.os.Looper.loop(Looper.java:135) [INFO] : art: art/runtime/check_jni.cc:65] at org.appcelerator.kroll.KrollRuntime$KrollRuntimeThread.run(KrollRuntime.java:112) [INFO] : art: art/runtime/check_jni.cc:65] {code} 2. We saw that when services are enabled on app creation CLI adds this code to the app.js which is causing the crash. {code} // added during app creation. this will automatically login to // ACS for your application and then fire an event (see below) // when connected or errored. if you do not use ACS in your // application as a client, you should remove this block (function(){ var ACS = require('ti.cloud'), env = Ti.App.deployType.toLowerCase() === 'production' ? 'production' : 'development', username = Ti.App.Properties.getString('acs-username-'+env), password = Ti.App.Properties.getString('acs-password-'+env); // if not configured, just return if (!env || !username || !password) { return; } /** * Appcelerator Cloud (ACS) Admin User Login Logic * * fires login.success with the user as argument on success * fires login.failed with the result as argument on error */ ACS.Users.login({ login:username, password:password, }, function(result){ if (env==='development') { Ti.API.info('ACS Login Results for environment `'+env+'`:'); Ti.API.info(result); } if (result && result.success && result.users && result.users.length){ Ti.App.fireEvent('login.success',result.users[0],env); } else { Ti.App.fireEvent('login.failed',result,env); } }); {code} 3. When services are enabled after the app has been created the app launches fine. h5.Expected Results: 1. The app should not crash after launch on splash screen. | 3 |
61 | CLI-710 | 06/27/2015 00:21:57 | Show notice banner when running CLI in preproduction | I would like to be able to more easily know if I'm running in preproduction when I run a command. Print out an explicit banner in the CLI when running a command against pre-production. This banner shouldn't show normally in production. | 1 |
62 | CLI-711 | 06/27/2015 20:42:15 | Appc run -h from within a Titanium project errors out on Windows with SyntaxError: Unexpected token ILLEGAL | h5.Description When running {{appc run -h}} or {{appc run --help}} on Windows the command errors out with the below {code} C:\Users\Windo_000\.appcelerator\install\4.1.0-4\package\node_modules\appc-cli-titanium\node_modules\.bin\titanium:2 basedir=`dirname "$0"` ^ SyntaxError: Unexpected token ILLEGAL at Module._compile (module.js:439:25) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:935:3 {code} Comparing the logging against {{appc run}} which run with no problems it appears that they are using a different titanium binary with the -h flag using {{C:\Users\Windo_000\.appcelerator\install\4.1.0-4\package\node_modules\appc-cli-titanium\node_modules\.bin\titanium}} and without the -h {{C:\Users\Windo_000\.appcelerator\install\4.1.0-4\package\node_modules\appc-cli-titanium\node_modules\titanium\bin\titanium}} h5.Steps to reproduce 1. On a Windows machine run {{appc run -h}} h5.Actual Result The command will error out h5.Expected Result The command should print out help text | 3 |
63 | CLI-716 | 07/02/2015 02:27:22 | Update platform sdk to use new api on login | {{lastname}} property is now available on login response. we can use this instead of calling User.find to get it. | 1 |
64 | CLI-717 | 07/06/2015 23:51:47 | Improve feedback when creating a module | h5.Description When creating a Windows platform module the process takes a lot longer than the other platforms, just android takes ~2s, Windows takes ~40s. This is unavoidable because there are certain steps to be taken such as moving all files to a temp directory if necessary due to path length issues. If module creation occurs from the Titanium CLI using {{ti create}} then there is logging as shown in logging.txt, this logging is not shown by the Appc CLI and there is just a spinner for ~40s, there should be some more feedback from the CLI to let the user know what is happening. h5.Steps to reproduce 1. Create a module using {{appc new --type timodule --name module --id com.module --force}} 2. Create a module using {{ti create --type module --name module --id com.module --platforms all --urlblah --workspace-dir . --force}} h5.Actual result 1. No logging occurs 2. Logging occurs h5.Expected result Due to the long creation time there should be some sort of feedback to the user other than a spinner | 3 |
65 | CLI-720 | 07/08/2015 18:28:33 | Appc info output is incorrect | The output for {{appc info}} is wrong. No platforms are shown, there are two banners, commands listed are for {{appc ti <command>}}, two newlines are needed before the "Appcelerator CLI" section, and the general output of the command seems to be for a different command altogether. {code} EWieberMBA:NewSmoke ewieber$ appc info Appcelerator Command-Line Interface, version 4.1.0-6 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Titanium Command-Line Interface, CLI version 4.0.1, Titanium SDK version 4.1.0.v20150706111546 Copyright (c) 2012-2015, Appcelerator, Inc. All Rights Reserved. Please report bugs to http://jira.appcelerator.org/ Usage: titanium <command> [options] Commands: build builds a project clean removes previous build directories config get and set config options create creates a new mobile application help displays this help screen info display development environment information module displays installed Titanium modules plugin displays installed Appcelerator CLI Installer = 4.1.0-1 Core Package = 4.1.0-6 Titanium CLI plugins project get and set tiapp.xml settings sdk manages installed Titanium SDKs setup sets up the Titanium CLI Global Flags: --no-banner disable Titanium version banner --no-colors disable colors --no-progress-bars disable progress bars --no-prompt disable interactive prompting -h, --help displays help -q, --quiet suppress all output -v, --version displays the current version Global Options: --config <json> serialized JSON string to mix into CLI config --config-file <file> path to CLI config file [default: /Users/ewieber/.titanium/config.json] -s, --sdk <version> Titanium SDK version to use to bootstrap SDK-level commands and parse the tiapp.xml; actual Titanium SDK used determined by <sdk-version> in the tiapp.xml [default: latest] {code} *Steps to reproduce issue* 1. Run {{appc info}} *Actual Results* The output is incorrect as explained above *Expected Results* The output should reflect the correct info for Appc CLI | 3 |
66 | CLI-722 | 07/09/2015 18:49:26 | appc info: Should display all relevant versions, not just Installer + Core | Now we're wrapping Titanium + ACS + Alloy CLI in the AppC CLI which itself is 2 parts, things get confusing :) It would help if {{appc info}} would give you more detail like: {code} - Appcelerator CLI 4.1.0 Update via: [sudo] npm i -g appcelerator |- Appcelerator Core 4.1.0 Select via: appc use | |- Titanium CLI 4.0.1 Use via: appc ti | | |- Alloy 1.6.2 Use via: appc alloy | |- Arrow 1.1.0 | | | - ACS CLI 1.0.25 Use via: appc acs |- Titanium sdk 4.1.0.GA Select via: appc ti sdk select - XCode 6.4 Switch via: [sudo] xcode-select -switch <path> - Mac OS X 10.10.4 - Node.js 0.10.39 Update via: |- NPM 1.4.28 Update via: [sudo] npm i -g npm - JDK 1.8.0_45 - Appcelerator Studio 4.1.0.201507071122 {code} It would even better if it would show incompatibilities etc. I think in the end we have to find an effective merge of {{appc ti info}} and {{appc info}} which has a good balance between detail and clarity. | 0 |
67 | CLI-724 | 07/10/2015 16:17:24 | Fixed user-agent header for registry client | Reporting: "userAgent": "Appcelerator Arrow SDK/1.0.0", For user-agent header for registry client in CLI. We should set it to the value of AppC.userAgent (from appc-platform-sdk) so we can get the correct version in our analytics. | 1 |
68 | CLI-725 | 07/10/2015 19:21:03 | Support for building Titanium 4.2 iOS apps | In Titanium 4.2, the iOS build changed how it copies files and this causes the encrypted files to be deleted prior to being packaged. appc-cli-titanium simply needs to unmark the encrypted files for deletion. | 5 |
69 | CLI-731 | 07/15/2015 06:32:31 | Error when publishing app | found publishable component appc-web-server at /Users/jhaynie/work/proto/appc-web-server loading for publish /Users/jhaynie/work/proto/appc-web-server/package.json Publishing application ... this could take several minutes loaded config host=https://admin.cloudapp-enterprise-preprod.appctest.com, port=443, sid=connect.sid=s%3AcknqSFoZhNpq3XLrN8OEr26e.bR0sqEdPpbZOvn8SGNSdgzajFwBikOBVvGBQSorYBlg sending {"method":"get","url":"https://admin.cloudapp-enterprise-preprod.appctest.com:443/publish/appc-web-server","headers":{"Cookie":"connect.sid=s%3addbR0sqEdPpbZOvn8SGNSdgzajFwBikOBVvGBQSorYBlg","User-Agent":"Appcelerator/1.1.2 (Macintosh; Intel Mac OS X 14_3_0; en_US) Version/1.1.1 Safari/0.0.0 appcelerator/4.1.1-1","Accept":"text/json, application/json"},"gzip":true,"json":{"orgid":14301}} receiving err=null, body={"success":true,"message":"Published version: 1.0.1. No version is deployed currently."} ERROR | TypeError: Cannot read property '1' of null at /Users/jhaynie/.appcelerator/install/4.1.1-1/package/node_modules/arrow/lib/cloud/index.js:229:24 at Request._callback (/Users/jhaynie/.appcelerator/install/4.1.1-1/package/node_modules/arrow/lib/cloud/index.js:186:4) at Request.self.callback (/Users/jhaynie/.appcelerator/install/4.1.1-1/package/node_modules/request/request.js:197:22) at Request.emit (events.js:110:17) at Request.<anonymous> (/Users/jhaynie/.appcelerator/install/4.1.1-1/package/node_modules/request/request.js:1050:14) at Request.emit (events.js:129:20) at Gunzip.<anonymous> (/Users/jhaynie/.appcelerator/install/4.1.1-1/package/node_modules/request/request.js:996:12) at Gunzip.emit (events.js:129:20) at _stream_readable.js:908:16 at process._tickCallback (node.js:355:11) | 1 |
70 | CLI-733 | 07/16/2015 22:37:59 | When building for Windows with encryption the build never gets further than JavaScript files need to be encrypted | h5.Description When building for Windows with encryption the build does not get further than {{JavaScript files need to be encrypted}}. This *is a regression* from 4.1.1-4 as the build works fine there h5.Steps to reproduce 1. Build a Windows project using {{appc run -p windows -T wp-device}} h5.Actual result The build will not pass {{JavaScript files need to be encrypted}} h5.Expected result The build should continue | 5 |
71 | CLI-734 | 07/17/2015 00:40:20 | Developer banner should not show when a command is run with --no-banner or -o json | h5.Description When logged into a developer account and running commands with {{\-o json}} or {{--no-banner}} the developer banner should not be shown. This is causing issues such as the dashboard not opening in Studio as seen [here|https://community.appcelerator.com/topic/2607/dashboard/3] {code} Ewans-MacBook-Pro:testApp eharris$ appc info -o json +---------------------------------------------------------------------------------------+ + This is a Developer trial account. You may use this software for evaluation purposes. + + Once you are ready to go to production, upgrade at https://billing.appcelerator.com + +---------------------------------------------------------------------------------------+ {code} {code} Ewans-MacBook-Pro:testApp eharris$ appc info --no-banner +---------------------------------------------------------------------------------------+ + This is a Developer trial account. You may use this software for evaluation purposes. + + Once you are ready to go to production, upgrade at https://billing.appcelerator.com + +---------------------------------------------------------------------------------------+ {code} h5.Steps to reproduce 1. Log into a developer account 2. Run {{appc info -o json}} and {{appc new --no-banner}} h5.Actual result The developer banner is shown h5.Expected result The developer banner should not be shown | 5 |
72 | CLI-735 | 07/17/2015 00:55:06 | Android : If remote encryption property is set & app is built to emulator when machine is offline, no security violation is seen | h6. This is a regression. This issue was not see when last time security was tested (Don't remember what CLI version we tested last time). h5.Steps To Reproduce: 1. Create a classic app. 2. Add the security property to the apps tiapp.xml {code} <property name="appc-sourcecode-encryption-policy" type="string">remote</property> {code} 3. As its a new app it has to be built once before we go offline on our machine, but we also don't want to auto launch the app by building it from studio. To prevent this, build the app using "-b" (build only) flag from CLI when your machine is online. 4. Now go offline & build to android emulator from studio. h5.Actual Results: 1. We see no security violation & the app launches fine. h5. Expected Results: 1. We should see security violation. | 5 |
73 | CLI-737 | 07/18/2015 00:26:26 | Files are encrypted on first build when building with development deploy type | h5.Description When building with a deploy type of development(simulator/emulator build) on the first build the files are being encrypted. On iOS and Android this appears to be handled fine, however on Windows there appears to be issues as the build will not get further than the encryption stage. See the below logging for a comparison between 4.1.0 and 4.1.1-7 CLI. I am *unsure if this is a regression* as it may be expected with the changes to build verification but it is a *change in behavior*. Due to this on the first build to a Windows Phone emulator the build will stop at {{Processing JavaScript files}} and not continue, killing the build and rebuilding will fix this. {code: title=4.1.0} [INFO] Building for Windows Phone emulator: 8-1-1 [INFO] Deploy type: development [INFO] Debugging disabled [INFO] Profiler disabled [INFO] Forcing rebuild: C:\Users\WINDO_~1\AppData\Local\Temp\hmm10\build-manifest.json does not exist [INFO] Launching emulator: 8-1-1 [INFO] Processing JavaScript files [INFO] Generating i18n files [INFO] Generating Native Type Wrappers [INFO] Generating stubs for: Platform.Object [INFO] Setting up native modules for CMakeLists.txt... {code} {code: title=4.1.1-7} [INFO] Building for Windows Phone emulator: 8-1-1 [INFO] Deploy type: development [INFO] Debugging disabled [INFO] Profiler disabled [INFO] Forcing rebuild: C:\Users\WINDO_~1\AppData\Local\Temp\hmm10\build-manifest.json does not exist [INFO] Launching emulator: 8-1-1 [INFO] Windows Phone emulator is ready [INFO] JavaScript files need to be encrypted [INFO] Processing JavaScript files {code} h5.Steps to reproduce 1. Create a project using {{appc new --type titanium --classic --name appName --id com.appc --force}} 2. Build using appc CLI 4.1.0 using {{appc run -p ios -T simulator}} 3. Create a project using {{appc new --type titanium --classic --name appName --id com.appc --force}} 2. Build using appc CLI 4.1.1 using {{appc run -p ios -T simulator}} h5.Actual result When building to simulator/emulator for the first time on 4.1.1-7 the files will be encrypted h5.Expected result Based on historical behavior when building to simulator/emulator the files should not be encrypted at all | 5 |
74 | CLI-740 | 07/22/2015 18:50:29 | Remove unnecessary secondary call to retrieve user information | h6.Accounts Details {quote} Account: [email protected] Joined: Jul 20, 2015 10:19 PM Last Updated: --- Organization: FIS Mobile Sandbox (100000356) Account: [email protected] Joined: Jul 20, 2015 10:20 PM Last Updated: --- Organization: FIS Mobile Sandbox (100000356) {quote} h6.Still asking for the auth code. Here is the terminal output: {code} 05:57:50 [~/App_Studio_Workspace/TitaniumPaydiantSDKiOS_ARC] óÔÔò ʕ·͡ᴥ·ʔ óÔÔò appc logout 18 ↵ Appcelerator Command-Line Interface, version 4.1.2 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. logged out 05:57:53 [~/App_Studio_Workspace/TitaniumPaydiantSDKiOS_ARC] óÔÔò ʕ·͡ᴥ·ʔ óÔÔò appc login Appcelerator Command-Line Interface, version 4.1.2 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ********** This computer must be authorized before you can complete your login. An authorization code was sent to your email at [email protected] ? Please enter the authorization code you received via your email at [email protected]: {code} | 5 |
75 | CLI-741 | 07/28/2015 15:54:42 | Allow for refreshing of session without logging in again explicitly | Although we have lengthened the session duration to three days, the better approach is to allow silent refresh of the session behind the scenes. Both Google and Salesforce have such a mechanism: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_understanding_refresh_token_oauth.htm https://developers.google.com/identity/protocols/OAuth2WebServer?hl=en | 8 |
76 | CLI-746 | 07/29/2015 00:18:54 | Add SPDX-compliant license string | We should use the SPDX "LicenseRef-LICENSE" instead of "Appcelerator Commercial" in our package.json files to avoid the warning "license should be a valid SPDX license expression" This would also include the addition of a LICENSE.md file at the root | 5 |
77 | CLI-747 | 07/29/2015 05:37:30 | Node processes are getting orphaned in certain cases | If you kill a top level process like appc run (the first process), the sub processes that are spawned are not killed and become orphaned. I am easily able to reproduce this with a test case. Sometimes you can reproduce it with killing the process with CTRL+C before fully started running. You can probably also easily reproduce this by starting an arrow server successfully then just sending a kill SIGINT to the main appc process from ps. | 1 |
78 | CLI-754 | 08/06/2015 03:28:07 | CLI: Add support for --no-progress flag to hide progress bars | The "appc" command uses a progress bar to show how much of an SDK has been downloaded or published. The problem is the progress bar keeps writing to stdout and if you subprocess the "appc sdk" command or pipe the output to a file, the output is all messed up. It would better to just have a flag that disables the progress bar. | 1 |
79 | CLI-755 | 08/06/2015 18:16:14 | Cannot run appc commands with CLI 4.2.0-5+ | When using CLI core 4.2.0-5+ I am unable to build, clean, or run {{appc info}}. I get the below error: {code} Failed to load appc-cli-titanium plugin from /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium: Cannot find module 'tmp' Preproduction Environment Active Error: Cannot find module 'tmp' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium/plugins/util.js:25:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) EWieberMBA:CardEngine ewieber$ appc run -p ios --force Appcelerator Command-Line Interface, version 4.2.0-5 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. WARN | Failed to load appc-cli-titanium plugin from /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium: Cannot find module 'tmp' Preproduction Environment Active Failed to load appc-cli-titanium plugin from /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium: Cannot find module 'tmp' ERROR | No valid targets for run. Are you in a project folder? {code} *Steps to reproduce issue* 1. Install and use CLI core 4.2.0-5+ 2. Build a project from the CLI *Actual Results* Commands fail with above error *Expected Results* Commands run without error *Notes* Workaround is to go to your appc-cli-titanium folder and run {{npm install}} {code} DEBUG | [PLUGIN-LOAD] 0ms /Users/ewieber/.appcelerator/install/4.2.0-5/package/appc.js appc:sdk set production to https://platform.appcelerator.com +0ms WARN | Failed to load appc-cli-titanium plugin from /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium Error: Cannot find module 'tmp' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium/plugins/util.js:25:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) DEBUG | [PLUGIN-LOAD] 0ms /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/arrow/appc.js appc:sdk set production to https://platform.appcelerator.com +0ms log level set to "trace" executing command "run" appc:sdk set preproduction to https://360-preprod.cloud.appctest.com +412ms Preproduction Environment Active set environment to {"registry":"https://software-preprod.cloud.appctest.com","security":"https://security-preprod.cloud.appctest.com","baseurl":"https://360-preprod.cloud.appctest.com"} checking credentials for existing session Attempting to load session info from config file check if session is invalidated appc:sdk api response, err=null, body='{"success":true,"result":{"_id":"52a6686f6f55f4c71f00000e","user_id":1502094,"guid":"140c7c37-542c-46f4-9fd2-9e3775972432","openid":"18a8f7e1-fb81-4163-b9cb-3941a69d78a8","firstname":"Eric","lastname":"Wieber","username":"[email protected]","email":"[email protected]","is_staff":true,"org_id":100001711}}' +317ms session expiry 1438899154275 false Arrow Cloud config file: /Users/ewieber/.acs found Arrow Cloud login { mid: '662eaf87211bfeea94c2d90fde5a774fe958c6e8', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise-preprod.appctest.com', username: '[email protected]', cookie: [ 'connect.sid=s%3ACEx4KSsQPqo7BytNjQ2C1egN.DXl385vkJcEKhpGc2KKVNEA0D4ymLyAxeUB9qh4S2Uc; Path=/; Expires=Thu, 06 Aug 2015 22:13:18 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise-preprod.appctest.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise-preprod.appctest.com Arrow Cloud cookie expiry [ 1438899198000 ] session already loaded in opts.session getCredentials() session: { "ipaddress": "172.16.0.28", "username": "[email protected]", "password": "<OMITTED>", "session": "<OMITTED>", "nonce": "<OMITTED>", "environment": { "name": "production", "isProduction": true, "acsBaseUrl": "https://preprod-api.cloud.appctest.com", "acsAuthBaseUrl": "https://dolphin-secure-identity.cloud.appcelerator.com", "nodeACSEndpoint": "https://admin.cloudapp-enterprise-preprod.appctest.com" }, "token": "<OMITTED>", "fingerprint": "662eaf87211bfeea94c2d90fde5a774fe958c6e8", "fingerprint_description": "Mac OSX Serial Number: C02H6083DRQ4", "org_id": 100001711, "expiry": 1438899154275 } loading plugins for command "run" run search paths: [ "/Users/ewieber/.appcelerator/install/4.2.0-5/package", "/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules", "/Users/ewieber/Documents/Appcelerator_Studio_Workspace_save/CardEngine/plugins", "/Users/ewieber/Documents/Appcelerator_Studio_Workspace_save/CardEngine/node_modules", "/Users/ewieber/Documents/Appcelerator_Studio_Workspace_save/node_modules", "/Users/ewieber/Documents/node_modules", "/Users/ewieber/node_modules", "/Users/node_modules", "/node_modules", "/Users/ewieber/.appcelerator/.npm/lib/node_modules" ] [PLUGIN-LOAD] 0ms /Users/ewieber/.appcelerator/install/4.2.0-5/package/appc.js appc:sdk set preproduction to https://360-preprod.cloud.appctest.com +0ms Failed to load appc-cli-titanium plugin from /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium Error: Cannot find module 'tmp' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/appc-cli-titanium/plugins/util.js:25:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) [PLUGIN-LOAD] 1ms /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/arrow/appc.js run plugin: /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/arrow plugin "arrow" failed its "when" function check, skipping... Duplicate option "colors" for command "run", removing... executing command "run" with the following plugins: [] ERROR | Error: No valid targets for run. Are you in a project folder? at async.series.async.each.executeArgs (/Users/ewieber/.appcelerator/install/4.2.0-5/package/lib/commands/run.js:26:15) at /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:607:21 at /Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:246:17 at iterate (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:146:13) at async.eachSeries (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:162:9) at _asyncMap (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:245:13) at Object.mapSeries (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:228:23) at Object.async.series (/Users/ewieber/.appcelerator/install/4.2.0-5/package/node_modules/async/lib/async.js:605:19) at run (/Users/ewieber/.appcelerator/install/4.2.0-5/package/lib/commands/run.js:21:8) at /Users/ewieber/.appcelerator/install/4.2.0-5/package/lib/core.js:498:12 appc:run signal received +2s exit sending to { domain: null, _events: { close: [Function] }, _maxListeners: 10, _closesNeeded: 1, _closesGot: 1, connected: false, signalCode: null, exitCode: 1, killed: false, _handle: null, pid: 6576, stdin: null, stdout: null, stderr: null, stdio: [ null, null, null ] } {code} | 5 |
80 | CLI-758 | 08/10/2015 17:13:13 | Cannot install 4.2.0-12+; memwatch-next install errors | When trying to install any CLI Core version 4.2.0-12 or higher, I get the below error: {code} EWieberMBA:Appcelerator_Studio_Workspace ewieber$ appc use 4.2.0-12 Before you can continue, the latest Appcelerator software update needs to be downloaded. Finding version 4.2.0-12 ... ✓ Validating security checksum ✓ Installing ... ✓ Compiling platform native modules ... └ extract-opts/typechecker ... ✓ └ bunyan/dtrace-provider ... ✓ └ extract-opts/typechecker ... ✓ └ socket.io-client/ws ... ✓ └ ws/bufferutil ... ✓ └ ws/utf-8-validate ... ✓ └ ldapjs/dtrace-provider ... ✓ └ arrow/memwatch-next ... npm WARN package.json [email protected] No repository field. ld: library not found for -lgcc_s.10.5 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [Release/memwatch.node] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23) gyp ERR! stack at ChildProcess.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:820:12) gyp ERR! System Darwin 15.0.0 gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /Users/ewieber/.appcelerator/install/4.2.0-12/package/node_modules/arrow/node_modules/memwatch-next gyp ERR! node -v v0.10.37 gyp ERR! node-gyp -v v1.0.1 gyp ERR! not ok npm ERR! [email protected] install: `node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is most likely a problem with the memwatch-next package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp rebuild npm ERR! You can get their info via: npm ERR! npm owner ls memwatch-next npm ERR! There is likely additional logging output above. npm ERR! System Darwin 15.0.0 npm ERR! command "node" "/usr/local/bin/npm" "install" "[email protected]" "--production" npm ERR! cwd /Users/ewieber/.appcelerator/install/4.2.0-12/package/node_modules/arrow npm ERR! node -v v0.10.37 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npm ERR! not ok code 0 {code} *Steps to reproduce issue* 1. Do not have CLI 4.2.0-12 or higher installed 2. Run {{appc use 4.2.0-12}} or any 4.2.0-X where X > 12 *Actual Results* I get the above error and cannot install *Expected results* I do not get an error and can install the CLI *Notes* Tested 4.2.0-12 through 4.2.0-24 | 1 |
81 | CLI-761 | 08/10/2015 19:52:20 | Publish titanium module into Marketplace | The appc-cli currently supports publishing only Arrow services to registry. It has to add support for publishing titanium modules into registry. While appc-cli creates a module, it should create a appc.json file in the root of the project directory and should contain information about the author/owner, type (timodule), module description, version, license, support details, access level, license etc. If the appc.json file is not available during publish, then it has to prompt for basic information, and then auto-create appc.json file, and then publish the module into registry. | 8 |
82 | CLI-762 | 08/10/2015 20:01:52 | Publish titanium project templates to Marketplace | The appc-cli currently supports publishing only Arrow services to registry. It has to add support for publishing project templates into registry. Users should be able to publish any existing titanium project as a template to Marketplace. If the root directory of the project already contains appc.json file specifying the type as 'template', then it should be able to publish the component to Marketplace, or if some information is missing, then appc-cli should prompt while the user is trying to publish. | 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.