[SOLVED] Codebase indexing error

After selecting a folder to open and then in settings/features Codebase indexing displays:

TypeError: Cannot read properties of undefined (reading ‘isErr’)

Clicking Retry Index does not solve the problem.
Uninstalled Cursor, deleted folder below does not resolve issue.

AppData\Roaming\Cursor

Windows 10 OS
Cursor 0.45.9

1 Like

same error

5 Likes

did you find a way to fix it? I am getting the same error

same error Version: 0.45.9

i reshuffled my repo then went into “cursor settings” and deleted the index. When i click to compute/retry index, i get this error. I even tried to be slick and kill all processes and rename my folder then open it as a separate workspace, but no dice.

big ole problem

it’s super bizarre. I even created new copy of repo, deleted .git directory, re-initialized brand new repo, different dir names and everything. Still, somehow Cursor is onto the fact this was the problem repo and indexing doesn’t work.

All other repos work just fine

it seems like there is logic that tries to retrieve previous index but there is no handling of the case where previous index doesn’t exist (in sub-case of index existing at one time but later being deleted).

I’m encountering the same issue on Mac.

same error on Xcode project

since we’re at it, “see all included files” function in the cursor-settings->features doesn’t work either (on any repo)

same on 0.45.5 windows 11

Also experiencing this

Version: 0.45.9
VSCode Version: 1.96.2
Commit: cce0110ca40ceb61e76ecea08d24210123895320
Date: 2025-02-02T06:44:49.761Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

having the same issue
Version: 0.45.9

VSCode Version: 1.96.2

Commit: cce0110ca40ceb61e76ecea08d24210123895320

Date: 2025-02-02T06:44:49.761Z (2 days ago)

Electron: 32.2.6

Chromium: 128.0.6613.186

Node.js: 20.18.1

V8: 12.8.374.38-electron.0

OS: Darwin arm64 24.1.0

edit: downgrading to 0.44 and reopening same filebase resolves for me

Thanks all for the reports, escalated this to the Cursor team and they’re looking into it right now.

4 Likes

Hang tight, dev team are on it, issue identified and fix incoming.

5 Likes

Looking good here now, seems like the dev team has turned around a super quick fix. Thanks all for your patience!

7 Likes