nextcloud/talk-android
No Notification because MagicFirebaseMessagingService.onDestroy is called
オープン
#1,011 opened on 2021/02/15
approvedbugfeature: notifications 🔔help wanted
Repository metrics
- Stars
- (731 個のスター)
- PR merge metrics
- (PR metrics pending)
説明
reproduce:
- Start new debug session (Build Variant: gPlayDebug )
- Make a call to the emulator
Issue: onDestroy is immediately called after receiving Push Notification. User won't recognize that someone tried to call. This happens (only?) on the first start of the debug session. So actually Push Notifications are delivered but somehow get discarded.
Temporarily made some log commands:
2021-02-15 16:28:52.229 31725-31958/com.nextcloud.talk2.debug D/MagicFirebaseMessagingService: start onMessageReceived
2021-02-15 16:28:52.231 31725-31958/com.nextcloud.talk2.debug D/MagicFirebaseMessagingService: start decryptMessage
2021-02-15 16:28:52.306 31725-31958/com.nextcloud.talk2.debug D/MagicFirebaseMessagingService: set MagicCallActivity as fullScreenIntent
2021-02-15 16:28:52.325 31725-31958/com.nextcloud.talk2.debug D/MagicFirebaseMessagingService: start checkIfCallIsActive
2021-02-15 16:28:52.343 31725-31958/com.nextcloud.talk2.debug D/MagicFirebaseMessagingService: startForeground for Notification
2021-02-15 16:28:52.370 31725-31725/com.nextcloud.talk2.debug D/MagicFirebaseMessagingService: start onDestroy
- examine how often this happens. Is this really "only" for the first time after startup?
related: https://github.com/firebase/quickstart-android/issues/933