nextcloud/talk-android

No Notification because MagicFirebaseMessagingService.onDestroy is called

Aperta

#1011 aperta il 15 feb 2021

 (7 commenti) (0 reazioni) (0 assegnatari)Kotlin (313 fork)auto 404
approvedbugfeature: notifications 🔔help wanted

Metriche repository

Star
 (731 stelle)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

reproduce:

  1. Start new debug session (Build Variant: gPlayDebug )
  2. 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

Guida contributor