Difference between revisions of "Version 5.3 (Mobile)"

Release

5.3.7 on 2026-11-03 Android: Store Preview

• The Client now displays task item Title and Details properties in full.
• Fixed an issue where documents did not load properly when switching the sync mode.
• The Client now displays a proper toast message when the CopyToClipboardCommand is performed.
• Default tab preselection via the TabSelector is now enabled for the standard Mobile Client.
• Fixed an issue where clicking out of a Property direct editing input field didn't confirm the value.
• Fixed an issue where created document files are not recognized (displayed, uploaded, etc.) when their file extensions do not match the configured cases.
• Fixed an issue where the app sometimes redirects to the login page on certain Android devices. For example, when the device changes the dark mode setting or uses float windows.

Known issues

• On some Android devices (Pixel 7A, iSafe 930.1 as we know), the app doesn't recognize the device cameras on the first launch after fresh installations. If this happens, please simply restart the app and it should be fine from then on.
• 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.