airsignal_flutter

Co-authored-by: Cursor [email protected]

Breaking

• Removed Airsignal.apiDomain / Airsignal.apiBaseUrl. The API host is fixed internally and is no longer readable or configurable.
• Removed Airsignal.user.setExternalId. Use Airsignal.login(externalId) / Airsignal.logout() instead.
• Removed AirsignalPushSubscription.token. Push tokens stay native-only; target sends with subscriberId / externalId.
• Removed non-product host APIs: Airsignal.instance, AirsignalNotification.rawPayload, airsignalSdkVersion, listener dispatch helpers, user cache helpers, and Airsignal.debug emit/forwarder methods. Keep Airsignal.debug.setLogLevel.

Changed

• Airsignal.login / Airsignal.logout now fail loudly on error instead of silently succeeding; the cached identity only updates once the server confirms.
• More reliable notification engagement tracking.
• Logs and error messages are fully branded — failures never leak internal API details.
• Soft operational skips log at verbose only; default warn stays business-minimal.
• Android device model prefers the user-visible device name, then the OEM marketing name when needed, then the hardware model code.
• README is minimal and points to the hosted Flutter docs and account signup.

Fixed

• Notification click callbacks now fire reliably when the app is opened from a background or killed state.
• Custom notification data is now delivered correctly to click and foreground listeners.
• Tapping a notification with a link no longer opens the app before the browser. The link now opens directly, and returning from the browser no longer forces the app into the foreground.
• Notification taps work on Android 12 and newer, where the system blocks the previous open path.
• Click engagement and open destination use one native processor (SDK tray → trampoline; system tray → inline). No host→trampoline handoff.
• Cold-start clicks emit once (native flush only; no Dart double-dispatch race).
• System-tray host dismiss runs only when the browser actually opened (not after app fallback).
• Android notifications request vibration permission and default sound + vibration together.
• Android posts to a vibrate-capable channel (Airsignal Push) so devices that already had an older channel still get vibration.