neodisk17/vscode-ext-flutter-color-viewer

Keeps outputting error message: trying to get `color` from undefined object

Closed this issue · 6 comments

lethefrost commented

It outputs the following messages to the output - extension host channel almost every second:

(v1.2.3 updated on Apr. 20, macOS Sonoma 14.4.1, VSC 1.88.1)

[error] [circlecodesolution.ccs-flutter-color] provider FAILED
[error] TypeError: Cannot read properties of undefined (reading 'color')
    at t.default.provideDocumentColors (/Users/username/.vscode/extensions/circlecodesolution.ccs-flutter-color-1.2.3/dist/extension.js:2:1379)
    at se.provideColors (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:152:113994)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:152:130551
    at Re.s (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:152:118853)
    at Re.$provideDocumentColors (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:152:130539)
    at u.S (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:149:5502)
    at u.Q (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:149:5268)
    at u.M (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:149:4323)
    at u.L (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:149:3440)
    at o.value (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:149:2227)
    at s.y (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:82:659)
    at s.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:82:876)
    at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:14173)
    at o.value (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:175:8018)
    at s.y (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:82:659)
    at s.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:82:876)
    at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:14173)
    at MessagePortMain.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:175:6298)
    at MessagePortMain.emit (node:events:517:28)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2285)
    at Object.callbackTrampoline (node:internal/async_hooks:130:17)
neodisk17 commented

Hi @lethefrost , Could you share the file that's causing the error? It would make debugging easier.

lethefrost commented

Hi @lethefrost , Could you share the file that's causing the error? It would make debugging easier.

Thank you for the quick response! I'd like to help, but it literally happens to every window, even with no files or workspace open, so I don't think it's related to any specific file. And I just double-checked in different windows, the output messages are all the same (the lines and files in the stack trace).

You could just open the output pane, and select either Extension Host channel or Window channel, you'll be able to see the messages.

  • 👍1
neodisk17 commented

Hi @lethefrost , thanks for the details.
After checking, it seems like this issue is happening from v1.2.0, I will check the cause of it and try to fix that as soon as possible

  • ❤️1
lethefrost commented

Hi @lethefrost , thanks for the details. After checking, it seems like this issue is happening from v1.2.0, I will check the cause of it and try to fix that as soon as possible

Thank you! I'd like to express my gratitude to your work. I've been using it for years, and it did help me a lot! Looking forward to a fix.

  • ❤️1
neodisk17 commented

Hi @lethefrost , this issue has been fixed.
To support this package, please consider giving a star rating on the following platforms:

GitHub
Visual Studio Code Marketplace
Open VSX

Thank you! 🌟

  • 👍1
lethefrost commented

Hi @lethefrost , this issue has been fixed.
To support this package, please consider giving a star rating on the following platforms:

GitHub
Visual Studio Code Marketplace
Open VSX

Thank you! 🌟

Thank you! 🎉 I actually had already left 5 stars.

  • ❤️1