iTunes 12.1.2 will not open

Question

Level 1

9 points

iTunes 12.1.2 will not open

After upgrading to iTunes 12.1.2, iTunes will not launch. Here is what I have found in the console.

4/9/15 11:02:36.319 AM pkd[686]: UNINSTALLED:com.apple.iTunes.today.TodayExtension com.apple.iTunes.today.TodayExtension(12.1.2) 10286EB1-CCFD-4E4C-B46A-719EE32C5DAD /Applications/iTunes.app/Contents/PlugIns/TodayExtension.appex

4/9/15 11:02:36.332 AM pkd[686]: INSTALLED:com.apple.iTunes.today.TodayExtension com.apple.iTunes.today.TodayExtension(12.1.2) <__NSConcreteUUID 0x7f9d63006450> 5038D233-BD3D-43C0-922A-E494B02F971E /Applications/iTunes.app/Contents/PlugIns/TodayExtension.appex

4/9/15 11:02:36.395 AM pkd[686]: PLUGIN REMOVAL:com.apple.iTunes.today.TodayExtension RESULT:3

4/9/15 11:02:47.130 AM com.apple.dock.ecti[1305]: Failed to connect (textField) outlet from (ECTIHelperApp) to (NSTextField): missing setter or instance variable

4/9/15 11:02:49.947 AM pkd[686]: UNINSTALLED:com.apple.iTunes.today.TodayExtension com.apple.iTunes.today.TodayExtension(12.1.2) 5038D233-BD3D-43C0-922A-E494B02F971E /Applications/iTunes.app/Contents/PlugIns/TodayExtension.appex

4/9/15 11:02:49.961 AM pkd[686]: INSTALLED:com.apple.iTunes.today.TodayExtension com.apple.iTunes.today.TodayExtension(12.1.2) <__NSConcreteUUID 0x7f9d63504290> D70CDFF3-2BB9-4FFB-AAD8-B7A288DFA3EA /Applications/iTunes.app/Contents/PlugIns/TodayExtension.appex

4/9/15 11:02:50.056 AM pkd[686]: PLUGIN REMOVAL:com.apple.iTunes.today.TodayExtension RESULT:3

4/9/15 11:03:04.929 AM Console[1308]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable

4/9/15 11:03:36.135 AM mdworker[1318]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

4/9/15 11:03:36.799 AM mdworker[1319]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Any suggestions?

Mac Pro (Late 2013), OS X Yosemite (10.10.3)

Posted on Apr 9, 2015 11:10 AM

Reply

Answer 1

Apr 9, 2015 12:43 PM in response to sccm_expert

I've had that happen to me today when I did the install on my MacBook Pro.

No solution yet. Thinking of reinstalling 10.10.3 but will have to wait for tonight when I'm home from work.

Reply

Answer 2

bruegge

Level 1

18 points

Apr 9, 2015 12:53 PM in response to Steve Werner

Same Problem here. 😟

Reply

Answer 3

Malumac

Level 1

0 points

Apr 9, 2015 12:53 PM in response to sccm_expert

Same problem here on 2013 iMac

Reply

Answer 4

Apr 9, 2015 12:58 PM in response to Malumac

I'm at work with my laptop, but it occurred to me that my iMac at home, also running 10.10.3, has the un-updated version of iTunes. I think I can copy the app from that computer to my MBP.

Reply

Answer 5

asipols

Level 1

0 points

Apr 9, 2015 1:00 PM in response to sccm_expert

Same problem. iTunes won't open after updating to version 12.1.2.

Reply

Answer 6

bruegge

Level 1

18 points

Apr 9, 2015 1:01 PM in response to asipols

Let's face it: Looks like a bug. Hope they'll fix it soon.

Reply

Answer 7

Ben.d

Level 1

5 points

Apr 9, 2015 1:25 PM in response to sccm_expert

I had this and managed to fix it:

Download iTunes from https://www.apple.com/itunes/download/
Open the Terminal
Run "sudo rm -r /Applications/iTunes.app"
Re-install iTunes

Reply

Answer 8

niedral

Level 1

5 points

Apr 9, 2015 1:30 PM in response to sccm_expert

Same for me (iMac 27", Late 2013).

I tried it with a new user as well - same result.

On my MacBook Pro (Retina, 13", Late 3013) it's working however.

Reply

Answer 9

sjam

Level 1

16 points

Apr 9, 2015 1:33 PM in response to sccm_expert

This has happened to me as well. I immediately called Apple support and after 45 minutes, they had me re install OS X....it did not fix the problem. The CS guy didn't hear anyone else so far calling about this issue...i think they will know now! waiting for a call back shortly to see if the OS X fixed it which DID NOT.

Reply