Digital In-app SDK 4.11.0

Released starting 25th May 2026

This release of Digital In-App SDK supports:
Note: These release notes cover Medallia Digital In-App SDK version 5.0.0 for React Native.

Release highlights

Documentation changes

The Digital Feedback In-app Mobile SDK administration documentation is updated to match the new V2 integration that has been deployed across the majority of customers.

Digital In-app SDK

Android

  • Important: From this release, the minCompileSDK has increased from API 21 to API 23 and our SDK now only functions for API 29 and above.
  • Survey form headers now support native tooltip, allowing users to long-press truncated survey headers to reveal the the full text when using large font sizes.

  • Eliminated potential local SQL injection vulnerabilities.

iOS

  • Survey form headers now support Large Content Viewer, allowing users to long-press truncated survey headers to reveal the full text when using large Dynamic Type sizes.

  • Device text resizing settings are now applied to the Thank You Page.

React

  • The React Native version of the Digital In-app SDK has been updated to support the new TurboModules architecture, introducing complete TypeScript type-safety and synchronous execution.

Resolved issues

General

Android only

  • Reduced the Intent bundle size for form activities to prevent potential TransactionTooLargeException crashes caused by exceeding payload thresholds.

  • Enhanced security by mitigating an insecure serialization vulnerability, updating Bundle.getSerializable calls to use the modern, type-safe API.

  • When attempting to display a Custom Survey using an invalid or unpublished form ID a crash could occur.

iOS only

  • For survey forms in a language other than English, when the respondent was using a screen reader VoiceOver would incorrectly read Invitation Banner buttons in English instead of the appropriate localized language.

  • In the rare event that the stopSDK method was called after a user had dismissed a survey, a memory leak could occur where SDK UI components incorrectly remained in memory.

  • The SDK's internal EventBus subscriber management could encounter a race condition and garbage collection issues.