25.6 Release Notes¶

Patch Release Notes Mobile Development Kit Client 25.6.3¶

This patch release includes the following minor updates and important bug fixes for Mobile Development Kit Client 25.6.3:

The fixed screen header no longer overlaps with the phone's status bar on Android after users select an item from the list picker.

Patch Release Notes Mobile Development Kit Client 25.6.2¶

This patch release includes the following minor updates and important bug fixes for Mobile Development Kit Client 25.6.2:

Cross Platform Fixes:

The edge-to-edge display issue on the modal page for Android is fixed
Duplicate tabs are no longer created when PreLoadTabs is set
The issue with redrawing rows in the grouping Object Table is resolved
The correct Android API level is set when building the Nativescript plugin
The default binding for static object cells now has the correct action binding
The style for icons on the Avatar Stack can now be set via rule
Android API level 35 is supported

Additionally, we upgraded SAP BTP SDK for Android to version 24.12.7.

Patch Release Notes Mobile Development Kit Client 25.6.1¶

This patch release includes the following minor updates and important bug fixes for Mobile Development Kit Client 25.6.1:

Cross Platform Fixes:

Removed extra back button for ActionBar
Validation rule wipes out binding on action
Action Bar PrefersLargeCaption display issue when combined with Subhead and styling
App Update not called when onboarded via QR Code

Enhancements include:

Clear all app related files/folder in a Wipe scenario in Single User mode

iOS Fixes:

SystemItem getter issue for the Toolbar Item
Crashing when running multiple download files together
Crashing when multiple Download Stream actions run in parallel
Disappearing Back button
Disappearing Side Drawer button during certain scenarios
App crashes on signing in with a second user after failed transaction from a previous user
Object Card Collection crash on scroll
App crashes on page redraw when closing modal page

Additionally, we updated SAP BTP SDK for iOS to version 24.12.8 and Xcode to version 16.4.

Android Fixes:

OnResume action triggers before app reinitialization when relaunched
SystemItem content description

Enhancements include:

File size and memory check before loading attachments to prevent crashes
Removed reset confirmation prompt triggered from logout action
Styling added for the Support Card Collection Footer Button

Additionally, we updated SAP BTP SDK for Android to version 24.12.6.

Mobile Development Kit Client 25.06¶

Minimum OS version requirements for this release:

iOS/iPadOS 16.x and iOS/iPadOS 18.x (It has been tested with Xcode 16.3, iOS/iPadOS 18.4)
Android OS 8.0 or newer (It has been tested with Android 12/13/14)

New and enhanced features available with the Mobile Development Kit Client 25.04:

Enhancements¶

Locking and Wiping Mechanism¶

We've introduced support for Locking and Wiping functionality on the Mobile Development Kit client, which works seamlessly with SAP Mobile Services. This new feature will significantly enhance security by protecting users' sensitive information from unauthorized access and preventing misuse of their devices.
Administrators can now lock users or wipe device registrations through the following options:
- Initiate Locking or Wiping actions directly from the SAP Mobile Services Admin UI using toggle buttons.
- Set up offline locking/wiping policies that automatically locks or wipes the device when the configured number of days is exceeded. Here, the number of days refers to how long the app has been disconnected from the server.

For more information, refer to Client Policy

`AppImages` Property for Launcher and Splash Icons¶

We’ve introduced a new property AppImages in the MDKProject.json file to automatically generate and configure launcher and splash icons for both Android and iOS. PNG/JPEG formats are supported; however, it is recommended to use PNG for better quality. Android also supports vector images (XML).

We strongly encourage users to adopt this new, automated method for generating app images, as it simplifies the process and ensures consistent results. For more details on the old customization method, refer to the Custom Logo and Splash Screen document.

Support `PlaceHolder` for `ListPicker`¶

With this release, we are introducing a new property for the ListPicker control: PlaceHolder, allowing you to set the text to be displayed when the ListPicker value is empty.

On the Android platform, Mobile Development Kit supports both dialog and bottom sheets for popovers. This release introduces a new option for popovers: IsBottomSheet.

When set to true, the popover is displayed as a bottom sheet.
When set to false or not defined, the popover is displayed as a dialog.

Support for Caption Position in Segmented Control¶

With this release, we are introducing a new property for the Segmented Control: CaptionPosition, allowing you to change the position of the caption relative to the segmented items. This property is only available on iOS. You can choose between two options: "Adaptive" (default) or "Top". When this property is set to Top, the control will always use stacked layout.

Generate Content API From Gemini¶

The Generate Content API from Gemini allows developers to create dynamic, structured content for articles, reports, and multimedia outputs, utilizing advanced AI models such as Gemini 1.0 Pro and Gemini 1.5 Pro.

Integration with the Mobile Development Kit The Mobile Development Kit now supports integration with the Gemini Generate Content API, enabling seamless content generation. To use this feature, SAP AI Core is required to manage the lifecycle of the AI models. Mobile Development Kit interacts with SAP AI Core models to ensure efficient and smooth API usage.
Setup Instructions For detailed, step-by-step guidance on setting up SAP AI Core, please refer to the official SAP AI Core Service Guide.
Supported Features
- Text Input: Submit text prompts to the API to receive AI-generated responses.
- Image Input: Enhance interactions by including images, allowing for a multi-modal conversational experience.
- Function Calling: Enable the AI model to invoke specific functions or execute commands based on the conversation's context.

Support for `getCell` in `DataTableRowProxy`¶

With this release, we are introducing getCell feature in DataTableRowProxy, enabling you to retrieve a DataTableCellProxy object using the column index of the target cell. This new functionality will seamlessly let you access and interact with specific cells within a table row.

Grouping Support¶

The Mobile Development Kit now supports grouping items in the Object Table section. Grouping is based on the $orderby query option of the control's Target Binding, allowing the users to choose which OData properties to use for grouping. For more information, refer to Grouping.

New UI Control¶

Card Body¶

With this release, we have introduced a new optional section, the card body, within the card structure in the card collection. It allows you to display supplementary content, such as text, labels, or other relevant information, right below the card header. The card body is flexible in height, supporting various components like Label Bar, Text, Separator, and customizable UI elements. This feature enhances the organization and readability of the card while keeping the design compact and contextually relevant.

Note

Card collection is only available on Android and iOS.

Donut Chart Style¶

With this release, AnalyticalCardCollection, ChartContent and Object Header Chat View will support the donut chart style. This new chart style will display data in a circular format, offering a more visually appealing alternative to standard charts.

Donut Chart Structure:

The Data format for donut charts is a 2D array, where each inner array contains a single value. For example: [[100], [100], [300], [400], [500], [700], [700]]. If an inner array contains more than one value, only the first value will be used.
Unlike other chart types, donut charts do not support categories, as they are one-dimensional.

New Client APIs¶

`isDeviceCompliant()` to Check Device Compliance¶

With this release, we are introducing a new security feature Device Compliance that allows app developers to check if the device is compromised. With the new client API isDeviceCompliant(), developers can easily determine whether a device is compliant (not rooted) or non-compliant (rooted), returning a Boolean value.

Additionally, the Device Root Status Reporting feature is now available for both Android and iOS, to collect the root status of the device and report to Mobile Services. By enabling Compliance Policy in the mobile services cockpit, detection is automatically performed during app login and on restart, with compliance status displayed for each device registration. For more information, refer to Device Compliance

Last update: October 2, 2025