This repository has been archived by the owner on Jan 19, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 44
Sync not working as expected #80
Comments
Ah looks like the file isn't created automatically (which it should). Which version are you running |
Well, I just installed it today, so I've got the latest. |
Ok, I'll fix this as soon as possible. |
I can confirm the Creating the folder made sync work, at least partially. I'll have a close look at it later. |
Looks like the Sync's constructor isn't called. This constructor should create the proper directories and files. Again, I'll fix it as soon as possible, but everybody is of course welcome to fix it and create a pull request. |
Fixed for next release (1.4.0) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Maybe I'm not running mopidy correctly, which I hope is the case, but when attempting to use the sync service, the GUI didn't return an error except when I clicked
GET
.I opened the Chrome console and saw a 500 error(would be nice to see an error popup when the server returns this), so I stopped mopidy and re-ran it as
mopidy -v
and found the culprit.Created the
mopidy-mopify
directory and then thesync.ini
file and then all was well.Simply adding a blurb to the wiki about creating the
mopidy-mopify
folder should be sufficient.The text was updated successfully, but these errors were encountered: