asked 2018-02-28 02:27:58 +0300
The android Wire stopped working for me. The app was trying to connect to internet without success. I uninstalled the application and re-installed it from Aptoide but now I cannot authenticate. I get the message "Something went wrong. Please try to login again." Anybody got same issue?
answered 2018-03-04 20:23:49 +0300
A couple of people have commented in this topic that downgrading to a previous version of the Wire app is no longer a way of getting it to work. This suggests to me that Wire might have changed something server-side that requires the current version of the app. This means that those of us who were using Wire on Sailfish have reached the end of the line, temporarily at least.
In an ideal world, someone would write a native Sailfish client for Wire, but I think that if anyone was planning to to that, we would have heard about it by now, if not here, then on the Sailfish OS forum of TMO. I also don't hold out any hope that the Wire developers will revert any of the changes that they have made recently that stopped Wire working completely for us: that would involve them putting in extra work to support a partial implementation of an obsolete platform (i.e. Alien Dakvik's support for Android 4.x without Google Play Services). IMHO the best chance of getting Wire functionality back is with this year's work by Jolla on Android support. To give this the best chance of happening we need to make some noise, both with Jolla and Wire. My own efforts so far have been my Wishlist for Android support in 2018 (which was motivated by the Wire problems) and my original TLS issue at GitHub.
I am going to close the github issue and open a new, more general one. Please keep contributing to the discussion, in particular to keeping SailfishOS on Wire's radar: I suspect that they know very little about it, other than what they have heard from me and @jsommer
Edit: here is my new issue on Wire's GitHub repo for the Android app: https://github.com/wireapp/wire-android/issues/1437
And Wire have confirmed that they are not going to do anything special for Sailfish OS, even in the context of the upgrade in Android support for Sailfish due in 2018. Any improvement in the current situation is down to Jolla's work on Android support being sufficient to support the Wire android app (or a native Wire app being written, but I think that that is unlikely in the near future).
pakman ( 2018-03-05 20:11:28 +0300 )editWhat is the alternative?
I checked Riot, but I was disappointed by the privacy policy. The marketing highlights privacy and security, but the privacy policy describes collection of personal data, even exchanged content: „Information we collect about you … the communication content that you send and receive while using our Service. This may include message content and timing information, including text, photo, video and other media files in the context of the communication history of a room.“
Telegramm and Threema are just text chat messengers and I don’t really trust the first one. Just for text messaging JTox seems to be a good solution, that is available as a native Sailfish app. Unfortunately this app doesn’t support audio and video messaging. I like the technical approach. Maybe, we can encourage the developer to go ahead with financial contribution.
Twinme looks interesting, at least for private use. It includes voice and video chat. But I can’t really rate the credibility. This app is available at the Harbour app. The business model is not clear. That is suspect.
jsommer ( 2018-03-05 22:56:45 +0300 )editanswered 2019-07-20 09:43:33 +0300
SFOS 3.1 enables TLS v1.2 by default.
Tested on Xperia X.
On Wire 3.34.781 get past the login screen then fail (tried some older version too, same result). The login is successful, I get a "new device" email from Wire.
E/AndroidRuntime(21450): FATAL EXCEPTION: Thread-123
E/AndroidRuntime(21450): Process: com.wire, PID: 21450
E/AndroidRuntime(21450): java.lang.NullPointerException
E/AndroidRuntime(21450): at com.waz.media.manager.router.AudioRouter.setupBluetooth(AudioRouter.java:227)
E/AndroidRuntime(21450): at com.waz.media.manager.router.AudioRouter.<init>(AudioRouter.java:117)
E/AndroidRuntime(21450): at dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 6837): Force finishing activity com.wire/com.waz.zclient.MainActivity
Looked in the code and maybe BluetoothAdapter.getDefaultAdapter(); returns null.
Can this be debugged in dalvik to make sure?
I noticed the upgrade to TLS in the release notes too. I'm not on EA, so I'll have to wait for a bit to try this out myself. TLS 1.3 is out of course, I hope that Jolla will be able to add support for this for Xperia X quicker than they did for 1.2. Otherwise, if we do get the Wire app working again it will only for as long as Wire support TLS 1.2
pakman ( 2019-07-20 14:23:17 +0300 )editMy X is still on 3.0.3.9 Hossa and Wire is 2.37.349. Wire WORKS fine. I like the transparent tile of the app when open. I'll keep it this way till it stops working as Wire is very important to me. Thought this might be of use to somebody.
On my XA2 3.1.0.11 with Wire 3.10.442, Wire is unusable because in video call I can barely hear what the other side says. Any solution on that will be appreciated.
777 ( 2019-07-21 17:44:23 +0300 )editjust discovered this after finally getting to create a log from logcat:
Wire dropped support for Android < 5
From what I was able to gather for Wire 3.37 the reason it crashes are some android framework resources (paths suggest UI mostly) could not be found. It seems the requested version (v7) is not present under AlienDalvik.
Well, with the update 3.38 all of that is obsolete anyways.
Let's root for the baseport 8.1 on the X!
rozgwi ( 2019-09-26 01:31:32 +0300 )editanswered 2018-02-28 13:11:12 +0300
It seems that part of the the issue is lacking TLS 1.2 support in Alien Dalvik
As suggested in the comments you could try to downgrade.
Downgraded to v3.4.382, v3.6.391 and v3.7.398. All fail.
objectifnul ( 2018-02-28 14:08:42 +0300 )editI experienced a problem with wire update from january in playstore. After that wire quits immediately with the message: unfortunately wire has stoppen. I downgraded to version 3-5-388. This version works in my case. The login process is buggy but trying several times and once I got it.
carepack ( 2018-02-28 14:20:47 +0300 )editI am running 3.5.388 without any google services on my xperia, with background services enabled.
Moo-Crumpus ( 2018-03-01 10:58:34 +0300 )editAsked: 2018-02-28 02:27:58 +0300
Seen: 1,941 times
Last updated: Jul 20 '19
Maybe same issue as this one
https://together.jolla.com/question/179953/a1-tv-android-app-no-longer-works-with-214/
which also seems to be a network thing. (Funny though that in the case of A1TV only parts of the app stay offline)
I also have an old app for reading dilbert that now claims the server is unreachable. I'm not sure, though, if in this case it's just the app that's too old. Need to install it on a real Android device.
ossi1967 ( 2018-02-28 09:57:34 +0300 )editWire bug confirmed (Xperia/SailfishX).
To read Dilbert comics, install Daily Comics (https://openrepos.net/content/tardypad/daily-comics)
objectifnul ( 2018-02-28 12:21:31 +0300 )editfetch any older version of wire from uptodown.
Moo-Crumpus ( 2018-02-28 12:54:31 +0300 )edit@Moo-Crumpus: you can actually download older releases from the Wire homepage. Just change the release in the URL.
E.g. https://wire-app.wire.com/android/prod/wire-3.4.382.apk
Note: This APK has a different signature than Playstore!
I think thats preferable to uptodown (I generally don't trust 3rd party markets too much). The version on Aptoide is ancient, by the way.
rozgwi ( 2018-02-28 13:08:37 +0300 )edit@rozgwi Great tip about downloading apk's direct from Wire. Are the available version numbers the same as the tags on github or do you have another source for them?
I don't see an ancient version on Aptoide, btw. It looks like the same version as on the Google Play Store to me: https://wire-swiss-gmbh-wire.en.aptoide.com/
Anyway, Wire is a problematic app on SFOS: it doesn't work properly or even at all with Alien Dalvik unless you also install Google Play Services (which takes away part of the point of not using Android in the first place). I'm hoping that either the improved Android support for SFOS later this year will help, or maybe someone will write a native SFOS client. (I'd love to write one myself, but don't have the time.) This is a pity: it is the only app of its type that I have found that:
- is similarly-featured to WhatsApp
- is palatable to non-techies who are used to WhatsApp
- has a reasonable stance on privacy.
pakman ( 2018-02-28 18:35:14 +0300 )edit