iTunes match locked me out for 90 days during vacation.

Discussion in 'Apple Music, Apple Pay, iCloud, Apple Services' started by NoHo, Oct 6, 2014.

  1. NoHo macrumors 6502

    Joined:
    Aug 2, 2011
    #1
    I have iTunes match and it's the best service I have ever used. I can't even imagine not having it.

    I've run into a problem, though.

    My wife and I are currently on vacation and right before we left she logged into her user id on my macbook and synced up her iTunes for the trip with her own id.

    Now when I try and use iTunes match on my own login it tells me this computer is already associated with another ID and I will have to wait 90 days.

    I can't access my music during vacation and it's really becoming a bummer.

    I sent a ticket into apple about my problem and 2 days later they replied back with instructions on how to turn on iTunes match, like I was an idiot who didn't know how to click the turn on iTunes match button, but the problem is that when I try to turn it on it tells me my Macbook is associated with another ID and I will have to wait 90 days. I'm sure it will be another 2 days before they reply back to me.

    Does anyone know how I can get iTunes match working on my computer again and not have to wait 3 months?
     
  2. JackieInCo macrumors 603

    Joined:
    Jul 18, 2013
    Location:
    Colorado
    #2
    I don't think that there is anything you can do but wait. It's doing exactly what this this is meant to do, prevent users from sharing iTunes Match accounts.

    This will happen again if you do this again.

    I had this happen once when I bought a new used Mac. Even though the computer was now mine, it would not let me transfer iTunes Match to the new computer till 90 days had past.
     
  3. Fuchal macrumors 68020

    Joined:
    Sep 30, 2003
    #3
    This has happen to me twice over the past few years and there is NOTHING you can do but wait. It is absolutely stupid. Now, I make sure never to use any other apple id on my computer.
     
  4. markyr17 macrumors 65816

    markyr17

    Joined:
    Apr 8, 2010
    #4
    This isn't entirely true, I had a real problem getting this fixed, but I was able to get this fixed by calling support, and they reset the account timer so I could re sign into my account.
     
  5. impaler macrumors 6502

    Joined:
    Feb 20, 2006
    Location:
    FL
    #5
    Unless you have success with what markyr17 did, you have to wait. I went through a painful, 1.5 year-long process to gain back music purchased under old iTunes Store accounts, going back to the creation of the store - even when songs were locked with DRM. I had to log into an account, go to purchases, download all previously purchased music, and wait 90 days before logging into the next one, and repeating. After I got them all done, logged into my primary account, added the songs to iTunes, then ran iTunes Match, which replaced the old songs under different Apple IDs under my unified Apple ID, and also removed DRM. Painful but finally got there.
     
  6. Gav2k macrumors G3

    Gav2k

    Joined:
    Jul 24, 2009
    #6
    Op you might want to change your thread title because this is nothing to do with iTunes match.

    I had this issue about three months ago and I emailed support and as a one off they removed the block.
     
  7. Rigby macrumors 601

    Joined:
    Aug 5, 2008
    Location:
    San Jose, CA
    #7
    Tip: If you have the ability to create virtual machines (using something like Virtualbox or VMWare), you can easily avoid this by creating a new VM per account ...
     
  8. impaler macrumors 6502

    Joined:
    Feb 20, 2006
    Location:
    FL
    #8
    Wish I knew this two years ago. :rolleyes:
     
  9. JackieInCo macrumors 603

    Joined:
    Jul 18, 2013
    Location:
    Colorado
    #9
    I got the warning that I would not be able to log into another computer using iTunes Match after I logged in on my new Mac Mini. I have only one iTunes Match account and did not log into anyone else's account. I did buy a Mac Mini base i5 and then exchanged it for the i7 so this is probably why I got the warning.

    I'm thinking about buying a MBP soon so I will not be able to log into iTunes Match on that computer for another 80 days from today.

    I guess they have a limit to the number of new computers you can log into using the same iTunes Match login as well in a certain time frame. Even though no one else logged in.
     
  10. Rigby macrumors 601

    Joined:
    Aug 5, 2008
    Location:
    San Jose, CA
    #10
    You can have 10 devices associated with one account, but no more than 5 of those can be computers. In case there are still older computers associated that you are no longer using, you can remove them by clicking on the account button in the iTunes store and going to "Manage Devices" in the "iTunes in the Cloud" section.
     
  11. Primejimbo macrumors 68040

    Joined:
    Aug 10, 2008
    Location:
    Around
    #11
    I think this is so stupid. My wife and I share a computer and iTunes, but the iTunes Match is under my Apple ID. If her Apple ID is an authorized user on the same iTunes library as mine, we should be able to both use iTunes match then.
     
  12. JackieInCo macrumors 603

    Joined:
    Jul 18, 2013
    Location:
    Colorado
    #12
    I only have one computer associated and I still got the warning that I would have to wait 90 days before associating another one.
     
  13. Fuchal macrumors 68020

    Joined:
    Sep 30, 2003
    #13
    That is nice. When it happened to me, they told me there was nothing they could do. Maybe they've gotten enough complaints they're a bit more lenient about it now.
     
  14. NoHo thread starter macrumors 6502

    Joined:
    Aug 2, 2011
    #14
    I ended up calling support and they fixed it as a ONE TIME exception.

    I didn't know I did anything wrong. When my wife logged into her iTunes on my Macbook under her own user id, it was nothing but for her OWN stuff, nothing having to do with mine.

    It was a bit frustrating that it's so easy to mess this up. iTunes is complicated enough and now tossing this in makes it even more complicated.

    Oh well. It's all fixed now after a long call with support. I just hope it never happens again.
     

Share This Page