Was just on a flight, and set my phone on airplane mode. Owntrack's notification complained about a "java.net.UnknownHostException: Unable to resolve host [url]...". A bit unnecessary, don't you think? More reasonable would be "No connection". If both mobile and wifi is down, either by flight mode or going into a cave or something, the app should know the reason it's unable to resolve the host.
The same message appears if the server only accepts a local connection and you're outside the local LAN (or the server happens to be offline). What about a "Server unreachable"?
I feel like error messages like "java.net.UnknownHostException" belong elsewhere, like the Status page in the app. You can already view the logs there.
Was just on a flight, and set my phone on airplane mode. Owntrack's notification complained about a "java.net.UnknownHostException: Unable to resolve host [url]...". A bit unnecessary, don't you think? More reasonable would be "No connection". If both mobile and wifi is down, either by flight mode or going into a cave or something, the app should know the reason it's unable to resolve the host.
The same message appears if the server only accepts a local connection and you're outside the local LAN (or the server happens to be offline). What about a "Server unreachable"?
I feel like error messages like "java.net.UnknownHostException" belong elsewhere, like the Status page in the app. You can already view the logs there.