everframe_flutter 1.6.2

Flutter bridge for Everframe reporting on Android, iOS, and web.

1.6.2

• Through the native iOS SDK, a rare crash (EXC_BAD_ACCESS in _platform_memmove) while the SDK listed its crash and release-health stores is fixed. It affected 1.1.0 through 1.6.1, once a session had collected more than about 115 crash-context files. No Dart API change.
• Through @everframe/web, Flutter web apps on Samsung Tizen, LG webOS, Hisense VIDAA, Titan OS and Vega OS TVs report the real device: OS and version, maker, model, the TV's app ID where it has one, and form factor tv.

1.6.1

• Devices are linked from Project settings → Devices in the dashboard now, not the organization's Settings. The README says so.
• Through the native Android SDK, Fire TV devices count as TVs when they declare Amazon's amazon.hardware.fire_tv feature, as well as by the television UI mode or the leanback feature. No Dart API change.

1.6.0

• Quick capture and device linking on real phones, through the native iOS and Android SDKs; no Dart API change. A shake on a phone linked on the dashboard (any build), or on a debug build, files a quick capture with the masked Flutter frame. enableQuickCapture is required for device captures too: without it a shake files nothing. start(quickCapture: false) also turns linking off. Release builds on end users' phones behave as before.
• Quick capture's gesture is ⇧B in the app on both the iOS simulator and the Android emulator, skipped while a text field has focus. The native SDKs handle the key, so no Dart change is needed; this needs native Everframe 1.5.1. iOS simulators also take the dashboard's other bindings (double Shift, ⌘ combos); Android emulators use the dashboard binding only when it is Shift plus a letter or digit, and ⇧B otherwise. npx @everframe/cli capture still works.

1.5.0

• Simulator quick capture for Flutter apps on the iOS simulator and Android emulator (debug builds only). The native SDK never takes its own screenshot in a Flutter app, so quick capture stays ignored until enableQuickCapture(boundaryKey:, sensitiveRegions:, replayBuffer:) supplies masked Flutter evidence. Each capture then sends the same masked screenshot as openReporter, plus, when session replay is enabled for the app, a snapshot of the replay buffer's masked frames. The dashboard's capture-hotkey replay force does not apply to Flutter replay. A capture whose masked frame cannot be produced safely fails, and no image is sent. disableQuickCapture() removes the registration.
• start(quickCapture: false) opts the app out of quick capture.

1.4.0

• Align the plugin and its Android, iOS, and web SDK dependency versions with the coordinated Everframe 1.4.0 release.
• The Dart API and Flutter bridge implementation are unchanged from 1.3.0.

1.3.0

• Native release-health sessions are enabled by default. releaseHealth: false opts out without disabling error reports; crash: false disables both. Native start(debugBuild:) forwards an explicit build flag. Dart errors remain outside the native crash rate.
• The web bridge forwards the health opt-out to Web SDK 1.2.2+, applies changed settings on repeated starts, and cancels deferred initialization when killed.

1.2.1

• The plugin ships on the same version as every other Everframe SDK. Its Android and iOS bridges resolve the native SDK of that exact version and any later patch on the same minor line.
• The native and web SDKs take the SDK key only as sdkKey: EverframeConfig(appId:) on iOS and the apiKey config field on the web are gone. The bridges already pass sdkKey, so the Dart API (appId, sdkKey) is unchanged.
• Errors captured with captureException from Flutter don't carry a session replay; the error-replay support in the native and web SDKs doesn't apply to Flutter apps.

1.2.0

• The Android bridge resolves native Everframe 1.2.x ([1.2.0,1.3.0), was [1.0.0,1.1.0)) and, like the iOS bridge, turns release health off: native 1.2 enables it by default and this plugin has no option for it yet.

• EverframeWebBridge.start(debugBuild:) says whether this is a debug build; Everframe never turns a debug build into a release. It passes the value to @everframe/web; null leaves detection to the web SDK. The Android and iOS plugins have no debugBuild option: the native SDKs detect debug builds themselves.

• The bridge passes the SDK key to the iOS SDK as EverframeConfig(sdkKey:) and to @everframe/web as sdkKey, matching those SDKs' renamed config, so the iOS plugin now requires native Everframe 1.2 (CocoaPods ~> 1.2.0, SwiftPM up to the next minor from 1.2.0). The Dart API (appId, sdkKey) is unchanged.

• start(crash:) turns native crash capture on or off (default on). On Android the native SDK now captures JVM exceptions, native crashes and ANRs by default.

1.0.0

• Stable Android, iOS, and web reporting with privacy masking and native SDK 1.0.0 integration.

0.1.1

• Document published installation, Flutter capture setup, privacy boundaries, and support limits.

0.1.0

• Initial Android and iOS bridge with masked Flutter screenshots, bounded image replay, and native reporter integration.