macOS Sierra 10.12.6, ConnectIQ SDK 2.3.2 - Simulator not starting

Former Member
Former Member
System:
macOS Sierra 10.12.6
ConnectIQ SDK 2.3.2

I was last developing a couple weeks ago and all was working. Recently had an update to the OS as well as an Eclipse update and new ConnectIQ SDK... and now trying to get back to updating my watch face and the simulator just won't launch.

I've tried to launch it manually from the sdk/bin/ directory but it just opens and closes.
When launching watch face from Eclipse it says failed to connect to simulator.

Ideas?
  • make sure that the plugin version matches the version of your sdk (you can update the plugin through help -> install software)

    in case that doesn't do it, in situations like these the "have you tried the off-on approach could work..." :
    update java
    remove eclipse
    install eclipse
    install plugin & sdk

    Cheers
    Peter
    my apps
  • Former Member
    Former Member
    I'm sorry you're having issues. I recently updated my mac as well, but I'm not experiencing this right now. Is this only with a certain app or all apps? I tried with the packaged sample apps.

    Thanks,
    -Coleman
  • Former Member
    Former Member
    Thanks for the suggestions Peter. Just found some time to try to reinstall everything... and... still nothing. doh.

    When trying to launch it manually by opening ConnectIQ.app in the /bin directory it just flashes like a window is going to appear and then nothing... makes me think it's being blocked in some way. But I don't get a Gatekeeper warning about unsigned developer or anything like that.

    I tried with Eclipse Oxygen and Garmin SDK 2.3.4. I also tried manually launching the simulator from older SDKs but still same behavior.
  • Have you tried running it manually from Terminal? Maybe you'll see something in the terminal window that might help.
  • Former Member
    Former Member
    Have you tried running it manually from Terminal? Maybe you'll see something in the terminal window that might help.


    I tried with "open ConnectIQ.app"
    Same symptom, looks like a window is appearing then nothing and nothing shows in Terminal.

    If you launch it from Terminal do you see any status prints?
  • Actually I'm on Windows, not Mac, but it was just an idea. (I've dabbled in OS X, but I don't have access to a Mac to try it out myself.)

    When I launch the sim successfully from a Windows command prompt, I do see some status messages. When I was having problems with Monkeygraph, launching it from the command prompt also produced some messages that helped me figure out what was wrong. Guess that's not the case here, unfortunately.
  • Former Member
    Former Member
    I'm sorry you're having issues. I recently updated my mac as well, but I'm not experiencing this right now. Is this only with a certain app or all apps? I tried with the packaged sample apps.

    Thanks,
    -Coleman


    Normally I can start the simulator and a blank window will open then I can select whichever app/run configuration combo and it will show up. I can't get just the simulator to launch.

    Do you know what else the simulator is dependent on to run? Is there something installed somewhere else on the system I might have to wipe?

    Thanks
  • Did you ever resolve this?

    Try browsing to the connectiq folder then run this i a terminal

    sudo ./ConnectIQ.app/contents/MacOS/simulator

    Fires and and works for me

    See this thread

    https://forums.garmin.com/forum/developers/connect-iq/1270367-mac-simulator-refuses-to-open
  • Former Member
    Former Member
    Did you ever resolve this?

    Try browsing to the connectiq folder then run this i a terminal

    sudo ./ConnectIQ.app/contents/MacOS/simulator

    Fires and and works for me

    See this thread

    https://forums.garmin.com/forum/developers/connect-iq/1270367-mac-simulator-refuses-to-open



    Oh man THANK YOU!!

    Works like a charm. Now... why does it need superuser to start?!
  • Former Member
    Former Member
    Now... why does it need superuser to start?!

    Another thing that might give more info is attaching a debugger to the sim on start. If you launch it from within lldb without superuser privileges, does it provide any more information than the launchd log line posted in the linked thread?