Software Engineer in E-commerce: Fixing Mobile App Crashes
Investigate a sudden post-release crash rate spike in an e-commerce mobile app and determine the correct engineering mitigation.
Context
You are a mobile Software Engineer at an e-commerce app company. Following the rollout of app version 4.2.0 yesterday, the Google Play Store crash rate jumped to 4.2%, well above the team's critical threshold of 0.5%. The product lead wants to roll back the newly introduced payment gateway SDK immediately, arguing that checkout drop-offs spiked at the exact same hour. The release lead has asked you to evaluate the issue and deliver an action plan before the end of the day.
Your Task
Provide your technical assessment and plan in three sections:
- Recommendation
- Impact
- Implementation Plan
Available Data
App Version Telemetry (Past 48 Hours)
| Version | Active Installs | Crash-Free Sessions | Main Reported Exception | Top Device OS affected |
|---|---|---|---|---|
| v4.1.8 | 450,000 | 99.6% | NullPointerException (ProductCard) | Android 12, 13, 14 |
| v4.2.0 | 120,000 | 95.8% | OutOfMemoryError (BitmapFactory) | Android 9, 10, 11 |
Crash reports for v4.2.0 show that 91% of exceptions are fatal `OutOfMemoryError` instances occurring during background image pre-fetching in feed carousels, specifically on low-memory devices running Android 11 and older. Concurrently, payment gateway timeouts on v4.2.0 increased by 15%, but with zero fatal crash logs originating from the payment SDK library.