@rubytech/create-maxy 1.0.778 → 1.0.779

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.778",
+  "version": "1.0.779",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/scripts/wifi-provision.sh

@@ -332,12 +332,27 @@ handle_connect_requests() {
     nmcli device set wlan0 managed yes 2>/dev/null
     sleep 2
 
+    # NM's wifi-list cache is empty immediately after wlan0 is handed back
+    # from hostapd, so `nmcli device wifi connect` reports "No network with
+    # SSID 'X' found" even when hostapd's pre-AP scan saw it. Trigger a
+    # rescan and poll until the target SSID appears in the cache (or 15s
+    # timeout) before attempting the connect.
+    nmcli device wifi rescan 2>/dev/null || true
+    local rescan_elapsed=0
+    while [ "$rescan_elapsed" -lt 15 ]; do
+      if nmcli -t -f SSID device wifi list 2>/dev/null | grep -Fxq "$target_ssid"; then
+        break
+      fi
+      sleep 1
+      rescan_elapsed=$((rescan_elapsed + 1))
+    done
+    log "rescan-before-connect: target=\"${target_ssid}\" elapsed=${rescan_elapsed}s"
+
     # Attempt WiFi connection. Capture exit code before || true so we
     # get nmcli's actual exit status, not the unconditional 0 from || true.
     local connect_output connect_exit
     # `--wait` / `-w` is a top-level nmcli option (must precede the
-    # subcommand), not an argument to `device wifi connect`. Putting it
-    # after the subcommand fails with "invalid extra argument '--wait'".
+    # subcommand), not an argument to `device wifi connect`.
     connect_output=$(nmcli --wait 30 device wifi connect "$target_ssid" password "$target_password" 2>&1)
     connect_exit=$?