Android

Upgrade from 1.x or 2.x to 3.x

Move an Android 1.x or 2.x integration to the Stay22 Android 3.x SDK.

This guide covers the move from the 1.x integration to Android 3.x. Android 2.0.0 already uses ensure, so from 2.x skip to Upgrading from Android 2.x. If you are staying on 1.x, the README at release 1.7.0 documents that integration. Read the release notes for the exact release you install.

Submit complete trips

Before:

Stay22.setTravelContext(TravelContext(address = "Paris, France"))

After: submit a NotificationRequest through Stay22.notifications.ensure, with the whole trip, timing and deadlines shown in Quick Start.

Omitted fields are now empty rather than merged with earlier context. Keep the same complete request when retrying it. A different ensure leaves the current receipt in place; use its reference with replace to change the trip and cancel to remove it. Replace clearTravelContext() cancellation with notifications.cancel.

Timing and test calls

Normal scheduling no longer waits for the app to enter the background. Use request timing instead of advanced.scheduleNotification. Replace persistent testing.force with the one-shot diagnostic request.

Events and privacy

Read notificationChanged receipts for scheduling and delivery outcomes, rather than the old scheduled, shown, skipped and cancelled event names. A receipt is not proof of visible presentation. Check both the request reason and any execution reason.

This version family adds prepared-link and app/request-identity data flows. Their minimum versions and current service eligibility are described in What reaches Stay22. Recheck your store privacy declarations.

The device home-city text check from 1.x no longer suppresses a trip. Account eligibility and frequency caps still apply. Review normal timing and cancellation behavior in your app before releasing the upgrade.

Upgrading from Android 2.x

Android 2.0.0 already uses the receipt-based request API this guide describes. Review the minimum-version notes in the overview for prepared links, report retries, and app/request identity. Test normal scheduling, cancellation and taps after updating the dependency.

On this page