search

TacoTheDank / Scoop

[ADB/Root] Catches a stack trace when an app crashes unexpectedly.
Apache License 2.0
321 stars 24 forks source link

When grouped, the last crash is given the same "ago" time as the first crash #37

Open uli-on opened 3 years ago

uli-on commented 3 years 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).

uli-on commented 3 years ago

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"

uli-on commented 3 years ago

Nope, no duplicates, just the wrong position. Just found several prooves.

TacoTheDank commented 3 years ago

Edited wrong issue smh

TacoTheDank commented 2 years ago

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).

opusforlife2 commented 2 years ago

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.