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

Activity tab becomes empty after auto-refresh or app backgrounding (random bug) #21792

Open
Horupa-Olena opened this issue Dec 10, 2024 · 2 comments

Comments

@Horupa-Olena
Copy link

Horupa-Olena commented Dec 10, 2024

Bug Report

Problem

The Activity tab occasionally becomes empty after the app performs an auto-refresh or is left in the background for some time. The transactions reappear only after logging out and logging back in.

Expected behavior

The Activity tab should consistently display the transaction history, regardless of auto-refresh or backgrounding.

Actual behavior

The Activity tab becomes empty after an auto-refresh or when the app is reopened from the background. Transactions reappear only after logging out and logging back in.

Image

Additional Information

  • Status version: release build 2.32.0 (20241210103906)
  • Operating System: Android, Grafana
  • Random bug, not consistently reproducible.

LOG for Android : (first occurrence of the issue was at 18:09 (UTC+2)) Status-debug-logs.zip
logcat.txt

@churik
Copy link
Member

churik commented Dec 10, 2024

Also was able to reproduce on my device (Graphene OS, Pixel 7A)

Status-debug-logs.zip

FILE.2024-12-10.18.13.09.mp4

@churik churik added this to the 2.32.0 milestone Dec 10, 2024
@smohamedjavid
Copy link
Member

From the original logcat posted in the issue description,

12-10 18:03:18.868 18720     0 E Go      : fatal error: concurrent map iteration and map write

we could see the crash happened in the status-go (in go-waku) a few seconds before the activity tab goes blank, it's the same crash that caused #21799. Maybe that's why the activity response is affected by it. I can not confirm the same as I couldn't able to reproduce it. But, I will check further.

However, The crash is fixed in #21815, and I see a mobile PR #21815 pointing to it. Please help us check using that PR build and let us know 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants