From 2e7216b6b20279e4988c20231bd321609691b4b5 Mon Sep 17 00:00:00 2001 From: Philip Abbey Date: Fri, 30 Aug 2024 21:18:56 +0100 Subject: [PATCH] v2.20 documentation update --- HISTORY.md | 1 + TroubleShooting.md | 2 ++ 2 files changed, 3 insertions(+) diff --git a/HISTORY.md b/HISTORY.md index ac6f67e..dc861bf 100644 --- a/HISTORY.md +++ b/HISTORY.md @@ -32,3 +32,4 @@ | 2.17 | Bug fix for reporting activity metrics that are not found on some devices. | | 2.18 | Bug fix for reporting activity metrics that might be `null` sometimes. This is unsimulatable situation, so this version is a change based on an informed guess. | | 2.19 | A template to evaluate is now optionally allowed on both `group` and `toggle` menu items. The template to evaluate is non-optional on a `template` menu item. All updates are performed in a single HTTP GET request for efficiency. Bug fix for negative heading values. Vibration now (optionally) confirms toggle menu items being tapped. | +| 2.20 | Simplified the code base now that templates have been requested in all menu items. This means the `template` menu item became a superset of `tap`. Therefore the `tap` code has been has been upgraded to include `template` and the latter deprecated. JSON menu definitions continue to support `template` items by instantiating a `tap` menu item, but the schema marks them as deprecated and users should migrate their menu definitions now. Use the [web editor](https://house-of-abbey.github.io/GarminHomeAssistant/web/) for assistance with changes. | diff --git a/TroubleShooting.md b/TroubleShooting.md index 3f2cb14..b99d268 100644 --- a/TroubleShooting.md +++ b/TroubleShooting.md @@ -310,3 +310,5 @@ Stack: ``` The only useful information we can glean from this log is the first line, `Error: Unexpected Type Error`. There is no useful mapping to a line of code unless someone can explain to us how to use the `pc` line. Being able to send us the error type does serve as a clue. + +More on [debugging Monkey C applications](https://developer.garmin.com/connect-iq/core-topics/debugging/#appcrashes). The filenames and line numbers must only be present for deployment of code instrumented for debug.