org.eclipse.core.runtime.CoreException: No signed in user

Appcelerator JIRA | Olga Romero | 2 years ago
  1. 0

    h5.Description When attempting to build a project on Windows the build fails with the following error *No User logged in*. When attempting to build from the CLI the build works with no issues. The stacktrace is the following {code} !ENTRY com.appcelerator.titanium.360.core 4 0 2015-04-01 20:09:24.460 !MESSAGE (Build 4.0.0.201504011425) [ERROR] No user logged in !STACK 1 org.eclipse.core.runtime.CoreException: No user logged in at com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:269) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.doGetOrganization(ThreeSixtyProject.java:153) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getOrganization(ThreeSixtyProject.java:127) at com.appcelerator.titanium360.ui.launch.contributor.VPCDeployTypeLaunchValidator.validate(VPCDeployTypeLaunchValidator.java:60) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.validateLaunchContributors(NodeAppcCLI.java:609) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.build(NodeAppcCLI.java:594) at com.appcelerator.titanium.android.core.launching.AndroidNodeJSCommandsHelper.build(AndroidNodeJSCommandsHelper.java:193) at com.appcelerator.titanium.android.core.launching.AndroidNodeJSCommandsHelper.runOnSimulator(AndroidNodeJSCommandsHelper.java:127) at com.appcelerator.titanium.android.core.launching.AndroidSimulatorLaunchConfigurationDelegate.launch(AndroidSimulatorLaunchConfigurationDelegate.java:229) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:883) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.appcelerator.titanium.360.core 4 100 2015-04-01 20:09:24.460 {code} Looking at this I believe Studio is querying 360 and not the CLI for log in information. h5.Steps To Reproduce 1. On a Windows machine create a new project in Studio 2. Build the project h5.Actual Result The build fails with the following h5.Expected Result The build should not fail

    Appcelerator JIRA | 2 years ago | Ewan Harris
    org.eclipse.core.runtime.CoreException: No user logged in
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    h5.Description When attempting to build a project on Windows the build fails with the following error *No User logged in*. When attempting to build from the CLI the build works with no issues. The stacktrace is the following {code} !ENTRY com.appcelerator.titanium.360.core 4 0 2015-04-01 20:09:24.460 !MESSAGE (Build 4.0.0.201504011425) [ERROR] No user logged in !STACK 1 org.eclipse.core.runtime.CoreException: No user logged in at com.appcelerator.titanium360.internal.core.Titanium360Manager.callAPI(Titanium360Manager.java:269) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.doGetOrganization(ThreeSixtyProject.java:153) at com.appcelerator.titanium360.internal.core.ThreeSixtyProject.getOrganization(ThreeSixtyProject.java:127) at com.appcelerator.titanium360.ui.launch.contributor.VPCDeployTypeLaunchValidator.validate(VPCDeployTypeLaunchValidator.java:60) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.validateLaunchContributors(NodeAppcCLI.java:609) at com.appcelerator.titanium.core.internal.cli.NodeAppcCLI.build(NodeAppcCLI.java:594) at com.appcelerator.titanium.android.core.launching.AndroidNodeJSCommandsHelper.build(AndroidNodeJSCommandsHelper.java:193) at com.appcelerator.titanium.android.core.launching.AndroidNodeJSCommandsHelper.runOnSimulator(AndroidNodeJSCommandsHelper.java:127) at com.appcelerator.titanium.android.core.launching.AndroidSimulatorLaunchConfigurationDelegate.launch(AndroidSimulatorLaunchConfigurationDelegate.java:229) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:883) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.appcelerator.titanium.360.core 4 100 2015-04-01 20:09:24.460 {code} Looking at this I believe Studio is querying 360 and not the CLI for log in information. h5.Steps To Reproduce 1. On a Windows machine create a new project in Studio 2. Build the project h5.Actual Result The build fails with the following h5.Expected Result The build should not fail

    Appcelerator JIRA | 2 years ago | Ewan Harris
    org.eclipse.core.runtime.CoreException: No user logged in
  4. 0

    PyDev for Eclipse / Mailing Lists

    sourceforge.net | 3 months ago
    org.eclipse.core.runtime.CoreException: Terminating: No debugger in target when resuming.

    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

      No signed in user

      at com.appcelerator.titanium.core.internal.cli.NodeTitaniumCLI.run()
    2. com.appcelerator.titanium
      IOSPackagerLaunchConfigurationDelegate$1.run
      1. com.appcelerator.titanium.core.internal.cli.NodeTitaniumCLI.run(NodeTitaniumCLI.java:177)
      2. com.appcelerator.titanium.core.internal.cli.NodeTitaniumCLI.packageProject(NodeTitaniumCLI.java:559)
      3. com.appcelerator.titanium.ios.core.launching.IOSNodeJSCommandsHelper.packageProject(IOSNodeJSCommandsHelper.java:542)
      4. com.appcelerator.titanium.ios.internal.ui.launching.packaging.IOSPackagerLaunchConfigurationDelegate$1.run(IOSPackagerLaunchConfigurationDelegate.java:86)
      4 frames
    3. Eclipse Jobs
      Worker.run
      1. org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
      1 frame