devtools can only access the first created engine when you have multiple engines in add to app
- Lenguaje dominante
- Dart
- Estrellas
- 1.7k
- Forks
- 404
- Merge medio
- 6 d 17 h
- PR fusionados (30 d)
- 18
Descripción
# 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
```bash
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
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.