-
-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/1724/missed call notification #2415
Conversation
c48a078
to
9979b06
Compare
Lint
SpotBugs (new)
SpotBugs (master)
|
af532ba
to
a390e0a
Compare
dc727fc
to
257c658
Compare
detekt checks are not fully satisfied. Some of the checks fail with ComplexMethod. While this is true and should be resolved in general, i suggest to review/merge anyway because this PR already changed a lot and seems stable for me. Further refactoring might take place in follow up PR's (after my vacation or later). feel free to improve minor things in this PR while reviewing @timkrueger |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- add missed call notifications in NotificationWorker and CallNotificationActivity - introduce refactoring of Notification handling (isolate firebase stuff from other logic). All "UI-notification" logic from ChatAndCallMessagingService was moved to NotificationWorker. ChatAndCallMessagingService was renamed to NCFirebaseMessagingService because it is now only responsible for firebase stuff. This separation should make it easier for alternative push services to dock with the app (if they are incorporated in the future). - for DEBUG mode: show delivery delay time in notifications (time between sending from firebase to receive on device). Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
this didn't make sense because time between firebase and devices is not synchronized, so the results were useless. Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
257c658
to
ca145d1
Compare
i reverted the calculation of the delivery time. This doesn't make sense because time is not synchronized... in the future we may be able to trigger a test push from the device itself and measure the full roundtrip time until it is received on the device again. But calculating a difference to a timestamp from firebease server doesn't make sense because it's not time-synchronized and never will be. |
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
APK file: https://www.kaminsky.me/nc-dev/android-artifacts/2415-talk.apk |
this PR will:
ChatAndCallMessagingService
was moved toNotificationWorker
.ChatAndCallMessagingService
was renamed toNCFirebaseMessagingService
because it is now only responsible for firebase stuff. This separation should make it easier for alternative push services to dock with the app (if they are incorporated in the future).Notes
notificationManager.activeNotifications
. This method is already in use (which might introduced problems for older phones in the past) but it is further used with this PR.possible follow up PR's:
NotificationWorker
still needs to be further simplified!