Summary
The original device-label regression from #8795 is fixed in Android Studio, but plain IntelliJ can still lose the device suffix in Run/Debug tab titles.
As reported by @blasko here:
I've just tried in Android Studio and it's working on the dev plugin: 92.0.0-dev.20260415-cb14614 (haven't tried stable yet).
I primarily use IntelliJ where the dev plugin worked a couple of week ago, but now fails (not sure if it's related to any IntelliJ updates etc.) - dev plugin: 92.0.0-dev.20260415-cb14614 (both stable and dev versions are not showing the device label).
This appears to be a separate follow-on regression specific to the newer split-debugger path used by IntelliJ.
Symptoms
In IntelliJ, Run/Debug tabs can fall back to the raw run configuration name (for example main.dart) instead of the device-qualified title (for example main.dart (macOS) or main.dart (iPhone 16 Pro)).
Android Studio may still show the expected labels at the same plugin revision.
Root cause
The original February fix in #8796 still works for the older descriptor-mutation path, but a later change for split debugging introduced a second place where the tab title has to be seeded:
FlutterDebugSessionUtils.startSessionAndGetDescriptor() switched newer IntelliJ builds onto XDebuggerManager.newSessionBuilder(), but never configured the builder with:
sessionName(...)showTab(true)contentToReuse(...)
On split-debugger builds, the visible tab title is derived from that builder configuration rather than from the later RunContentDescriptor.setDisplayName() mutation alone. That leaves Android Studio working on the older path while IntelliJ loses the device label.
Proposed fix
Seed the device-qualified tab title into the new session-builder flow before startSession() runs, while keeping the existing RunContentDescriptor.setDisplayName() fallback for the older path.
Related
Summary
The original device-label regression from #8795 is fixed in Android Studio, but plain IntelliJ can still lose the device suffix in Run/Debug tab titles.
As reported by @blasko here:
This appears to be a separate follow-on regression specific to the newer split-debugger path used by IntelliJ.
Symptoms
In IntelliJ, Run/Debug tabs can fall back to the raw run configuration name (for example
main.dart) instead of the device-qualified title (for examplemain.dart (macOS)ormain.dart (iPhone 16 Pro)).Android Studio may still show the expected labels at the same plugin revision.
Root cause
The original February fix in #8796 still works for the older descriptor-mutation path, but a later change for split debugging introduced a second place where the tab title has to be seeded:
76d8e587b3eb622940ce12d164e3c8dbd3d4ede6FlutterDebugSessionUtils.startSessionAndGetDescriptor()switched newer IntelliJ builds ontoXDebuggerManager.newSessionBuilder(), but never configured the builder with:sessionName(...)showTab(true)contentToReuse(...)On split-debugger builds, the visible tab title is derived from that builder configuration rather than from the later
RunContentDescriptor.setDisplayName()mutation alone. That leaves Android Studio working on the older path while IntelliJ loses the device label.Proposed fix
Seed the device-qualified tab title into the new session-builder flow before
startSession()runs, while keeping the existingRunContentDescriptor.setDisplayName()fallback for the older path.Related