Click in the link above if you are not automatically redirected in 10 seconds.
| FIX / ENHANCEMENT | Nomad: Changed behavior of MarvelClient during Nomad setup. If <ini:MC_DB> is not present, MarvelClient will now try to find its Config DB in one of the default paths on both the MailServer from namelookup and <ini:MailServer>. If a database can be found on the namelookup-based server, it will be used. If the server does not contain a Config DB, or cannot be reached, <ini:MailServer> is tried next. If the server does not contain a Config database, setup will continue and MC will be disabled. If the server cannot be reached, setup will fail (but in that case, Nomad setup will fail on its own as well). If <ini:MC_DB> is present, however, MarvelClient will behave more like on the Rich client, and use the <ini:MC_DB_*> variables to locate the config db. If any of the servers from those variables cannot be reached, setup will fail. A few more details: Before, MC would work the same as on a Rich client. If <ini:MC_DB> was missing, MC would try to find the Config database in one of its default locations. These default locations would oftentimes be on the user's homeserver, based on namelookup. If that server could not be reached, setup would fail. Since many customers have complex setup scenarios, where the homeserver is not necessarily the same as the server against which Nomad devices are being set up, this scenario could cause issues with failures happening in cases where they should not. The new behavior will prevent unwanted setup failures. |
| FIX / CHANGE | On Nomad, if MarvelClient is disabled, it will now set <ini:ExtConfigDone>=1. This serves to prevent a future start with MC being enabled again from running into issue because MC would wrongly consider it a setup case. |
| FIX / CHANGE | On *nix-derived operating systems (macOS, iOS, Android, ...) the config variable reporting scan duration did not contain a drive letter. Now it shows root instead: <os:db_scan_data_drive_root_duration> |
| FIX | Fixed an issue on iOS, where detecting the battery and device type for the new Platform selector would fail on certain models. |
| CHANGE | Nomad: Improved logging about how we find an MC Config DB during initial setup. |