Het forum

I've had this issue with PlayOnMac for some time now. I overcame it somehow before, but now it's happening again.

I just updated it and ran the new version, 4.3.4. I'm on the latest OSX 10.14.6.

I opened the .dmg, dragged PlayOnMac to my hard drive, ran it, it does a standard verfication scan, stops halfway with the error "“PlayOnMac.app” can’t be opened because the identity of the developer cannot be confirmed." with the only option being OK.

I have "install from anywhere" set in my gatekeeper security settings in the Mac System Preferences. There is no option there which appears to allow it to run.

Has anyone found this problem too? Any solution? Thank you!

EDIT: I see that it's a recognized bug: https://github.com/PhoenicisOrg/phoenicis/issues/1937

I was meant to be addressed in June. It's now August. Any updates?

Aangepast door Dadu042

I wanted to answer that the latest dev news are on Github, but I see you already participated into, and had a answer .

Aangepast door Dadu042

Rad, the issue with not being able to open the application resides in your System Preferences > Security & Privacy > General > Unlock the lock (left click on it) w/ Admin PW > Open PlayOnMac Anyway.  It's because PlayOnMac is not an Apple-"safe"-recognized app.   Once you click Open Anyway, PlayOnMac should compile.  Just don't upgrade to Catalina yet, we're still waiting for the 64-bit upgrade for Mac compatibility.

 

I've had this issue with PlayOnMac for some time now. I overcame it somehow before, but now it's happening again.

I just updated it and ran the new version, 4.3.4. I'm on the latest OSX 10.14.6.

I opened the .dmg, dragged PlayOnMac to my hard drive, ran it, it does a standard verfication scan, stops halfway with the error "“PlayOnMac.app” can’t be opened because the identity of the developer cannot be confirmed." with the only option being OK.

I have "install from anywhere" set in my gatekeeper security settings in the Mac System Preferences. There is no option there which appears to allow it to run.

Has anyone found this problem too? Any solution? Thank you!

EDIT: I see that it's a recognized bug: https://github.com/PhoenicisOrg/phoenicis/issues/1937

I was meant to be addressed in June. It's now August. Any updates?

 

 

Quote from radhamadhava