react native - 应用程序被杀死/未启动时未收到通知
Posted
技术标签:
【中文标题】react native - 应用程序被杀死/未启动时未收到通知【英文标题】：react native - not receiving notification when app is killed/not started 【发布时间】：2018-11-30 19:54:30 【问题描述】：我正在使用react-native-firebase@4.2.0 进行推送通知。
当应用在屏幕上打开时，我会通过 onNotification 收到通知，并按照我的代码的预期收到警报。
问题 1 当应用程序处于后台（未终止）时，我会在状态栏中收到通知，但点击它时，它会被关闭并且应用程序未打开。
我在 android logcat 中也遇到了这个错误：
06-21 17:26:03.892 5926 8672 D RNFMessagingService: onMessageReceived event received
06-21 17:26:03.913 5926 8600 E ReactNativeJS: No task registered for key RNFirebaseBackgroundMessage
--------- beginning of crash
06-21 17:26:03.932 5926 8601 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
06-21 17:26:03.932 5926 8601 E AndroidRuntime: Process: com.mycustomapp, PID: 5926
06-21 17:26:03.932 5926 8601 E AndroidRuntime: com.facebook.react.common.javascriptException: No task registered for key RNFirebaseBackgroundMessage, stack:
06-21 17:26:03.932 5926 8601 E AndroidRuntime: startHeadlessTask@57242:24
06-21 17:26:03.932 5926 8601 E AndroidRuntime: __callFunction@4106:49
06-21 17:26:03.932 5926 8601 E AndroidRuntime: <unknown>@3876:31
06-21 17:26:03.932 5926 8601 E AndroidRuntime: __guardSafe@4068:13
06-21 17:26:03.932 5926 8601 E AndroidRuntime: callFunctionReturnFlushedQueue@3875:21
06-21 17:26:03.932 5926 8601 E AndroidRuntime:
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.modules.core.ExceptionsManagerModule.showOrThrowError(ExceptionsManagerModule.java:56)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.modules.core.ExceptionsManagerModule.reportFatalException(ExceptionsManagerModule.java:40)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:374)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:162)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:194)
06-21 17:26:03.932 5926 8601 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
06-21 17:26:03.938 590 590 E SELinux : avc: denied find for service=opdiagnose pid=5926 uid=10238 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:opdiagnose_service:s0 tclass=service_manager permissive=0
06-21 17:26:03.939 590 590 E SELinux : avc: denied find for service=opdiagnose pid=5926 uid=10238 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:opdiagnose_service:s0 tclass=service_manager permissive=0
06-21 17:26:03.939 5926 8601 W OPDiagnose: getService:OPDiagnoseService NULL
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: Error while parsing timestamp in GCM event
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: java.lang.NumberFormatException: s == null
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at java.lang.Integer.parseInt(Integer.java:570)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at java.lang.Integer.parseInt(Integer.java:643)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at com.google.firebase.messaging.zzb.zzb(Unknown Source:81)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at com.google.firebase.messaging.zzb.zzc(Unknown Source:2)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at com.google.firebase.messaging.FirebaseMessagingService.zzd(Unknown Source:353)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at com.google.firebase.iid.zzg.run(Unknown Source:26)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at com.google.android.gms.common.util.concurrent.zza.run(Unknown Source:7)
06-21 17:26:03.946 5926 8672 W FirebaseMessaging: at java.lang.Thread.run(Thread.java:764)
问题 2 当应用程序被杀死或未启动时，我会在我的 android logcat 中收到这个：
W GCM：广播意图回调：result=CANCELLED forIntent act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg=com.mycustomapp（有附加功能）
就是这样。状态栏中没有推送通知或其他任何内容。
这些是我的AndroidManifest.xml中添加的服务：
<service android:name="io.invertase.firebase.messaging.RNFirebaseMessagingService">
<intent-filter>
<action android:name="com.google.firebase.MESSAGING_EVENT" />
</intent-filter>
</service>
<service android:name="io.invertase.firebase.messaging.RNFirebaseInstanceIdService">
<intent-filter>
<action android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
</intent-filter>
</service>
<service android:name="io.invertase.firebase.messaging.RNFirebaseBackgroundMessagingService" />
应用启动时调用的函数：
firebase.messaging().hasPermission()
.then(enabled =>
if (enabled)
// permissions granted
else
// permissions not granted
);
firebase.messaging().getToken()
.then(fcmToken =>
if (fcmToken)
// user has a device token
console.log(fcmToken);
else
// user doesn't have a device token yet
);
firebase.notifications().getInitialNotification()
.then((notificationOpen: NotificationOpen) =>
if (notificationOpen)
// App was opened by a notification
// Get the action triggered by the notification being opened
// Get information about the notification that was opened
);
this.onTokenRefreshListener = firebase.messaging().onTokenRefresh(fcmToken =>
// Process your token as required
console.log(fcmToken);
);
this.notificationDisplayedListener = firebase.notifications().onNotificationDisplayed((notification: Notification) =>
// Process your notification as required
// ANDROID: Remote notifications do not contain the channel ID. You will have to specify this manually if you'd like to re-display the notification.
console.log("onNotificationDisplayed", notification);
);
this.notificationListener = firebase.notifications().onNotification((notification: Notification) =>
// Process your notification as required
Alert.alert(
notification.title,
notification.body,
[
text: 'OK', onPress: () => console.log('OK Pressed'),
],
cancelable: true
)
);
this.notificationOpenedListener = firebase.notifications().onNotificationOpened((notificationOpen: NotificationOpen) =>
// Get the action triggered by the notification being opened
const action = notificationOpen.action;
// Get information about the notification that was opened
const notification: Notification = notificationOpen.notification;
console.log("onNotificationOpened", notification);
);
this.messageListener = firebase.messaging().onMessage((message: RemoteMessage) =>
// Process your message as required
console.log("onMessage", message);
);
这是我的 bgMessaging.js：
import AppRegistry from 'react-native';
import firebase from 'react-native-firebase';
// Optional flow type
import type RemoteMessage from 'react-native-firebase';
export default async (message: RemoteMessage) =>
// handle your message
console.log("RemoteMessage", message);
return Promise.resolve();
AppRegistry.registerHeadlessTask('AppBackgroundMessage', () => bgMessaging);
如果它完全相关，我使用react-native-navigation。如果您需要任何其他信息，请发表评论。
【问题讨论】：
【参考方案1】：headless 任务必须注册为 RNFirebaseBackgroundMessage。
更改您的代码：
AppRegistry.registerHeadlessTask('AppBackgroundMessage', () => bgMessaging);
到
AppRegistry.registerHeadlessTask('RNFirebaseBackgroundMessage', () => bgMessaging);
希望您已经完成this 4 steps 以在后台列出 FCM 消息。
【讨论】：
好的，这有帮助。现在，当应用程序处于后台（即未被杀死）时，我会收到通知。但是当应用程序被终止/未启动时，这会显示在 logcat:GCM : broadcast intent callback: result=CANCELLED forIntent act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg=com.mycustomapp (has extras) 中，但不会显示任何通知。我该如何解决这个问题？
你能生成签名的apk并再次测试吗？我认为它只发生在调试阶段。
试过了。和调试时一样。我应该在这个功能下添加一些东西吗？：[步骤 2] (rnfirebase.io/docs/v4.0.x/messaging/…) 让它显示通知？
@KetanMalhotra 你用的是什么版本的 android，在 android pie 中我有同样的问题，但在 android 6 中可以正常工作。【参考方案2】：
要在应用侦听来自 firebase 的通知时也在后台显示通知，您必须创建要显示的本地通知。
我会建议使用 react-native-fcm 库，它很容易使用https://www.npmjs.com/package/react-native-fcm
【讨论】：
react-native-fcm 已退役【参考方案3】：如果一切配置正确，以下文章可能会给出一些原因。
Why your Push Notifications never see the light of day
【讨论】：
以上是关于react native - 应用程序被杀死/未启动时未收到通知的主要内容，如果未能解决你的问题，请参考以下文章
react native - 应用程序被杀死/未启动时未收到通知
应用程序被杀死时的回调 - React Native [重复]
如何在 ios 中单击通知时接收数据，当应用程序被杀死时，（react-native-fcm 模块在 IOS 中获取推送通知）
Firebase crashlytics 中的非致命错误能否在不杀死应用程序 React Native 的情况下记录错误