flutter-v0.3.1

0.3.1 (2026-08-10)

Bug Fixes

• flutter: Attach opened nothing on Android (1531054)

0.3.0 (2026-08-10)

Features

• carry the panel's attribution switch through to the SDKs (9bfa29f)

0.2.0 (2026-08-09)

Features

• onReady, so a host can cover a blank WebView (9661c96)

flutter-v0.3.0

0.1.5 (2026-08-09)

Bug Fixes

• a client that cannot screenshot must say so (f263e99)

react-native-v0.2.0

0.1.4 (2026-08-09)

Bug Fixes

• a client that cannot screenshot must say so (f263e99)

react-native-v0.1.4

0.1.4 (2026-08-09)

Bug Fixes

• a client that cannot screenshot must say so (f263e99)

react-native-v0.1.3

0.1.3 (2026-08-09)

Bug Fixes

• the frame could not read a single message the SDK sent (5042b91)

react-native-v0.1.2

Bug Fixes

• the panel could not hear the frame at all (240812c)

@algosoftltd/algo-widget-react-native 0.1.0

0.1.0

First release. Everything from the wire protocol up to a one-call
AlgoWidget.init(...), tested without a device.

• Protocol — the session exchange that replaces the browser's Origin
  header on a native client: name the app, get a challenge, come back with a
  platform attestation minted against it. A 401 carrying a challenge is step
  one, not an error.

• TraceRecorder — the interaction trace. Head+tail retention (setup and
  failure survive; a ring buffer keeps only the failure), a media-time clock
  that does not accumulate a gap across pause, the element identity ladder, and
  the redaction rules: a request path never carries a query string, and there is
  no code path that reads a field's value.

• CrashReporter — per-launch, per-route and per-signature throttles,
  persistence across the dying process, and a signature that separates the same
  error on two screens while grouping one bug with its own repeats.

• Bindings — a fetch interceptor (recording FAILED requests only), a
  console capture that records an argument's SHAPE rather than its contents,
  ErrorUtils and unhandled-rejection handlers, and a navigation tracker that
  takes a route name so it works with React Navigation, Expo Router or a
  hand-rolled stack. Each chains rather than replaces — an app with Crashlytics
  keeps it — and restores exactly what it found.

• Frame bridge — the report panel is the same page the web widget serves, in
  a WebView. An unrecognised message is ignored rather than fatal, because the
  panel and the SDK version independently.

• AlgoWidgetPanel (from @algosoftltd/algo-widget-react-native/panel) — the
  report panel in a WebView, loading the same page the web widget serves. Behind
  a subpath so an app that builds its own report UI never pulls in React or
  react-native-webview.

Not in this release: the native capture layer (screen, voice, screenshot). Its
contract is defined (NativeCapture) and the Kotlin and Swift cores exist, but
no module is registered yet — so a panel offers steps only until you supply an
implementation. Everything else works today.

flutter-v0.2.0

0.1.5 (2026-08-09)

Bug Fixes

• a client that cannot screenshot must say so (f263e99)

flutter-v0.1.5

0.1.5 (2026-08-09)

Bug Fixes

• a client that cannot screenshot must say so (f263e99)

flutter-v0.1.4

0.1.4 (2026-08-09)

Bug Fixes

• flutter: publish the bridge fix — 0.1.3 never left the runner (abe2d1e)