Sorry if this is a known issue, but I haven’t been following progress towards Mopidy v4 lately…
Running Mopidy-Mobile on top of Mopidy 4.0.0a15 on Ubuntu 25.10, every time I try to play a Track I get something like:
INFO Core-10 (_actor_loop) pykka
Exception returned from Core (urn:uuid:c323c8db-c76c-4329-b769-48cb08ff9161) to caller:
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/pykka/_actor.py”, line 242, in _actor_loop_running
response = self._handle_receive(envelope.message)
File “/usr/lib/python3/dist-packages/pykka/_actor.py”, line 353, in _handle_receive
return callee(*message.args, **message.kwargs)
File “/home/tkem/.local/lib/python3.13/site-packages/mopidy/core/_tracklist.py”, line 180, in index
validation.check_instance(tl_track, TlTrack)
~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File “/home/tkem/.local/lib/python3.13/site-packages/mopidy/core/_validation.py”, line 112, in check_instance
raise exceptions.ValidationError(msg.format(arg=arg, name=cls.name))
mopidy.exceptions.ValidationError: Expected a TlTrack instance, not {‘model’: ‘TlTrack’, ‘tlid’: 1, ‘track’: {‘model’:
‘Track’, ‘uri’: ‘internetarchive:tsp2007-06-06.mbho.flac16#tsp2007-06-06.mbho.d1t06.mp3’, ‘name’: ‘Today’, ‘artists’: [{‘model’:
‘Artist’, ‘uri’: None, ‘name’: ‘The Smashing Pumpkins\’, ‘sortname’: None, ‘musicbrainz_id’: None}], ‘album’: {‘model’: ‘Album’,
‘uri’: ‘internetarchive:tsp2007-06-06.mbho.flac16’, ‘name’: ‘Smashing Pumpkins Live at Columbiahalle on 2007-06-06’, ‘artists’:
[{‘model’: ‘Artist’, ‘uri’: None, ‘name’: ‘Smashing Pumpkins’, ‘sortname’: None, ‘musicbrainz_id’: None}], ‘num_tracks’: None,
‘num_discs’: None, ‘date’: ‘2007-06-06’, ‘musicbrainz_id’: None}, ‘composers’: , ‘performers’: , ‘genre’: ‘Rock\’, ‘track_no’: 6,
‘disc_no’: None, ‘date’: None, ‘length’: 205000, ‘bitrate’: 194, ‘comment’: None, ‘musicbrainz_id’: None, ‘last_modified’:
1429313735}}
I checked the Changelog and already improved 4.x compatibility for my extensions (e.g. “uri” being mandatory in “Track”), but this seems to be some sort of encoding/decoding issue related to frontends (educated guess)…