vscode-icons: Custom Icon Folder Not Working on Latest VSCode
- I’m sure this issue is not a duplicate.
Platform: Windows 10 Code: Code Insiders
I’ve added the custom folder path at C:\Users\JGrote\AppData\Roaming\Code - Insiders\User\vsicons-custom-icons
and placed file_type_bicep.svg
and added relevant config to vsicons.associations.files
:
{
"icon": "bicep",
"extensions": [
"bicep"
],
"format": "svg",
},
However the icon does not apply after a reload window
:
But if I copy the file directly into the extension directory (C:\Users\JGrote\.vscode-insiders\extensions\vscode-icons-team.vscode-icons-11.1.0\icons
), it works fine:
I also tried a custom path with the extension setting with no luck. I tried adding the folder C:\users\jgrote\.vscode-insiders\vsicons-customicons
and tried several combinations without success:
C:/Users/JGrote/.vscode-insiders
C:\\Users\\JGrote\\.vscode-insiders
(double backslash in the json for escaping, reports correctly in the UI)
<<Above folders with vsicons-customicons appended even though that isn’t what is required per the wiki>>
Everything is on the same drive, no cross-drive boundaries.
Am I missing something here? Any logs to troubleshoot?
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 13
- Comments: 18 (1 by maintainers)
since nobody pointed this out yet i got i working with the vsicons.customIconFolderPath setting
as follows: add a folder “vsicons-custom-icons” in %userprofile%/.vscode/extensions/ add your custom icons there should look like this:
add
"vsicons.customIconFolderPath":"C:/Users/[USER]/.vscode/extensions/",
to your settings.json (change the [USER] part to your user profile)add config for association as usual
Reload Window/ Restart vscode should show up now
i chose the extensions folder since i read on the material icons issue tracker (where they also have problems with custom icons…) that they got it working putting their icons in a subfolder to the vscode extensions folder and since i was trying if that at least worked i came up with doing this here, I don’t know if other custom folder paths work
Edit: @ankurp-meditab pointed out something you might have to do aswell:
I’m seeing a similar issue with latest. For me, I have the custom icon folder set and it attempts to access the (valid) svg icon in the correct path (which I can verify in a browser window), however opening developer mode in vscode shows the file request as
(canceled)
:If I were to hazard a guess, this is like a CORS issue, but I’m not certain since I am unfamiliar with how to further drill down on this issue.
Please let me know if this looks like the same issue and, if not, I’ll migrate it to one of its own.
@AlexisDot The only missing thing in your workaround for me was to run the command (ctrl + Shift + P) >icons: Apply Icons Customization. After running the command it started working. Thank you very much for the workaround.
same problem here. VSCode 1.54.3 vscode-icons version 11.2.0
@robertohuertasm I tried:
C:\Users\latif\.vscode\extensions\vscode-icons-team.vscode-icons-11.4.0\icons
vsicons-custom-icons
to extension icons folderBoth of them didn’t work, the custom icons not showing, the integrity is compromised.
Then tried to move custom icons folder
vsicons-custom-icons
toC:\Users\latif\.vscode
and edit the settings:no integrity warning, but still cancelled, the custom icons not showing.
Additional info for VSCode version:
Info for extension:
Run on WSL and local has same behavior for me.
Thank you.
@ankurp-meditab Added it to my post so others don’t need to look for that particular bit
@AlexisDot Thanks, it worked.
Same problem here. VSCode version 1.54.3 vscode-icons version 11.2.0
After reinstalling VScode because it complained about my install being corrupt i ran into this same issue, non-insider version on my end so it actually seems like a problem with latest VScode in general,
my folders persisted from the previous install where it still worked
#2719 seems to be the same problem
@JustinGrote might change the title back since it’s not only insider specific?
FWIW, I am having the same issue in the latest VS Code (non-insiders) and no custom folder - with the same
(canceled)
statusSettings