Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to play podcasts

See original GitHub issue

Describe the bug

My mopidy server has the Mopidy-Podcast extension installed and configured. It used to work with Iris and musicbox webclient. It still works with musicbox webclient but not with Iris.

To Reproduce

Install Mopidy-Podcast. Here is the related section of sudo mopidyctl config:

[podcast]
enabled = true
browse_root = Podcasts.opml
browse_order = desc
lookup_order = asc
cache_size = 64
cache_ttl = 86400
timeout = 10

Configure Mopidy-Podcast. Here is my configuration file at /etc/mopidy/podcast/Podcast.opml:

matthias@argos:~ 
↳ cat /etc/mopidy/podcast/Podcasts.opml 
<?xml version="1.0" encoding="UTF-8"?>
<opml>
  <body>
    <outline text="Concordance des temps" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_16278.xml"/>
    <outline text="La conversation scientifique" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_13957.xml"/>
    <outline text="Le Feuilleton" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_11495.xml"/>
    <outline text="Le masque et la plume" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_14007.xml"/>
    <outline text="Les p'tits bateaux" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_10137.xml"/>
    <outline text="Signes des temps" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_19489.xml"/>
    <outline text="Le Cours de l'histoire" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_10076.xml" />
    <outline text="Une histoire particulière" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_16408.xml" />
    <outline text="La Compagnie des œuvres" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_15537.xml" />
    <outline text="Open jazz" type="rss" xmlUrl="http://radiofrance-podcast.net/podcast09/rss_12283.xml" />
  </body>
</opml>

Click on “Browse / Podcasts”, choose a podcast, then a track, click “play” from the track menu
See the toast “Mopidy failed to add some track”

Expected behavior

The choosen track is played.

Console log

Object { message: "Mopidy: Failed to add some tracks", data: [] }
app.min.js:111:227792

Environment details:

OS: Debian
Browser: Firefox
Iris version: 3.56.1

Issue Analytics

State:
Created 3 years ago
Comments:11 (2 by maintainers)

Top GitHub Comments

2reactions

jaedbcommented, Apr 2, 2021

This is yet another issue due to using URIs in the browser URL (browsers do their own manipulation, creating inconsistencies). I have now enlisted encoding to base64 and preserving whatever encoding was provided by Mopidy itself. So, in theory, the issues described above should now be resolved.

@orontee and @samytichadou can you confirm whether the issue is solved by upgrading Iris to at least 3.57.3? You will need to restart Mopidy and clear your browser cache after upgrading.

1reaction

rmalchowcommented, Mar 22, 2021

so the difference appears to be the “#” as the delimiter of the “fragment” component of the URL vs the “#” as part of, for example, a request parameter value.

if i want to send a request parameter with key = “hashtag” and value = “#foobar”, then i have to escape the “#”, precisely because it is a reserved character in RFC3986.

if i want to use the “fragment” as it is intended in the RFC:

The fragment identifier component of a URI allows indirect identification of a secondary resource by reference to a primary resource and additional identifying information.

then i must not escape it. in this case, when we’re using the parts left of the fragment delimiter to identify a series of podcasts, and then use the fragment to identify an episode, i think it is save to assume that this is exactly the “identify a secondary resource” use case from the RFC. thus escaping the “#” is actually incorrect.