Acknowledged
over 1 year ago

venu3 series devices can crash SDK 6.3.0/1 simulator

Simulators from older SDKs seem OK.

4 field simple datafields can crash the venu3 series simulator
This applies to the venu3, venu3S and vivoactive5.
1, 2 or 3 field displays are OK.

The simulator crashes when some numeric values are returned from the compute method.

Some examples:
return 1.23; // OK
return 12.3; // fails
return "12.3"; // OK
return "12.30"; /fails
return 123; // OK
return "123"; // OK
return 1234; // fails
return "1234"; // fails
return "123.4"; // fails
return "1.2.3"; // fails
return "1,2.3"; // OK
return "1.2,3"; // OK

scletts
Parents
  • over 1 year ago

    I tried reproducing these exact conditions using the Venu 3 device with the 6.3.0 SDK with 4 datafield layout and returning 1234 as an integer in the compute method, but was not producing a crash.

    Can you think of any other variations of your workspace that might be affecting something? For example its possible to leave the simulator open from a different SDK version and then build your app with a different SDK and have it run on the other simulator that is already open. I can't think of any breaking changes between 6.3.0 and SDKs prior to it, but some oddities have been known to happen from this.

Comment
  • over 1 year ago

    I tried reproducing these exact conditions using the Venu 3 device with the 6.3.0 SDK with 4 datafield layout and returning 1234 as an integer in the compute method, but was not producing a crash.

    Can you think of any other variations of your workspace that might be affecting something? For example its possible to leave the simulator open from a different SDK version and then build your app with a different SDK and have it run on the other simulator that is already open. I can't think of any breaking changes between 6.3.0 and SDKs prior to it, but some oddities have been known to happen from this.

Children
No Data