MacOS Application Unable to start

Problems
#1

I’m trying to launch the MacOS app, and I’m getting the following error

*** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[ITunesApplication sources]: unrecognized selector sent to instance 0x600000248e80’
*** First throw call stack:
(
0 CoreFoundation 0x00007fffaede465b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffc3c2348d objc_exception_throw + 48
2 CoreFoundation 0x00007fffaee662d4 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
3 CoreFoundation 0x00007fffaed55cf5 forwarding + 1061
4 CoreFoundation 0x00007fffaed55848 _CF_forwarding_prep_0 + 120
5 Turn Touch Mac 0x0000000103f1ee10 Turn Touch Mac + 900624
6 Turn Touch Mac 0x0000000103e87662 Turn Touch Mac + 280162
7 libdispatch.dylib 0x00007fffc4530524 _dispatch_call_block_and_release + 12
8 libdispatch.dylib 0x00007fffc45278fc _dispatch_client_callout + 8
<…>

#2

Are you on Mojave? We have a ticket from yesterday.

#3

Ohhh, can you post a screenshot of your iTunes sources? Like the whole list where it shows music, podcasts, playlists, etc. I wonder if you have anything I haven’t seen before in that list.

#4

The iMac is running Mac OS Sierra 10.12.6. I should be able to get a screenshot Monday

#5

Hey I’d love to get this fixed! If you can screenshot your list of iTunes sources I can see which one I haven’t tested against and fix it. Podcasts? Radio? Smart playlists?

#6

please fix Mojave issues! Please

#7

50%20AM
Screen Shot 2019-07-22 at 11.46.50 AM.png1101×723 43.5 KB

#8

@samuelclay Do you need any more details? Thanks for looking into this.

#9

@samuelclay Is there a way I can edit or change the settings for the app so I can get it to start?

#10

I’m not sure why it’s crashing, but I logged a ticket and hope to have it resolved soon:

#11

Thanks for the update! Let me know if you need anything else. I’ll watch the issue and look for an update.

#12

So it looks like you’re on an older version of OS X. Is there anything preventing you from upgrading to 10.13 or 10.14 (or the upcoming 10.15)? The bug is fixed in this OS releases.