@pemek got it. and saying ‘same credentials’ do you mean “username + apikey” or “apikey only”? I’m having hard times trying to understand if username is required for Nextcloud.Music
For eg. Subtracks (android app I use now) username and token is required.
tldr:
@pemek thank you for the info, the fix is on its way
to whom who may find this interesting:
For eg. Subtracks (android app I use now) username and token is required.
a funny bit about NextCloud is that technically it is not. what Nextcloud guys actually did was implement apiKey authorization, skip token authorization, which is required by the subsonic API, and expose an outdated (for 10 years) way to authorize using ‘username+password’ pair. technically, in both cases, they use only the password/apiKey field, and the username is matched to it by internal means. I can assume that in the Android case, the application just falls back to pre-1.13 authorization method, which works, but looks a bit ugly as far as my taste. what I did was add a check for apiKey extension support, and one will not need to enter a username in case it is not really required. as soon as everything is merged and built, it will be released to openrepos
3 Likes
@pemek version 0.8 on openrepos already contains these changes, so you can try it
@ohnonot except that, version 0.8 contains also mentioned Go to album feature. I’m not sure about page navigation, so feedback is appreciated, but in general it should cover your usecase.
2 Likes
Connected successfuly. Thank you for implementation and clarification.
1 Like
I recently got a notice that my primary music store, Bandcamp, has started offering access through Subsonic clients, so of course I tested all three clients I found for Sailfish OS. Sadly, none of them seem to work for accessing Bandcamp.
SubMusic gives an error: Server reply can’t be parsed, please check URL
What can I do to help debug this?
1 Like
You mean this?
It refers to this API: https://opensubsonic.netlify.app/ but also admits that currently only 3 clients work, all of them such I have never heard of.
First step of debugging is to a) check that you have taken care of the preliminaries as outlined in the article, then b) start submusic from the command line:
submusic
And see what you see.
1 Like
I would assume that the three clients they mention are the only ones they’ve tried. One seems to be for iOS, one for macOS, and one for macOS and Windows. My guess is that they primarily use Macs. I’ve tried using several Linux-supporting clients over the last few hours, and most work fine. I have not had much success in figuring out exactly what they do, though.