Call setupDirs before writeResolv in gateway init and start (#40)

On a normal app launch (setup already complete), setupDirs was never
called. If Android cleared the files directory after an upgrade, the
config/ directory was missing when writeResolv ran.

Now both init() and start() call setupDirs() first, matching the
bootstrap flow. The Kotlin-side writeResolvConf() also calls
setupDirectories() internally as a safety net.

Co-Authored-By: Mithun Gowda B <mithungowda.b7411@gmail.com>

Author: mithun50

flutter_app/lib/services/gateway_service.dart

@@ -41,8 +41,10 @@ class GatewayService {
 
     final alreadyRunning = await NativeBridge.isGatewayRunning();
     if (alreadyRunning) {
-      // Refresh resolv.conf so DNS keeps working even if the file was
-      // deleted or corrupted while the app was in the background.
+      // Ensure directories exist — Android may have cleared them after
+      // an upgrade or while the app was in the background (#40).
+      try { await NativeBridge.setupDirs(); } catch (_) {}
+      // Refresh resolv.conf so DNS keeps working.
       await NativeBridge.writeResolv();
       // Write allowCommands config so the next gateway restart picks it up,
       // and in case the running gateway supports config hot-reload.
@@ -137,6 +139,8 @@ fs.writeFileSync(p, JSON.stringify(c, null, 2));
     ));
 
     try {
+      // Ensure directories exist — Android may have cleared them (#40).
+      await NativeBridge.setupDirs();
       // Refresh resolv.conf before every start so DNS always works.
       await NativeBridge.writeResolv();
       await _writeNodeAllowConfig();