Unsafe implementation of the HostnameVerifier, Play Store rejects apps with this library (v0.11.2).

Lcom/deezer/sdk/network/b/Blues$1
To properly handle hostname verification, you’ll need to change the verify method in your custom HostnameVerifier interface to return false whenever the hostname of the server does not meet your expectations.
Please make appropriate changes to your app, and be sure to address the issues identified above. In addition to your Production release, if you have other release types that you use for testing and/or quality assurance checks (e.g. Internal test, Closed, Open), please make sure to update those tracks as well.
This rejection doesn’t impact the standing of your Google Play Developer Account, but repeated violations can result in the suspension of this app or your Google Play Developer account.
Before resubmitting your app for further review, please make sure to DEACTIVATE the non-compliant version: 22 and increment the version number of APK.

Locate the obfuscated class Lcom/deezer/sdk/network/b/Blues$1 in the Android sample and inspect its custom HostnameVerifier verify method. Compare its behavior with the issue’s hostname-matching requirement; done means mismatched server hostnames return false and the affected release versions are updated before resubmission.

索引モデルが issue の本文から書いたものです。