appwin_support 0.4.1
appwin_support: ^0.4.1 copied to clipboard
Flutter plugin wrapping the native Appwin Support SDK (ADR-0019).
0.4.1 #
- Documentation on the whole public API, up from 55%: what the product is, the two ways to open a session, and every member of the platform interface and the method channel.
0.4.0 #
- Breaking.
registerPushToken()moved toappwin_core. Push tokens are shared infrastructure for Support, Community and Notifications. - Removed the
AppwinNotificationsnative dependency from the iOS/Android glue (in-app messages already live inappwin_notifications).
0.3.0 #
- Breaking.
fetchPendingInAppMessages()andtrackInAppDelivery()are gone: in-app campaigns are the Notifications product, and they now live inappwin_notificationsasfetchPendingMessages()/syncOnAppOpen()andtrack(). - Breaking.
registerPushToken()moved toappwin_core(shared by every product).AppwinNotifications.registerPushToken()now delegates there. - New sibling package
appwin_notifications: automation events and in-app messages. The product existed natively and in React Native but had no Flutter package.
0.2.1 #
- Real example app: configure, initialise, then render from the answer. It was still the Flutter template, which called neither.
- Package page: simpler snippets that print the result instead of wiring state,
and a clearer note on installing
appwin_core(you do not).
0.2.0 #
Breaking. initialize() no longer takes an appId and no longer
configures the foundation. Call AppwinCore.instance.configure() first, then
initialize(), which answers whether this product may open for your app.
0.1.1 #
- Package page rewritten for pub.dev: what Appwin is, what this package does, installation, a minimal start, and links to the guide for the rest.
- Real licence file instead of the Flutter template placeholder.
0.1.0 #
- First published release.
0.0.2 #
- Android: messenger, identity, push token and in-app messages now go through the native Kotlin SDKs.
registerPushTokenderives the platform from the device instead of defaulting toios.- iOS: the push token, in-app messages and delivery tracking go through
AppwinSupportandAppwinNotificationsinstead of being re-issued as HTTP calls in the glue. Same endpoints as before, one fewer copy to drift. - iOS: those calls no longer replay
bootstrapSessionevery time. The bootstrap rotates the session token on the server, so repeating it before every push token registration invalidated the session in progress. - Depends on
appwin_coreand re-exports it:AppwinCore.instance.configurecomes with this package, one App ID for every product.
0.0.1 #
- Initial version.