No map rendering on Android 4 Kitkat

[giaotuancse]

Description

There's no map rendering on android 4 (Kitkat).
Same with this issue #115

Steps to Reproduce

Mapzen SDK & Android Version

Mapzen SDK - 1.3.3-SNAPSHOT
Tangram version 0.5.1

[matteblair]

Hi @giaotuancse, thanks for the report! Can you help us out with a few more pieces of information?

• What is the name/model of the device that produced this issue?
• Can you reproduce this issue on multiple devices?
• What is the log output from the application when this problem occurs? (i.e. using logcat)

[giaotuancse]

Hi @matteblair,
It's happens on all my android 4 devices (Asus zenphone 4 - Android 4.4.2 / Samsung Note 2 - Android 4.4.3). Btw, samples on github have same problem.
Here's the logs i can get. Hope it helps:

[Smilefounder]

Hi @matteblair , any solution to fix this issue yet?

[hjanetzek]

@matteblair this is probably the Android SSL protocol issue since our tile servers disabled SSL3. https://www.ssllabs.com/ssltest/analyze.html?d=tile.mapzen.com&s=151.101.1.95&hideResults=on

@Smilefounder, @giaotuancse please try with changing https to http for the tile url in the scene file.

[giaotuancse]

@hjanetzek It works now after i changed all https to http. Thanks

[hjanetzek]

@giaotuancse if you build the android-sdk yourself you can look for https://tile.mapzen.com in core/src/main/assets/styles/bubble-wrap/bubble-wrap-style-more-labels.yaml. Otherwise you could add your own scene file and load it like this:

MapFragment mapFragment = (MapFragment) getSupportFragmentManager().findFragmentById(R.id.map_fragment);
mapFragment.getMapAsync(new MapStyle("path_to_your_scene_asset.yaml"), new OnMapReadyCallback() {
  @Override public void onMapReady(MapzenMap map) {
    // Map is ready.
  }
});

https://github.com/mapzen/android/blob/master/docs/getting-started.md

[hjanetzek]

So the issue is that our SSL provider deprecated TLS 1.0 [1] and pre-Lollipop Android versions don't have TLS 1.2 enabled by default. The common solution when using okhttp seems to be this snippet square/okhttp#2372 (comment)

[1] https://www.fastly.com/blog/phase-two-our-tls-10-and-11-deprecation-plan