Difference between revisions of "Version 5.1 (Mobile)"

Release

5.1.?? 2026-??-?? Android: StoreiOS: Store

• The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see Flashlight
• Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.
• Added French localization to the app.

5.1.29 on 2026-02-2? Android: StoreiOS: Store

• Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).

5.1.28 on 2026-02-10 Android: StoreiOS: Store

• The following features which existed in pre 5.0 versions are now available again in 5.1.
  • Map view.
  • POI view. (Aruco and OCR are not yet supported)
  • Location service.
  • Native push.
  • Charts.
• UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.
• Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.
• Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.
• UBIKTabView supports both dynamic and static items in combination with lazy loading.
• Files in the app's data folder can now be opened or deleted directly in the developer settings.
• Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.
• Added support for configurable file-upload size restrictions, preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.
• Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.
• Fixed an issue where displayed file content does not update after you revert its changes.
• Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).
• The UI now updates correctly after mass deletion in multi-selection mode.
• Fixed issue that caused app to be stuck on splash screen after resuming from background.
• Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.
• Fixed an issue where the Chart Thresholds didn't update.
• Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.
• (Android) Fixed an issue in the WebView where some links could not be opened.
• Fixed an issue where toggling NA in the String Editor did not behave correctly.
• Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.
• Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.
• Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.

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.