Skip to content

When macOS apps crash on launch, no crash logs printed, fails with "Error waiting for a debug connection: The log reader stopped unexpectedly, or never started." #91830

New issue
New issue
Open
Open
When macOS apps crash on launch, no crash logs printed, fails with "Error waiting for a debug connection: The log reader stopped unexpectedly, or never started."#91830
Labels
P2Important issues not at the top of the work lista: triage improvementsMake GitHub issues easier to triage and more actionableplatform-macBuilding on or for macOS specificallyteam-macosOwned by the macOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-macosTriaged by the macOS platform team
@jmagman

Description

@jmagman
jmagman
opened on Oct 14, 2021

#85654 (comment) was very tricky to debug because the app crashed on launch with a codesigning error, but the flutter logging doesn't say what happened:

[hot_mode_dev_cycle_macos_target__benchmark] [STDOUT] stderr: [+1040 ms] Error waiting for a debug connection: The log reader stopped unexpectedly, or never started.

We should do something like #66092 for macOS to get crash logging from the debugger.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: triage improvementsMake GitHub issues easier to triage and more actionableplatform-macBuilding on or for macOS specificallyteam-macosOwned by the macOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-macosTriaged by the macOS platform team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions