fix(native): stop implicit dev server startup in setupEmulator

[AshrefRaj]

This fixes issue #204 where setupEmulator commands would leave a background dev server running silently. Added an optional timed prompt (10s) for IP updates instead.

[mayankmahavar1mg]

Claude review

Issue	Severity
promptUserWithTimeout — use existing promptUser instead	Must fix
saveConfig receives wrong shape from iOS (config vs { ios })	Must fix
handlePostSetupSteps hardcodes step keys it doesn't own	Must fix
initializeConfig differs from buildAppAndroid version — document clearly	Should fix
require mixed with import in setupEmulatorIos.js	Minor

[mayankmahavar1mg]

We should use exisiting prompt user inplace of timeout.

few functions are used in buildApp script as well, where they take care of specific environment, same utility function will not work there, so either we add as todo comment or handle them as well

Reading and writing file takes time , try minimise this.

[mayankmahavar1mg]

Why removed WEBVIEW_CONFIG ?

we are passing it further in different function.

[mayankmahavar1mg]

is this also going to save updated config?
we just save config above at line 54
we should have updated config and save them all in one go
move this section before save config and then call save config with updated config

[mayankmahavar1mg]

can we use existing prompt function

[mayankmahavar1mg]

prompt should be asked upfront, then only we should read config and all

[mayankmahavar1mg]

we are reading file again, we should pass related config

[Mrsandeep27]

Nice factoring — pulling initializeConfig/saveConfig/handlePostSetupSteps into utils.js removes duplication, and moving dev-server start behind an opt-in prompt addresses #204.

A few observations worth considering before merge:

1. handlePostSetupSteps reads + parses config.json twice (once in saveConfig, once here for port). If the file was just written by saveConfig, you already have the updated object in memory — passing it through would avoid another round-trip and a narrow window where a concurrent edit could desync the two reads.

2. iOS and Android save flow are now out of sync. In androidSetup.js the flow is saveConfig(...) → handlePostSetupSteps(...), but in setupEmulatorIos.js it's progress.start("saveConfig") → validateAndCompleteConfig → saveConfig(...) → complete. Worth confirming that the iOS path actually persists WEBVIEW_CONFIG before handlePostSetupSteps reads from disk for port lookup.

3. Default timeout of 10s for promptUserWithTimeout is short. On a first-time setup a user is unlikely to read the prompt, decide, and answer in 10 seconds. Silently defaulting to "n" is safe for #204 but surprising UX — consider 30s, or no timeout when stdin is a TTY.

4. startServerBackground() with the current readline still open. rl is created at module load in utils.js. After the last promptUserWithTimeout, rl is never closed, so the process will hang on exit even when the user selects "n" (skip server). Calling rl.close() at the end of handlePostSetupSteps (or in a finally in each setup entry point) would let the command exit cleanly, which is exactly what #204 is asking for.

5. Minor: const { getLocalIPAddress, ... } = require("./setupServer.js") in setupEmulatorIos.js mixes require with ESM import at the top of the file. The Android file uses an import for setupServer.js helpers — worth making them consistent.

Overall direction looks right. Fixing #4 is probably the most important bit — otherwise the server setup skips launching dev server but the command still doesn't exit.