Complete
over 4 years ago

WERETECH-9471

Fixed

Sensor.setEnabledSensors exception on Venu, Vivoactive 4

I have been getting numerous reports of app crashes due to the Sensor.setEnabledSensors call. This is occurring on a Venu with the new 4.90 firmware, and I've had reports of possibly the same error on Vivoactive 3 and 4 watches after they received their most recent firmware updates in the past week.

My call is

 Snsr.setEnabledSensors( [Snsr.SENSOR_HEARTRATE,Snsr.SENSOR_BIKECADENCE,Snsr.SENSOR_BIKEPOWER] );

(which has been unchanged for literally years) and this is causing this error:
Error: Array Out Of Bounds Error
Details: 'Failed invoking <symbol>'

Removing Snsr.SENSOR_BIKEPOWER from the array does not make any difference.

mappicus
Parents
  • over 4 years ago in reply to cjm007

    It's more the state of the watch than a specific sensor it seems.  As I said, I've seen it with Sensor.SENSOR_PULSE_OXIMETRY (but only once) and also where I'm passing an empty array to disable sensors in ERA.  In ERA, I also see it when I'm just using  SENSOR_TEMPERATURE.

    Based on the number of occurrences I see in ERA, it's really not that common, as I only see it a small number of times.  in the case of Sensor.SENSOR_PULSE_OXIMETRY, after rebooting the watch, I've not seen it again.

Comment
  • over 4 years ago in reply to cjm007

    It's more the state of the watch than a specific sensor it seems.  As I said, I've seen it with Sensor.SENSOR_PULSE_OXIMETRY (but only once) and also where I'm passing an empty array to disable sensors in ERA.  In ERA, I also see it when I'm just using  SENSOR_TEMPERATURE.

    Based on the number of occurrences I see in ERA, it's really not that common, as I only see it a small number of times.  in the case of Sensor.SENSOR_PULSE_OXIMETRY, after rebooting the watch, I've not seen it again.

Children
No Data