Notifications not working on /e/OS (with MicroG)

[ne20002]

⚠️ Before posting ⚠️

• This is a bug, not a question or an enhancement.
• I've searched for similar issues and didn't find a duplicate.
• I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
• I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

Use a phone with /e/OS (or MicroG)

While other Apps like e.g. WhatsApp, Signal, SBB, ZVV, MeteoSwiss do work with Firebase Cload Messaging the Nextcloud app does not.
Indeed, on the notifications tab in the app a message box appears claiming that Google services are not available.

Expected behaviour

Nextcloud Android app should work with MicroG and not depend on Google services directly but use the correct API.

Actual behaviour

Notifications not working

Android version

10 /e/OS

Device brand and model

Samsung S9

Stock or custom OS?

Custom (explain in "additional information")

Nextcloud android app version

3.21.2

Nextcloud server version

24.0.5

Using a reverse proxy?

Yes

Android logs

N/A

Server error logs

N/A

Additional information

Please see also ##8684

[strugee]

Possible duplicate of #3333. @ne20002, please provide your adb logcat logs. Thanks for contributing to Nextcloud!

[ne20002]

Not sure where I get adb logcat logs.
I just realized on my /e/OS phone (which I now use as primarily phone) that the Nextcloud app is complainin about missing propriatraty Google services.
Other apps can handle this.

[AlvaroBrey]

Not sure where I get adb logcat logs.

Instructions here: https://github.com/nextcloud/android/blob/master/README.md#getting-debug-info-via-logcat-mag

[AlvaroBrey]

Just quickly installed /e/OS on a spare phone to test this. I am not very familiar with this ROM, but it appears that the included app store will install the Nextcloud FDroid build and not the one from Google Play.

The F-Droid build does not include any FCM code (which explains the "Google services not available" message). You may want to check the "gplay-release" APKS from the GitHub releases page.

This is then not a bug but expected behaviour.