AdguardTeam
AdGuard MINI Lipo compatible
@windwak3r
Issue Details
AdGuard MINI is not compatiblr with lipo ( strip architecture binary )
Proposed solution
make it compatible like the rest apps out there
Alternative solution
No response
@JohnnyFireOne, hello!
AdGuard Mini is a fat (universal) binary.
You can check it with:
lipo -info "/Applications/AdGuard Mini.app/Contents/MacOS/AdGuard Mini"
Technically, lipo can operate on this binary just like on any other universal Mach-O file. But you should keep in mind that the app is code-signed and notarized.
What commands are you using?
@JohnnyFireOne, hello!
AdGuard Mini is a fat (universal) binary. You can check it with:
lipo -info "/Applications/AdGuard Mini.app/Contents/MacOS/AdGuard Mini"Technically, lipo can operate on this binary just like on any other universal Mach-O file. But you should keep in mind that the app is code-signed and notarized.
What commands are you using?
@windwak3r try pearcleaner for example and you see that removes the safari extensions if you lipoed (remove the intel binaries) old adguard for safari and the new that is a new code engine has this issue even adguard for mac...only proton and switch apps seems to work propertly
@JohnnyFireOne It's not a compatibility issue; that's how macOS security works. Modifying the binary breaks the signature and integrity of the bundle, causing Safari to no longer trust AdGuard extensions. You can try these before and after stripping:
spctl --assess --verbose "/Applications/AdGuard Mini.app"
codesign -vv "/Applications/AdGuard Mini.app"
You'll see that removing binaries will break the bundle.
@JohnnyFireOne It's not a compatibility issue; that's how macOS security works. Modifying the binary breaks the signature and integrity of the bundle, causing Safari to no longer trust AdGuard extensions. You can try these before and after stripping:
spctl --assess --verbose "/Applications/AdGuard Mini.app" codesign -vv "/Applications/AdGuard Mini.app"You'll see that removing binaries will break the bundle.
@windwak3r
i will try that but why happends only on electron apps and the new adguard mini with sciter code?
@JohnnyFireOne It's not a compatibility issue; that's how macOS security works. Modifying the binary breaks the signature and integrity of the bundle, causing Safari to no longer trust AdGuard extensions. You can try these before and after stripping:
spctl --assess --verbose "/Applications/AdGuard Mini.app" codesign -vv "/Applications/AdGuard Mini.app"You'll see that removing binaries will break the bundle.
@windwak3r this method not working after striping only adguard for safari extention is shown on safari the rest disapears and the app stops working like not block anything
@JohnnyFireOne Those commands are not provided to solve the problem, but to show that the bundle is not broken when it's not modified, and that it's broken after modifications.
@JohnnyFireOne Those commands are not provided to solve the problem, but to show that the bundle is not broken when it's not modified, and that it's broken after modifications.
@windwak3r yeap i find that out :P i hope the team will fix it or workaround it!