title: Google Play Warning: How to fix incorrect implementation of HostnameVerifier
body: <p>Today I just received this email from Google:</p>
  
  <blockquote>
    <p>Your app(s) listed at the end of this email have an unsafe
    implementation of the HostnameVerifier interface, which accepts all
    hostnames when establishing an HTTPS connection to a remote host with
    the setDefaultHostnameVerifier API, thereby making your app vulnerable
    to man-in-the-middle attacks. An attacker could read transmitted data
    (such as login credentials), and even change the data transmitted on
    the HTTPS connection.</p>
  </blockquote>
  
  <p>Sadly, I searched all my code and found no use of HostnameVerifier, nor setDefaultHostnameVerifier or even any HTTPS connections!</p>
  
  <p>I'm using Google's compatibility libraries in its latest version: 25.0.1, and in some of my apps the Google Ads 9.8.0. Will upgrade Ads to 10.0.1, as I can only assume the culprit is in there?!</p>
  
  <p>Did anyone received this alert and if so how did you solve it?</p>