Zagrios
[BUG] : TypeError crash while attempting to browse Beatsaver maps
Issue encountered
OS: Linux (Arch btw) BSM: v1.5.3 Flatpak
Clicking "Browse Maps" to download from BeatSaver crashes the app. This crash will occur both when accessing from the main maps menu and the maps tab in each downloaded version
The app hangs for about a second here...
... before the app crashes. Terminal reads:
$ flatpak run io.bsmanager.bsmanager
[3 zypak-helper] Wait found events, but sd-event found none
[3:0619/195841.733248:ERROR:bus.cc(408)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
19:58:41.969 › configureProxy: Unsupported platform
[3:0619/195842.001900:ERROR:bus.cc(408)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0619/195842.001952:ERROR:bus.cc(408)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
LaunchProcess: failed to execvp:
xdg-settings
19:58:42.166 › Downloaded SongDetailCache file from source: https://raw.githubusercontent.com/Zagrios/beat-saber-scraped-maps/master/song_details_cache_v1.gz ETAG: "4ef73810bb150f2f907ceee780300bb2f26618c4727f3f1f44beea490321feef" 304
19:58:42.172 › SongDetailsCache downloaded
...
9:58:44.671 › Getting mod manifest /home/liam/.local/share/Steam/steamapps/common/Beat Saber/Libs/protobuf-net.dll
19:58:44.671 › Getting mod manifest /home/liam/.local/share/Steam/steamapps/common/Beat Saber/Libs/Native/LookupID.dll
[52:0619/195846.014982:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[52:0619/195848.911458:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
19:58:59.181 › Failed to get JSON from URL: https://api.beatsaver.com/search/text/0?sortOrder=Relevance&leaderboard=All RequestError:
at ClientRequest.<anonymous> (/app/lib/io.bsmanager.bsmanager/resources/app.asar/dist/main/main.js:14:1633692)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:530:35)
at ClientRequest.emit (node:domain:489:12)
at emitErrorEvent (node:_http_client:104:11)
at TLSSocket.socketErrorListener (node:_http_client:518:5)
at TLSSocket.emit (node:events:518:28)
at TLSSocket.emit (node:domain:489:12)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)AggregateError:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1739:5)
at listOnTimeout (node:internal/timers:596:11)
at processTimers (node:internal/timers:529:7)
19:58:59.181 › RequestError:
at ClientRequest.<anonymous> (/app/lib/io.bsmanager.bsmanager/resources/app.asar/dist/main/main.js:14:1633692)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:530:35)
at ClientRequest.emit (node:domain:489:12)
at emitErrorEvent (node:_http_client:104:11)
at TLSSocket.socketErrorListener (node:_http_client:518:5)
at TLSSocket.emit (node:events:518:28)
at TLSSocket.emit (node:domain:489:12)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)AggregateError:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1739:5)
at listOnTimeout (node:internal/timers:596:11)
at processTimers (node:internal/timers:529:7)
19:58:59.190 › [
[
'Uncaught TypeError: e is not iterable',
'file:///app/lib/io.bsmanager.bsmanager/resources/app.asar/dist/renderer/renderer.js',
2,
1679093,
'Error: e is not iterable'
]
]
Beatsaver is loading normally via regular web browser
Expected Behavior
No response
Steps to Reproduce
Open BSM > Maps > Add > Browse Maps > sadness
Operating System
Linux
Version
v1.5.3 Flatpak
Additional Context
No response
@LiamillionSS can you check if master build or #872 PR resolves the issue.
Although looking into the logs, when it does fail on getting the json, it should just show an error tbh. I'll try to check if there is something weird here.
No crash when building master branch, fine to close this issue unless otherwise needed