flutter / flutter/devtools

devtools can only access the first created engine when you have multiple engines in add to app

Open
#9,668 2 comments 2 reactions 0 assignees View on GitHub
add-to-app cross-screen new feature P2
Dominant language
Dart
Stars
1.7k
Forks
404
Avg merge
6d 17h
Merged PRs (30d)
18

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
```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

Image

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.