Skip to content
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

Wrong date in notifications #1954

Open
xep22 opened this issue Jan 4, 2025 · 3 comments
Open

Wrong date in notifications #1954

xep22 opened this issue Jan 4, 2025 · 3 comments
Assignees
Labels

Comments

@xep22
Copy link

xep22 commented Jan 4, 2025

  • App build number: 2.5.3 420503003
  • Android version: 15
  • Device: OnePlus 11
  • Installation source: Google Play

In the notifications there is displayed the wrong date, every day is the 2025/01/01

Screenshot_2025-01-04-21-44-28-75_b783bf344239542886fee7b48fa4b892

@jpmens
Copy link
Member

jpmens commented Jan 4, 2025

Does that change at all if you switch from Move mode back to Significant changes mode?

@xep22
Copy link
Author

xep22 commented Jan 4, 2025

Does that change at all if you switch from Move mode back to Significant changes mode?

No it's the same.

@growse
Copy link
Collaborator

growse commented Jan 8, 2025

I think that date is the date that the notification was created, which is the default for all Android notifications.

This is a bug. We should be calling setWhen on the notification so it displays the timestamp of the last update, but I guess that Clock.system.now() is only evaluated once:

https://github.com/owntracks/android/blob/master/project/app/src/main/java/org/owntracks/android/services/OngoingNotification.kt#L60

@growse growse self-assigned this Jan 8, 2025
@growse growse added the bug label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants