Wire-android: Can't see medias

[Paviluf]

Hello,

I can't see the medias (images, audio, videos, drawing, gif, files) that are sent to me. I just see a white square or I have a message that the download of the file have failed. The rest of the feature (audio and video call) seem to work. I have a Motorola Razr i (x86) on CM11 (without any Google stuff) with Wire 2.25.305.

Thanks !

[Paviluf]

Maybe related to https://github.com/wireapp/wire-android/issues/220

[Paviluf]

After more tests I updated the first message accordingly.

[hThoreau]

I believe I'm experiencing this same problem. I can send and see the images and videos that I send, but not those that are sent to me. I use a modded version of android, having removed Google's dependencies as well (as much as I could, at the very least). Those who I talk to, who also use Android, do not suffer from this issue. To be more specific, I'm using a Sansung Galaxy Tab 3 with an Android 4.2.2 kernel version 3.0.31, and my interlocutor is using a Motorola Moto E and an Android 6.0. Both of us are using Wire 2.24.303. An by the way, when am I going to see you guys at Debian's repository? ;)

[Paviluf]

Here is a log
wire-2017-01-31-07-28-15.txt

[Paviluf]

@xuanzhaopeng do you think it's because we don't have google services ?

[xuanzhaopeng]

Hi @Paviluf thanks for your information. Could you please try again on latest build, to see whether you still could reproduce it?

I try to reproduce on Android 6.0 with CM 13, without Goolge service, but I cannot reproduce your issue. I guess the issue is related to OutOfMemeory(CM 11 is on Android 4.4 I guess), but I don't find that in your attached log. I have a similar issue for receving image, which could be the exception such as :

java.lang.Exception: Bitmap decoding failed, got empty bitmap for asset: 8e754fa3-2c2b-43af-ade0-23a9c4f2d575
     .... .....

If you still could reproduce it on latest build, please let me know and provide full log if possible, maybe with some screenshot will be helpful.

[Paviluf]

The problem it still here with the latest build. Here is a log and a screenshot after a test with otto the bot that send me a picture:

2017-02-06-21-41-36.txt

[Paviluf]

Did that help ? Do you think fixing this bug will take long ?
Because for now the app is almost useless for us :D

Thanks !

[xuanzhaopeng]

Hey, @Paviluf , thanks a lot for your information! Sorry for Inconvenient, I will try to reproduce it again in Monday. I will make the priority of this ticket as highest as possible :)

I will let u know as soon as possible I get something new .

Thanks again.

[xuanzhaopeng]

@Paviluf Hey I cannot reproduce it, but I guess I know the reason.

1) First of all, you don't have Google Play service, so you cannot recevie the message from GCM
2) So now you will recevie messages by our WebSocket
3) But your Websocket hand shake failed.

Ticket : https://wearezeta.atlassian.net/browse/AN-5010

[Paviluf]

I don't have access to atlassian but does that mean that you can fix it ?
Thanks !

[xuanzhaopeng]

Hey @Paviluf, could u please check:
Settings -> Security -> Trusted credentials

that you already trust : DigiCert Inc (Root CA) and DigiCert Inc (Global Root CA)

Merci!

[Paviluf]

It seem so

[darkbluelight]

I have the same big problem since the last 2-3 releases. I as well can only see images that I send myself. I'm using Wire on Android, version 2.27.314.

I as well didn't install Google's apps and services and I'm using migroG instead. But since Wire supports Websocket, I didn't register Wire for migroG.

I use a custom 4.4.4 Android with kernel 3.4.67, strict SELinux status.

DigiCert Inc (Root CA) and DigiCert Inc (Global Root CA) are trusted as well.

Is Wire specifically in need for any Google stuff for it to show images? If yes, what are those?

[Paviluf]

@xuanzhaopeng any news ? Do you need anything else ?

[xuanzhaopeng]

Hey @Paviluf, @darkbluelight @hThoreau , thanks a lot for your patience! Good news is that today we reproduce this issue!

And we almost find the reason is that your device may don't support TLSv1.2, that means your device maybe only could send TLSv1 request, that is not acceptable by our backend.

We are working on this issue now. cc: @JPonte

PS: as discussed with @JPonte , the Android which has API version lower than 20, doesn't support TLSv1.2 protocol by itself, but if you install Google Play Service, which will provide this protocol. So for your case, you cannot send request by TLSv1.2 at all because you don't have Google play service.

Thanks

[Paviluf]

Ok thank you very much ! I hope that you guys will be able to fix this quickly now :)

[Paviluf]

Is there any news ? Sorry to insist but I never be able to use the app and I really want to :)

[mykola-mokhnach]

@Paviluf Unfortunately this cannot be fixed on our side. Wire provides the highest level of security possible, but your current platform does not support TLS version 1.2. You must either update to Android 5.0 or install Google Play services with TLS 1.2 support.

[Paviluf]

Thanks for the update. Well I simply won't use Wire in this case... Let me explain, my phone, like a lot of phones, will never have anything newer than Android 4.4 and the point of using an app that respect my privacy is not to use Google Play Services that don't respect it.

Maybe you can make a fallback mode or integrate TLSv1.2 directly in Wire for those that don't have it ? It's too bad, I really like the app.

[mykola-mokhnach]

We'll check with the backend whether it's possible to use fallback for cases like yours. Thanks for your patience.

[Paviluf]

Thank you ! I really hope you will find a way.

[david-wire]

@Paviluf Thanks for your patience. We have thoroughly looked into this but unfortunately we cannot come up with a fallback option that would solve your issue (for security related reasons - due to the aforementioned lack of support for TLS version 1.2 on your device).
Apologies for the inconvenience.

[Paviluf]

Ok I understand. Too bad there is no solution, because I like the app :(

[Paviluf]

One thing that I don't understand is that messages, for instance, works. How could it be is since I don't have TLS 1.2 ?

[JPonte]

Not all endpoints seem to have this restriction and since we intend to drop older versions of TLS on the long run, there is little interest on updating those to support it.

[Paviluf]

@HazouPH build me a ROM with TLS 1.2 support but that didn't worked :(
It seem that a browser test without any gapps does indicate TLS 1.2 support.

https://forum.xda-developers.com/showpost.php?p=71306404&postcount=2184

Anyway is it possible to integrate TLS 1.2 in wire ?
Thanks !

[david-wire]

@Paviluf as previously mentioned, there is no solution for devices that run Android < 5.0 AND do not use Google Play Services. It will fall back to TLS 1.0. and we cannot provide a workaround.

[Paviluf]

No problem I use Signal now. It work perfectly :)

[cgruber]

This doesn't track. I have play services and am in modern Android (N) and have had this problem on a Samsung S8 and a Google Nexus 6p. Same symptoms exactly. :/

[Paviluf]

@david-wire by the way as I said here https://github.com/wireapp/wire-android/issues/518#issuecomment-284785273 I tested with a CM build that was built with TLS 1.2 support but that didn't worked. Maybe there is something else ?

[Paviluf]

It seem that it's totally possible to use TLS 1.2 on phone with Android 4.1+

https://github.com/square/okhttp/issues/2372#issuecomment-244807676

[IronJunkie]

@cgruber
same symptoms but I think you have a different problem, see https://github.com/wireapp/wire-android/issues/760

[IronJunkie]

Images (only got a photo so far) downloading & showing properly now for me on todays Wire update from Play Store. (linageOS 14.1.2 gps ver 11. Xxx)

[IronJunkie]

Sorry wrong thread, this does not fix your issue.