Chia-Network / chia-blockchain-gui

Chia blockchain GUI in electron/react

Home Page:https://chia.net

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Cannot read properties of undefined (reading 'walletKeyTheme')

ChiaMasters opened this issue · comments

What happened?

Error: Cannot read properties of undefined (reading 'walletKeyTheme')
at webpack://@chia-network/gui/src/components/addressbook/MyContact.tsx:41:51 walletKeyTheme
at webpack://@chia-network/gui/src/components/addressbook/MyContact.tsx:39:17 forEach
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:262:358 fk
at webpack://node_modules/scheduler/cjs/scheduler.production.min.js:18:342 unstable_next
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:122:324 eg
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:261:307 ek
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:261:214 ek
at webpack://node_modules/scheduler/cjs/scheduler.production.min.js:16:223 V
at webpack://node_modules/scheduler/cjs/scheduler.production.min.js:12:345 k

Version

2.0.0

What platform are you using?

Windows

What ui mode are you using?

GUI

Relevant log output or stacktrace

Cannot read properties of undefined (reading 'walletKeyTheme')

URL
#/dashboard/addressbook

Stacktrace
at webpack://@chia-network/gui/src/components/addressbook/MyContact.tsx:41:51 walletKeyTheme
at webpack://@chia-network/gui/src/components/addressbook/MyContact.tsx:39:17 forEach
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:262:358 fk
at webpack://node_modules/scheduler/cjs/scheduler.production.min.js:18:342 unstable_next
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:122:324 eg
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:261:307 ek
at webpack://node_modules/react-dom/cjs/react-dom.production.min.js:261:214 ek
at webpack://node_modules/scheduler/cjs/scheduler.production.min.js:16:223 V
at webpack://node_modules/scheduler/cjs/scheduler.production.min.js:12:345 k
commented

This was fixed in the 2.1.0 release.