Connect IQ 2.3 beta - blue arrow on startup

The blue triangle screen was recently added to the simulator to display something when an app is not running (you can now kill the app without killing the device). My initial thought was like Jim's, that your apps are crashing, but I'm not convinced that's the case. Let's try something and see what happens:

• Start the simulator via Eclipse (it is not necessary to launch an app)
  
• Open a CMD prompt
  
• cd to your 2.3.0 beta SDK's bin directory
  
• Now, issue the following commands (including the numbers in the square brackets):
  
  • shell
    
  • ciq
    
  • [1]openDevice fenix5 (or some other device that your app supports)
    
  • [2]startApp <the manifest ID of an app that has not worked, do not include dashes>
    
  
  

Here's a breakdown of what we're doing:

• The first command should print a series of messages similar to what it displayed in the Eclipse console, and you'll be placed at a ':>' prompt
  
• The second command should report "[1]shellConnected"
  
• The third command should start the specified device in the simulator, displaying the familiar blue triangle, and report back "[1]deviceStarted"
  
• The fourth command should start the app that matches the specified manifest ID, and report back "[2]appStarted"
  

If it helps to have a visual reference, here's my CMD window while executing these commands:



In my screen capture, there are a couple of lines that begin with '[3]' after the app has started--these are println() statements from my app, so you won't necessarily see these, but you may see other output from your app at this point if it launches. However, if the app does not start, that at least gives us a little better idea what's happening.

The first thing to check at this point is your windows %TEMP%\GARMIN\Apps directory to see whether the app's PRG file is getting copied there. This is PRG the sim actually runs, and it's placed in the temp directory by the Eclipse plug-in when you attempt to run an app. If it's not there, then you'll need to see if something is interfering with that temp directory. If it is there, but you're still not getting it to run, let me know and I'll see what the next steps are.