Widget inspector doest jump to source code

[YaserH25]

Hello
After i upgraded to Flutter 3.13, widget inspector stopped jumping to source code, i tried a new projects and still having the same issue

---

DevTools version: 2.25.0
Connected Device:
CPU / OS: arm64 (64 bit) android
Dart Version: 3.1.0
Flutter Version: 3.13.0 / stable
Framework / Engine: efbf63d9c6 / 1ac611c64e
Connected app type: Flutter native (debug build)

[kenzieschmoll]

FYI @CoderDake @DanTup

@YaserH25 are you using VS Code? If so, what version of the Dart Code extension are you using?

[YaserH25]

Im using Android Studio

[YaserH25]

FYI @CoderDake @DanTup

@YaserH25 are you using VS Code? If so, what version of the Dart Code extension are you using?

it does work on VS code

[kenzieschmoll]

@helin24 jump to source broken in Android Studio. I'm going to transfer this issue to the flutter-intellij repo.

[xkeyC]

+1
Flutter (Channel stable, 3.13.0, on macOS 13.5 22G74 darwin-arm64, locale zh-Hans-CN)

Android Studio Giraffe | 2022.3.1
Build #AI-223.8836.35.2231.10406996, built on June 29, 2023

Flutter intellij 75.1.2 Aug 04, 2023

But It work in Flutter (Channel stable, 3.10.6 )

[CoderDake]

@redfieldchristabel and @satishs22 have also reported this behaviour back in the DevTools repo: flutter/devtools#6222

[itsJoKr]

This was working before. I had an update yesterday to Inspector ("What's new" was shown) and since then it doesn't work. (using IntelliJ idea).

[redfieldchristabel]

@CoderDake hi there, i upgrade to flutter latest version again today. the problem still presist .

[helin24]

An upcoming change to the plugin will fix this, but in the current plugin, you will need to revert to an older Flutter SDK version (works for me on 3.7.0). Sorry about the inconvenience!

[Maslan34]

ı had same issue. Downgrading flutter to 3.10.5 version also worked for me.

[Pisey-Nguon]

I had the same issue on Flutter version 3.13.6

[muhsinzyne]

is there any fixes for this ??

[muhsinzyne]

I am also facing the same issue. when i revert back to flutter version 3.10.2 it's working but during the time i am having error while i run debug mode in ios physical devise

Could not run build/ios/iphoneos/myapp.app on 00008101-XXXXXXX.
Try launching Xcode and selecting "Product > Run" to fix the problem:
open ios/Runner.xcworkspace

Error launching application on xxxx's iPhone.

[redfieldchristabel]

An upcoming change to the plugin will fix this, but in the current plugin, you will need to revert to an older Flutter SDK version (works for me on 3.7.0). Sorry about the inconvenience!

its been a month, dart tool also fail on android studio, sometimes i need to rerun with vscode just to use this feature. please fix it it really needed feature and with this feature i can flex with other stack developer at my office but now i cant hahaha.

[kenzieschmoll]

An upcoming change to the plugin will fix this, but in the current plugin, you will need to revert to an older Flutter SDK version (works for me on 3.7.0). Sorry about the inconvenience!

@helin24 @jwren has the new plugin version with the fix been released?

[xkeyC]

There is still no new version to fix this problem:https://plugins.jetbrains.com/plugin/9212-flutter/versions

It's been almost two months since the issue was reported, and it's hard not to wonder if flutter-intellij has been forgotten.

Before releasing a new version, we may need to manually compile and install: https://github.com/flutter/flutter-intellij/tree/master/tool/plugin

[kenzieschmoll]

@jwren and @helin24 are actively working on getting this plugin rolled out. We appreciate your patience. In the meantime, consider using VS Code to unblock your immediate Flutter Inspector needs.

[CoderDake]

Just to close the loop, there are a couple of ways that one could get this working until a new release is made.

You could try any of the following based on your needs:

1. Use VSCode (it is actively supported for Dart/Flutter Development)
2. Keep Flutter SDK under 3.7.0 until an intellij plugin release can occur
3. Do a Dev build of the intellij plugin so you can get the new fix. See the instructions in this comment

[muhsinzyne]

@jwren and @helin24 are actively working on getting this plugin rolled out. We appreciate your patience. In the meantime, consider using VS Code to unblock your immediate Flutter Inspector needs.

please when i can expect this to be available ?

[jwren]

@muhsinzyne I am currently manually testing a new roll of the Flutter plugin to be released as early as this upcoming Monday.

[muhsinzyne]

@muhsinzyne I am currently manually testing a new roll of the Flutter plugin to be released as early as this upcoming Monday.

happy to hear... waiting for the rollout....

[muhsinzyne]

is this issues fixed ???

[muhsinzyne]

@muhsinzyne I am currently manually testing a new roll of the Flutter plugin to be released as early as this upcoming Monday.

Hi @jwren could you please update me the status i was searching for a new plugin support to resolve this issue. but as i can see that no plugin updates till now.. if you are in the testphase, could you please provide me the beta version or any early access options. as i am really stuck due to this and it's very hard to switch my IDE...

[jwren]

@muhsinzyne I uploaded a new version before you posted this 5 hours ago. See https://plugins.jetbrains.com/plugin/9212-flutter/versions/stable/423005. I am not sure why it isn't updating in the IDEs yet. (No downloads yet for the new versions.)

[DanTup]

FWIW the new version shows for me in Android Studio on Windows

[jwren]

Thanks Danny.

all-- Do let me know if this issue is not resolved in this release.

[satishs22]

im getting this message, any idea how to solve this?

[sarope]

@jwren also getting the same error as @satishs22 above. The link to open in the browser works as expected though

[Hactieuho]

@satishs22 @sarope

• If you face the error The JxBrowser license could not be found, please open Android Studio's setting -> Language & Framework -> Flutter -> Scroll down and check Use JCEF browser to show embedded DevTools:
  

• And choose JCEF boot runtime:

1. Select Help > Find Action from the Android Studio menu.
2. Enter "Choose Boot Java Runtime for the IDE" and select it from the suggestion list.
3. Select the runtime that comes with JCEF support as shown in the image below:
   

https://stackoverflow.com/questions/69171807/markdown-editor-and-preview-not-working-in-android-studio

[satishs22]

@Hactieuho thanks, after following the steps mentioned, i'm able to use the flutter inspector now

[muhsinzyne]

hey still the fix does not did any value addition to the developer as instead of jumping the code to layout it' goes to the directory or library view files. it should be the screen as per my understanding and my previous experience. now the jump to souce code is working like overperfromed till the basic flutter layout libraries.

[muhsinzyne]

hey still the fix does not did any value addition to the developer as instead of jumping the code to layout it' goes to the directory or library view files. it should be the screen as per my understanding and my previous experience. now the jump to souce code is working like overperfromed till the basic flutter layout libraries.

i tried with both newest android studio version as well as Flamingo

[rayliverified]

Is there a way to disable this behavior? The "jump to source code" is not desired for me and makes DevTools almost unusable for my use case of inspecting the widget tree.

Feel free to mark as off topic.

[TheMaverickProgrammer]

Is there a way to disable this behavior? The "jump to source code" is not desired for me and makes DevTools almost unusable for my use case of inspecting the widget tree.

Feel free to mark as off topic.

Did you ever find a solution for this? We're having the same issue when we only have one monitor available at a time.

[rayliverified]

Unfortunately not, it's infuriating because you lose the widget your inspecting if you click somewhere else in your code.

[TheMaverickProgrammer]

Unfortunately not, it's infuriating because you lose the widget your inspecting if you click somewhere else in your code.

We completely agree. Often times we just want to look at the widget highlighting in our app next to the widget tree docked on the right side of the screen. When our editor jumps to the code, it dominates the layout and we can no longer read the widget tree.