Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Unidentified developer" when opening universal app

See original GitHub issue

Hello, we switched from an app for x86_64 to an universal app. The app runs fine on all platforms when I sign them locally with my developer identity.

However, when we go through Testflight, we are greeted with a “… cannot be opened because the developer cannot be verified” message. This only happens with the universal build, the x86_64 only one works fine. And if I force-resign the app, then it also works fine.

This is how we sign:

electron-osx-sign --entitlements=./entitlements/entitlements.mac.plist --entitlements-inherit=./entitlements/entitlements.mac.inherit.plist --entitlements-loginhelper=./entitlements/entitlements.mac.inherit.plist --identity=${CERTIFICATE_DEVELOPER_SHA} --keychain=signing-cert-keychain --provisioning-profile=./embedded.provisionprofile --type=distribution "${appName}"       productbuild --component "${appName}" /Applications --sign "${CERTIFICATE_INSTALLER_SHA}" "app-name-${params.UPLOAD_ARTIFACT_VERSION}.pkg"

Checking the app with the usual tools (codesign,pkgutil, spctl) gives no clue to any problems. Only at runtime it doesn’t work.

I have run out of ideas to try…

Issue Analytics

State:
Created a year ago
Comments:10

Top GitHub Comments

1reaction

gpronetcommented, Oct 4, 2022

I meant that resigning locally with my developer identity makes it runnable for me, but I have not tried uploading the resigned app onto Testflight.

I see, I also have no problems running the app locally when it is signed with the developer identity and notarized. However for TestFlight and the Mac Store it has to be signed either with 3rd Party Mac Developer Application or Apple Distribution certificate. And when we do this we get the above problem.

Did you test if the same problem occurs when you attempt an app store release? Speculating if this is a problem with Testflight…

Yes, the app gets rejected for the same reason. I created a separate issue with more info since I am using electron-builder (not osx-sign directly) here:

https://github.com/electron-userland/electron-builder/issues/7171

I’ve attached a build log there which confirms signing goes well, so the problem has to be elsewhere.

0reactions

lukas2commented, Oct 11, 2022

Wow, happy to hear! 🙂

Actually it clicked for me when you said in the other thread that the “Move to Bin”-deleted files are hidden in Trash. I examined mine and saw my module in unsigned form. Then I knew there had to be more than one… 😃

Ok closing this.

Top Results From Across the Web

Open a Mac app from an unidentified developer - Apple Support

In the Finder on your Mac, locate the app you want to open. Don't use Launchpad to do this. · Control-click the app...

Fix the “App can't be opened because it is from an unidentified ...

Right-click (or control-click) the application in question and choose “Open” ; Click the “Open” button at the next dialog warning to launch the ......

How to open a Mac app from an unidentified developer

Open System Preferences. Go to the Security & Privacy tab. Click on the lock and enter your password so you can make changes....

“App can't be opened because it is from an ... - YouTube

Can't open app error message on macOS Catalina. ... “ App can't be opened because it is from an unidentified developer ” -...

[Fixed]Can't be opened because it is from an unidentified ...

mojave #macbookinstall #macfixMacOS is a sophisticated operating system with a high level of security. By default, it does not allow you to ...