-
Notifications
You must be signed in to change notification settings - Fork 376
Open
Labels
P2important to work on, but not at the top of the work list.important to work on, but not at the top of the work list.add-to-appcross-screenIssues that affect multiple DevTools screens, i.e. shared functionality and widgetsIssues that affect multiple DevTools screens, i.e. shared functionality and widgetsnew feature
Description
Overview
When you have a add-to-app with multiple flutter engines active at the same time, the devtools takes the first valid isolate and sets it as main, making it impossible to use widget inspector and other tools
Minimal Example App - https://github.com/AshishSingh2001/minimal-add-to-app
Steps to reproduce
- run the android app
cd android_app
./gradlew installDebug- Attach flutter debugger to the dart VM service (you can get this from logcat)
Issue
In the debugger you will always see homeTab and don't have a way to switch to another tab
The widget inspector is build with keeping normal flutter apps in mind, where only one isolate can be the main isolate, but in add-to-app there can be multiple isolates which can render flutter separately

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2important to work on, but not at the top of the work list.important to work on, but not at the top of the work list.add-to-appcross-screenIssues that affect multiple DevTools screens, i.e. shared functionality and widgetsIssues that affect multiple DevTools screens, i.e. shared functionality and widgetsnew feature