vscode icon indicating copy to clipboard operation
vscode copied to clipboard

Import Profile feature does not finishes the process (looping)

Open alefragnani opened this issue 10 months ago • 5 comments

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.97.0
  • OS Version: macOS Sequoia

Hi,

I was organizing my profiles, between Stable and Insiders release installations, and when I tried to import one to another, the Import process wasn't actually finishing, resulting in an loop experience.

Steps to Reproduce:

  1. Export a profile from VS Code Insiders
  2. Import a profile to VS Code
  3. Click Create
  4. You can see the progress / toast saying it is installing extensions...
  5. The progress / toast finishes
  6. The Create button remains enabled and the unsaved profile indicators also remains there.
Image
  1. Click to close the profile and a modal window (to save profile changes) is show, even without changing anything after importing the profile
Image
  1. Click save
  2. The same progress / toast appears, installing extensions for the profile
  3. The progress / toast finishes
  4. But the Create button remains
  5. You notice the loopI have tried the same process a few times, closing and reopening VS Code, and at some time, the profile appeared, even without the saving/importing process finishing with success

Thanks in advance

alefragnani avatar Feb 09 '25 19:02 alefragnani

Stuck on the same problem. This makes it impossible to synchronize configuration between vscode on different machines.

v0y4g3r avatar Mar 21 '25 03:03 v0y4g3r

Same issue when trying to sync my extensions on a new machine. VSCode version: 1.98.2 (universal) Mac OSx: Sonoma 14.7.4

Aleal2 avatar Mar 25 '25 23:03 Aleal2

Same problem here. Version 1.99.0 on Sequoia 15.3.2 (arm64). Also experienced it on Debian 12 aarch64.

Edit: This is pretty clearly a problem with one or more extensions, as the import works if I switch extensions to "Default" or "None". But since there's no error reporting or logging (that I could find), and no way to cherry pick which extensions you want to pull in from the imported file, figuring out which extensions are problematic won't be simple.

Edit2: For what it's worth, a most-recent version of code-server imported the same profile without complaint or looping. (I was sort of hoping for it to fail and log the problem to the console.)

ptous avatar Apr 07 '25 15:04 ptous

Is there an update on the bug? I'm having the same issue on VS Code 1.100.2 and Windows 11 24H2. I think the import profile from file method fails if the profile contains VS code extensions that are not compatible with the current version of VS Code. I think the behavior should be that an error message pops up and says which extensions are incompatible. Right now, the import fails silently.

williamchiu-nmic avatar May 21 '25 20:05 williamchiu-nmic

My solution was to open the list of extensions on the profile and installing each one manually from the extensions tab. After that the import worked for me.

Aleal2 avatar May 22 '25 01:05 Aleal2

I just had this problem. Happy to provide failing config for someone to test.

eleqtrizit avatar Nov 24 '25 19:11 eleqtrizit