Go to definition does not work in SPM project which builds no problem

[rssole]

Hi, I am trying to figure out what is wrong, I have last versions (ATM) of both VS Code and Sweetpad.

Schemes are disovered properly and none of scheme is missing,
the scheme I am working with builds from Sweetpad no problem
(I didn't build ALL schemes from SPM package project tho).

Still, "go to definition" does not work for me, and that is really showstopper for me as
better navigation and superior code editing features to XCode are only reasons
why I am making effort to make this work.

Xcode build server config is present in root alongside Package.swift.

Any advice/help on what I might be doing wrong is very welcome.

Thanks

[opi-smccoole]

I'm having this exact same problem myself. I've tried setting up my base project definition at every level but the "go to" functionality still seems to only recognize code within the main app target itself and ignores any code in local SPMs. It can find by name (command-P) and as the OP mentioned, the project builds and runs just fine with SweetPad. I too find this to be a show stopper for me as I lean heavily on "go to" functionality in the large codebases I typically work in.