My work on Khedmah Delivery includes maintaining customer, driver, and vendor React Native apps, improving error handling, investigating production issues, and monitoring releases. This study connects that experience with a practical crash-debugging workflow: find an actionable report, reproduce the failing journey, fix the cause, and check the released version. The workflow below is guidance informed by that work, rather than a reconstruction of a single incident.
01 / THE CHALLENGE
Delivery apps combine authentication, ordering, payments, notifications, and live tracking. A failure during startup or an order update can leave a user unsure whether to retry, wait, or reopen the app. A successful development build does not establish that these journeys work on customers’ devices.
The first challenge is identifying the kind of failure. An unhandled JavaScript exception, a native crash, a frozen interface, and a handled API error need different evidence. Treating them all as crashes can hide the actual problem and make stability reports misleading.
02 / THE APPROACH
In Khedmah Delivery, my responsibilities included API and error-state handling, production monitoring, and suitable hotfixes. For a crash investigation, I would use the following sequence to turn those responsibilities into a reviewable fix.
Validate crash reporting in a controlled test build and confirm that reports identify the correct app version and platform. Keep test events separate from production analysis. An empty dashboard can mean missing telemetry; it does not establish that the app has no failures.
Release stack traces may be obfuscated. Preserve the JavaScript source map matching the shipped bundle, including the correct OTA bundle when relevant. Native Android mapping files and Apple debug symbols serve different purposes. Check the reporting integration’s support rather than assuming that native symbol uploads also resolve JavaScript frames.
Record the affected release, device, operating system, screen, and last meaningful action. For an ordering app, useful checks include expired authentication, a slow initial request, missing response fields, and returning from the background. These are investigation scenarios, not a claim that every one caused a Khedmah incident. Use sanitized diagnostic context without payment details or access tokens.
A failed request should leave the screen in a defined state. Clear loading indicators, handle absent data deliberately, and show a useful recovery action. Avoid automatically replaying order or payment submissions: first establish whether the server accepted the original operation and whether the API supports safe retries.
A render error boundary can provide a fallback for supported React rendering failures, but it cannot catch every asynchronous error or native crash. Handle request failures where they occur, investigate native failures with platform evidence, and keep enough diagnostic information to understand an unexpected condition instead of silently swallowing it.
Repeat the failing journey in a release build, then check nearby flows such as login, cart updates, checkout, and notifications. After rollout, review the affected version and whether the same issue recurs. Use the supported release mechanism for the change; native code and dependency changes can require a new store build.
03 / WORKFLOW
Identify the failure type and affected app release.
Collect readable stack traces and sanitized journey context.
Reproduce the issue with matching build and network conditions.
Implement the fix and verify recovery without duplicate operations.
Test the release build and monitor recurrence after rollout.
04 / OUTCOMES
Crash-free sessions and crash-free users are different measures. Any before-and-after comparison needs a consistent metric, a defined observation window, release adoption, and enough traffic to be meaningful. A short crash-free window does not guarantee future stability. This study describes the investigation and validation process without assigning it a new numerical improvement.
CONTINUE EXPLORING
Share the affected platform, app version, and failing journey.
Discuss a React Native crash fix