CRITICAL BUG: Broken Path Resolution & Inconsistent Indexing on macOS M1 (Premium User)

[kaspy003]

Hello,

I am a Premium user experiencing critical failures with Intelephense on macOS (Apple Silicon M1 Max). I have spent hours troubleshooting this with a clean environment, and the extension is currently unusable for navigation.

The Issues:

Broken Path Resolution (Main Issue): Navigation via include/require or Cmd+Click on filenames fails completely, regardless of project location.

I am using standard definitions like define('ROOT', DIR) or const ROOT = DIR.

The extension identifies the ROOT constant but fails to resolve the concatenated path (e.g., include ROOT . '/file.php').

Result: I cannot navigate my project. I was forced to install a third-party extension ("PHP File Link" by pwarchol) just to get basic file linking working. A Premium PHP extension should handle this natively.

Inconsistent Indexing (Dropbox vs Desktop):

On Dropbox (File Provider API): The indexer aborts after ~1 second, finding only ~2000 files out of 5000. It seems unable to read files correctly via the macOS File Provider.

On Desktop (Local SSD): The indexer finds all ~5000 files, BUT still finishes suspiciously fast (2-3 seconds) and fails to provide path navigation as described in Issue #1.

Environment:

Hardware: Mac Studio M1 Max / MacBook Pro M1 Pro

OS: macOS Sequoia

Editor: VS Code (Antigravity build)

Troubleshooting tried:

Full reinstall of extension.

Cleared workspaceStorage cache multiple times.

Tested intelephense.environment.includePaths with various configs (., ${workspaceFolder}).

Changed intelephense.runtime to system Node (v24).

Conclusion: The extension seems fundamentally broken on this architecture regarding path parsing and file system access. I should not need to rely on 3rd party regex-based plugins to open files in a paid PHP extension.

Please investigate path resolution logic on Apple Silicon.

[bmewburn]

The extension identifies the ROOT constant but fails to resolve the concatenated path (e.g., include ROOT . '/file.php').

It should do this but it will not return a result if the file is not indexed. Which I presume is the underlying problem here.

On Dropbox (File Provider API): The indexer aborts after ~1 second, finding only ~2000 files out of 5000. It seems unable to read files correctly via the macOS File Provider.

I'm not familiar with macOS file provider. Does it work on some OS level that enables the Nodejs fs module to read the file as if it was local? If it requires a custom solution to interact with an apple api then there are no plans to support this.

On Desktop (Local SSD): The indexer finds all ~5000 files, BUT still finishes suspiciously fast (2-3 seconds) and fails to provide path navigation as described in Issue #1.

Check the output panel for any warnings about file sizes being too large and set intelephense.files.maxSize accordingly. Also see below if you reference files that are external to the workspace folder.

Tested intelephense.environment.includePaths with various configs (., ${workspaceFolder}).

This setting accepts absolute paths or paths relative to the workspace folder that is open in vscode. It will not expand vscode or environment variables. If the workspace folder does not contain the full project code then you must add the dependency paths to this setting so the indexer scans these folders. Does this help?

Could you give an example of your project structure so I can investigate further?