everframe_flutter 1.2.1

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

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.