portify Transfering just stops before finish

If I transfer a playlist it doesn't finish. E.g. I have a 840 track playlist and it stops at trackDone() 793/840. Something similar happens with other playlists.

I added the track to the console output and found out that the last track processed is always the track that was last added to the playlist.

Dec 29 '13 17:12 stonedsquirrel

Mines just done this too. It stopped on a playlist (it was on playlist 3 of 6) on track 56/79. It's just hanging there.

Jan 03 '14 10:01 rickmills

Same here installed on ubuntu 12.10 npm release from: sudo add-apt-repository -y ppa:chris-lea/node.js

Jan 05 '14 20:01 tiki1980

I've got a theory: I think the problem is with tracks that were added locally. I'll look if the numbers match tomorrow. Would be nice if those track were at least properly skipped. Maybe I'll be able to write a patch myself but no promises. Don't have that much time at the moment.

Jan 05 '14 20:01 stonedsquirrel

Same problem here on Mac OS X 10.6.8

And @stonedsquirrel I think you're right. All playlists portify has got stuck on got (a) locally added track(s)

Jan 07 '14 09:01 creynders

I just went through my Spotify library and combed it for local tracks. I'm on a newly installed system, so any local tracks should show up as unavailable. I removed a bunch of them, and now when I try portify again, I get a new error:

trackDone() 735/1238

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: getaddrinfo ENOTFOUND
    at errnoException (dns.js:37:11)
    at Object.onanswer [as oncomplete] (dns.js:124:16)

Jan 08 '14 22:01 MrDrMcCoy

I can confirm that it hangs for songs not available on mobile device. Removing those from playlist makes it continue .- but it would be better if those songs either were transferred - or at least marked as not found/transferred.

Apr 19 '14 08:04 JeppeTh