Tapping "Mark all as read" icon in upper right corner freezes or even crashes the app in version 1.0.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the upper-right “Mark all as read” action and the code that updates warnings in the “All warnings” and place views. Reproduce with multiple warnings, including ones already read, and inspect the app logs or warning update flow for the freeze or crash. Done means marking all warnings read leaves the app responsive and does not crash.
Written by the indexing model from the issue text.
Description
Describe the bug
When there are multiple warnings either for a single place or in the "All warnings" view, and I tap the "mark all as read" icon in the upper right corner of the screen, the app becomes unresponsive or even crashes.
To Reproduce
Steps to reproduce the behavior:
- More than 1 warning in the "All warnings" view or for one of your places. They can be already read.
- Tap the "Mark all as read" button in the upper right corner
- The app will become unresponsive for a few seconds. Scrolling or tapping on any of the warnings will not work.
- If you tap on a warning or the back button in the upper left corner the app may also crash with a popup showing "FOSS Warn isn't responding" and the options "Close app", "Wait", and "Show details"
Expected behavior
The app should remain responsive and not crash.
Device :
- Device: Pixel 6
- OS: GrapheneOS (Android 16, latest security patch)
- App-version: 1.0.0.
- Battery optimization: false
- push distributor is Sunup with default server "push.services.mozilla.com"
I would have shared the log but when clicking "Open Logfile viewer" I now only get:
Error: Can not read logfile. No logfile to display
- Dominant language
- Dart
- Stars
- 259
- Forks
- 13
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nucleus-ffm/foss_warn
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nucleus-ffm/foss_warn#330 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
nucleus-ffm/foss_warn#286 · 3 reactions ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 56/100
nucleus-ffm/foss_warn#329 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
nucleus-ffm/foss_warn#325 · 1 comment · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
nucleus-ffm/foss_warn#324 · 2 comments ·
All issues in nucleus-ffm/foss_warn
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 4 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 3 days
-
area-clientside-dartpad
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
'图片收藏'功能无法滑动Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
venera-app/venera-prime#50 ·