Skip to main content
operations

Release Notes

active
Audience: developerUpdated 2026-07-25

What changed, when, and what it means for your integration.

What changed, when, and what it means for your integration. For the itemized, per-change list, see the Changelog.

1.0.0 — 2026-07-20 — first stable release (Native SDK)​

This is the first stable release of the Binoban Native SDK (Android + iOS), and the release the compatibility matrix is pinned to.

Breaking change: apiHost is now required​

What changed: apiHost no longer has a default. Earlier versions of the Native SDK fell back to a hardcoded host if you didn't set one; 1.0.0 removes that fallback.

What it means for you: if your existing integration relied on the default, it will now initialize disabled (a safe no-op — it won't crash, but it also won't send anything) until you set apiHost explicitly. Set it to api.binoban.io for cloud, or your tenant's own host for on-prem/air-gapped. See On-prem and the go-live checklist.

Deprecated APIs removed​

1.0.0 begins Binoban's semantic-versioning commitment, so this release also removes every API that had previously been marked deprecated — the last chance to do so before a major-version bump would otherwise be required. If you only used the standard Binoban(apiKey, sourceIdentifier) { … } factory and the event methods (track, identify, flush, reset), you need no code change.

More resilient by default​

  • Failed uploads (network errors, rate-limiting, server errors) are now retried with backoff instead of being dropped outright; only a genuine client error drops a batch.
  • Queued-but-unsent events now persist in your app's private storage rather than a temp directory, so they survive more restart/cleanup scenarios.

iOS additions​

  • A privacy manifest (PrivacyInfo.xcprivacy) now ships with every framework slice.
  • Swift Package Manager is now available as a second distribution channel alongside CocoaPods.
  • Device advertising signals (IDFA) are now included in event context when the user has authorized App Tracking Transparency.

Migration notes​

  • If you don't set apiHost today, set it before upgrading — see On-prem for cloud vs. tenant-host guidance.
  • If you call a screen, group, or alias method directly, note these are internal, not part of the public method surface — see the Native SDK reference for the supported methods.
  • Everyone else: the standard factory and event methods are unchanged; no action required beyond pinning to 1.0.0.

Per-surface status​

SurfaceThis release
Native SDK (Android + iOS)1.0.0 — first stable release
React Native bridge1.0.0 — released alongside the Native SDK
Web SDKnot yet on a public release version — see the compatibility matrix
Docscross-cutting reference pages filled in 2026-07-25

Next steps​

Last updated on