App can't load Protection tab
Please answer the following questions for yourself before submitting an issue
- [x] Filters were updated before reproducing an issue
- [x] I checked the knowledge base and found no answer
- [x] I checked to make sure that this issue has not already been filed
AdGuard version
8.0.0 nightly 1 (5075)
Browser version
Firefox nightly
OS version
Windows 11 24H2
Traffic filtering
- [x] yes, I do
Ad Blocking
No response
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Other
No response
Language-specific
No response
Which DNS server do you use?
DNS protection disabled
DNS protocol
None
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Steps to reproduce:
- Update to 8.0.0 nightly 1
- Open the 'Protection' tab
- Wait a very long time and see nothing happens.
Expected Behavior
When clicking on the protection tab the filters menu should open so one can see and edit the active filters and related settings.
Actual Behavior
A little rotating circle is visible.
Screenshots
Screenshot 1
Additional Information
Also,when browsing the interwebs, there are a lot of cookie popups that have been blocked in older versions of AdGuard, which makes me think that not all blocking lists are being used. Or maybe they dissappeared. That's why I wanted to check the filter lists.
Oh, and I did restart the computer after AdGuard updated.
Experiencing the same issue with the Protection Tab.
I updated to version 8.0 nightly 1(5075) and it wouldn't start. I am stuck on the launch page and cannot enter the application. System: Windows 11 24h2 26100.4202
I updated to version 8.0 nightly 1(5075) and it wouldn't start. I am stuck on the launch page and cannot enter the application. System: Windows 11 23H2 Version 10.0.22631.5335
Only idiots would use adguard 8.0. I gave up after using it for two days. There are too many bugs.
@RonKhondji Greetings! Can You try the latest nightly version and let us know, if issues gone away? If it's not, please, collect and send us logs according to this instruction:
- Collect the debug log as it's explained here.
- Remember the exact time when the issue was reproduced.
- Send the archive to [email protected]:
- include
[windows]keyword andISSUE_NUMBERin the subject of your email - specify the exact time when the issue occurred.
Hello.
Nightly 3 shows no improvements. Log file is sent.
Nightly 4 still does not fix this issue.
Nightly 4 still does not fix this issue.
Is this issue resolved with Nightly 5?
I had to downgrade due to this issue and don't want to risk it again.
Nightly 4 still does not fix this issue.
Is this issue resolved with Nightly 5?
I had to downgrade due to this issue and don't want to risk it again.
This issue remains in Nightly 5.
Nightly 4 still does not fix this issue.
Is this issue resolved with Nightly 5? I had to downgrade due to this issue and don't want to risk it again.
This issue remains in Nightly 5.
Thanks for checking, mate. Not sure why Adguard is not fixing this one as a priority, this makes the new app pretty much unusable in regards to Protection settings.
v8.0.5111 (Nightly 6) is still not fixed.
v8.0.5111 (Nightly 6) is still not fixed.
我注意到大多是中文用户提交了这个bug,是否尝试过用英文版Windows打开呢,有可能是字符编码问题
v8.0.5111 (Nightly 6) is still not fixed.
I noticed that most of the bugs were reported by Chinese users. Have you tried opening it with an English version of Windows? It may be a character encoding issue.
I'm a primary English user. It's not a character encoding issue. It's an issue with the app.
v8.0.5111 (Nightly 6) is still not fixed.
我注意到大多是中文用户提交了这个bug,是否尝试过用英文版Windows打开呢,有可能是字符编码问题
這不是重點,重點是他們應該修復這個錯誤。 That's not the point. The point is they should fix this error.
Additionally, the problem with nightly 8 still hasn't been resolved.
Guys, any luck with Nightly 9?
Nope. Still broken.
It seems that v8.0.5172 has fixed this issue. However, they still haven't resolved the issue of the extremely slow interface response, which is a major UX problem that cannot be ignored.
It seems that v8.0.5172 has fixed this issue. nice to read. @RonKhondji, @XBadFellaX, @SekiBetu please try with the latest nightly
Looks ok :)
If the issue will appear again, feel free to reopen the issue