Fails to compile rules (rule list parsing error)

[Shnub]

Please answer the following questions for yourself before submitting an issue.

• I am running the latest version
• I made sure all content blockers are enabled in Safari settings
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

2.0.4.942

Environment

- OS: Sequoia 15.7.3
- Safari version: 26.2

Issue Details

After updating from AdGuard for Safari to AdGuard Mini in the App Store, the app seems to completely fail to compile any rules. It states under Settings > Safari Extensions (for all extensions):

The state.txt file (attached) reports:

Last error: E: (SafariExtensionManagerImpl: reloadContentBlocker(_:)) Error when reloading the content blocker general: unknown(Error Domain=WKErrorDomain Code=6 "(null)" UserInfo={NSHelpAnchor=Rule list parsing failed: Domains must be lower case ASCII. Use punycode to encode non-ASCII characters.})

Indeed I can observe in Activity Monitor that the com.apple.Safari.ContentBlockerLoader process doesn't become active (i.e. jumps to ~ 100 % CPU utilization) after enabling/disabling or changing blocking or element hiding rules. This used to work fine before the update, which I know because I routinely monitor com.apple.Safari.ContentBlockerLoader after changing user rules so I know when my changes have actually been applied in Safari.

Reinstalling the app, disabling and re-enabling all extensions in Safari and restarting Safari didn't help (unsurprisingly if there is a rule list parsing issue). Removing AdGuard Mini and reinstalling the latest version of AdGuard for Safari (1.11.24) restores normal operation.

In this condition, AdGuard Mini is basically useless, as no ad blocking occurs at all.

(Other logs not attached for privacy reasons.)

state.txt

[windwak3r]

@Shnub, hello!
Did you have any user rules enabled or custom filters added to AdGuard for Safari? Is the list of enabled filters in the state.txt file you sent correct?

We'll also need the debug logs:

1. Go to AG Mini Setting and enable Debug logging.
2. Reproduce the problem (enable any filter in Settings > Filters) and remember the time of reproducing.
3. Click Export logs on the Settings tab.

Please send resulting files to qa@adguard.com:
- include [agmini] keyword and 1163 in the subject of your email
- specify the exact time when the issue occurred
- if you used any custom filters or user rules please send them also

[Shnub]

Did you have any user rules enabled or custom filters added to AdGuard for Safari? Is the list of enabled filters in the state.txt file you sent correct?

Yes and yes. But disabling the user rules from within AG Mini didn't have any effect, Safari still receives no content blocking rules at all.

We'll also need the debug logs:

if you used any custom filters or user rules please send them also

Sorry, I will not be sending you any logs or block lists containing private information. If there is something more specific I can do, let me know.

Though I must say my motivation to experiment further with AG Mini is very limited – I installed it again today (2.1.0 this time) and now the extension popup in Safari doesn't even get past telling me to launch AG Mini (which is already running). And the new design is terrible in so many ways (besides not blocking ads at all). The previous version worked great for so many years, I would even have considered paying for a license to continue using it. But this new release erased all trust I had. You now want money for "pro" features but the app is just about as far from being "pro" as it could be. I'll just continue using AdGuard for Safari for the time being and if that stops working and AG Mini is still not in a good state, I'll have to switch to another ad blocker – sadly, because I always considered AdGuard superior to all other offerings.

[zzebrum]

@Shnub I understand your concerns about privacy and really appreciate you taking the time to report the issue.

Would you be open to recording a debug log with minimal system/user data? The steps below are designed to avoid collecting any personal information, and you can review the log yourself before sending it.
If that works for you, could you please:

1. Quit Safari browser.
2. Temporarily remove your user rules (Export --> Import options are available).
3. Enable debug logging.
4. Go to
   ~/Library/Group Containers/TC3Q7MAJXF.com.adguard.mac/Library/Logs/com.adguard.safari.AdGuard.
5. Delete the file AdGuard Mini-group.log (it will be recreated automatically).
6. Enable any filter to reproduce the issue.

After that, you can simply take the newly created log file from that folder and send it here. No extra data should be included, and you’re free to inspect the file before sharing it.

Totally understand if this still doesn’t feel comfortable. Just wanted to suggest a safe option that could help us investigate the bug more effectively.