[Solved] Strava (Android app) not working anymore [answered]

asked 2019-01-12 17:47:03 +0200

ziellos gravatar image

updated 2019-06-04 15:08:55 +0200

It seems Strava is the next Android app that refuses to work with its cloud service due to outdated SSL/TLS in Alien Dalvik on my Aquafish and Xperia X (both on Sipoonkorpi 3.0.1.11). Synchonizing data as well as logging in don't work. Here are the error messages:

I/com.strava.net.ApiClientImpl(25736): POST https://m.strava.com/api/v3/oauth/internal/token?hl=de-DE failed: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xabefe538: Failure in SSL library, usually a protocol error
I/com.strava.net.ApiClientImpl(25736): error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure (external/openssl/ssl/s23_clnt.c:770 0xd8df5e94:0x00000000)

If the issue has the same root cause as the DB Navigator problems described here, I am wondering why Android-based Firefox is still able to show the Strava website? Shouldn't the browser be affected by the same TLS library or certificate incompatibilities?

Forgot to mention that I use microG 0.2.6.13280 (Strava depends on Google play services). The app was working well until a few days ago.

[Edit 2019-01-16] Strava works again after installing Google play services instead of microG. So it seems microG lacks some recent TLS libraries required by apps like DB Navigator and Strava.

[Edit 2019-06-04] After upgrading microG Services Core to version 0.2.7.17455 the Strava app works again! And also DB Navigator seems to work, at least it is possible to load my Bahncard which failed before.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by ziellos
close date 2019-06-04 15:09:20.331295

Comments

3

Not an answer, but Laufhelden supports Strava, obviously not as feature rich as the real app, but you can upload and view your activities (the strava api prevents viewing friends activities)

pigg ( 2019-01-12 18:54:13 +0200 )edit

Thanks @pigg, I know Laufhelden, and I use it occasionally. What I use the mobile app for is the social networking features. The features third-party apps could not offer.

I'm afraid that more and more services might be unusable with Aliendalvik based Android apps due to TLS issues, including browser. If that is the case, the last hope is that Jolla is able to significantly update Alien Dalvik.

ziellos ( 2019-01-12 20:03:23 +0200 )edit

@ziellos, Jolla is about to relase upgraded Alien dalvik support. For example, Xperia XA2 will have Android 8.0 API levels and if I remember correctly Xperia X will have about Android 6.0 or 7.0. So yes, I would say they will be significantly updated.

What comes to the Android based Firefox, I'll think Firefox may have other modules that include up to date TLS libraries so the method to request the data from the server is little different than on an app. Also the app may use different APIs in the first place.

Sakke ( 2019-01-12 22:51:13 +0200 )edit

Such upgraded Android compatibility for legacy devices (everything before Xperia XA2) is eagerly needed, however it does not seem Jolla has precise plans about it. In one of his comments to a blog post, James Noori said "As for Xperia X, we will have to evaluate the feasability of it before making a decision."

When taking Jolla's typical wording into account, We will have to evaluate doesn't sound good.

ziellos ( 2019-01-13 19:06:17 +0200 )edit

Isn't the lazy way of using TLS in Android apps to let google play services(api) handle communication? Not having google apps = not having the lazy way of TLS working.

yomark ( 2019-01-15 01:13:20 +0200 )edit