frequent errors when opening items undefined is not an object (evaluating 'r.data.ParentLogoItemId.length')

[foss-]

Describe the bug
When clicking item on home view, instead of opening item details, an error is shown.

To Reproduce
Steps to reproduce the behavior:

1. Click on album cover on home screen
2. see error: Something went wrong: undefined is not an object (evaluating 'r.data.ParentBackdropImageTags[0]')
   Also happens for photos or movies or TV shows.

Expected behavior
Show item details

Screenshots

Desktop (please complete the following information):

• OS: macOS 13.6.4
• Version 0.0.4-dev

[prayag17]

Is this still an issue with latest builds?

[foss-]

Thanks for the ping and new main builds.

In 0.0.4-dev (20240224.092219) for some albums loading them works as expected: clicking album covers on home screen does load album info. But for quite a few albums the error message is persisting.

It is interesting that the albums that work and those that don't seem to be consistent over JellyPlayer restarts. Both are MP3s so unsure how the albums would differ and why some load and others won't.

[foss-]

Should this be closed?

In 0.0.5-dev (20240317.114520) just tried to load an album view which loaded a blank page and no way to return to a functional view.

Other albums are not loading but error message has changed:

Something went wrong: undefined is not an object (evaluating 'r.data.ParentBackdropImageTags[0]')

[wolflord212312]

On windows 11 i have encountered something like this on the latest And its odd as only happens when i click on a

When Clicking on a EP to view info on the EP itself rather then a series i get some form of these errors

one reads 0 as im assuming it does not like that the EP has no description who knows

But the first one is undefined length

[prayag17]

Closing this in favor of #338

[foss-]

Doesn't this make it harder to keep track of the individual issues, their state and discussing one issue at a time?

[prayag17]

This issue is related to multiple components and routes and is not really a page specific issue