I'm telling you that I'm tired of wasting time with your buggy software and your solution is to have me waste more time? I'm not going to build a sample project because this has nothing to do with my project. I checked out a commit from months ago that worked fine and now it doesn't work. How about this, under no circumstances should an extension that builds fine not be loaded. I'm already paying you, go figure why this is happening and stop making me waste more time.

Thanks for trying to help. It's a desktop only Safari extension. I have this extension published for more than two years so I know the process to build and run it. They probably messed something up in some update of Safari or XCode or who knows what and now I can't run the extension. You also don't get any errors or hints or any information of what could be wrong. I actually just published an update without being able to test it first, let's hope everything is all right. This is probably the last update I make to the Safari extension because I can't deal with this anymore, having to spend days troubleshooting every time I want to update the extension.

I figured it out. I was missing distribution certificates. I don't know why the error didn't state that instead of leading me astray with the missing sandbox key message.

Could I get some help with this? I'm stuck with this and I can't publish my extension update. Why on earth does it keep saying that I don't have the app-sandbox entitlement when everywhere I check its set to true. If I select custom when validating I can see in the "Review app.pkg content" screen in both the app and the extension it clearly appears in the entitlements section that com.apple.security.app-sandbox is set to true.

Both. The previous codesign output was for the containing app and this is for the extension: <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0"><dict><key>com.apple.security.app-sandbox</key><true/><key>com.apple.security.files.user-selected.read-only</key><true/><key>com.apple.security.get-task-allow</key><true/></dict></plist>

It looks like it expects the number to be pressed from the numpad. This has to be a bug since this behavior has changed and there's also no way to press those keys in most macs.

After some more testing, it looks like the only shortcuts that broke are those that involve MacCtrl-Shift-{number}.