🐞 white screen on collection variables

[josh-i386g]

When I go to collection settings -> eye variables I get a white screen

electron : 21.1.1
chrome : 106.0.5249.103
node : 16.16.0
v8 : 10.6.194.17-electron.0

[Its-treason]

Looks like the problem I encountered a few days ago during testing. I already fixed it on my fork. I'll open a PR for this in the evening.

[timwhite]

More debugging in #1968 for what appears to be the same issue

[mig8447]

-1711824312867.log

Adding log. Experiencing the exact same issue

[DanaEpp]

I am seeing this behavior as well with Bruno v1.12.3 on MacOS Sonoma 14.4.1.

My only option is to force quit the app to recover.

Stacktrace error:

TypeError: n.map is not a function
    at KeyValueExplorer (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/951-d020733b4cdea97a.js:1:181742)
    at Xh (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:60991)
    at x (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:119446)
    at Vk (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:99131)
    at file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:98998
    at Jk (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:99005)
    at Ok (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:95761)
    at Fk (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:96150)
    at jg (file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:44900)
    at file:///Applications/Bruno.app/Contents/Resources/app.asar/web/_next/static/chunks/framework-80ea8c0f440c6a32.js:9:93662

[end3rbyte]

Same bug here, here is the stack trace

[helloanoop]

Thanks for the PR @Its-treason !

Issue has been fixed.
This will go out in the 1.13.0 release. Please subscribe to Discord announcement channel to stay notified on the releases.