-
Type:
Bug
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: 2.0, 2.1, 2.2
-
None
-
FLW Sprint 25, FLW Sprint 26, FLW Sprint 27, FLW Sprint 28
-
FLW Mobile App
-
Prod
As an ASHA user,
I want the app to run smoothly without unexpected crashes,
so that I can complete my tasks without interruption and trust the app for my needs.
Acceptance Criteria:
- The app no longer crashes during normal usage scenarios previously reported by users.
- Crash logs should be collected and analyzed to identify root causes of failures.
- The development team implements fixes for all reproducible crash scenarios.
- QA team should test and confirm that the app remains stable after fixes.
Note: Add a new Task for every crash form crashlytics with the description of the crash and details of crash to this story.
- relates to
-
FLW-403 App crash in view ANC after edit ANC visit
-
- Closed
-
-
FLW-367 Crashalytics Issue 14
-
- Closed
-
-
FLW-364 Crashalytics Issue 11
-
- Closed
-
-
FLW-365 Crashalytics issue 12
-
- Closed
-
-
FLW-366 Crashalytics Issue 13
-
- Closed
-
-
FLW-368 Crashalytics Issue 15
-
- Closed
-
-
FLW-371 Production App Crashed
-
- Closed
-
-
FLW-369 FLW_Niramaya II _ Application crash issue post latest update from play store
-
- Closed
-
-
FLW-370 FLW_Xushrukha_Application crashed post update from Play Store
-
- Closed
-
-
FLW-333 Play Console crash Issue 1
-
- Closed
-
-
FLW-350 Crashalytics issue 6
-
- Closed
-
-
FLW-351 Crashalytics issue 7
-
- Closed
-
-
FLW-334 Play Console crash Issue 2
-
- Closed
-
-
FLW-335 Play Console crash Issue 3
-
- Closed
-
-
FLW-336 Play Console crash Issue 4
-
- Closed
-
-
FLW-337 Play Console crash Issue 5
-
- Closed
-
-
FLW-360 Crashalytics Issue 8
-
- Closed
-
-
FLW-361 Crashalytics Issue 9
-
- Closed
-
-
FLW-362 Crashalytics Issue 10
-
- Closed
-