Endless Permission requests that are never honored

[dcoke22]

There's another thread where people have chatted on this topic. I don't know if it contains the answers, however.

Issue with MakeMKV 1.16.5 on M1 Macs running macOS Monterey (needs code signing)

I run MakeMKV on Monterey on Intel. I don't see the repeated permissions requests.

[mmaslar]

There's another thread where people have chatted on this topic. I don't know if it contains the answers, however.

Issue with MakeMKV 1.16.5 on M1 Macs running macOS Monterey (needs code signing)

I run MakeMKV on Monterey on Intel. I don't see the repeated permissions requests.

That’s the thread I referenced earlier in this thread, but as WAYFLIX pointed out, that issue only impacts the installation. Anyway, the “solution” in that thread is to pay $99 for a developer account and sign the app yourself, so not really much of a solution.

[larry47591]

Still no real fix for this? Might Just start running mkv in parallels

[blake27182]

The above solution works for me as well -- Opening it through Terminal.

I tried creating a symlink for it in /usr/local/bin but it seems makemkv uses relative paths to open supporting files, so it cant find find them when invoked that way. Not too anoying for me though since i usually do these long-winded ripping sessions without closing the application. Still a good kink to work out in the future though.

[cinemaslavejoe]

I can't believe this still hasn't been fixed. Yes, it works through Terminal, but I didn't think programs would get harder to run after buying a Silcon Mac.

[Billycar11]

but I didn't think programs would get harder to run after buying a Silcon Mac.

thats exactly what i would have expected apple making it scarier to run anything out of their app store that they cant make $$$ on.

[immutableme]

I've got a fix that worked for me. In terminal.app, run
codesign --force --deep --sign - /Applications/MakeMKV.app

If successful, you should get "replacing existing signature" response.

Now, jump over to Privacy & Security -> Files and Folders
Here you may want to uncheck and recheck. If you have two MakeMKV listed and one has a terminal icon, remove it.

Before doing the replacing existing signature, the terminal icon MakeMKV permission was for Removable Drive, but the Desktop and Documents was with a different permission that had MakeMKV logo. After doing the signature replacement, the Removable Drive permission showed up properly under the MakeMKV logo permission. After which, it never asked for permissions again.

Problem solved for me, and hopefully for you all.

[mmaslar]

I've got a fix that worked for me. In terminal.app, run
codesign --force --deep --sign - /Applications/MakeMKV.app

If successful, you should get "replacing existing signature" response.

Now, jump over to Privacy & Security -> Files and Folders
Here you may want to uncheck and recheck. If you have two MakeMKV listed and one has a terminal icon, remove it.

Before doing the replacing existing signature, the terminal icon MakeMKV permission was for Removable Drive, but the Desktop and Documents was with a different permission that had MakeMKV logo. After doing the signature replacement, the Removable Drive permission showed up properly under the MakeMKV logo permission. After which, it never asked for permissions again.

Problem solved for me, and hopefully for you all.

Wow... It worked! Thanks for much for sharing!

[immutableme]

Wow... It worked! Thanks for much for sharing!

Awesome! So glad to hear it! One thing unknown to me is whether the fix will persist after subsequent updates or if we’ll need to repeat this procedure. Fingers crossed it’s the former.