Switch to full style
Discussions about Coollector.
Post a reply

Coollector and Mac OS 10.15 Catalina

Mon May 04, 2020 3:23 pm

Hi Everyone !

I just tried the last Mac OS version ("Mac OS 10.9 and above") but it crashes every time at launch, "Can't open Coollector...", I suspect the non 32bits-compatible limit to be the cause of the crashes...

Did anyone successfully launched it in OS X 10.15(4) ?

Thanks for your replies !!

elRod

Re: Coollector and Mac OS 10.15 Catalina

Mon May 04, 2020 4:35 pm

The app is 64-bit (it wouldn't be on the Mac App Store otherwise) and should work with Catalina. The crash must have another explanation.

I suppose you've tried the version from our website. Please try the LITE version from the Mac App Store to see if you have more success with it:

https://apps.apple.com/fr/app/coollector-movie-database-lite/id598827525?mt=12

Re: Coollector and Mac OS 10.15 Catalina

Mon May 04, 2020 11:46 pm

Thanks for your reply

Well I downloaded from the Mac App Store the 'Lite' version and it... works !! like a charm !

So in order to remove the 50 items limitations, should I buy the (for me as I'm in France) 9,99 euros full version directly from the Mac App Store ?

Best regards,

Rodrigo

Re: Coollector and Mac OS 10.15 Catalina

Mon May 04, 2020 11:54 pm

Yes, the paid version from the Mac App Store will most certainly work.

But it's weird because the version from outside the Mac App Store should work too. Maybe your Mac security settings are set to block any app downloaded from the internet. Or maybe the file was damaged and downloading the app again will fix it...

Re: Coollector and Mac OS 10.15 Catalina

Mon May 04, 2020 11:57 pm

I think I know what's the problem! Did you use Winzip to unzip the app? I've already had a couple of users in this case. Winzip doesn't extract the app as an app but as a normal file :doh:

If you use any other unzipper, it'll work, for example 7zip.

Re: Coollector and Mac OS 10.15 Catalina

Sun May 24, 2020 11:45 pm

I've finally found the explanation, it should be working now. Thank you very much for reporting that issue!
Post a reply