You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice the constantly growing list that does not take up the entire vertical space of the left hand side and the gray image on the right hand side after selecting a component.
What do you expect?
I expected the list of components to be usable and the details view to appear as expected.
How can we reproduce this?
Ensure the DevTools extension assets are built. Run melos devtools-build.
Run the examples/ app, and open the Rogue Shooter game.
Open DevTools and switch to the Flame tab.
What steps should take to fix this?
No response
Do have an example of where the bug occurs?
No response
Relevant log output
Exception (minified, so you'll need to repro in debug mode to get a useful stack trace):![Screenshot 2024-08-27 at 3 10 59 PM](https://github.com/user-attachments/assets/4b23d4dc-0300-4d35-aa03-7953723249e8)
Execute in a terminal and put output into the code block below
The gray box issue reproduces on the PadRacing game as well. I just clicked around through the components to reproduce. In this screenshot I have selected the main PadRacingGame component:
What happened?
Notice the constantly growing list that does not take up the entire vertical space of the left hand side and the gray image on the right hand side after selecting a component.
What do you expect?
I expected the list of components to be usable and the details view to appear as expected.
How can we reproduce this?
melos devtools-build
.examples/
app, and open the Rogue Shooter game.What steps should take to fix this?
No response
Do have an example of where the bug occurs?
No response
Relevant log output
Execute in a terminal and put output into the code block below
Output of: flutter --version
Affected platforms
All
Other information
This happened from the tip of the main branch: 981bb34
Are you interested in working on a PR for this?
The text was updated successfully, but these errors were encountered: