Uploaded image for project: 'Appcelerator Studio'
  1. Appcelerator Studio
  2. TISTUD-7371

Windows: Attempting to run a project fails with No User logged in

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Release 4.0.0
    • Fix Version/s: Release 4.0.0
    • Component/s: Windows
    • Environment:

      Mac OSX 10.10.2
      Appc Studio: 4.0.0.201504011425
      Appc CLI (NPM): 0.3.37
      Appc CLI (Registry): 0.2.218

      Description

      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

      !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
      

      Looking at this I believe Studio is querying 360 and not the CLI for log in information.

      Steps To Reproduce

      1. On a Windows machine create a new project in Studio
      2. Build the project

      Actual Result

      The build fails with the following

      Expected Result

      The build should not fail

        Attachments

          Activity

            People

            • Assignee:
              pinnamuri Praveen Innamuri (Inactive)
              Reporter:
              eharris Ewan Harris
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: