-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXC_BAD_ACCESS (Code Signature Invalid) MAS-DEV #4074
Comments
If I use this guideline, I get the app signed with correct entitlements and can run it: Now I am just waiting for yet another review, hopefully it passes this time :-) |
+1 |
This is happening for me on 21.1.2. No issues on 21.0.3 and older. |
I've had sandboxed mas-dev builds running perfectly for months. Now I'm trying to get a mas-dev build with hardenedRuntime working for days ... all errors, no luck. Here's an interesting output from this script:
Configured as:
notarize.js
Output during build:
@develar, Any idea why this is trying to notarize the |
And of course, if I read the documentation it clearly states, "You can only notarize apps that you sign with a Developer ID certificate. If you use any other certificate—like a Mac App Distribution certificate, or a self-signed certificate—notarization fails with the following message:" - https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/resolving_common_notarization_issues There's this, though, that says we should be able to run MAS apps with a hardened runtime. https://forums.developer.apple.com/thread/111145?q=Notarize%20MAS%20* Now... I need to figure out why a user reports that my Electron app throws an error on Catalina that looks very much like it's running in quarantine with a hardened runtime. This is what led me down this rabbit hole... |
@semireg According to the output, I noticed that it seems to be signing mas apps twice:
Shouldn't it only sign it once? Seems like I am having the same issue and noticed the same problem with mine. Still trying to figure this out. UPDATE: Nevermind, that seems like it might be correct since this is a mas-dev build, which is signing with your dev identity. |
I have the same issue with |
Possibly related: #4179 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
stale[bot] <[email protected]>于2019年10月23日 周三10:20写道:
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4074?email_source=notifications&email_token=ABQZYVY67DRRVSMTX3C4QTTQP6YGZA5CNFSM4IFTMSE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7ZYEA#issuecomment-545233936>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQZYV7G7TPDBQNJUXGUWP3QP6YGZANCNFSM4IFTMSEQ>
.
nope
|
The stale bot is a jerk... |
Well at least, the bot removed the label. We should be thankful. |
After investigation, the bug is caused by this commit c8c37f2. Still, if you distribute |
@quanglam2807 Setting |
@johannesjo This bug has been fixed in the latest version already so your change won’t help. It must be something else. Can you post the error? |
@quanglam2807 It's the same error as above (though I am not sure atm if it did come in the 0x0, 0x1 or 0x2 flavor). I will recheck and post some more details as soon as I get access to my mac, which might unfortunately take a couple of days... There are also some suggestions made here, which I will try then too. The error happens both for mas and mas dev. |
So this is the exact error message:
|
@quanglam2807 So this is a little bit embarrassing, but it turns out I was not running mas-dev, but rather the regular mas build and that's what seems to have caused the error. Very sorry for the inconvenience. In my defense: After switching config properties around for hours I tend to get a little dizzy Thank you very much for your help! |
@johannesjo, it's a terribly complicated system... Good luck! |
Missing entitlements was the reason for me. I fixed this by adding those via cli args:
the file looks like this <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.security.cs.allow-jit</key>
<true/>
<key>com.apple.security.cs.debugger</key>
<true/>
</dict>
</plist> |
21.1.1
mas & mas-dev
Problem:
Building for mas-dev gives EXC_BAD_ACCESS (Code Signature Invalid) and I also get the same results when submitting it for review.
4 min video:
https://drive.google.com/file/d/1WbclNwMxcxgrohI9SS0SpmFVa2IHpCtN/view?usp=sharing
Details:
Using MacOS Mojave 10.14.5 with newly created certs, provisionprofiles and a clean installation of https://github.com/electron/electron-quick-start, gives signature error after sign. This happens with all of my electron projects, even if I go back in git where it worked before with earlier versions of electron-builder / electron / electron-osx-sign.
More details here, trying to sign app manually with electron-osx-sign with same error:
electron/osx-sign#200
Notice that the apple developer portal just changed their gui, I don't know if they also made some other changes.
I also tried with hardenedRuntime set to true & gatekeeperAssess set to false.
The text was updated successfully, but these errors were encountered: