org.eclipse.core.runtime.CoreException: {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."}

Appcelerator JIRA | Eric Merriman | 3 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    h5. Description: While testing Field Service App (FSA) I repeatedly imported the sample, got it running, and then ran on simulator. For 3 runs, two failed service enablement (one test service, one cloud) on the initial creation attempt to enable services. Enabling after creation works. According to Praveen this is due to the service enablement timing conflicting with the task of changing the default GUID to a unique one, which happens for imported samples. If the service enablement occurs too quickly (before the unique GUID is generated), then the service enablement will fail. This does not seem to be a regression, as the process has not changed. But it is intermittent. Studio log shows the following when failure occurs: {code} !ENTRY com.appcelerator.titanium.360.core 4 0 2014-09-24 13:48:04.475 !MESSAGE (Build 3.4.0.201409231834) [ERROR] {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."} !STACK 1 org.eclipse.core.runtime.CoreException: {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."} at com.appcelerator.titanium360.internal.core.Titanium360Manager.handleResponse(Titanium360Manager.java:439) at com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:360) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getACSKeys(ThreeSixtyProject.java:849) at com.appcelerator.titanium360.core.services.ACS360Service.installService(ACS360Service.java:74) at com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installService(Titanium360ProjectUtil.java:177) at com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installServices(Titanium360ProjectUtil.java:87) at com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil$2.runInWorkspace(Titanium360ProjectUtil.java:313) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 com.appcelerator.titanium.360.core 4 400 2014-09-24 13:48:04.475 !MESSAGE {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."} {code} h5. Steps to reproduce: 1) Import the FSA sample 2) Watch for service enablement to fail during the import process If no failure, delete the FSA with "remove from disk" option checked and try again. h5. Result: Log records failure, tiapp.xml editor shows failure to enable service h5. Expected Result: Service enabled correctly, with the appropriate GUID

    Appcelerator JIRA | 3 years ago | Eric Merriman
    org.eclipse.core.runtime.CoreException: {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."}
  2. 0

    h5. Description: While testing Field Service App (FSA) I repeatedly imported the sample, got it running, and then ran on simulator. For 3 runs, two failed service enablement (one test service, one cloud) on the initial creation attempt to enable services. Enabling after creation works. According to Praveen this is due to the service enablement timing conflicting with the task of changing the default GUID to a unique one, which happens for imported samples. If the service enablement occurs too quickly (before the unique GUID is generated), then the service enablement will fail. This does not seem to be a regression, as the process has not changed. But it is intermittent. Studio log shows the following when failure occurs: {code} !ENTRY com.appcelerator.titanium.360.core 4 0 2014-09-24 13:48:04.475 !MESSAGE (Build 3.4.0.201409231834) [ERROR] {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."} !STACK 1 org.eclipse.core.runtime.CoreException: {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."} at com.appcelerator.titanium360.internal.core.Titanium360Manager.handleResponse(Titanium360Manager.java:439) at com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:360) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getACSKeys(ThreeSixtyProject.java:849) at com.appcelerator.titanium360.core.services.ACS360Service.installService(ACS360Service.java:74) at com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installService(Titanium360ProjectUtil.java:177) at com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installServices(Titanium360ProjectUtil.java:87) at com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil$2.runInWorkspace(Titanium360ProjectUtil.java:313) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 com.appcelerator.titanium.360.core 4 400 2014-09-24 13:48:04.475 !MESSAGE {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."} {code} h5. Steps to reproduce: 1) Import the FSA sample 2) Watch for service enablement to fail during the import process If no failure, delete the FSA with "remove from disk" option checked and try again. h5. Result: Log records failure, tiapp.xml editor shows failure to enable service h5. Expected Result: Service enabled correctly, with the appropriate GUID

    Appcelerator JIRA | 3 years ago | Eric Merriman
    org.eclipse.core.runtime.CoreException: {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."}
  3. 0

    Issue 13 - testng-eclipse - TestNG does not appear in Run As context menu. - Eclipse plug-in for TestNG - Google Project Hosting

    google.com | 1 year ago
    org.eclipse.core.runtime.CoreException: No property tester contributes a property isTest to type class org.eclipse.core.internal.resources.File at org.eclipse.core.internal.expressions.TypeExtensionManager.getProperty(TypeExtensionManager.java:109) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:95) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:69) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:43) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:282) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.getApplicableConfigurationTypes(LaunchConfigurationManager.java:714) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.getApplicableLaunchConfigurations(LaunchConfigurationManager.java:747) at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.getResourceLabel(LaunchingResourceManager.java:303) at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.computeLabels(LaunchingResourceManager.java:207) at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager$2.run(LaunchingResourceManager.java:125)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    User reported the following exception is seen in the log when prompted for updating the npm packages, and the installation failed: {code} !ENTRY com.appcelerator.titanium.update 4 4 2013-01-01 16:24:30.649 !MESSAGE Error encountered during update !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2013-01-01 16:24:30.649 !MESSAGE !STACK 0 java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableMap.put(Unknown Source) at com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.install(NodePackageManager.java:174) at com.appcelerator.titanium.update.TitaniumNPMRelease.install(TitaniumNPMRelease.java:43) at com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:591) at com.appcelerator.titanium.update.TitaniumSDKUpdater.access$0(TitaniumSDKUpdater.java:556) at com.appcelerator.titanium.update.TitaniumSDKUpdater$2.run(TitaniumSDKUpdater.java:388) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2013-01-01 16:24:30.649 !MESSAGE !STACK 0 java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableMap.put(Unknown Source) at com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.install(NodePackageManager.java:174) at com.appcelerator.titanium.update.TitaniumNPMRelease.install(TitaniumNPMRelease.java:43) at com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:591) at com.appcelerator.titanium.update.TitaniumSDKUpdater.access$0(TitaniumSDKUpdater.java:556) at com.appcelerator.titanium.update.TitaniumSDKUpdater$2.run(TitaniumSDKUpdater.java:388) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY com.appcelerator.titanium.alloy.ui 4 0 2013-01-01 16:24:30.659 !MESSAGE (Build 3.0.1.201212181159) [ERROR] Failed to add Alloy templates !STACK 1 org.eclipse.core.runtime.CoreException: Unable to find 'alloy' binary. at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplatesWithNewCommand(AlloyTemplateInstaller.java:261) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplates(AlloyTemplateInstaller.java:246) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.access$0(AlloyTemplateInstaller.java:244) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:151) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.appcelerator.titanium.alloy.ui 4 0 2013-01-01 16:24:30.659 !MESSAGE Unable to find 'alloy' binary. {code}

    Appcelerator JIRA | 4 years ago | Michael Xia
    org.eclipse.core.runtime.CoreException: Unable to find 'alloy' binary. at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplatesWithNewCommand(AlloyTemplateInstaller.java:261) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.getTemplates(AlloyTemplateInstaller.java:246) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller.access$0(AlloyTemplateInstaller.java:244) at com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$1.run(AlloyTemplateInstaller.java:151)
  6. 0

    GitHub comment 9#30126535

    GitHub | 3 years ago | lrkwz
    org.eclipse.core.runtime.CoreException: Error creating server instance. Check access permission for the directory C:/Program Files/springsource/vfabric-tc-server-developer-2.9.3.RELEASE and its files and subdirectories. at com.vmware.vfabric.ide.eclipse.tcserver.internal.core.TcServerUtil.handleResult(TcServerUtil.java:130) at com.vmware.vfabric.ide.eclipse.tcserver.internal.core.TcServerUtil.executeInstanceCreation(TcServerUtil.java:91) at com.vmware.vfabric.ide.eclipse.tcserver.internal.core.TcServer21ServerHandlerCallback.configureServer(TcServer21ServerHandlerCallback.java:33) at org.springsource.ide.eclipse.commons.internal.configurator.server.ServerDescriptor$ServerHandlerCallbackDelegate.configureServer(ServerDescriptor.java:40) at org.springsource.ide.eclipse.commons.configurator.ServerHandler.createServer(ServerHandler.java:318) at org.springsource.ide.eclipse.commons.configurator.ServerHandler.createServer(ServerHandler.java:157) at org.springsource.ide.eclipse.commons.internal.configurator.server.ConfigurableServerExtension.configure(ConfigurableServerExtension.java:70) at org.springsource.ide.eclipse.commons.internal.configurator.ConfiguratorImporter$4.run(ConfiguratorImporter.java:419)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.eclipse.core.runtime.CoreException

      {"message":"Failed to create app: app with guid 'f4d35fcf-e8ca-4e70-a43c-959ca3dd7f07' already exists."}

      at com.appcelerator.titanium360.internal.core.Titanium360Manager.handleResponse()
    2. com.appcelerator.titanium360
      Titanium360ProjectUtil$2.runInWorkspace
      1. com.appcelerator.titanium360.internal.core.Titanium360Manager.handleResponse(Titanium360Manager.java:439)
      2. com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:360)
      3. com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getACSKeys(ThreeSixtyProject.java:849)
      4. com.appcelerator.titanium360.core.services.ACS360Service.installService(ACS360Service.java:74)
      5. com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installService(Titanium360ProjectUtil.java:177)
      6. com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil.installServices(Titanium360ProjectUtil.java:87)
      7. com.appcelerator.titanium360.ui.util.Titanium360ProjectUtil$2.runInWorkspace(Titanium360ProjectUtil.java:313)
      7 frames
    3. Core Resource Management
      InternalWorkspaceJob.run
      1. org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
      1 frame
    4. Eclipse Jobs
      Worker.run
      1. org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
      1 frame