In brief: Version 1.1.1 is bug fix rollup, with two minor additions.
| Added, changed or removed feature | Requires changes in MDM data? | Importance |
| Requires minimum iOS 16.1. Please contact us for a version that can work with version 15 or 14. | – | – |
| Added: Message with last error message before heartbeat restored. (1). Note: The last message is shown on device in Settings panel login (2). | No | Low |
| Added: Adjustable heart beat request timeout, in case the default value (60 seconds for iOS 17 & others) proves to be insufficient, using key HBRequestTimeout | * No | Low |
| Fixed: conf_misreads no longer triggers on some non-read-error cases, and is reset for each config loading | No | Low |
| Please see Release notes for ManagdWALplus, version 1.1.0 for important information still valid for version 1.1.1. | No | Low |
- There is normally no need to add the HBRequestTimeout key. The default value of 60 seconds is in most cases sufficient, to make sure that the roundtrip time from request is made to server, until confirmation from server is received by the app is sufficient to not trigger heartbeat transfer abortion.
(1) The last error message before heartbeat restored is shown underneath in three scenarios that followed in sequence. The total number of heartbeats is the sum of hearbeat_success (delivered to logging server) and heartbeats_failed, and can be computed on logging server. Note new label (heartbeat last error report): hrtbt_last_err_reprt. See the table in *** for more detail of probable error descriptons. While some error descriptions are application specific, others are iOS specific, and may vary over time.
A) No errors recorded (empty string):
{
"hrtbt_succ_snc_fail": "5",
"batt_charge": "100%",
"ChrgStat": "Full",
"(Optional)Label of Apple´s choosing": "(Optional) Greetings to those reading the heartbeat log!",
"heartbeat_success": "5",
"hrtbt_fail_snc_succ": "0",
"heartbeats_failed": "0",
"ManagdWALplus": "heartbeat_data",
"offline_en": "false",
"iOSVer": "17.7.1",
"device_id": "TouristInfo Boot 14",
"misread_desc": "(no misreads)",
"conf_misreads": "0",
"MB_RAM_in_use": "30 MB",
"AppVer": "1.1.1/113",
"hrtbt_last_err_reprt": "",
"BasicUsageStatistics": "qLI01=0 qLI02=0 qLI03=0 qLI04=0 qLI05=0 qLI06=0 qLI07=0 qLI08=0 qLI09=0 qLI10=0"
}
B) Errors recorded (here exemplified with Network request FAILED: (Note that two heartbeat messages have been blocked (failed) due to network problems, logging server busy or similar, cf. hrtbt_fail_sinc_succ).
{
"hrtbt_succ_snc_fail": "0",
"batt_charge": "100%",
"ChrgStat": "Full",
"(Optional)Label of Apple´s choosing": "(Optional) Greetings to those reading the heartbeat log!",
"heartbeat_success": "6",
"hrtbt_fail_snc_succ": "3",
"heartbeats_failed": "3",
"ManagdWALplus": "heartbeat_data",
"offline_en": "false",
"iOSVer": "17.7.1",
"device_id": "TouristInfo Boot 14",
"misread_desc": "(no misreads)",
"conf_misreads": "0",
"MB_RAM_in_use": "36 MB",
"AppVer": "1.1.1/113",
"hrtbt_last_err_reprt": "Network request FAILED",
"BasicUsageStatistics": "qLI01=3 qLI02=0 qLI03=0 qLI04=0 qLI05=0 qLI06=0 qLI07=0 qLI08=0 qLI09=0 qLI10=0"
}C) No new errors have occured, so no new message will be transferred this time. Note that this message will go away after it has been transferred one (1) time:
{
"hrtbt_succ_snc_fail": "1",
"batt_charge": "100%",
"ChrgStat": "Full",
"(Optional)Label of Apple´s choosing": "(Optional) Greetings to those reading the heartbeat log!",
"heartbeat_success": "7",
"hrtbt_fail_snc_succ": "0",
"heartbeats_failed": "3",
"ManagdWALplus": "heartbeat_data",
"offline_en": "false",
"iOSVer": "17.7.1",
"device_id": "TouristInfo Boot 14",
"misread_desc": "(no misreads)",
"conf_misreads": "22",
"MB_RAM_in_use": "36 MB",
"AppVer": "1.1.1/113",
"hrtbt_last_err_reprt": "",
"BasicUsageStatistics": "qLI01=0 qLI02=0 qLI03=0 qLI04=0 qLI05=0 qLI06=0 qLI07=0 qLI08=0 qLI09=0 qLI10=0"
}
(2) Screendump of settings login page, with Last known transfer error message shown, indicating that the transfer to the logging server was not completed as normal, due to a failed network request.
Date: November 2024. Text version: 1.0