Difference between revisions of "Version 4.1 (Xamarin)"

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.

Release

Beta

4.1.50 on 2022-08-19

• Fixed an issue where the config files for property based content filtering get corrupted when you update the filters.
• Some minor UI updates including icons.
• Fixed an issue where the UI doesn’t update when PropertyViewModel.LinkedLevel becomes available.

4.1.48 on 2022-08-17 Android: Store Beta iOS: Store Beta

• Fixed an issue where dynamic selective list items are not always updated when the dependent property values are changed.
• Fixed an issue where the app crashes when browsing properties with extremely long texts. (We now truncate a property's DisplayValue to max. 500 characters. If it's absolutely necessary, you can use DisplayValueUntruncated for the full text. Although please be aware, 900,000 characters seem to be beyond the capability of the Xamarin Forms Label control.)

4.1.47 on 2022-07-20 Android: Store Beta iOS: Store Beta

• Fixed an issue where the scanner in string editors ignores the try-color-inverted-code setting.

4.1.43 on 2022-07-07 Android: Store Beta iOS: Store Beta

• (iOS) Fixed an issue where the enabled state in context menu does not update properly.
• Fixed an issue where content lists are not resorted when navigating back.

Preview

4.1.39 on 2022-07-04 App Center

• Fixed an issue where POIs sometimes do not update their UI (e.g. live values) until selected.
• (iOS) Fixed an issue where the menu in the content page is difficult to scroll.

4.1.38 on 2022-07-01 App Center

• Fixed an issue where the app sometimes incorrectly falls back to the default English locale when the device is set to use Chinese.
• Solved a bug which prevented users to see live value details, after leaving and reentering the page.

4.1.37 on 2022-06-30 App Center

• Small UI adjustments to e.g. editors, building level buttons, scan result texts.
• Fixed an issue where content pages flicker randomly (every time the device receives a location update).
• Fixed an issue where username and password are not properly updated when you switch profiles.
• Fixed an issue where it's sometimes difficult to click on map pins (when icons have empty parts or holes).
• Fixed an issue where a map pin is sometimes not scaled up when you show that object on the map.
• Reduced the size of map pins from 64px to 48px.
• Fixed a bug that caused OCR scanning to not work.
• Fixed an issue where the close POI group button does not work in the map page.
• Fixed an issue where outdated results are presented in most scan features such as QR code, RFID, AR marker scanning. It happens after the code related property values of the result objects have changed until a new user session.
• Fixed an issue where the scan result list doesn’t update when a new scan yields no result.
• Fixed an bug that would cause the geo data input to break when selecting and deleting the whole line.
• Solved a bug which prevented users to see live value details, after leaving and reentering the page.
• Added back the Teach-In button to Geo Editing page.
• Fixed an issue where tasks sometimes stop responding after being editing inline (e.g. user toggling the NA button).

4.1.34 on 2022-06-22 App Center

• Some UI updates including button styles, page layouts, etc.
• It's now possible for users to request exclusive access for UBIK content to prevent others from editing it at the same time.
• Custom UBIKContentArea templates can now be chosen automatically based on certain properties of the context object.
• The managed app configuration on Android now supports for rolling out up to 25 UBIK^® profiles in an enterprise environment.
• Some properties now need to be authenticated first before editing (Authentication Properties).
• The scroll positions of property lists are now by default also remembered (just like content lists).
• Fixed an issue when scanning QR codes with line breaks on Android/iOS.
• Fixed an issue where file (profiles, XAMLs, etc.) import fails on Android due to the outdated permission handling.
• Fixed an issue where the root list is not updated the first time with an empty database.
• Fixed an issue where the LaunchDocumentByReferenceCommand can potentially crash the client on non existing document files.

4.0.13 on 2022-02-24 App Center

• Xamarin Android now supports managed app configuration for rolling out up to 9 UBIK^® profiles in an enterprise environment.
• Property direct editing. However, unlike in the UWP 4.0 client, direct editing is not fully enabled by default due to the limited size of the device screen.
• Some security related improvements.
  • The app now informs the web service to terminate the user session upon logout or app closing.
  • The app no longer allows self signed server certificates.
• UBIK^® clients are now able to log all webservice communication related activities (in UBIKWebserviceDebug.log) for better trouble shooting. It can also be turned off using the EnableSyncLogging setting in the profiles.
• UBIK^® now supports In-App Camera Calibration.
• The app's entire login page is now customizable.
  • As a result, the old feature which allows customizers to configure the background image of the login page (bg_portrait.png/bg_landscape.png) is removed. Because it only worked for Xamarin.UWP and can now be done with regular XAML customizing.
• The app's default profile is now only generated during app startup when no other profiles are detected.
• Fixed an issue where the Logout button sometimes disappeared.
• Fixed an issue where unnecessary messages are logged. ("Message is null")
• Fixed an issue where the SetPropertyValueCommand always saves changes regardless of the AutoSave parameter value.

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.