I build mobile apps, and everything they need to ship.

Problem

After AppsAirPush installed an update and reloaded the app, Android still ran the previous JavaScript. People only saw the update after killing and reopening the app.

Cause

React Native 0.80's DefaultReactHost builds its JSBundleLoader once per process, from a fixed path. The SDK's in-place reload re-ran that same loader. iOS re-reads bundleURL on every reload, which is why it never showed the bug.

Fix

Build the release ReactHostImpl by hand, with a loader that asks for the bundle path every time JavaScript loads. Debug builds keep the default host. It compiles clean and goes out with the next Android release.

object : JSBundleLoader() {
  override fun loadScript(delegate: JSBundleLoaderDelegate): String {
    val path = AppsAirPushModule.getJSBundleFile(applicationContext)
    if (path.startsWith("assets://")) {
      delegate.loadScriptFromAssets(applicationContext.assets, path, true)
    } else {
      delegate.loadScriptFromFile(path, path, false)
    }
    return path
  }
}

Takeaway When a framework caches something, find out exactly when it reads it.

Problem

On the KIA-15 live map, BMTC's route path arrives a moment after the map. On iOS with the New Architecture it was never drawn, and neither was the radius circle once the location came in.

Cause

In react-native-maps on iOS, polylines and circles are only drawn if they exist when the map is created. Anything added later is ignored. A map created off-screen has the same problem until its camera moves.

Fix

Treat a new route or a new circle as a new map, by keying the MapView on both. On Home, the map is only created once it scrolls into view.

<MapView
  // a new route or circle means a new map
  key={`${route?.routeId ?? 'no-route'}|${center ? radius : 'no-circle'}`}
  ref={map}
  style={styles.fill}
>

Takeaway If a native view ignores updates, make the update a remount.

Problem

I added driver columns to kia_15_routes and uploaded the schema file before the ALTER had run. For about a minute, every read of that table failed.

Cause

The API's query builder selects every column listed in the schema file, even for a bare *. One column in the file that wasn't in the table made every query invalid.

Fix

Reverted the file at once, ran the migration, then deployed again. The deploy notes now say: migration first, code second, and compare the live file with the local original before overwriting it.

-- 1. the database first
ALTER TABLE `kia_15_routes`
  ADD COLUMN `driver_id`   VARCHAR(20)  NULL AFTER `profilepic`,
  ADD COLUMN `driver_name` VARCHAR(150) NULL AFTER `driver_id`;
-- 2. then tableSchema.php, 3. then the portal

Takeaway Order a deploy so that every step in between still works.

Problem

Medicine search runs in Dart when the phone is offline and in PHP when it isn't. Two copies of text-matching rules drift apart the moment one of them gets a fix.

Fix

PHP is the reference. A script runs it over a list of real queries and writes the expected results to a file, and flutter test replays every case against the Dart code. Udyoga Alerts does the same for listing status: one date rule, two languages, 726 cases.

php backend/tests/make_search_vectors.php   # PHP writes the expected results
flutter test                                # Dart has to match every case

Takeaway If logic must live in two places, let a test be the source of truth.

Problem

CodeMirror styles itself by injecting <style> tags. In the Android build the text area was blank and only the line numbers showed.

Cause

Tauri adds a nonce to style-src in the app's Content Security Policy. Once a nonce is present, browsers ignore 'unsafe-inline', so every style CodeMirror injected was blocked.

Fix

Stop Tauri changing style-src (scripts keep their nonces), and add a self-test step that checks the editor really renders text.

"security": {
  "dangerousDisableAssetCspModification": ["style-src"]
}

Takeaway Test what the user sees, not just what loaded.

Cause

iOS 27 requires the UIScene lifecycle. Deployment targets below iOS 15 became build errors. And Simulator.app is now DeviceHub.app, which the React Native and Expo CLIs didn't know about.

Fix

A postinstall script in all sixteen React Native and Expo apps patches the CLI so it finds the new simulator. Every Podfile lifts pods to iOS 15.1. A SceneDelegate starts React Native in a window scene, done first for the three transit apps.

installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
    current = config.build_settings['IPHONEOS_DEPLOYMENT_TARGET']
    if current && current.to_f < minimum_ios.to_f
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = minimum_ios
    end
  end
end

Takeaway Fix it once, in a file every project shares.