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

Flutter Widget Inspector - Not displaying #5237

Open
felix9ia opened this issue Feb 12, 2023 · 11 comments
Open

Flutter Widget Inspector - Not displaying #5237

felix9ia opened this issue Feb 12, 2023 · 11 comments
Assignees
Labels
P3 issues we think are valid but not important

Comments

@felix9ia
Copy link

<-- Please describe your problem here. Be sure to include repro steps. -->


intellij idea info:IntelliJ IDEA 2022.3.2 (Ultimate Edition)
Build #IU-223.8617.56, built on January 26, 2023
Licensed to East China University Of Science And Technology / li meng
Subscription is active until May 10, 2023.
For educational use only.
Runtime version: 17.0.5+1-b653.25 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.1
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 4
Metal Rendering is ON
Registry:
debugger.new.tool.window.layout=true
ide.experimental.ui=true

Kotlin: 223-1.8.0-release-345-IJ8617.56
DevTools version: 2.20.0
Connected Device:
CPU / OS: arm64 (64 bit) ios
Dart Version: 2.18.6
Flutter Version: 3.3.10 / stable
Framework / Engine: 135454af32 / 3316dd8728
Connected app type: Flutter native (debug build)

@CoderDake
Copy link
Contributor

@felix9ia does this issue and solution help your situation?
#5038 (comment)

@felix9ia
Copy link
Author

@felix9ia does this issue and solution help your situation? #5038 (comment)

I can't find that configuration in intellij idea settings: devtool port

I followed that comment and changed the port, but i cant find dart devtool port in intellij idea settings,
i just find
intellij idea - settings - Languages & Framworks - Dart - webdev server port
53322 -> 53321

@jacob314
Copy link
Contributor

Can you attach a screenshot to show what not displaying means. Do you see a blank inspector tree or a completely blank devtools window?

@felix9ia
Copy link
Author

Can you attach a screenshot to show what not displaying means. Do you see a blank inspector tree or a completely blank devtools window?

like this:
image

The page status on the device:
image

@StoyanTinchev
Copy link

StoyanTinchev commented Feb 27, 2023

I have the same problem with IntelliJ. Any solutions?

@CoderDake
Copy link
Contributor

When this occurs, if you click on the settings icon, inside the widget inspector tab, Is there a little spinner spinning for that package directories?

@StoyanTinchev
Copy link

Yes

@StoyanTinchev
Copy link

@CoderDake any suggestions?

@CoderDake
Copy link
Contributor

Hey @StoyanTinchev I have some changes coming through that will hopefully help in generating helpful logs to help determine what is going on here.

When #5404 is merged to the devtools master branch, then we will have our first implementation for debug logging.

When that change is merged could you please do the following to collect some logs, and post them back here?

Instructions

  1. Clone the flutter/devtools repo
  2. checkout the master branch
  3. Change your flutter's channel to master using
    flutter channel master; flutter upgrade
  4. Change to the devtools app directory
    cd devtools/packages/devtools_app
  5. Update the packages
    flutter pub get
  6. Run devtools with
    flutter run -d chrome
  7. Once Devtools opens up you should be able to connect to your app.
  8. Click on the settings at the top right

Screenshot 2023-03-07 at 10 12 42 AM

  1. Enable the verbose logging setting.

  2. Next click the "Clear logs" button beside the "enable verbose logging" setting
    Screenshot 2023-03-15 at 4 15 02 PM

  3. Now go reproduce the behaviour

  4. after reproducing, come back to the settings and click the "Copy logs" button beside the logging setting

  5. ⚠️ check to make sure there is no sensitive information. ⚠️

  6. then you should be able to upload those logs here, hopefully it will help point out what is going wrong.

@StoyanTinchev
Copy link

@CoderDake Please pin me, after the PR is merged. Thank you very much!

@CoderDake
Copy link
Contributor

@StoyanTinchev the first blush of the logging code has been submitted!
If you get a chance feel free to give #5237 (comment) a spin and post back some logs here.
Hopefully it will be a good start to discovering what might be happening :D

@CoderDake CoderDake added the P3 issues we think are valid but not important label Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 issues we think are valid but not important
Projects
None yet
Development

No branches or pull requests

4 participants