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
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.
Additional Information
Status version: release build 2.32.0 (20241210103906)
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 🙏
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.
Additional Information
LOG for Android : (first occurrence of the issue was at 18:09 (UTC+2)) Status-debug-logs.zip
logcat.txt
The text was updated successfully, but these errors were encountered: