custom Equalizer "cannot read properties of undefined (reading 'map')"

[badr49]

Platform:
debian 12
Nuclear version:
0.6.48
Description of the issue:
just installed nuclear, went to the equalizer view, once i clicked the custom preset got an error "cannot read properties of undefined (reading 'map')", got redirected to the dashboard and now trying to go to the equalizer tab again, instantly triggers the same error. I even purged and re installed, I still cannot access the equalizer view

[nukeop]

Can you post your settings json here? Should be in ~/.config/nuclear.

[badr49]

i am so sorry, i literally just removed the config folder using 'rm -rf ~/.config/nuclear', and now i can go to the equalizer view. i will try to re create this issue, and share the json settings

[nukeop]

Yeah that's another way to fix it too. There must have been something wrong withthe settings.

[badr49]

so, i managed to recreate the issue, this is the console output:
[22215:0726/004731.121556:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[22215:0726/004956.791398:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
renderer › Cannot read properties of undefined (reading 'map')
ipc api › ==> ELECTRON_NUCLEAR_LOGGER_ERROR: Array
ipc api › ==> restore
renderer › Cannot read properties of undefined (reading 'map')
ipc api › ==> ELECTRON_NUCLEAR_LOGGER_ERROR: Array
ipc api › ==> restore
renderer › Cannot read properties of undefined (reading 'map')
ipc api › ==> ELECTRON_NUCLEAR_LOGGER_ERROR: Array
ipc api › ==> restore
and here is my json settings (literally vanilla other than the equalizer option):
{
"lastFm": {},
"settings": {
"invidious.url": "https://invidious.snopyta.org",
"language": "en-US",
"userId": "d85f4678-41d1-4940-a088-ddf1fef62c4f"
},
"playLists": [],
"favorites": {
"tracks": [],
"artists": [],
"albums": []
},
"downloads": [],
"equalizer": {
"custom": {
"label": "custom",
"id": "custom"
},
"selected": "custom",
"enableSpectrum": false
},
"last-thumb-clean-date": 1753487243951,
"nuclear": {
"identity": {}
},
"plugin": {
"selected": {
"metaProviders": "Spotify Metadata Provider",
"streamProviders": "Youtube",
"lyricsProviders": "Simple Lyrics Provider"
}
}

[badr49]

i can see that the intended implementation was for the user to actually try to change the band for a frequency, which will set the preset to custom, and will have additional 'values' and 'preAmp' preperties (they are missing on the config.json i sent you). when, i straight up clicked custom preset without touching any frequency band. those 2 properties werent added, which explains the error, could map on missing properties. i feel like initializing values and preamp properties would fix it