codeskop_tracker 0.3.1

Codeskop SDK Flutter plugin — captures Dart and native failures and forwards them to the Codeskop ingest backend.

Changelog

0.3.1

• Fixed (Flutter, iOS): the pub.dev package now includes CodeskopSDK.xcframework. Earlier packages left it out, so iOS apps installing codeskop_tracker from pub.dev couldn't build.
• iOS: Codeskop.track and Codeskop.screen now work (they returned MethodNotImplemented).
• Codeskop.init takes optional environment, captureNetwork, heartbeatEnabled, captureExceptionMessages and captureScreens.
• recordError(..., attributes: {...}) sends attributes with the error.
• Native SDK 0.3.1: the identified user survives an app restart, environment is sent, and captureNetwork / heartbeatEnabled are honoured.

0.3.0

• Product analytics (Growth and Scale): Codeskop.track(name, properties: …), Codeskop.screen(name), and CodeskopNavigatorObserver to record named routes as screens. identify traits are sent for user profiles and segments.
• Native SDK 0.3.0: sessions end after 30 minutes without activity.

0.2.0

• Coordinated release with the native SDK 0.2.0: Android crashes during startup (while the remote-config fetch is in flight) are now captured, and the native CodeskopConfig gains an opt-in captureExceptionMessages (default off). No Dart API change.

0.1.0

• Initial release: Dart API, platform channel bridge to native :tracker-android (AAR) and iOS (CodeskopSDK.xcframework), FlutterError.onError / PlatformDispatcher.onError / runZonedGuarded hooks, and an optional Dio interceptor for Dart-side network capture. Native crashes underneath Flutter are captured by the native SDK's own installed handlers.