Problems with receiving messages

[provokateurin]

Receiving messages works right after initialization.
When restarting the app and receiving a message after that it doesn't work anymore. In the logs I can see the Android code is definitely called.
When the app is in background or closed, receiving a message also doesn't work (same as above with receiving on the Android side).

Maybe these are actually the same problem, I suspect the callback is just never called for some reason.
I tried the embedded FOSS FCM and nfty distributors, both have the same problem and from the logs I collected I'm very confident this problem is distributor independent.

I will try to investigate it a little bit and see if adapting stuff from https://github.com/firebase/flutterfire/blob/master/packages/firebase_messaging/firebase_messaging/android/src/main/java/io/flutter/plugins/firebase/messaging/FlutterFirebaseMessagingBackgroundService.java helps.

[karmanyaahm]

Hey👋

I'm really excited to see a Nextcloud w/ UP app. I will try to look at what might be going wrong today/tmrw.

(I'm sure @p1gp1g's android expertise will be helpful if they have time to look too)

[provokateurin]

I'm pretty sure something like OneSignal/OneSignal-Flutter-SDK#464 is needed for this to work. Afaict most of that code is copied from https://github.com/firebase/flutterfire/tree/master/packages/firebase_messaging/firebase_messaging/android/src/main/java/io/flutter/plugins/firebase/messaging.

So how can we coordinate this? I can put some time into implementing this, but I don't want to do the work if someone else is already working on it. If you want to fix it then do it, because then I can continue working on other stuff for the notifications in the app.

[provokateurin]

I did some small refactoring and now at least the notifications work on subsequent runs. Background still not working.

[provokateurin]

FluffyChat also uses UP, so maybe I can check what they are doing, because I guess that works.

[p1gp1g]

What tests did you do ? Because the example (and fluffychat) definitely work in background and/or closed ?

[provokateurin]

What do you mean with tests? My implementation just doesn't work. I didn't try the examples yet, because as I said in the second comment I don't want to duplicate efforts if someone is already working on it. I will check the examples now.

[provokateurin]

LOL example works in background. Then I'm pretty sure I know what is wrong. The documentation just doesn't help a lot. I'll make a PR towards it to fix it.

[p1gp1g]

I though you did some tests with the example and you had trouble to receive message with the app in background or closed.

PR to improve our doc are very welcomed :)

[provokateurin]

Somehow I now don't receive the messages at all already on the Android side (looking at the logs). Message definitely arrives at the distributor.

[provokateurin]

I just always get GCM : broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=de.provokateurin.harbour (has extras) } in the logs. That it is cancelled seems to be the problem.

[p1gp1g]

Are you trying to use foss_embedded_fcm_distributor ? If so, we should close this issue and continue there. And remind that the foss embedded fcm distrib is still in beta :)

[provokateurin]

Yes I'm trying the foss distributor. I can temporarily switch to the non-foss, but I need to use the foss one to publish on f-droid. I don't think the non-foss will help though, because I have the same problem when using nfty. I'll try anyway.

[provokateurin]

Tried the same with the non-foss distributor. I don't think any of this is related to the distributor that is used.

[p1gp1g]

You should try with ntfy then. I don't know if the GCM message is related to your problem but it is definitely dependent on Google Services.

Do not forget to wipe data of your app sometime, there might be using introduced in development, not wiped after code changes.

I can give a look at your code if it can help. You must receive notifications in background :)