Version 5.2 (Mobile)

Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.x. Please refer to Convert Xamarin XAMLs to Maui for migrating them to the new client.

UBIK 5 clients can only connect to UBIK® Servers of version 3.6 and higher!

The minimum supported OS versions are: Android 9; iOS 12.

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.

Android: Store Preview: Available through Google Play Store's invitation link.

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

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

Windows: Store Preview: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our release portal.

Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️

[edit]

• Release Notes
• ⚠️ XAML Notes

Release Notes

Release

5.2.? on 2026-08-?? Android: StoreiOS: Store

• UBIK^® now supports credentials containing accented (and other special) characters, enabling users to authenticate successfully with a wider range of credential formats.

5.2.3 on 2026-08-04 Android: StoreiOS: Store

• Fixed an issue where documents did not reload properly.
• Fixed an issue where it was not possible to toggle the text input scanner from within the string edit dialog, and added a button to do so to the default UI.

5.2.2 on 2026-07-21 Android: Store BetaiOS: Store Beta

• Added support for Offline SSO Login, allowing users to securely access the UBIK Client in offline mode after a successful online SSO authentication.
• UBIK LABs (Experimental) The update interval for live value updates (LiveValueUpdateIntervalMs) can be configured in profiles.
• Updated all client localization translations.
• Updated misleading text resources on dialogues to delete an object on the server and to locally discard an object.
• Fixed an issue where DocumentViewModel.ShowDocumentCommand did not work when combined with InvokeCommandAction.

Known issues

• Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.
• When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.
• When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the dependency property values in dynamic selective lists). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.
• Currently, the Samsung keyboard doesn't show , at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if . is unacceptable.
• The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).
• There are still some known issues with free text and text markup annotations.
• It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.
• SfPullToRefresh was removed due to existing issues, and replaced with a Refresh option in the Context menu.

⚠️ XAML Notes

• UBIKEditString now uses ScanningIsActive rather than CallingViewModel.ScanToInput to show/hide the text input scanner/QR reader. Backwards compatibility is retained for existing customizings, inlcuding that of a scan to input button to trigger property editing. However, the ScanningIsActive binding is more dynamic and can be toggled in realtime, whereas the CallingViewModel.ScanToInput is only applied once when the page is first rendered.