Fixed checkForSnapUpdate in updateService.linux.ts to correctly identify snap version #63716
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This issue stems from the following discussion where it appears that the snap build of vscode by snapcrafters was throwing warnings for being outdated.
snapcrafters/vscode#29
Credit to @meddario as he was able to identify exactly the failing function.
The main issue in this case is that product.applicationName is looking for the name 'code', whilst the SNAP is mounted under the name 'vscode'.
Using https://github.com/snapcore/snapd/wiki/Environment-Variables
It seems that the environment variable SNAP is useful for identifying the mount point for the snap.
I have tested the backtick and functionality of the new code under a node shell.
snap connect --run vscode
The code executed as expected.