Fix a mobile app that works in development but crashes in release

The development build behaves normally, but an installed release closes immediately or fails on one screen. Development tooling can mask differences in configuration and timing.

Why this happens

Release builds may use different environment values, assets, native configuration and optimisation behaviour. A JavaScript exception and a native crash require different diagnostics.

Step-by-step solution

1. Reproduce with a release-like build and collect the relevant device and application logs. Identify whether the failure occurs before or after JavaScript starts.

2. Compare environment configuration and bundled assets with development. Verify that required native modules and permissions are included in the binary.

3. Reduce the failing path to a small reproducible case, then test the fix in the same build mode that failed.

Worked example

A release accidentally pointing to a laptop-only API can look like an application defect. Check the resolved public API origin before changing unrelated UI code.

Verify the fix

Install the rebuilt application cleanly and test the original failing path, offline behaviour and a warm restart. Do not rely solely on a successful simulator development session.

Prevent a repeat

Keep a release smoke-test checklist and preserve symbol or source-map information according to the crash-reporting setup.

Reference

Official documentation or standards guidance

An original Gistmax troubleshooting guide. Scenarios and sample values are illustrative; configuration depends on your software version and environment. Cover diagram: Gistmax Tutorials.