has anyone run this on sierra? just wondering...
nevermind: ran it, and all is well...
nevermind: ran it, and all is well...
Last edited:
has anyone run this on sierra? just wondering...
nevermind: ran it, and all is well...
I've run monolingual on EVERY release of the system software -- even beta releases.
It ALWAYS works fine.
Not sure you did read/understand my post correctly.
I did not say Monolingual isn't working. I was trying to explain it messes with .app files (removing the lproj files) and the result is that the .app file has a broken codesign signature. You can test this yourself by using the Terminal.
Apple provides security APIs that can test the codesiging to see if the app has been patched/cracked. Many devs use this to trigger a protection scheme.
So thats why I say .. don't use such tools.
and in the real world: what happens? been using monolingual for years; everything works, have had no issues relating to missing lproj files... so, seriously... what is the actual outcome of using this?
About 50% of all apps use the security APIs to check codesiging. Meaning the apps will not work 100% (mostly they seem to work nice but some feature fail).
I strongly doubt that. Do you have a source for these claims? Most developers probably only use code signing to comply with Gatekeeper. Few developers care and so something about tampering.
A list with all apps that are doing codesign checks (not only at first run) would be too long to list here.
I would suggest mailing the support of CleanMyMac for this list. They have a similar feature and they use a large database for skipping apps that do check code signing.
I don't think Monolingual uses such list because I had problems with this years ago.