Resolving HTTPS compatibility issues

There are many compatibility issues with HTTPS filtering for now, and we need to resolve them in an efficient way. The good way to resolve compatibility issue is to add some particular domain or a pair of domains to ssl_exception list. To do that we need to:

0. Check that HTTPS filtering is working on device and it is in whitelist mode, turn on full logging
1. Determine application in question and install it on device
2. Guess from info in issue what kind of problem user reported and what particular function is not working in that app
3. Try to trigger connection errors in application twice in 10 seconds, then you will have such line in the logcat:

Adding endpoint com.yahoo.mobile.client.android.weather_188.125.82.141_443_weather-flickr-yql.media.yahoo.com to exceptions due to class java.nio.channels.ClosedChannelException: null

A little explanation:

com.yahoo.mobile.client.android.weather - package name of the app
weather-flickr-yql.media.yahoo.com - domain that we are not able to MITM, can add to exceptions

To quickly get logcat logs from device you can use this command line:

adb logcat -v time -d | grep "adguard" > adguard_logcat.log

You can change "adguard" to "to exceptions due to" and get much smaller log.
If you are unable to repeat connection error twice in a 10 second period you can search for java.io.IOException: Internal TLS error, this could be an attack in the log and look upper lines to determine the domain that the app was trying to connect to.

Okay, if you determined the domain(s) you must enter it (or them) in HTTPS whitelist and try to use that app. But, before you proceed you must do a full restart for Adguard to reset temporary exceptions.

If the problem is gone after adding a domain or two to exceptions you must write the domains in a comment for the issue and reassign it to a developer, i.e. Revertron.