mirror of
https://github.com/VSCodium/vscodium.git
synced 2026-02-04 03:51:16 -06:00
VSCodium installation creates Microsoft/DeveloperTools/deviceid file in ~/Library/Application\ Support (macOS) #296
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cspence001 on GitHub.
Describe the bug
Upon installation of VSCodium - a Microsoft directory is created in ~/Library/Application\ Support, with a unique deviceid file.
Please confirm that the issue/resolution isn't already documented
To Reproduce
Steps to reproduce the behavior:
open -a Finder ~/Library/Application\ Support/Microsoft/DeveloperTools/deviceidor
cat ~/Library/Application\ Support/Microsoft/DeveloperTools/deviceidExpected behavior
Considering VSCodium's intent to remove Microsoft's telemetry, the creation of a Microsoft directory with a unique device ID in ~/Library/Application Support/Microsoft/DeveloperTools/deviceid on macOS for VSCodium is an unexpected behavior.
Desktop (please complete the following information):
Additional context
@daiyam commented on GitHub:
Mine was created on the 4th June but maybe by VSCode.
Updating VSCodium or restarting it don't regenerate the file.
Updating VSCode or restarting it don't regenerate the file.
The package
@vscode/deviceidand the functiongetdevDeviceId()are responsible for creating the file.@cspence001 commented on GitHub:
Yes I have seen this, as well as citation to its use-case as a developer telemetry API . This is where the ms node creates the dir @vscode-deviceid/src/storage.ts. The package looks to be relatively new within the last 2-3 months.
Notes:
"telemetry.machineId": "$IDval",
"telemetry.devDeviceId": "$IDval"
@github-actions[bot] commented on GitHub:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@github-actions[bot] commented on GitHub:
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.