Simulator and accelerometer creates unexptected behaviour

[Pietero]

I've expanded my app with the a new function requiring the acceleromter.

The simulator behaves strange when the app tries to read acceleromter data. Ofcourse the simulator does not provide accelerometer data but the whole messaging api starts to disfunction.

Could this be fixed in the next simulator version? Or is there a method to detect if the app is running on the simulator or on a normal watch?

[JonFitbit]

There isn't currently a way to determine if you're running in the simulator or not.

Are you checking for null values before trying to send them using messaging?

[Pietero]

Hi Jon,

I'm looking for null values. For now, i have a global variable which is called OnSimulator. When its true, I simply do not initialize the accelerometer. It solves the problem... And it is not affecting testing since you cannot test the accelerometer at all. Let this Post be usefull for developers who stumble upon the same issue.

[LiamFitbit · Accepted solution]

This should be fixed in the next release of the simulator, thanks for the report!

You'll still not get any data from the accelerometer in the simulator, since there's no source of movement data available, but the rest of your application such as calls to the Messaging API and related events should now function correctly.