The heartbeat can report a a number of different error messages related to errors in network connectivity, in logging server setup, and in the app itself. The values below are valid from ManagdWALplus version 1.1.1 onwards. If you need to contact us to discuss error messages, please do so via the support request contact form. We will reply via the email provided, and may require more info to help you (or us) find & correct the error(-s). If necessary, console logs from an Mac attached to the device may be required to pin down any app internal problems, since the app will provide very verbose internal informaion when the Debg key of the config file is given a value of 3 (or higher). This will grab all errors, important messages and informational messages during execution. Please refer to the instructions for debugging using an attached Mac.
Note that the list below is not exhaustive. Errors may be defined in the iOS operating system that are less known to the developers, and very seldom triggered in real life. Please also note that codes related to HTTP responses are also very briefly explained or commented below, and if necessary refer to relevant literatur for more information.
hrtbt_last_err_reprt messages/codes | comments/explanations | actions |
Netw. unavail. or URL unwrap err | The network is unavailable, or the URL could not be successfully unwrapped. | Check network connection. Check URL for correctness. |
The data couldn’t be read because it isn’t in the correct format | This error occurs when the provided JSON object cannot be serialized. | Please alert us, an error has occured in the forming of the heartbeat messate. |
The value for key ‘key’ is not valid JSON. | This error is thrown when one or more values in the JSON object are not valid JSON-compatible types.. | Please alert us, an error has occured in the forming of the heartbeat message. |
The input object is not valid JSON. | Unlikely error, since JSON is made by the app itself, according to stringent rules. | Please alert us, an error has occured in the forming of the heartbeat message. |
Unable to convert to data. | This error can occur if there is insufficient memory available to serialize the provided object into JSON data. | Make sure to remove memory hungry applications from the device. If necessary, reboot device, try again. If error persists, please contact us. |
The operation couldn’t be completed. Unable to convert the given object to data. | A generic error has occured. | Please alert us, an error has occured in the forming of the heartbeat message. |
The Internet connection appears to be offline. | The device is unable to connect to the internet, either due to no Wi-Fi, cellular issues, or a misconfigured network. | Try again. If the error persists, please check connection, and if necessary contact local network admin. |
The request timed out. | This may be due to logging servers not responding in time | Please check the logging server logs and setup. Is the server properly configured? Does it have a performance issue? Please alert us, if the issue persists. |
Client side codes (400’s) | ManagdWALplus has probably failed to form the request to the logging server correctly | Please alert us, an error has occured in the forming of the heartbeat message. |
Server side codes (500’s) with description: The operation couldn’t be completed. (com.apple.nsurl.error.domain error 500-something). | Something has gone wrong on the logging server side. Has it been inadvertently reconfigured? | Check & fix logging server config. |
The URL is invalid. | There appears to be an error in the URL of the logging server. | Check & fix URL value of the HBSrv key in app config. Consider using a link shortener. |
The operation couldn’t be completed. The request was cancelled. | Unprobable error. | Please alert us, describing the circumstances this happened. |
The certificate for this server is invalid.” (or a more generic SSL-related error) | SSL/TLS handshake failures, such as when the server uses an invalid or expired certificate, or when the client is unable to validate the certificate chain. | Please check if there might be an issue with the SSL certificate. |