Difference between revisions of "Version 4.3 (Xamarin)"

Additional Notes

This was originally the release note page for version 4.2 and several preview builds were distributed for internal testing. However, we have to shift it to version 4.3 since other urgent features need to be delivered first in 4.2. For archiving reasons, earlier distributed preview builds will still have the 4.2 version tags and will be documented here as such.

Availability

Android: StoreiOS: Store: Publicly available in Google Play Store / Apple App Store.

Android: Store Beta: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.

iOS: Store Beta: Available through Apple App Store's invitation link.

UWP: App CenterAndroid: App CenteriOS: App Center: Available to those who have access to the Augmensys App Center.

Preview

4.3.? on 2023-03-?? App Center

• Fixed an issue where the user set sync mode was set to "Automatic" when logging out.
• Fixed an issue where selecting an item in a selective list would not be saved.
• Adapted the position of the branch download state symbol to prevent overlapping with other elements.
• Fixed an issue where clicking on new list items in the Multi Select mode triggered Navigation instead of Selection.
• Fixed an issues where buttons showed wrong glyphs. Find the workaround here
• Fixed an issue where selected items didn't behave properly when new items got added to the list.

4.3.13 on 2023-02-10 App Center

• Fixed an issue where all objects are locked after login, when there are a large number of tasks which happen to be data templates as well.
• Greatly improved the UI performance when dealing with a large number of tasks.
• Added the basic support for the developer mode.
• Fixed an issue where some list items occasionally do not respond to clicks.

4.3.12 on 2023-02-08 App Center

• The multi select mode can now be turned on independently for XAML filtered lists (UWP/Xamarin) that share the same source list.
• The dynamic selective list items are now updated even when the relevant dependency properties/objects have changes that are not yet saved.
• For better diagnostics, log entries in UBIKWebserviceDebug now additionally include summaries of webservice responses.
• Activated the text search functionality for the XAMARIN PDF viewer.
• Now enterprise customers can add their policy / readme documents to the UBIK^® client and access them offline.
• Now it's possible to choose whether the device sends crash reports or not.
• Fixed a bug where the app session could be destroyed by failed Push operations.

4.3.9 on 2022-11-18 App Center

• The client now supports a multi select mode which includes actions based on multi select and mass editing properties.
• (Android) Branch downloads are now performed in a dedicated background service and will work while the device is locked or in sleep mode.
• Now it's possible to copy the device ID by clicking on it in the settings page.

4.2.1 on 2022-09-27 App Center

• (iOS) Pushes can now also be updated while the app is in the background and/or the mobile device is in sleep mode, with a deduced frequency (around every 15 minutes).
• Optimized the push processing (including e.g. content updates) so that it can be performed in the background.

4.2.0 on 2022-09-26 App Center

• Deep linking support added, including the possibility to directly navigate to an object and to create (share) a link directly navigating to an object.
• (Android only for now, soon on iOS) Pushes can now also be updated while the app is in the background and/or the mobile device is in sleep mode, with a reduced frequency (around every 15 minutes).
• Adjusted the setting so that whenever the user changes the sync mode in the client, it gets saved to the profile.
• Fixed unintended client spamming requests to server in specific situations (when it loses connection and tries to reconnect).

Known issues

• Sometimes, objects shift their positions in the lists after being edited. We found out that this is related to the 3rd party list control we use and are considering replacing it. However, this will take some more time in order to make all features we build around the control still function.