You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no visual clue that the empty list means no crashes found or ongoing search.
When the CPU is busy, because of other apps, the search takes longer. I mistakenly think that no crashes were found and close LogFox before it completes. Instead, if I wait more than usual, the crashes eventually appear.
For example, I mistakenly filed #142, because I thought that LogFox had a bug that it could not find the crash.
The text was updated successfully, but these errors were encountered:
Thank you for the quick reply. I'd appreciate a visual feedback whenever I should wait for a background job.
Are you talking about
1. "Loading" while crashes are being searched using search bar
2. "Loading" when you open crashes tab and until you see apps in list
3. "Loading" before crash is handled and appeared in list?
Crashes
.When the CPU is busy, because of other apps, the search takes longer. I mistakenly think that no crashes were found and close LogFox before it completes. Instead, if I wait more than usual, the crashes eventually appear.
For example, I mistakenly filed #142, because I thought that LogFox had a bug that it could not find the crash.
The text was updated successfully, but these errors were encountered: