TypeError: filterWrapper is not iterable

[abaza738]

Error

/<project_dir>/node_modules/ytsr/lib/utils.js:23
  for (const filterGroup of filterWrapper) {
                            ^

TypeError: filterWrapper is not iterable
    at Object.exports.parseFilters (/<project_dir>/node_modules/ytsr/lib/utils.js:23:29)
    at module.exports (/<project_dir>/node_modules/ytsr/lib/main.js:60:24)
    at runMicrotasks (<anonymous>)
    ...

Details

For some reason, the value of searchSubMenuRenderer is sometimes returned as this:

{
  "trackingParams": "CDIQkXUiEwjSt4yGr4T9AhU2O_EFHQmlCT8="
}

Hence filterWrapper is undefined.

[eugabrielsilva]

Same error! Waiting for a fix, since this lib is the main tool used in my application... @TimeForANinja

[ArmyaAli]

I'm having this issue as well. This occurs so randomly as well

[TimeForANinja]

can you try changing filterWrapper to sth like

- const filterWrapper = (wrapper.subMenu || wrapper.submenu).searchSubMenuRenderer.groups;
+ const filterWrapper = (wrapper.subMenu || wrapper.submenu).searchSubMenuRenderer.groups || [];

can't recreate the error myself...

[abaza738]

I guess I can submit a PR with that change, but I don't have any knowledge of what the code does in there.

[dev-syn]

I also have this issue now and then it just randomly occurs like when I try searching for various songs some fail and then when I try again it works I can't reproduce it every time

[AaronMeyers]

i’m also having this issue

[dafatov]

Created a PR related to this defect. See plz. @TimeForANinja
#203

[BrijeshNenwani]

Earlier, It was failing 4 out of 5 times, and now it doesn't fail at all, thank you for this 👉#180 (comment)
BTW, your library serves one of the major feature in my application, and its awesome.
Note: This was my first comment on github.

[NotYuzuru]

can you try changing filterWrapper to sth like

- const filterWrapper = (wrapper.subMenu || wrapper.submenu).searchSubMenuRenderer.groups;
+ const filterWrapper = (wrapper.subMenu || wrapper.submenu).searchSubMenuRenderer.groups || [];

can't recreate the error myself...

this worked indeed, thanks!