为什么即使消息服务进程不存在，Android应用仍然可以接收Firebase通知？
[英]Why android app still can receive firebase notification even though the messaging service process not exists?
问题描述
I wrote an app which implemented the FirebaseMessagingService; 
我写了一个实现FirebaseMessagingService的应用程序； I killed the process which the service belongs to, but the app can still receive the notification from firebase console, except that I forced to stop the app. 我终止了该服务所属的进程，但是该应用程序仍然可以从Firebase控制台接收通知，但我被迫停止了该应用程序。
So, I just want to know why the app can still receive the notification event though the service not alive? 因此，我只想知道为什么该应用程序仍无法运行，为什么该应用程序仍可以接收通知事件？ What's the mechanism of android? android的机制是什么？
1 个解决方案
解决方案1
0 2016-08-19 07:42:49
I don't have experience in Firebase, but in previous Google Cloud Messaging it was working this way: at first notifications (pushes) are received by Google Play Services and then redirected to your app starting proper broadcast receiver or service. 我没有使用Firebase的经验，但是在以前的Google Cloud Messaging中，它是这样工作的：首先，Google Play服务会收到通知（推送），然后将其重定向到您的应用，以启动适当的广播接收器或服务。 probalby Firebase is working same way - it's starting new service when it is not running currently probalby Firebase以相同的方式工作-当前未运行时正在启动新服务
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.