Capacitor

Upgrade from 0.1.x to 0.2.x

Move a Capacitor 0.1.x integration to the 0.2.x consent and native dependencies.

Upgrade from 0.1.x to 0.2.x

Plugin 0.2.0 wraps iOS and Android SDK 1.4.0. Plugin 0.1.2 wraps iOS 1.3.0 and Android 1.2.0; those are separate native versions despite sharing one plugin version.

Update the GitHub tag, run npx cap sync, and follow the 0.2.x quick start. Android's minimum moves from API 26 to API 24. The iOS minimum remains 15.0.

If Stay22 must not contact its server before affirmative consent, add the native Stay22RequiresConsent and com.stay22.sdk.RequiresConsent keys, then call Stay22.setEnabled({ enabled: true }) after consent. A JavaScript opt-out alone can arrive after native startup. An enabled value stored before the native 1.4.0 upgrade does not count as an affirmative choice.

The 0.2.0 release also fixes cancellation when a scheduling decision is in progress and Android persistence of a consent choice set before initialization. Recheck both opt-out and trip-cancellation behavior after upgrading. Review the privacy disclosures and your store declarations.

Earlier 0.1.x packages

Use 0.1.2 when maintaining the 0.1.x line. It fixes coexistence with the normal Capacitor local-notifications plugin when load order changes. The README at that release documents the 0.1.x integration. Version 0.1.0 was withdrawn because its iOS half did not build. See the Capacitor changelog.

Continue using setTravelContext and forceNotification in these plugin releases. Newer native notification-receipt APIs do not become available until the wrapper adopts and releases them.

On this page