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

  • Well, it works OK.

    As far as I know I've changed nothing. I have a vanilla Windows 10 setup, my device configs were up to date & I've made no personalisation tweaks.

    I went round & round in circles previously and it always crashed with certain values. Now it doesn't.

    I couldn't explain it then & I can't explain it now but as I've moved on to using newer SDK's I more or less forgot about it.

    Thanks for looking at it.

  • 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.

  • We'll see if we can reproduce this. Are your device configs up to date?

  • I quite agree, it makes no sense. All I know is I made a test DF that does nothing but return an explicit number or string. It crashes in the cases I said and doesn't where I said it doesn't. I tried lots of combinations. I assumed it was to do with numbers & decimal places but as you've said "1.2.3" fails but "1,2.3" doesn't. I also wondered if it was to do with width but long text strings are OK.

    Incidentally times also fail, e.g. 12:34.

    SDK 6.2.2 and older are OK, 6.3.x aren't.

    All very odd.

  • this makes no sense IMHO. Are you sure that the only difference is the string/number you return? Can you reproduce the problem in 100% of the cases by replacing the compute with

    return "1.2.3";
    vs
    return "1,2.3";

    ?