Old (Smart) Playlists/Folders still are in DJay despite removal from iTunes

Bug Reports
28

Hui there…
Another release, another try.

I just bumped into this newest release 5.2.10 for macOS and installed it.

I see this in the release notes of 5.2.10: ‘Fixed Local Music source showing empty or nonexistent playlists from Music app (macOS).’

Is this the fix that should resolve this issue?

1 Like
29

Hi @DJ_Big_Blender, sorry for the delayed response on this one. Yes, I believe this was supposed to be addressed in 5.2.10. I’ve sent a follow up to engineering to see if any additional steps are required to remove the playlists/folders. I’ll report back as soon as I have news. Thanks!

30

I confirm it is fixed (at least for me) !!!

I have to thank @Slak_Jaw , I think you raise this issue directly to the dev team and they’ve fixed within a quite decent time :clap:t5::clap:t5::clap:t5:

31

Thanks for confirming @djkom. You’re very welcome!

32

It didn’t solve anything for me…

33

Hi @DJ_Big_Blender, I double checked with the team and no additional steps are required for this fix. Are these old playlists empty? Because the fix relies on hiding/ignoring the playlist only if it is empty.

34

No, the playlists aren’t empty on my end either – as you can also clearly see in the original video I included here. So the issue is still happening for me. :pensive_face:

Others like @Criwo, @PatriceCros, and @Five-0 have also mentioned similar issues – and I assume they’re still experiencing them too (please correct me if I’m wrong!).

Question: Has the team already reached out to Apple’s developer support about this annoying bug?

Other tools like Rekordbox also use the Apple Music framework (Apple Music Kit), but they don’t seem to display those old, deleted playlists. So there must be a workaround for sure!

35

I just even consulted ChatGPT about this issue, and it came up with the following:

Possible causes to consider:

  • Cached data not being cleared: The app might be displaying old playlists from a previous session that are still stored locally. If there’s no automatic cache refresh, outdated data can remain visible.
  • Irregular or no synchronization with the Apple Music API: If the app doesn’t periodically refresh the user’s library using the MusicKit API, changes (like deleted or updated playlists) won’t be reflected in the app.
  • Permanently stored playlists in the local app database: It’s possible that once a playlist is accessed through djay, it gets stored in a local list or history, even if it no longer exists in the user’s Apple Music library.
  • Outdated or incomplete implementation of the MusicKit API:
    The integration may be relying on outdated methods or endpoints that no longer accurately reflect the current state of a user’s Apple Music library. For instance, if deprecated endpoints are used (or endpoints that don’t fully support dynamic updates to the user’s content), the app could retrieve incomplete or stale data. Ensuring the app uses the most up-to-date MusicKit endpoints — including proper scopes for library access and content filtering — is essential for accurate syncing and display.

==
Maybe this could give some ideas.

36

Thanks for the additional info @DJ_Big_Blender. I will pass this along and report back when I hear back…

37

Hi again @DJ_Big_Blender, engineering is asking if you could share your iTunes library? It should be a file bundle called Music Library.musiclibrary wherever you have your iTunes library path set. You can send me this in a DM. This will help them investigate things further. Thanks!

38

Thanks.
I just did send it.

1 Like
Playlists still showing on Djay Pro MacBook Pro after being deleted from ITunes.
39

I just noticed there are a lot more user who submitted this issue in the past:

2 Likes
42

Hi,
it’s been quiet here. Just wanted to give this a bump.
Any outcome from the file that @DJ_Big_Blender did sent in april?

43

Hi @Criwo, thanks for following up on this. I spoke with engineering. They haven’t been able to figure out what exactly is the problem, but it is unfortunately on the AM/macOS side of things so mostly out of their control to fix. They will keep investigating though…