Atomic Changelog

SDK
iOS
Android
React Native

SDK releases: Android stability fixes, a React Native event change, and an iOS cleanup

Four releases since February 6 focused on stability: Android login, rotation, and app-switching fixes, a standardized React Native event payload, and quieter iOS console output.

Since the February 6 SDK update we have published four additional releases across Android, React Native, and iOS. This window is primarily about stability and compatibility. The main items to review are Android fixes for login, session recovery, and app switching, one React Native event payload change, and an iOS cleanup for background task warnings.

Impact summary

  • Android fixes improve reliability around connector login, device rotation, app switching, and authentication edge cases
  • React Native v3.15.0 bundles recent native fixes and standardizes onTaskStatusUpdate payloads across iOS and Android. This is a breaking change if you parse those payloads within the iOS side of the React Native SDK
  • iOS 3.27.2 removes the background task warning noise previously seen in Xcode console output
  • Android teams still on Kotlin 1.9 now have a cleaner AGP 8.1 path through the legacy SDK variant

New features

Manage is the only product with net-new feature surface in this window. In Android v3.17.0, manage is now supported as a product type in deeplink and task apps, and transactions has been renamed to expenses in app-driven Manage routing. React Native v3.15.0 also standardizes onTaskStatusUpdate payloads across iOS and Android, an important interface change for teams that consume those events directly.

Resolved issues

  • Fixed Android “Webpage not available” errors when members navigate back from connector login pages
  • Resolved Android rotation-related freezes, ANRs, and memory warnings during active Transact sessions
  • Fixed unexpected Transact closure when members switch between apps during a session on Android
  • Fixed intermittent authentication failures caused by multi-valued HTTP headers on certain sites
  • Removed the iOS background task warning pattern previously seen in Xcode console output
  • React Native picks up the recent Android and iOS stability and packaging fixes through the updated native SDKs

Upgrade considerations

  • Breaking change: review React Native v3.15.0 before rollout if your app parses onTaskStatusUpdate directly. The payload shape is now standardized across iOS and Android, so your iOS implementation may be affected
  • Prioritize Android v3.16.1 or v3.17.0 if your team has seen connector-login issues, app-switch instability, rotation-related ANRs, or authentication edge cases
  • Lower priority if your integration is stable, you are not seeing these issues, and the React Native payload change does not affect your app
  • Fixes unexpected Transact closure when members switch between apps during a session
  • Fixes intermittent authentication failures when certain websites return multi-valued HTTP headers
  • Adds manage as a supported product type and renames transactions to expenses in deeplink and task app routing
  • Improves background task handling and removes the background task warning noise seen in Xcode console output
  • Breaking change: onTaskStatusUpdate payloads are now standardized across iOS and Android. iOS no longer wraps data in a status object, and both platforms use _id consistently
  • Includes the Android v3.16.1 and iOS 3.27.1 native SDK updates
  • Fixes the connector-login back-navigation issue that could surface as a “Webpage not available” error
  • Resolves rotation-related ANRs and memory warnings
  • Expands AGP 8.1 compatibility for the legacy -kotlin1.9 variant

No Flutter release landed in this window.

Unlock the action layer of your financial app

To connect with us, please fill out the form. Expect a response within one business day.

Contact sales

Reason

By submitting this form, you agree that your information is collected in accordance with our Privacy Policy.

Our team has received your message.

Here's what to expect for next steps: