Emulator Issues #11587

macOS: " can't be opened because the identity of the developer cannot be confirmed"

Added by 8times9 over 1 year ago. Updated over 1 year ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


macOS Mojave 10.14.3

On any system with GateKeeper enabled (enabled by default and only possible to disable with Terminal or bypassable by right clicking > Open) Dolphin will not be allowed to open. This is a new issue, development builds used to open fine on macOS.

Dolphin cannot be opened.png (69.7 KB) Dolphin cannot be opened.png 8times9, 02/25/2019 11:16 PM
Dolphin 5.0-9664.png (85.7 KB) Dolphin 5.0-9664.png 8times9, 03/01/2019 10:16 PM


#1 Updated by JosJuice over 1 year ago

  • Regression changed from No to Yes
  • Milestone set to Current
  • Operating system OS X added
  • Operating system deleted (N/A)

#2 Updated by spycrab0 over 1 year ago

  • Fixed in set to 5.0-9662
  • Status changed from New to Fixed

Should not be the case with newer builds.

Please try again with (a clean Applications folder and) and up.

If it's not fixed, I'll reopen it.

#3 Updated by 8times9 over 1 year ago


Still occurring with 5.0-9664.

#4 Updated by spycrab0 over 1 year ago

Are you running this from within the dmg image? If so you shouldn't.

#5 Updated by MayImilae over 1 year ago

  • Priority changed from Normal to Urgent
  • Status changed from Fixed to Accepted

Confirmed. Bisected with builds from the Downloads page, here is what I got. Also just to be clear, I did not use the updater, all builds are just straight downloads from the downloads page, which I then took out of the dmg and ran to see how gatekeeper would react. Using the "App Store and identified developers" Gatekeeper setting.

5.0-9301 works
5.0-9357 works
5.0-9413 works
5.0-9429 broken
5.0-9464 broken
5.0-9501 broken
5.0-5969 broken
5.0-9664 broken

This seems to be about when the buildbot initially failed, so it seems the new builds have a broken certificate. Confirming this is that the builds that work have "dolphin" within the dmg package, whereas the ones that fail have "Dolphin". That certainly implies a build configuration change!

EDIT: Oh right! System specs:

MacBook Pro 13in mid-2018 with Touch Bar
macOS 10.14.3 (fully up to date as of this writing)
Core i7-8559U @ 4.5ghz
Intel Iris Plus Graphics 655
16GB 2133MHz LPDDR3

#6 Updated by 8times9 over 1 year ago

Okay, retested from /Applications and ~/Downloads and it works fine.

Is there any reason I shouldn’t run it from the dmg? That always used to work in older development builds and it made bisecting without git easier.

#7 Updated by 8times9 over 1 year ago

Disregard my testing as MayImilae‘s suggests otherwise.

Though I’m still curious about running Dolphin from the dmg

#8 Updated by spycrab0 over 1 year ago

  • Fixed in deleted (5.0-9662)
  • Status changed from Accepted to Fixed

This was fixed a while back and was caused by a buildbot issue. Most builds should be fine now (regardless if run from a DMG or not).

Also available in: Atom PDF