Support Topics Documentation Slack YouTube Blog

Android FCM

(Andrés) #1

Hi. I am trying to add push notifications to my app. I have already created the Firebase app but noticed that this guide:

there is a comment that says it is sort of outdated. I have tried to follow it but I do not see any devices in the messaging tab in backendless console. Is there any updated guide for it?


(Andrés) #2

Found the problem! I needed to add the registration intent to the receiver:

                <action android:name="" />
                <action android:name="" />

                &lt;category android:name=&quot;${applicationId}&quot; /&gt;

Could you please add that missing line in the official documentation?


(Mark Piller) #3

I am not convinced that it is needed for the newer version of the Android SDK. See the discussion at:

(Mark Piller) #4

Take a look at the docs from google:

Specifically, this part:</img>

(Andrés) #5

Hi Mark.

You are right about the documentation, but I am testing this on Android 5.0 and, if I remove that line, I don’t see the device registered. I will try to test in a different device to see if I get the same result.

I am also having some problems sending messages from the backendless console. I read this documentation, and I am sending this:

  • In Message Text, I put ‘simple text message’
  • In Headers:“android-ticker-text”:“Sample push text”,“android-content-title”:“Basic content title”,“android-content-text”:“Another context text”
    I got the push in my device but I don’t see anything in the ‘Messages’ tab.


(Sergey Kukurudzyak) #6

push notifications do not appear on ‘Messages’ section. There you can see only pub/sub messages

(Andrés) #7

Is there a tab or page in the console where I can see the push notification I sent?

(Sergey Kukurudzyak) #8

no, if you send only push than it would not be stored anywhere.

(Ralph R Njeim) #9


I have migrated my project from GCM to FCM. I haven’t found the updated documentation of Backendless on this subject so I have some question regarding an issue I am facing:

I am using my own PushService that extends the BackendlessPushService and I need to know how to adapt the Manifest file to take into account my receiver.

In fact, the code was the following with GCM:

<action android:name=“” />
<action android:name=“” />
<category android:name=“fr.livelovecite” />

Removing the above causes the app to crash so I have replaced it with the following:
<action android:name=“”/>
<action android:name=“”/>
<service android:name=“fr.livelovecite.push.PushService”

No more crashes but the notification does not appear.

Thank you for your help.

(Vladimir Upirov) #10

Hi Ralph
Here is a doc for FCM

(Ralph R Njeim) #11

Hi Vladimir,
Thank you for your prompt reply.

In the documentation com.backendless.push.BackendlessFCMService is declared as the service but nothing for com.backendless.push.BackendlessService. The app is crashing with the following stack:

E/AndroidRuntime: FATAL EXCEPTION: main
Process: fr.livelovecite, PID: 13319
java.lang.IllegalStateException: A reference to BackendlessPushService is missing in AndroidManifest.xml. Make sure to add to the manifest file.Alternatively, if you have a custom push service implementation, make sure your class inherits from"com.backendless.push.BackendlessPushService" and is registered in the manifest fileas
at com.backendless.push.BackendlessPushService.getPushServiceClassName(
at com.backendless.push.BackendlessPushService.enqueueWork(
at com.backendless.push.FCMRegistration$1$1.onComplete(
at Source:4)
at android.os.Handler.handleCallback(
at android.os.Handler.dispatchMessage(
at android.os.Looper.loop(
at java.lang.reflect.Method.invoke(Native Method)

(Oleg Vyalyh) #12

What version of sdk do you use?

(Oleg Vyalyh) #13

The latest is 5.2.1

(Ralph R Njeim) #14

I am using the 5.2.0.

Found the solution, adding:
<service android:name=".push.PushService"

resolves the issue of my custom service.

Nonetheless, processed notifications by BackendlessPushService override the sound of android by ignoring the sound state ( Ring, Vibrate, Silent). This means that even when on silent, received push notifications have sounds.

(Oleg Vyalyh) #15

Firstly, please upgrade version to 5.2.1, because it has fixes for FCM.
Secondary, for FCM you shouldn’t use any service except from the documentation one.

point 2:
<service android:name=“com.backendless.push.BackendlessFCMService”>
<intent-filter> <action android:name=“” /> </intent-filter> </service>

And the last one, use methods registerDevice() and unregisterDevice() intended for FCM (no for GCM)

(Ralph R Njeim) #16


SDK 5.2.1 resolves the issues. I can now extend BackendlessFCMService and declare my own Service in the manifest.

The only remaining problem is the one related to the notification sound, but that’s only a detail.

Thank you for your help !!
Ralph :slight_smile:

(Anton Govorushkin) #17

Hi Ralph!

Regarding the sound problem you are facing - please create a separate topic and describe your use case in details. I’ll try to help you out with this


(Ralph R Njeim) #18

Hi Anton,

here’s the created ticket:

Thank you for your help!