Forums

I upgraded to 4.2.7 but no matter what I put the Mac OS X (latest, I always upgrade) security settings to, I cannot get permission to run, even when the security settings are set to "Anyone." I always get the message that the developer cannot be identified and the Mac will not allow the app to open. Fortunately I have a backup of 4.2.6 which runs fine. But 4.2.7 will not run at all.

Can you try to run

codesign --verify --verbose=4 PlayOnMac.app/

On a terminal with PlayOnMac 4.2.7?

 

Many thanks

Hi to all,

I have the same issue. Here's the output of the codesign command:

--prepared:/Applications/PlayOnMac.app/Contents/Frameworks/Python.framework/Versions/Current/.
--validated:/Applications/PlayOnMac.app/Contents/Frameworks/Python.framework/Versions/Current/.
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/badlang.applescript
--validated:/Applications/PlayOnMac.app/Contents/MacOS/badlang.applescript
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/bados.applescript
--validated:/Applications/PlayOnMac.app/Contents/MacOS/bados.applescript
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/badplace.applescript
--validated:/Applications/PlayOnMac.app/Contents/MacOS/badplace.applescript
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/libwx_osx_cocoau-2.9.5.0.0.dylib
--validated:/Applications/PlayOnMac.app/Contents/MacOS/libwx_osx_cocoau-2.9.5.0.0.dylib
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/libwx_osx_cocoau_gl-2.9.5.0.0.dylib
--validated:/Applications/PlayOnMac.app/Contents/MacOS/libwx_osx_cocoau_gl-2.9.5.0.0.dylib
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/playonmac.real
--validated:/Applications/PlayOnMac.app/Contents/MacOS/playonmac.real
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/please_reboot.applescript
--validated:/Applications/PlayOnMac.app/Contents/MacOS/please_reboot.applescript
--prepared:/Applications/PlayOnMac.app/Contents/MacOS/python
--validated:/Applications/PlayOnMac.app/Contents/MacOS/python
PlayOnMac.app/: valid on disk
PlayOnMac.app/: satisfies its Designated Requirement

Looks good to me, but I can not start the actual version of PlayOnMac.

 

With best regards,

Thomas

Hey, all...

Same issue here, same output. Yosemite 10.10.4

Also to note- the uninstaller does open fine.

Same story on 4.2.8, app can't be opened because it's from an unidentified developer - even when security settings are set to "Anywhere." You can, however, open the app by right-clicking the icon in the Dock and choosing "Open" from there. That is the only way the app will run.

That is really weird .... Can you have a look at your system log file and see if there is something wrong?

Maybe this seems to be the relevant part of log messages:

14.05.15 11:48:06,036 CoreServicesUIAgent[483]: Error -60005 creating authorization
14.05.15 11:48:09,204 CoreServicesUIAgent[483]: File /Applications/PlayOnMac.app/Contents/Resources/unix/image_magick/bin/animate failed on loadCmd /ImageMagick-6.4.8/lib/libMagickCore.2.dylib
14.05.15 11:48:09,204 CoreServicesUIAgent[483]: Fails dylib check

These entries come up in log after open it from security plugin in settings.

Maybe you can try to remove these two files from the package

Which files do you mean? If I remove anything from the PlayOnMac package the integration test fails at start.

After deleting these 2 files and core resigning...

 

15/05/15 14:08:10,100 CoreServicesUIAgent[21900]: unexpected message <OS_xpc_error: <error: 0x7fff79f83c60> { count = 1, contents =
    "XPCErrorDescription" => <string: 0x7fff79f83f70> { length = 18, contents = "Connection invalid" }
}>

 

Can you try

spctl --assess --verbose=4 --type execute PlayOnMac.app 

With the original POM bundle?

Just downloaded 4.2.8

Moved app to /Applications; right click -> open: No Issues

double-click opened: No Issues

pinned to dock while running; single click open: No Issues

 

 # spctl --assess --verbose=4 --type execute PlayOnMac.app

PlayOnMac.app: accepted

source=Developer ID

override=security disabled

Edité par underscoredot

So problem solved for you?

Can't speak for the others, but mine is working fine. Thanks.

tried it the same way underscoredot did and that worked. It is maybe a problem with Path Finder. I never tried to start it through pure Finder before. After the first successful start through Finder it works now also with Path Finder.