Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix inspector to become alive when application resumes from a --start-paused. #2081

Closed
terrylucas opened this issue Jun 14, 2020 · 0 comments · Fixed by #4527
Closed

Fix inspector to become alive when application resumes from a --start-paused. #2081

terrylucas opened this issue Jun 14, 2020 · 0 comments · Fixed by #4527
Assignees
Labels

Comments

@terrylucas
Copy link
Contributor

DevTools correctly handles --start-paused to resume all isolates that are paused. Also fixes exceptions when isWidget, etc. are called and Flutter is paused on start (see PR).

After the application resumed (switch Debugger tab and press 'Resume' button).

Then switch to the inspector tab notice the inspector does not correctly load the widget tree (even after the 'Refresh Tree' is pressed).

The inspector needs to properly reconnect when Flutter is running again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants