This behavior seems like a bug, as the code should handle the scenario where field is undefined, especially when processing unknown data. It's advisable to report this issue to Garmin's development team for a fix. In the meantime, as a workaround, you might consider modifying the SDK locally to add additional checks for the existence of field before accessing its properties. glance.intuit.com