Browse In-App Agent

Android SDK — Release Notes

ai.revrag:embed-android · release history, newest first. Install the latest with implementation("ai.revrag:embed-android:2.0.0"); confirm the current version on Maven Central.


2.0.0: upgrading from 1.2.3

Upgrade

implementation("ai.revrag:embed-android:2.0.0")

Drop-in. Nothing has been removed or changed in the public API, the dependencies are the same as 1.2.3, and so are the toolchain requirements (minSdk 24, compileSdk 34, Kotlin 2.0+, JDK 17). No code changes are needed.

As before, your repositories must include JitPack (maven("https://jitpack.io")).

The agent's presses are now reported as click events. If your dashboards, funnels or rules count *_pressed, *_toggled or *_selected events as user activity, read The agent's presses are reported and filter on source before you ship.


Changed

The agent's presses are reported

When the agent presses something in your app, the SDK now sends the same analytics_data click event a person's tap produces, with source: "agent". Your users' taps keep source: "user". This covers a tap, an option the agent picks, and a checkbox or switch it changes. Reads, highlights, typing and sliders are not reported. Both sources share one click_sequence, repeats are de-duplicated per source, and the agent's press never counts as the user touching your app. React Native and web already report agent presses this way.


Fixed

The agent never presses or reads one number for another

Numbers are now matched as whole values, in order. The agent no longer takes ₹1,080 for ₹10,800, builds "Pay ₹6,000" out of a card that reads "Pay in 6 EMIs" and "₹3,000 per month", or takes "Due 11/11/2026" for "11/12/2026" or "03/04/2026" for "04/03/2026". When the exact element is not on screen, the agent scrolls to find it or reports it as not found.

A value that just changed is read correctly

Ask for the processing fee after changing the loan amount, and the agent reads the new fee, even though it planned the step from the screen before the change. This applies only to reading and highlighting, never to pressing or typing. In a list that loads rows as you scroll, the agent scrolls to the exact row instead of reading a similar one, and a different tenure, account number or rate is never taken for a changed value.

Bottom-bar tabs can be pressed

The agent measured the tabs of a bottom bar as hidden behind the bar, scrolled for them and refused to press them. In 1.2.2 and 1.2.3, "go to Events" on a bottom tab bar failed, and so did a full-width button pinned to the bottom of the screen. The bar's own elements are now pressed where they are. Content behind the bar is still scrolled into view first.

Grid and list tiles that use OnItemClickListener can be pressed

In a GridView or ListView whose tiles are not clickable themselves, with the click on the list's OnItemClickListener, the agent pressed the list as a whole and nothing opened. It now presses the tile through performItemClick, as a finger does, and only where a finger would fire the item click: the list and the item are enabled, the row holds no button or field of its own, and nothing in between takes the touch.

A tap whose click handler throws is not repeated

If your click handler threw an exception, the SDK retried the step and ran the handler again, possibly after it had already started a payment. The step now fails once and is not retried.

The agent's memory of a screen stays current

A value that changed now replaces its old copy instead of sitting next to it, so the agent is no longer offered stale amounts from earlier on the screen. A row is forgotten only when the SDK sees the whole list without it, never because a sheet or dialog covers it.


Known limitations

  • PIN and OTP keypads that show each digit as a dot (•). The agent cannot see the dot appear, so it stops after the first digit. Users enter these themselves.
  • A switch or checkbox without a label of its own, such as a Switch next to a Text in a Row, cannot be found by name. Give it a contentDescription, or make the whole row toggleable with the label inside.
  • Text longer than a field's maxLength is cut short by Android, and the agent reports the step as not applied.
  • Opening the tab that is already showing is reported as unconfirmed, so a multi-step command stops at that step.

1.2.3: upgrading from 1.2.2

Upgrade

implementation("ai.revrag:embed-android:1.2.3")

Drop-in. Nothing has been removed or changed in the public API, the dependencies are the same as 1.2.2, and so are the toolchain requirements (minSdk 24, compileSdk 34, Kotlin 2.0+, JDK 17). No code changes are needed.

As before, your repositories must include JitPack (maven("https://jitpack.io")).

Click analytics event names change in this release. If your dashboards, funnels or rules use the SDK's *_pressed events, read Taps on your app are named by what they do before you ship.


Changed

Taps on your app are named by what they do

While the button is visible, the SDK reports taps on your app as analytics_data events. It now follows the web SDK's naming, and reports Compose taps for the first time.

Control1.2.21.2.3
Button, tab, icon button<name>_pressed<name>_pressed, type: button_click
Checkbox, switch<name>_pressed<name>_toggled, type: checkbox_toggle
Radio button, selectable option<name>_pressed<name>_selected, type: radio_select
Dropdown<name>_pressed<name>_opened, type: button_click
Any other clickable element<name>_pressed<name>_pressed, type: element_click
Anything built in Composenot reportedreported

The <name> comes from your own identifier first, used as written: a Compose testTag, a View's String tag, or its android:id. An existing btn_pay_pressed stays btn_pay_pressed. Without one, the SDK uses the accessibility label or visible text, cleaned up to at most four words, with digits and currency words left out:

1.2.21.2.3
Loan amount_pressedloan_amount_pressed
terms_checkbox_pressed (a checkbox)terms_checkbox_toggled
nothing (a Compose "Apply now" button)apply_now_pressed

When a name changes, the old one is sent alongside it as legacy_event_name, so dashboards can map old names to new. Each event's data also gains type, kind, role, checked (the state after the tap) and source. The existing element_id, click_sequence, component, x and y are unchanged.

No longer reported: a scroll or drag that ends over a control, a tap that only focuses a text field, a tap on a disabled control, and a second identical event within 300 ms. Taps inside a dialog are now matched to the dialog, not the screen behind it.

See Taps on your app for the full naming rules.

The call card follows more of your dashboard colors

Dashboard color1.2.21.2.3
Gradient colorstwo colorsany number of colors, in order
Text colornot used; name and status always whiteagent name, status line and captions icon
Border coloroutline around the cardoutline around the Start Call button, as in React Native
Button color, when not settranslucent whiteblack, as in React Native

The captions (CC) icon is filled when captions are on and outlined when off. If your card uses a light gradient, set a dark text color so the name and status stay readable.


Fixed

The agent can always see sliders and inputs

On a busy screen, the SDK trims what it sends the agent. It used to drop controls that have no text first, so an unlabelled slider such as a loan-amount slider disappeared. The agent then refused to set it, or typed the amount into nearby text instead. Inputs, buttons and controls such as sliders, switches and checkboxes now always come before plain text. The size limit has also risen from 15 KB to 25 KB, as in React Native, so most screens are sent whole.

A slider the user drags is read at its final value

After the user dragged a slider, the agent could read the value from the middle of the drag for several seconds. The SDK now also updates the agent when the finger lifts.

Scrolling to an element settles in one move

When the agent scrolled to an element to highlight or tap it, list items at the bottom of the screen were mistaken for a bottom bar. The element bounced up and down for about 2 seconds before settling. It now settles in one move. Pinned bars, such as a "Confirm and proceed" footer, are still kept clear.


1.2.2: upgrading from 1.2.1

Upgrade

implementation("ai.revrag:embed-android:1.2.2")

Drop-in. Nothing has been removed or changed in the public API, the dependencies are the same as 1.2.1, and so are the toolchain requirements (minSdk 24, compileSdk 34, Kotlin 2.0+, JDK 17). No code changes are needed.

As before, your repositories must include JitPack (maven("https://jitpack.io")).


Fixed

Floating dialogs are no longer stretched to full screen

Since 1.1.0 the SDK moves its button into your dialogs automatically, so the button stays on top of them. In a floating dialog, such as an AlertDialog, a default DialogFragment or a small loader, that move stretched the dialog to the whole screen. It happened even on screens where the button was hidden. The SDK's own microphone-permission dialog was affected the same way.

Automatic adoption now applies only to full-screen windows, such as bottom sheets and full-screen dialogs. Floating dialogs keep their size, and the button stays in the Activity window underneath them. If you added a workaround, such as pinning a dialog's size, you can remove it.

To keep the button on top of a floating dialog that you have sized yourself, call EmbedProvider.attachOverlay(dialog, activity) as before.

The agent scrolls an element into view before acting on it

Before the agent taps, selects, checks, types into or moves an element, it now makes sure the element is on screen. If less of it is showing than the auto-scroll threshold (60% by default, set on the Revrag dashboard), the agent scrolls the element into view, confirms it is visible, and only then acts.

Before, an element further down a scrolling list could be selected without the screen moving, so the user never saw the change. If an element cannot be brought on screen, the step now fails instead of acting out of sight.

Highlights disappear when the agent clears them

When the agent cleared a highlight, the box used to stay on screen for its full duration of 6 to 9 seconds. It is now removed at once.


Improved

The agent stops when the user takes over

If the user touches or scrolls your app while the agent is highlighting or acting on it, the agent now stops. The running step is cancelled, the highlight and the edge glow disappear, and the SDK reports the interruption to the agent.

Taps on the agent's own button and call bar do not count. A touch while the agent is idle changes nothing.

The busy edge glow follows your dashboard settings

The glow around the screen edges while the agent works now uses the Action config from your Revrag dashboard. These are the same settings the React Native and Flutter SDKs read:

SettingControls
colors.activeBorderGradientThe glow's colors
flags.activeBorderGlowWhether the glow shows at all
effects.activeBorderIts size, boldness and fade timings

The glow now stays on while the agent is working and fades a few seconds after it finishes. Before, it was a fixed 5-second flash in a built-in palette. Dashboard values that previously had no effect on Android now apply, so check that they look the way you want.

The call bar no longer says "Listening" while the user is muted

When the user's microphone is muted and the agent is not speaking, the status line now shows ..... instead of "Listening". When the agent has just finished speaking, "Speaking" stays for 2 seconds first.


New

Two optional functions control which dialogs the button moves into:

EmbedProvider.setAutoAttachDialogs(false)   // turn automatic dialog adoption off entirely
EmbedProvider.excludeFromWidget(dialog)     // keep the button out of one dialog
EmbedProvider.excludeFromWidget(window)     // the same, for a Compose Dialog's window

Deprecated

UIActionEffectOverlay(). The SDK draws the edge glow itself, so nothing needs to call it. Existing calls keep working.


1.2.1: upgrading from 1.2.0

Upgrade

implementation("ai.revrag:embed-android:1.2.1")

Drop-in. Nothing has been removed or changed in the public API, the dependencies are the same as 1.2.0, and so are the toolchain requirements (minSdk 24, compileSdk 34, Kotlin 2.0+, JDK 17). No code changes are needed.

As before, your repositories must include JitPack (maven("https://jitpack.io")), which the SDK's LiveKit dependency needs for its audio-routing library.


Fixed

Crash when a call starts: KotlinReflectionInternalError … requestFocus

Apps could crash when a call started, or when moving between screens during a call:

kotlin.reflect.jvm.internal.KotlinReflectionInternalError: Function 'requestFocus'
(JVM signature: requestFocus()Z) not resolved in class androidx.compose.foundation.…
    at ai.revrag.embed.android.intelligence.UITreeCapture.extractStringValue

It needed all three of these:

  • a release build minified with R8
  • an app that includes kotlin-reflect
  • Jetpack Compose foundation 1.9.0 or newer (Compose BOM 2025.08.00 or later)

When the SDK read the screen for the agent, it converted Compose's accessibility actions to text. On Compose 1.9+, that conversion throws under kotlin-reflect and R8. The SDK no longer converts them.

The bug has existed since 1.1.0 but only surfaced once an app moved to Compose 1.9. We verified the fix on a device: the same test app crashes on 1.2.0 and runs normally on 1.2.1.

R8 may rename the exception, for example to kotlinx.coroutines.CoroutinesInternalError after retracing. The message Function 'requestFocus' … not resolved is what identifies this crash.


Improved

Stability: SDK failures stay inside the SDK

1.2.0 kept failures inside the widget's own UI from reaching your app. 1.2.1 extends that to the other places where the SDK runs code on your app's threads. It also now catches JVM errors, not just exceptions, such as a NoSuchMethodError or NoClassDefFoundError from a library-version mismatch. When something fails, only that SDK feature stops; your app keeps running.

  • Navigation: the SDK's listener on your NavController can no longer throw into your navigate() or popBackStack() calls.
  • Lifecycle callbacks: the SDK's handling of these can no longer throw:
    • fragment start and resume
    • dialog dismissal
    • Activity destruction
    • the app going to the background
    • back presses
    • permission results
    • scroll listeners
  • Taps: the SDK's tap tracking can no longer throw into your touch handling.
  • Background work: failures in the SDK's network requests, events, call handling and on-screen agent missions are contained.
  • Mounting the widget: if attachOverlay or EmbedProviderComposable fails to mount, your app keeps running without the widget. attachOverlay still returns a handle, which safely does nothing.
  • Detaching: detach() can no longer throw.
  • Initializing: calling EmbedSDK.initialize off the main thread no longer throws. The SDK now registers its app-lifecycle observer on the main thread itself.
  • Your listeners: an onAvatarState listener that throws no longer stops your other listeners from being notified.

Calls

  • If connecting fails with an unexpected error, the SDK now resets. Before, it could stay stuck in "connecting" and refuse every later call until the app restarted.
  • If disconnecting fails when a call ends, the call state still resets.
  • A failure while handling one in-call event no longer stops the SDK from handling the rest of the call's events, such as agent messages, captions and disconnects.

The on-screen agent

  • Sliders: when the agent types a value into a slider, such as a loan-amount slider, the slider now moves to that value. It accepts 200000, 2,00,000, ₹2,00,000 and 1 500.50. Words such as "2 lakh" or "max" are refused cleanly, so the agent can retry with a number. Before, these steps always failed.
  • Message sending: if sending one message fails, later messages are no longer held up.
  • Screen snapshots: if a snapshot fails, the SDK skips that snapshot instead of removing the widget.

Changed behaviour

  • Click analytics element_id.
    • A view's tag is now used as its element ID only when the tag is a String.
    • Other tag objects, such as ViewHolders or lambdas, are skipped, and the next fallback (the view's resource ID name) is used.
    • Before, any tag object was converted to text.
    • Views with a content description are unaffected, because that is still checked first.
  • Debug-build logs. Each contained failure is logged in debug builds of your app, naming the SDK feature and the error's class, never its message or any user data. Filter with adb logcat | grep RevragEmbed. Release builds still print nothing.

Known issue (also in earlier versions)

If your release build does not use Android's default ProGuard files (getDefaultProguardFile(...)) and your app does not include RecyclerView, R8 can fail with Missing class androidx.recyclerview.widget.RecyclerView. Add this to your ProGuard rules:

-dontwarn androidx.recyclerview.**

1.2.0: upgrading from 1.1.0

Upgrade

implementation("ai.revrag:embed-android:1.2.0")

Drop-in. Nothing has been removed or changed in the public API, and the toolchain requirements are the same as 1.1.0 (minSdk 24, compileSdk 34, Kotlin 2.0+, JDK 17). If your app doesn't use the new APIs below, no code changes are needed.


New

WebView pages as separate screens: setSubScreen

For apps that show a WebView with several pages on one screen or nav route (KYC, DigiLocker, eSign, partner pages). Each web page reaches the backend as its own screen, while the widget follows the route that hosts the WebView.

webViewClient = object : WebViewClient() {
    override fun doUpdateVisitedHistory(view: WebView, url: String?, isReload: Boolean) {
        if (!isReload) embedHandle?.setSubScreen(pageNameFor(url))  // no tokens, IDs or personal data
    }
}
  • List the route that hosts the WebView in allowedScreens, not the web pages.
  • Moving between pages doesn't flicker the widget or end a live call.
  • Leaving the route clears the page name automatically.
  • If you used setCurrentScreen for web pages, switch to setSubScreen: setCurrentScreen replaces the route, so an unlisted page name hid the widget.

embedHandle is the EmbedOverlayHandle returned by EmbedProvider.attachOverlay(...).

App version at initialization

EmbedSDK.initialize(context = this, apiKey = key, appVersion = "2.4.0") { result -> }

Optional. Without it, the SDK keeps detecting your app's versionName, as in 1.1.0.


Improved

The on-screen agent

  • It no longer targets controls hidden behind a bottom sheet or dialog.
  • It detects disabled buttons and fields and won't tap or type into them.
  • Custom views that expose themselves through accessibility are now visible to it.
  • Field labels are linked to their fields, so it types into the right field.
  • Guided tours skip a missing element instead of stopping, and highlights are centred.
  • Highlights and taps on Compose bottom sheets and dialogs land in the right place.

Stability

  • Bad configuration values from the backend can no longer crash your app (zero-length animations, oversized avatars, negative padding, empty charts).
  • A failure inside the SDK stays inside it: the widget is removed and your app keeps running. Exceptions thrown in your own SDK listeners are isolated too.
  • The SDK's screen cache has memory limits, and a leak that kept an Activity alive is fixed.

UI

  • The microphone-permission explainer uses its own floating dialog theme, in light and dark. Under some app themes it used to open full-screen.

Changed behaviour

  • Logs in debug builds of your app. The SDK now prints lifecycle logs (initialization, screen changes, visibility decisions, call steps) when your app is a debug build. In 1.1.0 the published SDK printed nothing at all, which made integration hard to diagnose. Filter with adb logcat | grep RevragEmbed. These logs never include on-screen text or user data.
  • Release builds are unchanged: the SDK prints nothing.

Known limitations

  • setSubScreen is Android only; it isn't on iOS yet.
  • The agent still can't read or fill content inside a WebView.
  • Two library warnings can appear in release logs and aren't SDK faults: Lottie ("You have N images…", from the avatar animation) and three SLF4J lines at startup.

More detail: the Android Integration Guide (setup, screen naming and WebView steps) and the Android Copilot Integration prompt (full 1.2.3 contract for AI coding agents).