iTunes doesn't work: "for you", "browse" and "radio" go blank

Question

macalienz Author

Level 1

11 points

iTunes doesn't work: "for you", "browse" and "radio" go blank

iMac late 2007.

MacOs El Capitan 10.11.6

iTunes 12.8.2.3

Apple Music Subscription

One week ago, suddenly, iTunes "for you" "browse" "radio" went blank (Library and Store work).

I tried:

1) unlog/log in again (iTunes account)

2) unlog/log in again (user account)

3) reset iMac (unplug, disconnect peripherials, etc)

4) reset iTunes cache

5) look for a solution in web forums (Apple Community included): issue spread, but no solution!

6) call Customer Service: they didn't support me (old device... yeah, I know, but the Apple Music subscription is current...) - just said to wait: in some cases this issue fixes without any intervention!!!!

My Apple Music account works perfectly on other devices (other iMac, iPhone).

Any suggestion?

Note: I DON'T WANT TO REINSTALL THE OS FOR A STUPID ISSUE LIKE THIS!!!

iMac, OS X 10.11

Posted on May 8, 2019 9:35 AM

Reply

Answer 1

PhilN

Level 1

4 points

May 8, 2019 6:18 PM in response to macalienz

Same problem. On 4May, iTunes was working properly. Tried again yesterday (7May) and the "Browse", "For You" and "Radio" pages are blank. Can't listen to anything via Apple Music either.

I've checked the Web and see that some people advise re-installing iTunes: did that but no help. Others advise upgrading to the latest iOS. My iMac is 10 years old and each time I've upgraded in the past, performance goes down and troubles go up. I don't want to upgrade.

My iPhone and Apple TV work fine, just the iMac has the problem.

Will this be fixed or should I cancel my Apple Music subscription?

Reply

Answer 2

Ro_hin

Level 1

4 points

May 17, 2019 12:37 PM in response to PhilN

Important detail: I was waiting for it to "fix itself", but nothing happened until I reset the iTunes cache, and immediately Apple Music showed up again. (iTunes>Preferences>Advanced>Reset iTunes Cache). I think the combo of Apple fixing something on their end, plus resetting was what made it work again for me.

Reply