Hi everyone,
I am updating my ongoing case regarding a severe issue with my Apple Music Replay on my iPad (32GB model). The first-line Apple Support Advisors keep giving me standards responses forcing me to update my iPadOS.
Here is the updated timeline
The Setup: Heavy Apple Music user on a Family Plan. "Use Listening History" and "Sync Library" are always toggled ON on all devices.
Late 2025 - Feb 2026: My Replay froze on the iPad. The only tracks that registered during this period were the few songs I briefly played on my iPhone (which runs an older iOS version).
March to August 2026 (The Sudden Fix): for 6 straight months, my heavy daily background streams on the iPad logged perfectly into my monthly Replays.
September 2026 (The Current Breakdown): The bug returned. My September Replay page completely broke and shows "Not enough listening data". This time it completely broke me because I strictly streamed thousands of songs only on my iPad for the entire month as a test, and completely avoided using my iPhone.
My iPhone currently has a significantly older iOS version than my iPad, yet its data tracked perfectly back in early 2026.
My iPad managed to track 100% perfectly from March to August 2026 on the exact same OS version it is running right now. No software update occurred on the device prior to it breaking again in September.
My third-party hardware audio scrobbler (Last.fm) successfully captured thousands of plays from my iPad throughout September 2026. The music plays physically, but the internal Apple Music telemetry token for this specific iPad has frozen on the iCloud server end once again.
Steps already taken:I have toggled listening history, done a full Reset All Settings, and tested the Replay website on multiple non-Apple devices and browsers without luck.
The backend data sync token for my iPad device profile is clearly getting stuck or blocked periodically on Apple's main servers. Since I cannot clear up enough physical space on this 32GB iPad to trigger a massive iOS update (which shouldn't even be required since it worked fine two months ago (?), how can I get this escalated to a senior network engineer who can force-refresh my account's device telemetry tokens from the backend?
Any help or similar experiences would be greatly appreciated. Thank you!