Changelog

Here you find information about the recent changes we did to continuously improve MOOVAL.

v1.8.05 - May 26, 2017

Groove Music support was restored so it should be fully usable again. Sorry for the delay but our free time was precious the last few months.

Changes:
  • Adjust to changes in Groove Music authorization scheme.
v1.8.04 - Mar 16, 2017

MOOVAL is fully encrypted now and Spotify-support was enhanced so that reading liked albums works now.

Changes:
  • Add support for HTTPS.
  • Implemented new Spotify API endpoints to read liked albums.
v1.8.03 - Jan 5, 2017

Internal fixes.

Changes:
  • Adjust log-level for Deezer-API error-responses
v1.8.02 - Dec 27, 2016

Several fixes

Changes:
  • Do check for correct length of returned parameters for Deezer authentication-token response.
  • Fix issue with possible empty artist information when fetching artist-likes from Deezer.
  • Show Donate-button more prominently when transfer has succeeded as we don't even get enough donations to keep the servers running..
v1.8.01 - Nov 28, 2016

Fixed possible issue with Deezer-authentication

Changes:
  • Do check for correct length of returned parameters upon successful authentication-response before accessing them.
v1.8.0 - Sep 30, 2016

Added support for new service: Welcome Napster!

Changes:
  • -
v1.7.20 - Sep 25, 2016

Fixed an issue where a search using an invalid ISRC on Groove Music failed and caused the whole MOOVAL-process to be aborted.

Changes:
  • Catch ApiUsageException when trying to search using an ISRC on Groove Music and log a warning.
v1.7.19 - Sep 22, 2016

Fixed an issue where a search using a tracks ISRC on Groove Music failed and caused the whole MOOVAL-process to be aborted.

Changes:
  • URL-encode a tracks ISRC (which should never contain any non-URL-conform characters) before querying
v1.7.18 - Sep 21, 2016

Fixed an issue where a search on Groove Music failed and caused the whole MOOVAL-process to be aborted.

Changes:
  • Restrict the maximum length of a query-string to 200 characters
v1.7.17 - Sep 2, 2016

Fixed an issue where the Spotify-API could return playlist-entries without a valid track.

Changes:
  • Check if a playlist-entry contains a track entry before processing it further
v1.7.16 - Aug 29, 2016

Patched used Spotify-API library to not fail in case a track has no href-field set. So in case you got errors that a playlist could not be read, you may now retry!
Fixed an issue where the playlist-name was too long for Groove-Music to accept it.
Actively rate-limit requests to Deezer-API to 10 req / sec to avoid rate-limit-exceeded errors.

Changes:
  • check for empty field before trying to read fields of track-objects from Spotify-API
  • restrict playlist-names to 100 characters max (97 characters + '...')
  • rate-limit requests to Deezer-API to 10 req / sec
v1.7.15 - Aug 12, 2016

Patched used Spotify-API library to not fail in case a track has no disc-number set.

Changes:
  • check for empty field before trying to read as JSON object
v1.7.14 - Jul 29, 2016

Patched used Spotify-API library to not fail in case a track has no album-information set.

Changes:
  • check for empty field before trying to read as JSON object
v1.7.13 - Apr 22, 2016

Distinguish between 'not authorized' and 'not authenticated' when communicating with Deezer-API.

Changes:
  • correctly interpret error-code 300 as 'not authenticated and error-code 200 as 'not authorized'
v1.7.12 - Apr 18, 2016

Fixed issue that could be caused by searching in Groove-Music catalog using an empty query-string.

Changes:
  • when query-string is blank, do not call the API but return an empty collection instead
v1.7.11 - Apr 5, 2016

Fixed another issue that could cause you to see ... because it does (no longer) exist when transferring to Spotify.

Changes:
  • ignore caught 404-exception during search-request to Spotify-API
v1.7.10 - Apr 4, 2016

After having changed the server-infrastructure to a more powerful machine, we encountered maxed-out TCP-connection limits which lead to MOOVAL not being reachable anymore.
This was caused by connections that were kept open until GC kicked in. With more memory being available to the application, GC didn't need to run for a long time...

Changes:
  • close connections immediately after usage
v1.7.09 - Mar 31, 2016

In case you experienced the error ... because it does (no longer) exist when transferring to Spotify, you may now try again!

Changes:
  • ignoring Spotify 404 response when using the search endpoint and interpret it as 'no results available' instead of aborting the analysis process
v1.7.08 - Mar 29, 2016

In case you experienced the error Authentication failed while fetching playlist XXX from Deezer' with Deezer as export-service, you may now try again!

Changes:
  • ignoring playlists that can no longer be read from Deezer. These playlists normally are playlists of other users that you are following, where the owner later decided to make them private
v1.7.07 - Mar 22, 2016

In case you experienced the error ... because it does (no longer) exist with a track/album/artist that contains a '/' when transferring to Spotify, you may now try again!
This was caused by a bug in the Spotify API (see https://github.com/spotify/web-api/issues/187)

Changes:
  • remove '/'-character from search queries targeted at Spotify until bug is resolved

Back to MOOVAL