v0.2.2

• Fixed: InstallResponse.fromJson no longer throws when the backend returns deepLinkData: {} for an organic (unattributed) install, which surfaced as an error out of initialize(). An empty — or otherwise unusable — deepLinkData object is now treated as "no deep link" (null), the same as an explicit null.

pub.dev: linkforty_flutter: ^0.2.2

Recommended for everyone on 0.2.1 or earlier: every organic (unattributed) install failed SDK initialization before this fix, not just the deep-link portion of it. Ports mobile-sdk-ios#4 (iOS 1.4.1) and mobile-sdk-android#4 (Android 1.3.2).

This release is also the first validated by CI (#8): tests, analyze, format, a generated-sources check, and publish validation now run on every PR.

v0.2.1

• URL parameters are now delivered on a direct open (app already installed), not just after a deferred install. A link shared as ?slug=titanic previously returned only the link's stored configuration on a direct open, because _resolveUrl discarded the local parse of the tapped URL. customParameters now carries both, with URL values winning on a collision — the same precedence the server applies on the deferred path. linkId, deepLinkPath, appScheme, the store URLs and utmParameters remain server-provided (#9).
• The reserved-parameter filter now excludes fp_* and lf_click in addition to the UTM keys, matching the server. Fingerprint signals and the click-correlation id could previously reach an app inside customParameters as if you had set them. Matching is now by prefix, so any utm_ or fp_ name is covered whatever the suffix (#9).

Published to pub.dev: https://pub.dev/packages/linkforty_flutter/versions/0.2.1

v0.2.0

• SDK identity — sdkName/sdkVersion on install + event payloads and an X-LinkForty-SDK header on all requests.
• Last-click attribution — every in-app event is stamped with the deep link that most recently opened the app plus a per-app-open sessionId; the newest open supersedes, the active link persists across restarts, and organic activity stays session-only.
• Screen-view tracking — LinkForty.instance.trackScreenView(name) plus a LinkFortyNavigatorObserver for automatic named-route tracking.

All additive and backward compatible.