anyreplay_flutter 0.2.0

Session replay for Flutter apps. Records the screen as a tree of words and boxes, never as screenshots, so every replay can be read and translated.

Changelog

0.2.0

• Breaking: what people type is masked by default. maskAllInputs now defaults to true, as in every AnyReplay SDK: a text field's value is recorded as asterisks. Set maskAllInputs: false in AnyReplay.init to keep recording typed values. Secure, credential, one-time-code and payment fields and card numbers stay masked either way.
• Children that change order, or a child inserted between its siblings, are now sent in their new order. 0.1.0 kept a moved child where it first stood, so a replay could show a list in its old order.
• An open dropdown menu is drawn on its own surface, above the page.

0.1.0

The first release.

• Records a Flutter app as a tree of boxes and words — the recording format the React Native SDK sends — read from the element and render trees every 500 ms, between frames. No screenshots.
• Text with its style; fields with their value, hint and label; buttons, switches, checkboxes, radios, sliders, progress, pickers; icons by name; network images by address and bundled images by content hash; scroll views with their offset; dialogs, menus and sheets as layers; the keyboard and the system bars as frames; web views, maps, videos and custom painting as opaque boxes.
• Masking: secure, credential, one-time-code and payment fields and card numbers — whole, still being typed, or written inside longer text — always; maskAllInputs, maskAllTyping, maskImages and AnyReplayMask on request.
• Consent (requireConsent, consent(true/false)), sampling, 30-minute sessions resumed across launches, taps at touch-up with rage-tap detection, AnyReplayNavigatorObserver for screen names, uncaught errors from FlutterError.onError and PlatformDispatcher.onError, track, trackError, identify.
• identify follows the SDK contract §8.2 as the web and React Native SDKs do from 0.2.3: called before the session's first chunk has been accepted (right after init, the usual place), it waits for that chunk and is sent once, two calls while waiting going as one request; after that it goes at once. An applied: false answer after the first chunk is tried once more after the next one, unless newer traits came meanwhile. A new session — after 30 idle minutes, in the background or the foreground, or resumed at launch — waits for its own first chunk, and is linked again to the latest traits.
• Delivery in chunks of at most 200 events and about 256 KB, with backoff, Retry-After, an offline buffer and a flush when the app goes to the background.
• Passes the AnyReplay SDK contract's conformance scenario with no errors and no warnings.