Traxx

This may be a bit late, but you can extend the `FirebaseMessagingService` on Android pretty easily. [This](https://firebase.google.com/docs/cloud-messaging/android/client?authuser=3) is a good starting point. The main idea is: - create a new...

Heads up: the issue I was talking about is non-existent. There was an oversight in the Firebase documentation, which has been rectified. You're good to go.

Wondering the same thing. However, we already established that the SHA1 in Android ID must match the signing key of the app package, so my guess is you quota should...

From the issue you opened, I read that immediate handling of data-only notifications (eg displaying a local notification in response) isn't even the intended behavior? So the fact that (although...

Is there any way of achieving exactly that? Handling notifications while the app has been killed?

Chat feature in the app should display notifications as soon as they come (minus delay and restrictions, but before the user manually opens the app). As user could still just...

That is a nice idea. However, it would mean double the calls to firebase cloud functions (if I had a server that could handle a call on every message, I'd...

Just for the sake of being thorough: I just tested the behavior in a production (non-debug) app via internal testing track on google play. - messages before the most recent...

This might be a bit off-topic, but for anyone passing here on the hunt for a solution to my problem, adding your own FirebaseMessagingService extender doesn't play well with capacitor...

> Lame title doesn't exist but this is probably the most robust workaround: > > ``` > width={500} > height={400} > data={data} > > > > Title > > >...