core/core.g library

Properties

adbExecutable ↔ String

getter/setter pair

Functions

analyzeLaunchFailure(String output, {int maxContextLines = 15}) → LaunchFailureAnalysis

buildAppDiedException({int? pid}) → Future<AppDiedException>

Builds an AppDiedException by reading the log tail and, when possible, performing a best-effort OS-level reason lookup.

canKillAppPidOnHost() → bool

cleanupTempFiles() → void

extractDevicesJson(String output) → String?

Extracts the JSON array from flutter devices --machine output.

hasMeaningfulSessionFiles() → bool

isAndroidAppPidAlive(int pid) → bool

isAndroidTarget() → bool

isAppPidAlive(int pid) → bool

isProcessAlive(int pid) → bool

projectPathFromSessionDir() → String

readAppId() → String?

Reads the persisted app bundle id / package name from .fdb/app_id.txt.

readAppPid() → int?

Reads the app VM PID from appPidFile written by fdb launch after the VM service is confirmed reachable.

readControllerPid() → int?

readControllerPort() → int?

readControllerToken() → String?

readDevice() → String?

readLastLogLines() → List<String>

Reads the last _logTailLines lines from .fdb/logs.txt.

readLogCollectorPid() → int?

Read the log collector PID from its PID file.

readPid() → int?

readPlatformInfo() → ({bool emulator, String platform})?

Returns (platform, emulator) from the platform file, or null if absent.

readVmUri() → String?

writeAppId(String appId) → void

Persists appId to .fdb/app_id.txt so later commands (e.g. crash-report) can use it without requiring --app-id.

writePlatformInfo(String targetPlatform, bool emulator) → void

Stores the Flutter target platform string and emulator flag for the active session. Written by fdb launch, read by fdb screenshot.

Typedefs

LaunchFailureAnalysis = ({String category, List<String> contextLines, String? remediationHint, String rootCause})

Exceptions / Errors

AppDiedException

Thrown when the target Flutter app process has died while fdb is trying to communicate with it via the VM service.