What process are you using to launch that app on Sierra?
The application is a custom app bundle (http://github.com/OpenShot/openshot-qt/releases/download/v2.3.2/OpenShot-v2.3.2-x86_64.dmg). The user downloads the DMG, drags the app bundle into /Applications, and the tries to launch the app (probably via LaunchPad). An error pops up, "... can't be opened because the identity of the developer cannot be confirmed".
The application is a custom app bundle. The user downloads the DMG, drags the app bundle into /Applications, and the tries to launch the app (probably via LaunchPad). An error pops up, "... can't be opened because the identity of the developer cannot be confirmed".
When I check the code signing using the following command, here is the output I get:
codesign -dv --verbose=4 OpenShot*.app
Output:Executable=/Applications/OpenShot Video Editor.app/Contents/MacOS/launch-mac.sh
Identifier=OpenShot Video Editor
Format=bundle with generic
CodeDirectory v=20200 size=165 flags=0x0(none) hashes=1+3 location=embedded
Hash type=sha1 size=20
Authority=Developer ID Application: OpenShot Studios, LLC (C94ZNQ5JF3)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=May 11, 2017, 7:12:25 PM
Sealed Resources version=2 rules=12 files=2076
Internal requirements count=2 size=232
My DMG + App Bundle works fine on older versions of OS X, but on Sierra, it no longer passes Gatekeeper checks.
On Sierra, what happens if that app is selected in the Finder and a right-click is used to bring up the contextual menu to 'open' - do you see a choice to do so then, or is the process still blocked with the same dialog as before?
Right clicking and selecting 'Open' launches the app just fine on Sierra.
I believe that's the new normal...
So, even though I pay Apple for a developer license, codesign my app bundle and DMG, the end-users are still not allowed to simply launch my application? That just doesn't make sense to me.
I found something interesting. When an end-user running Sierra runs the following command:
spctl --assess --verbose OpenShot*.app
Here is the output:
OpenShot Video Editor.app: rejected (the code is valid but does not seem to be an app)
The output of that command on older OS X versions is always "accepted". So, maybe the above error is a clue about what is failing.
You might want to burn a support ticket w/DTS via the Member Center to see what they have to say - you'll need a buildable example project.
Solved the issue myself! I made 2 changes, and I'm not sure exactly which one fixed it... but here are the changes I made:
I added the following key to the Info.plist:
I also found 3 files inside my app bundle (the /MacOS/ folder) which were not executable files. I symlinked them from the Resources folder:
- launch.py (Python source file)
- openshot.py (Python source file)
- openshot-icon.hqx (Icon file)
So, not sure if it was the non-executable files in the /MacOS/ folder, or the missing Info.plist key, but my app bundle and DMG now work correctly in OS X Sierra! Hopefully this helps someone in the future!
Good info, thanks for the followup and best of luck w/your application(s).
Greetings and thanks from the future. My notarized app was working without complaint on macOS 10.15 but not 10.14 - setting CFBundlePackageType to APPL in Info.plist fixed the issue.