AdguardTeam / AdguardForiOS

The most advanced ad blocker for iOS
https://adguard.com/
GNU General Public License v3.0
1.43k stars 202 forks source link

App says “Couldn’t communicate with a helper application” when disabling and the reenabling protection from home screen #2206

Open unbeatable-101 opened 1 year ago

unbeatable-101 commented 1 year ago

Issue Details

Expected Behavior

I expect that the app enables protection just fine from the home screen

Actual Behavior

It says that it couldn’t communicate with a helper application, though everything seems to work fine and no other errors are shown.

This error only happens when enabling and disabling using the big switch on the home screen, doing them individually on the protection screen does not give an error.

Screenshots

Screenshot: ![IMG_6983](https://github.com/AdguardTeam/AdguardForiOS/assets/58151048/172e1f17-b9fc-44a4-a85e-0d1099a9d513) https://github.com/AdguardTeam/AdguardForiOS/assets/58151048/1543a49e-56fc-4878-a2de-f4cc05e08559

Additional Information

AdGuard_logs.zip

unbeatable-101 commented 1 year ago

Actually I do see some ads, so it isn’t working perfectly

ESurina commented 1 year ago

We know about this problem. It is because content blockers not updating correctly after converting safari rules. We will fix it in the next major update! Now you can try to reduce the number of enabled filters and rules, it may solve the problem.

unbeatable-101 commented 1 year ago

Thanks, reducing to only the default ad blocking filters fixed it for now Definitely seems the same as this bug https://github.com/AdguardTeam/AdguardForiOS/issues/2188, which is weird since it had been working perfectly for me since the last iOS beta released.

MadeByPP commented 10 months ago

+1

The same problem occurred after the Adguard 4.5.1 (1007) update on iOS 17.1.

t0niX commented 8 months ago

Problem is still present with the current beta 4.5.2 (1010). It occurred multiple times on iOS 17.2.

BlazDT commented 5 months ago

@artemiv4nov @zzebrum Issue seems to happen in latest iOS beta too (see linked duckduckgo issue.