Complete
over 2 years ago

bug: Data Field Is Not Running in onUpdate()


Error Name: Data Field Is Not Running
Occurrences: 25
First Occurrence: 2022-10-25
Last Occurrence: 2022-11-19
Devices:
Venu®: 7.20
Venu® 2: 11.08
Venu® 2: 10.24
fēnix® 5X / tactix® Charlie: 25.00
vívoactive® 4: 7.20
Venu® Sq. Music Edition: 3.80
App Versions: 2.1.0
Languages: ces, cht, eng, fre, pol
Backtrace:
ExtHRMField.onUpdate:218  var obscurityFlags = getObscurityFlags();

public function onUpdate(dc as Graphics.Dc) {
  var obscurityFlags = getObscurityFlags();
}

flocsy🤠
  • over 2 years ago

    I believe the above bug is not in my code but in the VM-s. I saw this in all versions of my app. Even now in the latest that was compiled a few days ago with SDK 4.2.2. As you see in the example getObscurityFlags is used in onUpdate as it is documented, and still I get "Data Field Is Not Running" errors. At least in these devices:

    fēnix® 5X Plus: 17.10
    fēnix® 5S Plus: 17.10
    fēnix® 5X / tactix® Charlie: 25.00
    D2Tm Air X10: 6.00
    Venu®: 7.80
    Venu® 2: 11.16
    Venu® Sq. Music Edition: 3.80
    vívoactive® 3: 8.20,
    vívoactive® 3 Music: 6.30
    vívoactive® 4: 7.80
    vívoactive® 4S: 7.80

    (from each device only included the latest version where I saw it)

  • over 2 years ago

    Generally, app crashes occur at runtime due to app-related bugs, while a device crash indicates a bug in the Connect IQ VM (which we naturally try to avoid at all costs). ERA errors are app crashes that should first be investigated & addressed by the app developer. If you've done everything you can to address the issue in app code and the issue persists, it's possible that there's a VM bug at the root of the problem, but we'd need to have code snippets, reproduction steps, etc., that show why you believe the problem is not an app issue.

  • over 2 years ago

    Garmin, it would be nice if somehow it was indicated in these ERA error reports whether the error is something that should concern the developer (an error that most probably needs to be fixed by the developer) vs if the error is something that only Garmin can (or can't) fix. I'm not sure what causes this error, but in the forum the word is that "Data Field Is Not Running" and "System Error" are errors we need to ignore, 'cause there's nothing we can do (except maybe reporting it somewhere, but even that is just an assumption, maybe it's regarded as spam 'cause Garmin already gets these reports from their system anyway)