Simulator Bugs

Here's the status of all your reports with 1.1.2. For those we didn't fix, they're still on our plate. We just weren't able to get to them for 1.1.2 for one reason or another. Please keep reporting issues with the simulator in this thread and we'll address them.

Fixed

• If you are doing makeJsonRequest(), after that's called 10 times, the simulator crashes.
  
• It would also be nice to be able to toggle things like "phoneConnect" in the simulator
  
• provide a way to generate ActivityMonitor History.
  
• This is a minor complaint, but the Low Power Mode menu is wonky.
  
• I'm seeing a bug where the Back button on the simulated Vivoactive is being treated like a PreviousPage, not Back.
  
• The font sizes don't match to actual for FONT_NUMBER_MEDIUM on VA (unless it was fixed in the 1.1 update) and possibly other font issues as well.
  
• Also, if the simulator is running and you "enter low power" mode, and you start another watch face, it will start with the face in regular power mode, but the settings are still checked as "enter low power" in the simulator menu
  
• This issue (https://forums.garmin.com/showthread.php?244357) reported last month appears to only occur in the simulator.
  
• if you look at the screenshot of that app, you will not the TOD and the HR data fields are ON TOP / touching the horizontal line on the simulator. On the watch, it works perfectly and there is a couple pixels worth of separation
  

Not Fixed

• Not a bug, but a suggestion. When running "Simulate>Fit Data>Playback File", any chance it could remember the last directory used, so you don't have to navigate back all the time?The simulator does not show the mark lap screen when auto-lap is invoked or a lap is set by the source code. The F3 does, though. Here I consider it an F3 bug, not a simulator bug
  
• Again, this may be on the list already, but just to make sure. Things that aren't available on the real device and probably will never be, such as "TextPicker" on the va, probably should be caught in the simulator when simulating a va. Another example us using "tones" in a va simulation.
  
• Heading data is always "0 degrees" in both cases, and the quality is always "QUALITY_LAST_KNOWN";
  
• I've noticed that if you periodically pulse the vibration motor (say once or twice a second), the simulated watch will shake so much that the simulation isn't too responsive to key presses anymore.
  

Simulator Crashes with Permissions Set

I encountered an issue where the simulator crashes after trying to kill an app or when relaunching an app. I've notice that this occurs after I set the "steps" permission in the project settings. This was done on windows 8.1 with connect IQ version 1.1.2 and 1.1.3

I don't have access to my setup but if I recall these are the steps to reproduce:

Configure Project Permissions:

• Right-click project and goto Properties>Connect Iq
  
• Under Permissions check off "steps" (this was the only permission I checked off)
  
• Apply settings
  

Run Application in Simulator:

• Set up run configuration for current project
  
• Run the project configuration (causing the simulator to open)
  
• With the application running, kill the application using ctrl-k (alternatively, run the configuration again)
  
• Observe dialogue box saying that simulator.exe has crashed
  

I may have missed an instruction as I am just going from memory. I will confirm these instructions when I get home.

I encountered an issue where the simulator crashes after trying to kill an app or when relaunching an app. I've notice that this occurs after I set the "steps" permission in the project settings. This was done on windows 8.1 with connect IQ version 1.1.2 and 1.1.3

I don't have access to my setup but if I recall these are the steps to reproduce:

Configure Project Permissions:

• Right-click project and goto Properties>Connect Iq
  
• Under Permissions check off "steps" (this was the only permission I checked off)
  
• Apply settings
  

Run Application in Simulator:

• Set up run configuration for current project
  
• Run the project configuration (causing the simulator to open)
  
• With the application running, kill the application using ctrl-k (alternatively, run the configuration again)
  
• Observe dialogue box saying that simulator.exe has crashed
  

I may have missed an instruction as I am just going from memory. I will confirm these instructions when I get home.

I'm not sure the "steps" permission is used for anything. I never set it, but can access the step data without a problem in widgets and watchfaces.

I'm not sure the "steps" permission is used for anything. I never set it, but can access the step data without a problem in widgets and watchfaces.

I found this to be true as well. I am not using it in my watch-app but I thought I would try it out to see what it does and noticed the issue.