-
Notifications
You must be signed in to change notification settings - Fork 25
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
When grouped, the last crash is given the same "ago" time as the first crash #37
Comments
FYI: It must not be several "dates", literally taken, it's also enough if there's any time difference at all, like "just now" and "1 min ago" |
Nope, no duplicates, just the wrong position. Just found several prooves. |
Edited wrong issue smh |
Notes for myself: What happens is that a new crash comes in and is put at the top of the list. For some reason, the crash at the bottom of the list is given the same "ago" time as the newest crash, even though the crashes are ordered by age (from top to bottom). When "combine same apps" is disabled, this issue does not manifest (for some reason). |
I've been seeing this for ages and finally decided to get off my ass and report it. Turns out... BTW if you delete the newer crash the old one gets back its correct time-ago. |
Prerequisites:
Settings "Combine same apps" and "Combine same crashes" are both activated.
Whenever crashes are listed from several dates, there's a weird thing happening, that looks like the topmost crash is restacked to the very bottom in that app's group (or a duplicate is made and restacked to bottom? Can't tell yet because of #36).
The text was updated successfully, but these errors were encountered: