You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Version 1.11.11 (build 275, CT 2.0.34)
Environment
- OS: 13.3.1 (22E261)
- Safari version: Version 16.4
What filters do you have enabled?
AdGuard Base filter
Issue Details
Nothing is required for the Settings window to open. It just pops open from day to day, it seems.
Expected Behavior
In the past, this Settings window rarely opened on its own.
Actual Behavior
When working on your MacBook, the Adguard settings window appears. You click the red button in the top left of the window for it to close, then the next day, it does the same thing.
Screenshots
Screenshot 1:
Additional Information
No response
The text was updated successfully, but these errors were encountered:
My apologies. My App Store didn't notify me of the available update (or some other updates that were waiting) and I thought I was on the latest version. Thanks for the quick response.
Please answer the following questions for yourself before submitting an issue.
AdGuard version
Version 1.11.11 (build 275, CT 2.0.34)
Environment
What filters do you have enabled?
AdGuard Base filter
Issue Details
Nothing is required for the Settings window to open. It just pops open from day to day, it seems.
Expected Behavior
In the past, this Settings window rarely opened on its own.
Actual Behavior
When working on your MacBook, the Adguard settings window appears. You click the red button in the top left of the window for it to close, then the next day, it does the same thing.
Screenshots
Screenshot 1:
Additional Information
No response
The text was updated successfully, but these errors were encountered: