xgem-cli 2.0.0-alpha.5 → 2.0.0-alpha.7

package/README.md

@@ -115,7 +115,7 @@ engine (`lib-win/`, driven by `bin/xgem.js`) so `npm install -g xgem-cli` actual
 in `cmd.exe`/PowerShell, no WSL required.
 
 What works on Windows: `init`/`add`/`run`/`terminate`, `doctor`, the git workflow
-commands, and Flutter builds for **APK and Windows desktop** targets. What doesn't:
+commands, and Flutter builds for **APK, App Bundle, and Windows desktop** targets. What doesn't:
 Flutter **iOS/macOS** builds — Xcode has no Windows equivalent, so `xgem doctor ios`
 explains that plainly instead of pretending. `swift` isn't offered as a framework
 choice on Windows for the same reason. If you're inside WSL, none of this applies —

package/bin/xgem.js

@@ -164,7 +164,7 @@ function printFrameworkHelp(fw) {
     }
     if (fw === 'flutter') {
         console.log('');
-        logInfo("Flutter builds on Windows support APK and Windows desktop targets. Run 'xgem doctor ios' for why iOS/macOS aren't available here.");
+        logInfo("Flutter builds on Windows support APK, App Bundle, and Windows desktop targets. Run 'xgem doctor ios' for why iOS/macOS aren't available here.");
     }
     console.log('');
 }

package/lib/flutter.sh

@@ -105,7 +105,7 @@ _flutter_build_ios() {
     mkdir -p "$archive_dir"
     archive_path="$archive_dir/Runner $archive_time.xcarchive"
 
-    if ! xcodebuild -workspace ios/Runner.xcworkspace \
+    local -a archive_cmd=(xcodebuild -workspace ios/Runner.xcworkspace \
         -scheme Runner \
         -sdk iphoneos \
         -configuration Release \
@@ -113,10 +113,35 @@ _flutter_build_ios() {
         -archivePath "$archive_path" \
         "BUILD_NUMBER=$build_number" \
         "MARKETING_VERSION=$build_name" \
-        -allowProvisioningUpdates > "$log_file" 2>&1; then
-        log_error "Archive FAILED"
-        cat "$log_file"
-        die "xcodebuild archive failed" "$?"
+        -allowProvisioningUpdates)
+
+    if ! "${archive_cmd[@]}" > "$log_file" 2>&1; then
+        # Static pre-checks can miss cases the real SwiftPM resolution
+        # catches (different plugin manifest layouts, symlinked package
+        # dirs, etc.) — Xcode's own error is authoritative, so parse it
+        # directly and retry once before giving up.
+        local retry_required
+        retry_required=$(ios_parse_required_from_build_log "$log_file")
+        if [ -n "$retry_required" ]; then
+            log_warn "Archive failed on a SwiftPM platform-version mismatch Xcode reports directly (requires iOS $retry_required). Retrying with that applied..."
+            ios_pbxproj_patch_deployment_target "$retry_required" "."
+            ios_regenerate_generated_package "."
+            local regenerated
+            regenerated=$(ios_generated_package_target ".")
+            if [ -z "$regenerated" ] || _ios_ver_lt "$regenerated" "$retry_required"; then
+                ios_patch_generated_package_target "$retry_required" "."
+            fi
+
+            if ! "${archive_cmd[@]}" > "$log_file" 2>&1; then
+                log_error "Archive FAILED again after retry"
+                cat "$log_file"
+                die "xcodebuild archive failed" "$?"
+            fi
+        else
+            log_error "Archive FAILED"
+            cat "$log_file"
+            die "xcodebuild archive failed" "$?"
+        fi
     fi
     log_success "Archive created at: $archive_path"
 
@@ -164,20 +189,21 @@ cmd_flutter_build() {
     echo ""
     echo "Select Target Platform:"
     echo "1) APK (Android)"
-    echo "2) iOS"
-    echo "3) macOS"
-    echo "4) Windows"
-    echo "5) Linux"
+    echo "2) App Bundle (Android, .aab — required for Play Store uploads)"
+    echo "3) iOS"
+    echo "4) macOS"
+    echo "5) Windows"
+    echo "6) Linux"
     local platform_choice
-    read -r -p "Choose [1-5]: " platform_choice
-    if ! [[ "$platform_choice" =~ ^[1-5]$ ]]; then
+    read -r -p "Choose [1-6]: " platform_choice
+    if ! [[ "$platform_choice" =~ ^[1-6]$ ]]; then
         die "Invalid platform choice '$platform_choice'."
     fi
 
     local mode="--release"
     [[ "$is_release" == "n" || "$is_release" == "N" ]] && mode="--debug"
 
-    if [ "$platform_choice" -eq 2 ]; then
+    if [ "$platform_choice" -eq 3 ]; then
         _flutter_build_ios "$build_name" "$build_number" "$mode"
         return
     fi
@@ -185,9 +211,10 @@ cmd_flutter_build() {
     log_info "Initializing Flutter Build ($mode) for version $build_name+$build_number..."
     case $platform_choice in
         1) flutter build apk "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
-        3) flutter build macos "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
-        4) flutter build windows "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
-        5) flutter build linux "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
+        2) flutter build appbundle "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
+        4) flutter build macos "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
+        5) flutter build windows "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
+        6) flutter build linux "$mode" "--build-name=$build_name" "--build-number=$build_number" ;;
     esac
 }
 

package/lib/ios.sh

@@ -103,9 +103,11 @@ ios_required_spm_deployment_target() {
     local packages_dir="$project_dir/ios/Flutter/ephemeral/Packages/.packages"
 
     if [ -d "$packages_dir" ]; then
-        find "$packages_dir" -maxdepth 4 -name "Package.swift" -print0 2>/dev/null \
-            | xargs -0 grep -ohE '\.iOS\(\.v[0-9_]+\)' 2>/dev/null \
-            | grep -oE '[0-9]+(_[0-9]+)?' | tr '_' '.' \
+        # -L: per-plugin dirs here are frequently symlinks into pub-cache;
+        # without -L, find silently skips descending into them.
+        find -L "$packages_dir" -maxdepth 4 -name "Package.swift" -print0 2>/dev/null \
+            | xargs -0 grep -ohE '\.iOS\(\.v[0-9_]+\)|\.iOS\("[0-9.]+"\)' 2>/dev/null \
+            | grep -oE '[0-9]+(\.[0-9]+)?(_[0-9]+)?' | tr '_' '.' \
             | sort -g | tail -1
         return 0
     fi
@@ -142,9 +144,12 @@ for pkg in data.get("packages", []):
     except OSError:
         continue
 
-    for m in re.finditer(r"\.iOS\(\.v(\d+(?:_\d+)?)\)", content):
+    # Both SPM syntaxes: enum .iOS(.v15) and string .iOS("15.0") (the form
+    # Flutter's own generator uses).
+    for m in re.finditer(r'\.iOS\(\.v(\d+(?:_\d+)?)\)|\.iOS\("(\d+(?:\.\d+)?)"\)', content):
+        raw = m.group(1) or m.group(2)
         try:
-            fv = float(m.group(1).replace("_", "."))
+            fv = float(raw.replace("_", "."))
         except ValueError:
             continue
         max_target = max(max_target, fv)
@@ -188,21 +193,40 @@ ios_generated_package_swift_path() {
         echo "$guess"
         return 0
     fi
-    find "$project_dir/ios" -maxdepth 6 -type f -name "Package.swift" \
+    # -L: plugin package directories under ephemeral/Packages/.packages are
+    # frequently symlinks into the pub-cache; a plain find silently skips
+    # symlinked directories instead of descending into them.
+    find -L "$project_dir/ios" -maxdepth 6 -type f -name "Package.swift" \
         -path "*FlutterGeneratedPluginSwiftPackage*" 2>/dev/null | head -1
 }
 
+# SPM's SupportedPlatform.iOS accepts two syntaxes: the enum form .iOS(.v15)
+# for the fixed known-version cases, and a string form .iOS("15.0") for
+# arbitrary versions — Flutter's own code generator uses the *string* form
+# for FlutterGeneratedPluginSwiftPackage, not the enum form. Matching only
+# the enum form (as an earlier version of this function did) means the
+# patch step silently never matches anything on a real generated package:
+# sed finds no match, writes back an identical file, and "succeeds" while
+# doing nothing.
+_ios_extract_platform_version() {
+    grep -oE '\.iOS\(\.v[0-9_]+\)|\.iOS\("[0-9.]+"\)' | head -1 \
+        | grep -oE '[0-9]+(\.[0-9]+)?(_[0-9]+)?' | tr '_' '.'
+}
+
 ios_generated_package_target() {
     local project_dir=${1:-.}
     local pkg
     pkg=$(ios_generated_package_swift_path "$project_dir")
     [ -n "$pkg" ] && [ -f "$pkg" ] || return 1
-    grep -oE '\.iOS\(\.v[0-9_]+\)' "$pkg" | head -1 | grep -oE '[0-9_]+' | tr '_' '.'
+    _ios_extract_platform_version < "$pkg"
 }
 
 # Last-resort workaround for the still-open upstream desync bug: directly
 # patch the generated package's platform declaration. Always logged loudly
 # — this is a documented workaround for a known bug, never a silent hack.
+# Writes the string form (.iOS("15.0")) since that's what Flutter's own
+# generator uses in this file — matching its existing convention rather
+# than introducing a different syntax.
 ios_patch_generated_package_target() {
     local new_target=$1
     local project_dir=${2:-.}
@@ -214,10 +238,9 @@ ios_patch_generated_package_target() {
     fi
 
     log_warn "Working around known Flutter SPM bug (flutter/flutter#186804): the regenerated package still doesn't match your deployment target, so patching it directly."
-    local token=${new_target//./_}
     local tmp
     tmp=$(mktemp)
-    sed -E "s/\.iOS\(\.v[0-9_]+\)/.iOS(.v${token})/g" "$pkg" > "$tmp"
+    sed -E "s/\.iOS\(\.v[0-9_]+\)/.iOS(\"${new_target}\")/g; s/\.iOS\(\"[0-9.]+\"\)/.iOS(\"${new_target}\")/g" "$pkg" > "$tmp"
     mv "$tmp" "$pkg"
     log_success "Patched generated package platform to iOS $new_target."
 }
@@ -229,6 +252,21 @@ ios_regenerate_generated_package() {
     ( cd "$project_dir" && flutter pub get )
 }
 
+# ios_parse_required_from_build_log <log_file>
+# Statically scanning plugin manifests to predict the required deployment
+# target has proven unreliable in practice (plugin authors structure SPM
+# manifests differently, package dirs can be symlinks, etc.). Xcode itself
+# always computes this correctly and states it plainly in its own error:
+# "requires minimum platform version X for the iOS platform". Parsing that
+# directly is the authoritative fallback when the static pre-check misses
+# something.
+ios_parse_required_from_build_log() {
+    local log_file=$1
+    grep -oE "requires minimum platform version [0-9]+(\.[0-9]+)?" "$log_file" 2>/dev/null \
+        | grep -oE '[0-9]+(\.[0-9]+)?' \
+        | sort -g | tail -1
+}
+
 ios_known_issue_check() {
     log_warn "Known upstream issue (flutter/flutter#186804, #189422, #162072): FlutterGeneratedPluginSwiftPackage's deployment target can desync from your app's IPHONEOS_DEPLOYMENT_TARGET — independently, even when the app's own target is already high enough. Currently open — xgem detects and works around it automatically below."
 }

package/lib/version.sh

@@ -1,7 +1,7 @@
 #!/bin/bash
 # xgem version info.
 
-XGEM_VERSION="2.0.0-alpha.5"
+XGEM_VERSION="2.0.0-alpha.7"
 
 print_version() {
     echo "xgem $XGEM_VERSION"

package/lib-win/flutter.js

@@ -67,9 +67,10 @@ async function cmdBuild() {
 
     console.log('\nSelect Target Platform:');
     console.log('1) APK (Android)');
-    console.log('2) Windows');
+    console.log('2) App Bundle (Android, .aab — required for Play Store uploads)');
+    console.log('3) Windows');
     console.log('(iOS/macOS require a Mac; Linux desktop can\'t be cross-built from Windows.)');
-    const platformChoice = await prompt('Choose [1-2]');
+    const platformChoice = await prompt('Choose [1-3]');
 
     const mode = (isRelease === 'n') ? '--debug' : '--release';
     const buildArgs = [`--build-name=${buildName}`, `--build-number=${buildNumber}`];
@@ -78,6 +79,9 @@ async function cmdBuild() {
         logInfo(`Building APK (${mode})...`);
         flutter(['build', 'apk', mode, ...buildArgs]);
     } else if (platformChoice === '2') {
+        logInfo(`Building App Bundle (${mode})...`);
+        flutter(['build', 'appbundle', mode, ...buildArgs]);
+    } else if (platformChoice === '3') {
         logInfo(`Building Windows desktop app (${mode})...`);
         flutter(['build', 'windows', mode, ...buildArgs]);
     } else {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xgem-cli",
-  "version": "2.0.0-alpha.5",
+  "version": "2.0.0-alpha.7",
   "description": "Framework-aware automation CLI: scaffolds and runs clean/build/dev scripts per project type, an environment doctor, a SwiftPM-aware iOS build engine, and a git workflow helper. Runs natively on macOS, Linux, and Windows.",
   "bin": {
     "xgem": "bin/xgem.js"