Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

com.facebook.lite - cannot detect that IPv6 is unreachable #3031

Closed
Alex-302 opened this issue Aug 26, 2019 · 3 comments
Closed

com.facebook.lite - cannot detect that IPv6 is unreachable #3031

Alex-302 opened this issue Aug 26, 2019 · 3 comments

Comments

@Alex-302
Copy link
Member

@adguard-bot commented on Sun Aug 25 2019

Issue URL (Incorrect Blocking)

https://play.google.com/store/apps/details?id=com.facebook.lite

Comment

Facebook Lite app no longer starts after latest Adguard update. I tried disabling Adguard settings one by one to identify the cause, without success. No other changes were made on my phone except Adguard updating to the last version. I had to add Facebook Lite to the exclusion list eventually, which works but is not the solution I want.

Screenshots

Screenshot 1

Screenshot 1

Screenshot 2

Screenshot 2

System configuration

Information value
Platform: And 7.0
AdGuard version: v3.2.140 (1.4.138cl)
AdGuard mode: VPN
Filtering quality: High-quality
HTTPS filtering: enabled
DNS requests blocking: enabled
Filters: AdGuard Mobile Ads,
ROList,
AdGuard Annoyances,
AdGuard Base,
ROLIST2,
AdGuard Tracking Protection,
AdGuard Social Media
@Alex-302
Copy link
Member Author

This app works only when AdGuard rptection is disabled in the app settings

@AdguardTeam AdguardTeam deleted a comment from Alex-302 Aug 26, 2019
@ameshkov ameshkov changed the title com.facebook.lite - broken app com.facebook.lite - cannot detect that IPv6 is unreachable Aug 26, 2019
@ameshkov ameshkov added this to the 3.2 milestone Aug 26, 2019
@ameshkov
Copy link
Member

The current solution is to keep pref.vpn.disable.reconfigure disabled in the case when Facebook Lite is detected on the device.

@artemiv4nov
Copy link
Contributor

artemiv4nov commented Nov 6, 2019

A note:
This bug can be reproduced if you connect to IPv4 only network and turn on the low-level setting: pref.vpn.disable.reconfigure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants