Custom Query (1067 matches)


Show under each result:

Results (13 - 15 of 1067)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#1344 fixed unsafe implementation of the interface X509TrustManager cp15 kazer
Description Hello Google Play Developer,

Your app(s) listed at the end of this email use an unsafe implementation of the interface X509TrustManager. Specifically, the implementation ignores all SSL certificate validation errors when establishing an HTTPS connection to a remote host, 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. If you have more than 20 affected apps in your account, please check the Developer Console for a full list.

To properly handle SSL certificate validation, change your code in the checkServerTrusted method of your custom X509TrustManager interface to raise either CertificateException or IllegalArgumentException whenever the certificate presented by the server does not meet your expectations. For technical questions, you can post to Stack Overflow and use the tags “android-security” and “TrustManager.”

Please address this issue as soon as possible and increment the version number of the upgraded APK. Beginning May 17, 2016, Google Play will block publishing of any new apps or updates containing the unsafe implementation of the interface X509TrustManager.

To confirm you’ve made the correct changes, submit the updated version of your app to the Developer Console and check back after five hours. If the app hasn’t been correctly upgraded, we will display a warning.

While these specific issues may not affect every app with the TrustManager implementation, it’s best not to ignore SSL certificate validation errors. Apps with vulnerabilities that expose users to risk of compromise may be considered dangerous products in violation of the Content Policy and section 4.4 of the Developer Distribution Agreement.

Apps must also comply with the Developer Distribution Agreement and Content Policy. If you feel we have sent this warning in error, contact our policy support team through the Google Play Developer Help Center.


The Google Play Team
#1343 fixed Navigation status OSD shows "unknown" image after window resize mvglasow (2) mvglasow (2)
Description Resizing the application window (on desktop versions, tested on Linux) or changing screen orientation (tested on Android) causes the status OSD to display an "unknown" image.

Log output below – first the OSD is displayed correctly, then the window is resized and the placeholder image is shown, as a nonexistent image path is set.

error:navit:osd_std_config:Error in saved command: not_ready, item=0xe25e40.
error:navit:osd_std_config:Error in saved command: not_ready, item=0xe61d20.
error:navit:graphics_image_new_scaled_rotated:No image for '/home/michael/workspaces/navit/navit-linux/navit/xpm/status_unknown_14087168)_wh_64_64.png'
error:osd_core:osd_navigation_status_draw:failed to load /home/michael/workspaces/navit/navit-linux/navit/xpm/status_unknown_14087168)_wh_64_64.png in -1x-1
#1342 fixed "Set distance to" in POI search results is no longer clickable cp15 mvglasow (2)
Description When trying to extend the search range for POIs, the distances are no longer clickable. Instead, the entire line is highlighted and nothing else happens.

All platforms seem to be affected (tested on Linux and Android).

Bisecting revealed that the bug was introduced with commit 8bdcd53: Add:gui_internal:Navigating menus with rotary encoder.[[Image(navit_distance_bug.png)]]
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.