Version 1.10.0-379-dev - "work in progress", not in Google Play

[SergeSPb]

Re: При "встроенном выборе" контактов проявляется одна недоработка

Согласен. Ну нет в мире совершенства

Смешно:)

[throwaway1287]

Re: Tried 378 but it crashes on startup for me:

Please try 379 posted above.

379 works, thanks!

Yeah I'm connected to the internet, 3G. Google Play Services 1084000. I upgraded from 1.9.0-316-dev-1cc5c37ef3ee which didn't crash.

[Kostya Vasilyev]

Re: 379 works, thanks!

Thanks for confirming!

[throwaway1287]

Spoke too soon. Notifications don't work anymore. Looks like you've switched to using Firebase for notifications, which my phone does not support. That's OK, I'll stay on 1.9.0. Thanks.

[mikeone]

Spoke too soon. Notifications don't work anymore. Looks like you've switched to using Firebase for notifications, which my phone does not support. That's OK, I'll stay on 1.9.0. Thanks.

... mh, notifications are still working also with version 1.10.0.379-dev (... 1.10.0.382-dev).

Could you describe your issue more specifically please?

[throwaway1287]

If I have to guess:

AquaMail must be using new versions of the FCM/GCM libraries (i.e. changed similarly to newbielink:https://github.com/vector-im/riot-android/commit/15bba9dce4a96e49fd4bd5132e2f60b57bdf1059 [nonactive]) These new versions are broken on my phone. This is because I'm not using Google's Play Services, but a reimplementation of them.

So, notifications (presumably) work fine except in my particular phone, because of the way I have it set up, and I don't expect anyone to fix it for me. I do appreciate Kostya fixing the crash, as now I have a test case I can use to potentially fix my version of Play Services.

Apologies if I sounded like I meant to imply otherwise. Thanks.

[mikeone]

If I have to guess:

AquaMail must be using new versions of the FCM/GCM libraries. These new versions are broken on my phone. This is because I'm not using Google's Play Services, but a reimplementation of them.

So, notifications (presumably) work fine, except in my particular phone, because of the way I have it set up, and I don't expect anyone to fix it for me. I do appreciate Kostya fixing the crash, as now I have a test case I can use to potentially fix my version of Play Services.

Apologies if I sounded like I meant to imply otherwise. Thanks.

Thanks for your feedback and clarification.

[Kostya Vasilyev]

Yes we did switch the low-level push transport from GCM (deprecated by Google) to Firebase Cloud Messaging (current, supported).

Just to be clear since Firebase is a dozen or more different technologies under one "umbrella":

- We do not use Firebase Notifications
- Or Firebase Analytics
- Or Firebase anything else

Just the low-level technology for "server sends a short data message to the app on a specific device and it gets delivered by Google's cloud magic".

Re: This is because I'm not using Google's Play Services, but a reimplementation of them

Sorry about this, no idea such things existed.

Oh and it would be a good idea for this "reimplementation" to throw an exception from Firebase.getToken if that's not supported. Remember the crash?  On your phone getToken returned "null" and no exception. Bad.