Android

1.2.0 — September 8, 2026

Documented that the SDK installs no cookie handler. Stay22's responses set a session22 cookie carrying the same session id the SDK already sends as a parameter. Android's HttpURLConnection defers to the process-wide CookieHandler.getDefault(), which is your app's to set, so the SDK cannot opt out per connection the way the iOS SDK now does and will not install one on your behalf. If your app has a cookie handler it will keep that cookie; the SDK never reads it either way.

Event handling now documents, and the sample now demonstrates, that a when over Stay22Event needs an else branch. The sealed class ships in a separately compiled binary, so a when covering only today's subclasses throws NoWhenBranchMatchedException once a new event is added. Matches the iOS change.

Partner config is now fetched from /ext/partner/settings instead of /ext/partner. The old path is blocked by an unrestricted rule on AdGuard's spyware filter list, so on a device running a system-wide URL filter the SDK never received its config, never scheduled a notification, and retried on every foreground forever. /ext/partner/settings was added for exactly this reason and the web moved to it in April; both paths are registered to the same handler and return the same payload.

Integration self-check via Stay22.diagnostics, reporting each prerequisite as pass/warn/fail with the remedy for anything that fails.
Stay22.requestNotificationPermission { granted -> }, which reports the user's actual answer. The existing no-argument overload returns the state before the prompt is answered and is now documented as such.
Stay22.advanced.scheduleNotification(force:) for verifying an integration without waiting out the normal delay. Defaults to false and never bypasses partner settings.

A transient failure no longer loses that trip's notification permanently.
Repeated travel-context updates no longer defer a notification indefinitely.
A notification can no longer be delivered twice after an interrupted network call.
Notification events raised while the app is not running now reach the host app on next launch.
The SDK can no longer crash the host app on unexpected internal errors, or in apps with a custom background-work setup.
Release builds no longer strip classes the SDK needs; minified builds are covered by CI.
Notification permission is no longer requested when the system cannot show a prompt.

Notification impression reporting when a Stay22 notification is displayed.
A notification_channel_blocked skip reason, so a blocked channel is distinguishable from a missing runtime permission.

SDK activity reporting now includes the installed SDK version for release-level diagnostics.

Treat a blocked notification channel as unavailable. Notifications are no longer scheduled or posted when the user has turned off the destination-suggestions channel while leaving notifications enabled for the app.

The locally built fallback notification link now applies device-context provider exclusions, matching the link the server builds.

Retry loading partner configuration when the app returns to the foreground, so a failed or interrupted initial fetch no longer blocks notifications for the rest of the session.

Notification frequency is now recorded when a notification is shown instead of on the next app launch, so suppression windows start on time and undelivered notifications never count as shown.
Travel context is cleared once its notification is shown; set travel context again to schedule the next one.

A scheduled notification that never appears (for example when the system cancels or defers the background work) is no longer recorded as shown. This prevents an undelivered notification from starting the post-notification cooldown and suppressing later notifications.

Initial binary distribution of the Stay22 Android SDK (.aar) via a Maven repository.

Full release notes and downloads: Android releases