Plugin compatibility state not restored after JetBrains Toolbox rollback of failed Android Studio upgrade

Answer to the Question

After a Toolbox rollback of a failed Android Studio upgrade, the IDE binary is replaced with the previous version, but the user configuration directory (where plugin enable/disable flags and plugin‑specific settings live) is left untouched. Consequently, any plugins that were automatically disabled during the failed upgrade remain disabled after the rollback, and their configuration files stay in the same state they had before the rollback.

Why the config directory isn’t rolled back

• Toolbox only rewrites the AndroidStudio/bin and lib directories.
• All per‑user settings live in ~/.config/Google/AndroidStudio (Linux/macOS) or %APPDATA%\Google\AndroidStudio (Windows).
• Plugin enable/disable flags are stored in disabled_plugins.txt, and each plugin’s XML config lives under plugins/ inside that config directory.

Safe Recovery Procedure (no loss of customizations)

1. Backup the config directory first. cp -r ~/.config/Google/AndroidStudio2024.1 ~/.config/Google/AndroidStudio2024.1.bak (Linux/macOS) or copy the folder in Explorer (Windows).
2. Launch the rolled‑back Android Studio.
3. When the Import Settings dialog appears, click Skip or Do not import – it only offers to import from other IDEs or older major versions, not from the current config.
4. Open Settings → Plugins → Installed and re‑enable any plugins that were disabled during the failed upgrade.
5. Restart the IDE to make sure the changes persist. Verify that the plugin’s disabled_plugins.txt entry has been removed.
6. If a specific plugin’s configuration is suspected to be corrupted, delete only its subdirectory, e.g. rm -r ~/.config/Google/AndroidStudio2024.1/plugins/flutter (Linux/macOS) or rmdir /s /q %APPDATA%\Google\AndroidStudio2024.1\plugins\flutter (Windows). The IDE will recreate the folder with default settings on next launch.

What to Avoid

• Deleting the entire config directory unless you have exported all custom keymaps, inspection profiles, and UI preferences via File → Manage IDE Settings → Export Settings.
• Choosing Reinstall in Toolbox if you want to keep your customizations; Reinstall removes the config directory, whereas Rollback preserves it.

Verification Checklist

• Check that disabled_plugins.txt still lists the previously disabled plugins after rollback.
• Confirm that plugins/ directories exist and are unchanged.
• After re‑enabling, restart and ensure the plugin appears as enabled in the Plugins list.

Missing Diagnostic Detail

Could you tell me which plugins were disabled during the failed upgrade? Knowing the exact plugin IDs helps confirm whether the config files were indeed preserved or if they need targeted deletion.