[error] Error: Config Not Found. (file: <filename>) lists the file being sent not the config file

[cliff-in-auld-reekie]

Do you read the FAQ?

• Yes. And I looked thru' issues for any duplicate.

Describe the bug
When I try to upload I get an error and that's fine as I'm setting up new targets. However, the stated filename is not the config file SFTP can't find but the file I'm trying to upload.
That's a tad useless as I know what I'm trying to upload but I don't know which config file(s) it is looking for or where exactly it is looking.

To Reproduce
Right click, Upload file

Expected behaviour
The error message stating the name and location of the config file(s) it is not finding.

Screenshots
Wouldn't really help

Desktop (please complete the following information):

• OS: MacOS Sequoia 15.1
• VSCode Version Version: 1.95.1
• Extension Version v1.16.3

Extension Logs from Startup - required
[11-07 12:14:10] [trace] run command 'Upload File'
[11-07 12:14:10] [error] Error: Config Not Found. (file:///Users/cliffwallace/Desktop/_VSCode/rpi/MagicMirror/docs/install.text)
at Object.l (/Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:296202)
at t.default. (/Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:221424)
at Generator.next (:null:null)
at /Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:220593
at new Promise (:null:null)
at n (/Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:220338)
at /Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:221365
at Array.map (:null:null)
at t.default. (/Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:221357)
at Generator.next (:null:null)
at s (/Users/cliffwallace/.vscode/extensions/natizyskunk.sftp-1.16.3/dist/extension.js:2:220395)

[MHagood]

Possibly related, albeit on a Windows machine: I receive this exact error when I try to deploy using a network share, SMB or otherwise. As a control, I temporarily moved my entire vs code project onto my local disk to re-attempt deployment with the exact same config; it worked fine.

My consistent workaround while continuing to use network shares is to deploy manually via right-clicking my solution's root folder: Sync Local -> Remote. For some reason, that works fine even on a remote share.

I was looking around these forums for a network share related issues but couldn't find one. If your issue turns out to be unrelated, sorry to waste your time and I'll open a separate issue later.

Here's my config for reference. I use a UN:PW auth method since I couldn't get password-based PKI to work with this tool for the life of me:

{
	"name": "some_site",
	"host": "192.168.0.30",
	"context": "W:/Source/Sites",
	"protocol": "sftp",
	"username": "deployment",
	"password": "super_secret",
	"remotePath": "/var/www",
	"syncOption": {
		"update": true,
		"delete": true
	},
	"uploadOnSave": false
}

uploadOnSave: false disables the broken auto-save logic
syncOption: {} helps keep the destination dir clean as I rename my deployment files trillions of times

[gsabater]

@cliff-in-auld-reekie and @MHagood

I've encountered an unusual situation:

• When opening the folder using Project Manager or similar tools, the upload on save action fails with a configuration not found error.
• However, when opening the folder directly using VS Code's built-in "Open Folder" option, the upload on save works correctly.

Try it out and let me know if it also works for you.