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

iOS: Cannot build for iOS simulator or device

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: iOS
    • Environment:

      Studio 3.2.0, OS-X 10.9.1, Xcode 5.0.2

      Description

      I just upgraded to 3.2.0, OS-X 10.9.1 (Mavericks),Xcode 5.0.2 Launching existing or new projects to the iOS simulator I'm getting: An internal error occurred during: "Launching Titanium iOS Simulator - iOS Simulator - ProjectName". java.lang.NullPointerException Note that I can open the iPhone simulator (7.0.3) from Xcode - the problem is with the new Studio.

      Studio log file:
      !SESSION 2013-12-21 22:04:03.045 -----------------------------------------------
      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/Marek/.eclipse_keyring -showlocation
      Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/Marek/.eclipse_keyring -consoleLog -showlocation

      !ENTRY org.eclipse.core.net 1 0 2013-12-21 22:04:05.925
      !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 2 0 2013-12-21 22:04:06.140
      !MESSAGE Warnings while parsing the images from the 'org.eclipse.ui.commandImages' extension point.
      !SUBENTRY 1 org.eclipse.ui 2 0 2013-12-21 22:04:06.140
      !MESSAGE Cannot bind to an undefined command: plug-in='com.appcelerator.titanium.android.ui', id='com.appcelerator.titanium.mobile.command.run_on_device.android'
      !SUBENTRY 1 org.eclipse.ui 2 0 2013-12-21 22:04:06.140
      !MESSAGE Cannot bind to an undefined command: plug-in='com.appcelerator.titanium.android.ui', id='com.appcelerator.titanium.mobile.command.debug_on_device.android'

      !ENTRY org.eclipse.core.jobs 4 2 2013-12-21 22:04:46.093
      !MESSAGE An internal error occurred during: "Launching Titanium iOS Simulator - iOS Simulator - ttt".
      !STACK 0
      java.lang.NullPointerException
      at com.appcelerator.titanium.ios.ui.launching.simulator.IOSSimulatorLaunchConfigurationDelegate.launch(IOSSimulatorLaunchConfigurationDelegate.java:62)
      at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
      at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
      at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
      at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

      1. barber.txt
        21 kB
        Mark Mokryn
      2. diagLog.txt
        43 kB
        Mark Mokryn
      3. log.log
        20 kB
        Dustin Hyde
      4. prefs-platforms-ios.txt
        10 kB
        Mark Mokryn
      5. titanium.txt
        8 kB
        Mark Mokryn
      6. titanium-ios.txt
        4 kB
        Mark Mokryn
      1. Screen Shot 2013-12-22 at 4.32.34 AM.png
        256 kB
      2. Screen Shot 2013-12-22 at 4.56.02 AM.png
        331 kB

        Activity

        Hide
        ingo Ingo Muschenetz added a comment - - edited

        Hi Mark. Note that it appears to have been fixed for Aaron once he uninstalled/reinstalled the CLI and Alloy, which makes some sense. I actually don't believe Studio has anything to do with it--it's confused by the lack of output from the CLI. My current guess is that during the update, something is not properly overwritten in the 'titanium' package. This, however, is outside of our control. We're just using the npm node.js 'update' command.

        It's possible we could first uninstall and then reinstall instead of doing an update, though it seems heavy-handed.

        Show
        ingo Ingo Muschenetz added a comment - - edited Hi Mark. Note that it appears to have been fixed for Aaron once he uninstalled/reinstalled the CLI and Alloy, which makes some sense. I actually don't believe Studio has anything to do with it--it's confused by the lack of output from the CLI. My current guess is that during the update, something is not properly overwritten in the 'titanium' package. This, however, is outside of our control. We're just using the npm node.js 'update' command. It's possible we could first uninstall and then reinstall instead of doing an update, though it seems heavy-handed.
        Hide
        mokesmokes Mark Mokryn added a comment -

        Ingo, the fact is it's happening to plenty of people, you can see reports of this in the Q&A as well. I'm guessing there's some issue with your npm packaging, but not sure. In any case, "heavy handed" would have saved me a lot of time

        Show
        mokesmokes Mark Mokryn added a comment - Ingo, the fact is it's happening to plenty of people, you can see reports of this in the Q&A as well. I'm guessing there's some issue with your npm packaging, but not sure. In any case, "heavy handed" would have saved me a lot of time
        Hide
        dhyde Dustin Hyde added a comment - - edited

        This can be reproduced using steps:

        1. Open Studio, Create Project, Open Run Configs menu using current environment.

        You should be able to create an ios simulator run config.

        2. Uninstall titanium.

        sudo npm uninstall -g titanium

        3. Install titanium 3.1.2

        sudo npm install -g titanium@3.1.2

        Now the simulators disappear if you create an ios simulator run config.

        Run ti info to verify the simulators do not appear via cli:

        titanium info -o json -t ios

        4. Install titanium 3.2.0.

        sudo npm install -g titanium

        Now the existing run configs are still missing simulators.

        The workaround is to install titanium 3.2.0 and create a new ios simulator run config. This will fix existing run configs as well.

        Note: There is a separate npe if an ios simulator run config is created and no project exists in the workspace.

        Show
        dhyde Dustin Hyde added a comment - - edited This can be reproduced using steps: 1. Open Studio, Create Project, Open Run Configs menu using current environment. You should be able to create an ios simulator run config. 2. Uninstall titanium. sudo npm uninstall -g titanium 3. Install titanium 3.1.2 sudo npm install -g titanium@3.1.2 Now the simulators disappear if you create an ios simulator run config. Run ti info to verify the simulators do not appear via cli: titanium info -o json -t ios 4. Install titanium 3.2.0. sudo npm install -g titanium Now the existing run configs are still missing simulators. The workaround is to install titanium 3.2.0 and create a new ios simulator run config. This will fix existing run configs as well. Note: There is a separate npe if an ios simulator run config is created and no project exists in the workspace.
        Hide
        dhyde Dustin Hyde added a comment -

        This is fixed in Studio 3.2.1.

        Show
        dhyde Dustin Hyde added a comment - This is fixed in Studio 3.2.1.
        Hide
        dhyde Dustin Hyde added a comment -

        Duplicate of TISTUD-5954.

        Show
        dhyde Dustin Hyde added a comment - Duplicate of TISTUD-5954.

          People

          • Assignee:
            pinnamuri Praveen Innamuri (Inactive)
            Reporter:
            mokesmokes Mark Mokryn
          • Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: