Wire-android: Wire doesn't work with microG

[Salothin]

Wire can't receive GCM while the user is using microG.

Logcat error:

W/BroadcastQueue(xxx): Permission Denial: receiving Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x30 pkg=com.wire cmp=com.wire/com.waz.zms.GcmBroadcastReceiver (has extras) } to com.wire/com.waz.zms.GcmBroadcastReceiver requires com.wire.permission.C2D_MESSAGE due to sender com.google.android.gms (uid xxxxx ) Date xxxx

Cross issue at microG: https://github.com/microg/android_packages_apps_GmsCore/issues/115

[Salothin]

v2.13.265 finally asked for GCM registratation intent to microG -noticed this using xprivacy-, yet it can't receive GCMs with same logcat warnings. While GCM of microG works with most apps(?); Signal, Whatsapp, Snapchat, a few news apps, like BBC and a push message test app. Wire is the only one that doesn't work in apps that I've checked.

• microG is a free -as in freedom- replacement for some Google play services.
• Xprivacy is an xposed module for privacy protection.

[mrshankly69]

I have also run into this issue on a device without Google Play Services installed. Have microG framework installed and working with other apps (Signal, WhatsApp, Threema) but Wire does not work.

[Salothin]

2.14.275 it still dosn't work. Same errors.

[ghost]

I'm having the same issue, but I'm not sure whether it's caused by microG - a friend of mine who uses Play Services also doesn't get notifications. I'll look into logs soon and see if they can shed some light on things.

[BengaloBongali]

Same here.

[ghost]

+1

microG framework installed and working with other apps

Same. Wire notifications are the only ones that fail so far.

[vova-bezhenar]

Should be fixed in next release.

[Salothin]

v2.16.282

It still doesn't work. It's the same error.

[ghost]

2.17.284 and some other earlier release work for me. Thanks!

[Salothin]

2.17.284
It still doesn't work here. It's the same error.

[ghost]

Maybe I'm getting this wrong. Previously, I didn't get any notification on new messages. Now I do. Or is there something more to it? (excuse the ignorance, I'm new to smartphones)

[Salothin]

@kehugter It might be my setup that's broken. Let's see if we can get any more feedbacks.

[ghost]

For the record, I'm fetching from the microG official F-Droid repos.

[Awerick]

Same problem here!
My experience is that Wire sometimes works if it was used a few moments before (sometimes even some hours) but not always. Maybe this is the reason why the issues seemed to be fixed for @kehugter? @kehugter: Do you still get the notifications reliably?

Some new information:
One of my Wire contacts uses Android (Android 5.0.1) without a Google Account but the original Google Apps installed (incl. original Google Play-Services). She experienced the same notification problem (=sometimes it works, sometimes not)! (The problem still existed after updating (=sideloading) the Google Play-Services (i.e. GmsCore) to a recent version.)

_Could it be that the problem is not with microG but with the missing Google Account?_

[ghost]

@Awerick no, I stopped getting notifications in 2.20.293 so I rolled back to 2.17.284 to see if that build was still working, but it wasn't.

@Salothin the issue I'm referring to is probably a different one, because I don't have GCM enabled.

[nels83]

I also experience this problem with microG but not with original Google Play Services.

According to https://github.com/microg/android_packages_apps_GmsCore/issues/259#issuecomment-269533711 microG seems to be more strict than Google. After changing

<permission android:name=".permission.C2D_MESSAGE" android:protectionLevel="signature" /> <uses-permission android:name=".permission.C2D_MESSAGE" />

to

<permission android:name="com.wire.permission.C2D_MESSAGE" android:protectionLevel="signature" /> <uses-permission android:name="com.wire.permission.C2D_MESSAGE" />

in app/src/main/AndroidManifest.xml, everything works for me when using microG.

[Salothin]

@hakonbo pinging you as a wire dev because it looks like @nels83 found the solution to this bug.

[hakonbo]

@Salothin Hey, sorry I missed your ping. I'll update our manifest, thank you all for helping out! Should be included in the upcoming 2.27 release.

[hakonbo]

@nels83 Thanks for the solution. For potential future fixes, feel free to create a PR, might be merged quicker then...

[Salothin]

I've tested with two 2.27.314 clients. Video calls, voice calls and text messages are working with microG (v0.2.4-76-gd2b2ee5), no GCM errors, I am closing this issue.