JetBrains / JetBrains/intellij-streamdeck-plugin
Property Inspector UI shows empty fields for Run/Debug configuration after plugin update
- Dominant language
- Java
- Stars
- 64
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
## Description
After updating the JetBrains IDE Stream Deck plugin, the **Property Inspector panel shows all configuration fields empty**, even though the actions still work correctly (they execute the right Run/Debug configuration).
## Steps to reproduce
1. Have an existing Stream Deck profile with **Run** or **Debug** actions configured (e.g. with a Run/Debug Configuration Name set to `DEV`, `LOCAL`, etc.)
2. Update the JetBrains IDE Stream Deck plugin to the latest version
3. Open the Stream Deck app and click on any of the previously configured Run/Debug buttons
4. Observe the Property Inspector panel on the right side
## Expected behavior
The Property Inspector should display the previously saved Run/Debug Configuration Name in the corresponding field.
## Actual behavior
All fields in the Property Inspector appear **empty**, but the action still executes correctly (it launches the correct Run/Debug configuration in IntelliJ).
## Root cause analysis
Inspecting the plugin files, the issue appears to be a mismatch between:
- `idea-plugin-bundle.js` → reads the settings key **`runConfig`** (used to execute the action)
- `idea-property-inspector-bundle.js` → references both `run_config` and `run_config_name` internally, but the HTML element has `id="run_config_name"`
The saved settings in the profile `manifest.json` use `runConfig` (the old key), but the Property Inspector UI no longer correctly reads/maps this field for display purposes, resulting in empty fields.
## Environment
- **OS:** macOS
- **Stream Deck software version:** v6 (ProfilesV3 format)
- **Plugin version:** 1.0.5.0 (`com.jetbrains.ide`)
- **IntelliJ IDEA version:** IntelliJ IDEA Ultimate
## Workaround
None available without losing the saved configuration. The actions continue to work but cannot be edited through the UI.
Contributor guide
Assessment
This issue has not been assessed yet.