-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solution: Cannot read properties of undefined (reading 'split') #838
Comments
Reload fixed mine, not sure why VSCode didn't let me know. |
Exact the same. I suggest adding some way to let the user know they have to update the extension, like using a vscode notification |
Same issue |
Reload and relogin does not fix this for me |
1 similar comment
Reload and relogin does not fix this for me |
Sorry, my bad, it works after plugin update |
I am on VS code insiders and copilot pre release , still getting this error again and again |
I didn't reload vscode, but it works when I open a new copilot chat session. |
Just use the "+" button to open a new window to fix this issue, I'm guessing this is due to old chat format not working with the new code. |
Duplicate of #796 (comment) Related on Stack Overflow: Cannot read properties of undefined (reading 'split') with VSCode Copilot |
Users on older versions of Copilot Chat see an increased number of chat messages failing with
Cannot read properties of undefined (reading 'split')
. If your error traces show github.copilot-chat-0.11.1 you are NOT on the latest version.Double-check you have VS Code 1.86 and Copilot Chat 0.12 and there are no blue notification dots for Restart to update!
Update your VS Code (Command: Check for Updates...) + Copilot Chat extension (Command: Extensions: Update All Extensions). Close and re-open VS Code just to make sure, as this applies any pending updates.
Common update blockers:
extensions.autoCheckUpdates
andupdate.mode
If you can't update, please share what blocks you from updating here so we can better understand and improve this process in the future.
The text was updated successfully, but these errors were encountered: