Skip to content

Area: Developers

Integrations changelog

Each entry is one SDK release, summarised from that SDK’s release notes. The list starts with the releases of October 2026. It does not list the JavaScript SDK releases after 0.62.4 or the Android (Kotlin) SDK yet. For the highlights of each month, see What’s new.

October 2026

· Flutter SDK 0.3.2

Push fixes on iOS and for signed-in users, and banners as you styled them

  • This is the first Flutter SDK release on pub.dev since 0.2.1. It also brings the changes of 0.3.0 and 0.3.1, which were not published on their own.
  • Breaking: the SDK needs firebase_messaging ^16.7.0 and Flutter 3.27 (Dart 3.6) or later. With it, push taps reach the SDK in iOS apps that use the UIScene lifecycle.
  • When a push tap starts the app, onNotificationTapped now waits for the first frame with your root widget, so navigation through your navigatorKey works. The click is still tracked at once.
  • A push that arrives while the app is in the foreground is now shown on iOS, once. If your app wants foreground pushes hidden, set the presentation options again after you enable tracking.
  • Overlapping enablePushEngagementTracking calls set up push handling once, so foreground pushes are no longer shown and tracked twice.
  • After a sign-in, a logout or an account switch (setProfileId(newId, true)), the SDK registers the device’s push token under the new profile. Before, a signed-out user’s pushes could reach the device for up to 24 hours, and after a first sign-in the token stayed on the anonymous profile. After an upgrade, the SDK uploads the stored token once.
  • Registering a push token no longer clears the pending cart, wishlist, profile and device changes, so the next tracking call sends them.
  • Bars, flyouts and pop-ups use the card colour, size, corner radius, position, offsets and close button styles set for the banner. A pop-up is now a card sized to the design, not a full-screen view.
  • In landscape, a flyout’s content clears the Dynamic Island and screen cutouts.
  • The Notification Service Extension template attaches WebP images, never attaches an error page, and no longer delivers a non-Releva notification twice. Its action button category id now matches the SDK’s. Copy the template into your extension again to get these fixes.
  • Behaviour change: the NPS survey’s dark appearance follows the device’s dark mode, not your app’s theme.

· iOS SDK (Swift) 5.2.1

Your app's notification delegate keeps working

  • After enablePushEngagementTracking(), the SDK forwards to the UNUserNotificationCenterDelegate your app set before the call: willPresent for notifications that are not Releva’s, didReceive for every tap once the SDK has handled it, and openSettingsFor. Set your delegate before you call enablePushEngagementTracking().
  • Upgrade note: the SDK already tracks a Releva tap as opened. If your didReceive calls trackEngagement(userInfo:type: .opened), remove that call, or each tap counts twice.

· React Native SDK 0.4.3

Expo adapter: iOS push taps are tracked and routed

  • On iOS, the Expo adapter now reads Releva’s data from the push, so a tap, live or from a cold start, calls onNotificationTapped and records the click. The new export relevaDataFromExpoNotification(notification) does the same for your own addNotificationReceivedListener.
  • On Android, the adapter shows each push once and dismisses Expo’s own copy. With the app closed, the phone can still alert twice for a moment.
  • On Android apps drawn edge to edge, the ✕ of a flyout and of a story can be tapped again.
  • Session ids no longer need a global crypto, so apps without react-native-get-random-values no longer fail on every screen view. The uuid dependency is removed.
  • On Android, the notification channel no longer reports a missing custom sound named default.

· JavaScript SDK 0.62.4

Banners no longer stretch to the window height

  • An Unlayer design whose body has a minimum height of 100% kept it inside the banner, so the card stretched to the height of the window. Every banner now resets that minimum height, so the card is as tall as its content.
  • Before, only banners with a subscription form got the reset, so two identical banners could render differently.
  • A design without such a minimum height looks the same.

· JavaScript SDK 0.62.3

A styled banner's close control stays on screen on phones

  • On a narrow screen, the ✕ of a styled banner could sit partly or wholly off the right edge. It now keeps its overhang only as far as there is room beside the card, so a full-width card ends flush with the screen edge.
  • A Custom css rule that set the close control’s position still applies. The top offset and the card itself do not change.

· JavaScript SDK 0.62.2

Images in banners keep their alignment

  • Unlayer image blocks keep the left, centre or right alignment they were designed with, also on shops whose theme styles table cells. The rules are scoped to each banner.
  • On pop-ups, flyouts and bars, the banner’s own Custom css still overrides them.

· JavaScript SDK 0.62.1

Rounded banner cards clip their content

  • A banner card with a corner radius now clips its content to the rounded corners, so a coloured row or a full-bleed image no longer paints square corners over it. The ✕ is not clipped.
  • Content wider than a rounded card is now cut off at the card’s edge instead of overflowing it.
  • A card with no radius renders as before.

· JavaScript SDK 0.62.0

Impersonation previews work across pages

  • A preview you start with Impersonate now lasts for every page you open in the same browser tab. It ends when you select Exit preview, when Releva reports the preview as ended, or when it expires.
  • A page in a preview sends no tracking: no events, engagement, impressions, web push, NPS or subscriptions. The previewed customer is not stored in your browser.
  • During a preview, the chat bot keeps the preview conversation apart from your own.

· React Native SDK 0.4.1

The banner close button follows your styling

  • The ✕ on pop-ups, bars and flyouts uses the colour, background, border, size and corner radius set for the banner’s close button.
  • This changes the close button on every banner. At the default settings it is a black ✕ on white with no border, as on the web, instead of a dark grey ✕ with a grey ring.
  • The web-only close button settings (symbol, padding, font weight, line height, top and right position) are ignored, as on the other mobile SDKs.
  • A swipe on the dimmed backdrop of a pop-up or flyout no longer closes it. A tap still does.

· JavaScript SDK 0.61.5

A pop-up placed against an edge keeps its close control on screen

  • The ✕ usually hangs outside the card’s top-right corner. On a card placed flush against the top or right edge of the window, it went off screen and the pop-up could not be closed. The overhang is now limited on an edge where the card meets the window.
  • This covers top-placed pop-ups, flyouts and bars, right-placed pop-ups, right-pinned flyouts and a bar’s right edge. The card’s own position does not change.

· JavaScript SDK 0.61.4

The rlv_c consent cookie is removed

  • push() takes consent from your hasConsent() option, so the rlv_c cookie only repeated it, and it was set and deleted on alternate pushes. The SDK no longer writes it, and it is gone from cookiesUsed() and dumpState().
  • push() deletes a leftover rlv_c from older versions once.
  • Search-as-you-type requests no longer carry profile.consent; the search endpoint never read it. push() requests do not change.

· JavaScript SDK 0.61.3

Flyout width in percent is measured against the window

  • A flyout’s cardWidth in percent was measured against the flyout’s own box, so 75% came out as 273px at both 390px and 1440px. It is now a share of the browser window, with the card at its set inset, as on the Kotlin, Swift, React Native and Flutter SDKs.
  • Flyouts with a percentage cardWidth change size with this release. If you raised the percentage to make up for the old behaviour, lower it to the width you want.
  • Flyouts with no cardWidth or a px width render as before. Pop-ups and bars do not change.

· iOS SDK (Swift) 5.2.0

Banners follow the editor's card, position and close button settings

  • Pop-ups, flyouts and bars use the card colour, width, height, corner radius, content alignment, position and offsets set in the banner editor. Their layout matches the React Native SDK.
  • The close button uses the colour, background, border, size and corner radius from the banner’s styles. At the default settings it is now a black ✕ on a white circle with no ring, as on the web.
  • A positive offset now moves a card away from the edge it is anchored to.
  • A pop-up or flyout is shown once per session, and a newer pop-up or flyout replaces the one on screen.
  • Flyouts are 80% of the window wide, dim the rest of the screen and close on a tap outside them. Pop-ups dim the screen black at 50%.
  • A Releva push that arrives in the foreground is also listed in Notification Center.
  • Banners, stories and the NPS survey carry the accessibility identifiers that the React Native SDK sets as test IDs.