@invarn/cibuild 2.9.4 → 2.9.7

package/dist/src/yaml/steps/xcode-app-product.d.ts

@@ -1,90 +0,0 @@
-/**
- * Which built `.app` belongs to the scheme that was built.
- *
- * A simulator build leaves every application bundle its graph produced under
- * `DerivedData/Build/Products/<configuration>-<platform>/`, and a scheme that
- * builds a watchOS or tvOS companion alongside the app produces two. Taking
- * whichever one a directory scan reaches first is a coin toss, and it lands the
- * wrong way often enough to matter: a project whose scheme builds both an iOS
- * app and a watch companion exported the 588 KB watch bundle as the app under
- * test. The build was green, the artifact manifest was non-empty, and the
- * thing a user downloaded could not be installed on the device they built for.
- * That is worse than delivering nothing, because nothing is visibly wrong and
- * a plausible wrong answer is not.
- *
- * The scheme already knows. A shared `.xcscheme` lists its build entries with a
- * `BuildableName` whose extension IS the product type, and `buildForRunning`
- * separates what the scheme builds from what it merely references — a scheme
- * may list several `.app` entries it does not build, so "mentions an app" is
- * not the question and a check that asked it would pick just as badly.
- *
- * Where the scheme gives no answer this falls back rather than failing. A
- * project with no shared scheme at all is ordinary — plenty of them never
- * commit one — and those builds work. Absence of evidence is not evidence, so
- * the destination's own platform directory decides, and failing to resolve an
- * app is left to the caller's existing guard.
- *
- * The whole resolver runs on the machine that did the build, against the
- * products that build actually produced, so it needs nothing from the step
- * generator but the scheme name and the destination.
- */
-/** A built application bundle, as found under `Build/Products`. */
-export interface BuiltApp {
-    /** The `<configuration>-<platform>` directory, or `''` directly under Products. */
-    platform: string;
-    /** The bundle's own name, e.g. `MyApp.app`. */
-    name: string;
-    /** Absolute path to the bundle. */
-    path: string;
-}
-/**
- * The SDK suffix the Products directory carries for a given destination.
- *
- * `-destination 'generic/platform=iOS Simulator'` builds into
- * `Debug-iphonesimulator`; the watchOS and tvOS spellings are the ones that
- * matter here, because a companion target is exactly what produces the second
- * bundle this resolver exists to skip past.
- */
-export declare function platformSuffixForDestination(destination: string): string;
-/**
- * The application bundles a scheme's build action actually builds.
- *
- * `buildForRunning="NO"` entries are listed and not built. A scheme can carry
- * three `.app` entries that are API-compatibility testers in other containers
- * beside the one framework it really produces, so the attribute is the whole
- * filter rather than a refinement of one.
- *
- * Returns an empty list for a file that cannot be read or carries no build
- * action — no evidence, which the caller must not read as "builds no app".
- */
-export declare function runnableAppProducts(schemeXml: string | null): string[];
-/**
- * The bundle to export, given everything that was built and what the scheme
- * says it builds.
- *
- * In order: the scheme's own product on the destination's platform, the
- * scheme's own product anywhere, anything on the destination's platform,
- * anything at all. The last two are the no-shared-scheme path, and they are
- * what keeps a project that never committed a scheme building exactly as it
- * did before.
- */
-export declare function chooseAppProduct(apps: BuiltApp[], schemeProducts: string[], destination: string): BuiltApp | null;
-/**
- * The resolver as it runs on the build machine: dependency-free CommonJS,
- * written to a temp file and invoked with
- * `node <file> <productsDir> <projectPath> <scheme> <destination>`.
- *
- * It prints the chosen bundle's path and nothing else, and exits non-zero with
- * no output when it cannot choose — which is the signal for the caller's
- * existing scan to take over, so a machine without a usable node is no worse
- * off than before this existed.
- *
- * Kept as source text rather than bundled because the step ships a shell
- * script, not a module graph. The three functions above are the same rules in
- * testable form, and `xcode-app-product.test.ts` holds them to each other.
- *
- * Must contain no backtick and no dollar-brace: it is emitted into a bash
- * heredoc, and it is a TypeScript template literal on the way there.
- */
-export declare const APP_PRODUCT_RESOLVER_SOURCE: string;
-//# sourceMappingURL=xcode-app-product.d.ts.map

package/dist/src/yaml/steps/xcode-app-product.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"xcode-app-product.d.ts","sourceRoot":"","sources":["../../../../src/yaml/steps/xcode-app-product.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH,mEAAmE;AACnE,MAAM,WAAW,QAAQ;IACvB,mFAAmF;IACnF,QAAQ,EAAE,MAAM,CAAC;IACjB,+CAA+C;IAC/C,IAAI,EAAE,MAAM,CAAC;IACb,mCAAmC;IACnC,IAAI,EAAE,MAAM,CAAC;CACd;AAED;;;;;;;GAOG;AACH,wBAAgB,4BAA4B,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CAMxE;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,mBAAmB,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,GAAG,MAAM,EAAE,CAatE;AAED;;;;;;;;;GASG;AACH,wBAAgB,gBAAgB,CAC9B,IAAI,EAAE,QAAQ,EAAE,EAChB,cAAc,EAAE,MAAM,EAAE,EACxB,WAAW,EAAE,MAAM,GAClB,QAAQ,GAAG,IAAI,CAOjB;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,2BAA2B,EAAE,MAqIzC,CAAC"}

package/dist/src/yaml/steps/xcode-app-product.js

@@ -1,247 +0,0 @@
-/**
- * Which built `.app` belongs to the scheme that was built.
- *
- * A simulator build leaves every application bundle its graph produced under
- * `DerivedData/Build/Products/<configuration>-<platform>/`, and a scheme that
- * builds a watchOS or tvOS companion alongside the app produces two. Taking
- * whichever one a directory scan reaches first is a coin toss, and it lands the
- * wrong way often enough to matter: a project whose scheme builds both an iOS
- * app and a watch companion exported the 588 KB watch bundle as the app under
- * test. The build was green, the artifact manifest was non-empty, and the
- * thing a user downloaded could not be installed on the device they built for.
- * That is worse than delivering nothing, because nothing is visibly wrong and
- * a plausible wrong answer is not.
- *
- * The scheme already knows. A shared `.xcscheme` lists its build entries with a
- * `BuildableName` whose extension IS the product type, and `buildForRunning`
- * separates what the scheme builds from what it merely references — a scheme
- * may list several `.app` entries it does not build, so "mentions an app" is
- * not the question and a check that asked it would pick just as badly.
- *
- * Where the scheme gives no answer this falls back rather than failing. A
- * project with no shared scheme at all is ordinary — plenty of them never
- * commit one — and those builds work. Absence of evidence is not evidence, so
- * the destination's own platform directory decides, and failing to resolve an
- * app is left to the caller's existing guard.
- *
- * The whole resolver runs on the machine that did the build, against the
- * products that build actually produced, so it needs nothing from the step
- * generator but the scheme name and the destination.
- */
-/**
- * The SDK suffix the Products directory carries for a given destination.
- *
- * `-destination 'generic/platform=iOS Simulator'` builds into
- * `Debug-iphonesimulator`; the watchOS and tvOS spellings are the ones that
- * matter here, because a companion target is exactly what produces the second
- * bundle this resolver exists to skip past.
- */
-export function platformSuffixForDestination(destination) {
-    const d = String(destination ?? '').toLowerCase();
-    if (d.includes('watchos'))
-        return '-watchsimulator';
-    if (d.includes('tvos'))
-        return '-appletvsimulator';
-    if (d.includes('visionos') || d.includes('xros'))
-        return '-xrsimulator';
-    return '-iphonesimulator';
-}
-/**
- * The application bundles a scheme's build action actually builds.
- *
- * `buildForRunning="NO"` entries are listed and not built. A scheme can carry
- * three `.app` entries that are API-compatibility testers in other containers
- * beside the one framework it really produces, so the attribute is the whole
- * filter rather than a refinement of one.
- *
- * Returns an empty list for a file that cannot be read or carries no build
- * action — no evidence, which the caller must not read as "builds no app".
- */
-export function runnableAppProducts(schemeXml) {
-    if (!schemeXml)
-        return [];
-    const build = /<BuildAction\b[\s\S]*?<\/BuildAction>/.exec(schemeXml);
-    if (!build)
-        return [];
-    const products = [];
-    for (const entry of build[0].matchAll(/<BuildActionEntry\b([\s\S]*?)<\/BuildActionEntry>/g)) {
-        const attrs = entry[1];
-        if (!/buildForRunning\s*=\s*"YES"/.test(attrs))
-            continue;
-        for (const ref of attrs.matchAll(/BuildableName\s*=\s*"([^"]*)"/g)) {
-            if (ref[1].endsWith('.app'))
-                products.push(ref[1]);
-        }
-    }
-    return products;
-}
-/**
- * The bundle to export, given everything that was built and what the scheme
- * says it builds.
- *
- * In order: the scheme's own product on the destination's platform, the
- * scheme's own product anywhere, anything on the destination's platform,
- * anything at all. The last two are the no-shared-scheme path, and they are
- * what keeps a project that never committed a scheme building exactly as it
- * did before.
- */
-export function chooseAppProduct(apps, schemeProducts, destination) {
-    if (apps.length === 0)
-        return null;
-    const suffix = platformSuffixForDestination(destination);
-    const onPlatform = apps.filter((a) => a.platform.endsWith(suffix));
-    const named = (list) => list.find((a) => schemeProducts.includes(a.name)) ?? null;
-    return named(onPlatform) ?? named(apps) ?? onPlatform[0] ?? apps[0] ?? null;
-}
-/**
- * The resolver as it runs on the build machine: dependency-free CommonJS,
- * written to a temp file and invoked with
- * `node <file> <productsDir> <projectPath> <scheme> <destination>`.
- *
- * It prints the chosen bundle's path and nothing else, and exits non-zero with
- * no output when it cannot choose — which is the signal for the caller's
- * existing scan to take over, so a machine without a usable node is no worse
- * off than before this existed.
- *
- * Kept as source text rather than bundled because the step ships a shell
- * script, not a module graph. The three functions above are the same rules in
- * testable form, and `xcode-app-product.test.ts` holds them to each other.
- *
- * Must contain no backtick and no dollar-brace: it is emitted into a bash
- * heredoc, and it is a TypeScript template literal on the way there.
- */
-export const APP_PRODUCT_RESOLVER_SOURCE = String.raw `
-var fs = require('fs');
-var path = require('path');
-
-var productsDir = process.argv[2];
-var projectPath = process.argv[3] || '';
-var scheme = process.argv[4] || '';
-var destination = process.argv[5] || '';
-
-// Every .app under Products, both directly and one platform directory down,
-// which is where -derivedDataPath leaves them.
-function builtApps(dir) {
-  var out = [];
-  var entries = readDir(dir);
-  for (var i = 0; i < entries.length; i++) {
-    var entry = entries[i];
-    if (!entry.isDirectory()) continue;
-    var full = path.join(dir, entry.name);
-    if (/\.app$/.test(entry.name)) {
-      out.push({ platform: '', name: entry.name, path: full });
-      continue;
-    }
-    var inner = readDir(full);
-    for (var j = 0; j < inner.length; j++) {
-      if (inner[j].isDirectory() && /\.app$/.test(inner[j].name)) {
-        out.push({
-          platform: entry.name,
-          name: inner[j].name,
-          path: path.join(full, inner[j].name)
-        });
-      }
-    }
-  }
-  return out;
-}
-
-function readDir(dir) {
-  try {
-    return fs.readdirSync(dir, { withFileTypes: true });
-  } catch (err) {
-    return [];
-  }
-}
-
-// Shared schemes only. A scheme under xcuserdata belongs to one developer's
-// checkout and is not in the repository, which is also what xcodebuild -list
-// would see here.
-function sharedSchemeFiles(dir, depth, found) {
-  var entries = readDir(dir);
-  for (var i = 0; i < entries.length; i++) {
-    var entry = entries[i];
-    var full = path.join(dir, entry.name);
-    if (!entry.isDirectory()) {
-      if (/\.xcscheme$/.test(entry.name)) found.push(full);
-      continue;
-    }
-    if (entry.name === 'xcuserdata' || entry.name === 'node_modules') continue;
-    if (entry.name.charAt(0) === '.') continue;
-    var container = /\.(xcodeproj|xcworkspace)$/.test(entry.name);
-    if (depth > 0 || container || entry.name === 'xcshareddata' || entry.name === 'xcschemes') {
-      sharedSchemeFiles(full, depth - 1, found);
-    }
-  }
-  return found;
-}
-
-// The products a scheme's build action RUNS. buildForRunning="NO" entries are
-// listed and not built, so a scheme naming three .app targets it merely
-// references must not be read as building any of them.
-function runnableAppProducts(schemeFile) {
-  var xml;
-  try {
-    xml = fs.readFileSync(schemeFile, 'utf-8');
-  } catch (err) {
-    return [];
-  }
-  var build = /<BuildAction\b[\s\S]*?<\/BuildAction>/.exec(xml);
-  if (!build) return [];
-  var products = [];
-  var entryRe = /<BuildActionEntry\b([\s\S]*?)<\/BuildActionEntry>/g;
-  var entry;
-  while ((entry = entryRe.exec(build[0])) !== null) {
-    if (!/buildForRunning\s*=\s*"YES"/.test(entry[1])) continue;
-    var nameRe = /BuildableName\s*=\s*"([^"]*)"/g;
-    var ref;
-    while ((ref = nameRe.exec(entry[1])) !== null) {
-      if (/\.app$/.test(ref[1])) products.push(ref[1]);
-    }
-  }
-  return products;
-}
-
-function platformSuffix(dest) {
-  var d = String(dest).toLowerCase();
-  if (d.indexOf('watchos') !== -1) return '-watchsimulator';
-  if (d.indexOf('tvos') !== -1) return '-appletvsimulator';
-  if (d.indexOf('visionos') !== -1 || d.indexOf('xros') !== -1) return '-xrsimulator';
-  return '-iphonesimulator';
-}
-
-function endsWith(text, suffix) {
-  return suffix.length <= text.length && text.slice(text.length - suffix.length) === suffix;
-}
-
-var apps = builtApps(productsDir);
-if (apps.length === 0) process.exit(1);
-
-var schemeProducts = [];
-if (scheme) {
-  var searchRoot = path.dirname(path.resolve(projectPath || '.'));
-  var files = sharedSchemeFiles(searchRoot, 3, []);
-  for (var k = 0; k < files.length; k++) {
-    if (path.basename(files[k]) !== scheme + '.xcscheme') continue;
-    var named = runnableAppProducts(files[k]);
-    for (var n = 0; n < named.length; n++) {
-      if (schemeProducts.indexOf(named[n]) === -1) schemeProducts.push(named[n]);
-    }
-  }
-}
-
-var suffix = platformSuffix(destination);
-var onPlatform = apps.filter(function (a) { return endsWith(a.platform, suffix); });
-
-function firstNamed(list) {
-  for (var i = 0; i < list.length; i++) {
-    if (schemeProducts.indexOf(list[i].name) !== -1) return list[i];
-  }
-  return null;
-}
-
-var pick = firstNamed(onPlatform) || firstNamed(apps) || onPlatform[0] || apps[0];
-if (!pick) process.exit(1);
-process.stdout.write(pick.path);
-`;
-//# sourceMappingURL=xcode-app-product.js.map

package/dist/src/yaml/steps/xcode-app-product.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=xcode-app-product.test.d.ts.map

package/dist/src/yaml/steps/xcode-app-product.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"xcode-app-product.test.d.ts","sourceRoot":"","sources":["../../../../src/yaml/steps/xcode-app-product.test.ts"],"names":[],"mappings":""}

package/dist/src/yaml/steps/xcode-app-product.test.js

@@ -1,202 +0,0 @@
-/**
- * The simulator build must export the app the scheme builds.
- *
- * A project whose scheme builds an iOS app and a watchOS companion produces two
- * bundles under Products, and the step took whichever a directory scan reached
- * first. It reached the watch companion: a green build whose artifact manifest
- * held a 588 KB watch app and not the application the scheme is named after.
- * An empty manifest is visibly wrong; a plausible wrong answer is not, and a
- * watch companion is common enough that this would not have stayed rare.
- *
- * Two halves are tested here — the rules, directly, and the resolver script
- * that runs on the build machine, by running it against a real directory tree.
- * The second is what the step actually ships, so the first alone would be a
- * test of a description.
- */
-import { execFileSync } from 'node:child_process';
-import { mkdirSync, mkdtempSync, rmSync, writeFileSync } from 'node:fs';
-import { tmpdir } from 'node:os';
-import { join } from 'node:path';
-import { APP_PRODUCT_RESOLVER_SOURCE, chooseAppProduct, platformSuffixForDestination, runnableAppProducts, } from './xcode-app-product.js';
-const app = (platform, name) => ({
-    platform,
-    name,
-    path: `/tmp/Products/${platform}/${name}`,
-});
-/** A scheme whose build action runs `products`, with `listed` merely referenced. */
-const schemeXml = (products, listed = []) => {
-    const entry = (name, runs) => `
-    <BuildActionEntry buildForRunning = "${runs ? 'YES' : 'NO'}" buildForArchiving = "${runs ? 'YES' : 'NO'}">
-      <BuildableReference BuildableName = "${name}"></BuildableReference>
-    </BuildActionEntry>`;
-    return `<?xml version="1.0" encoding="UTF-8"?>
-<Scheme version = "1.7">
-  <BuildAction parallelizeBuildables = "YES">
-    <BuildActionEntries>${products.map((p) => entry(p, true)).join('')}${listed
-        .map((p) => entry(p, false))
-        .join('')}
-    </BuildActionEntries>
-  </BuildAction>
-</Scheme>
-`;
-};
-describe('platformSuffixForDestination', () => {
-    test('an iOS simulator destination names the iphonesimulator products', () => {
-        expect(platformSuffixForDestination('generic/platform=iOS Simulator')).toBe('-iphonesimulator');
-    });
-    test.each([
-        ['generic/platform=watchOS Simulator', '-watchsimulator'],
-        ['generic/platform=tvOS Simulator', '-appletvsimulator'],
-        ['generic/platform=visionOS Simulator', '-xrsimulator'],
-    ])('%s builds into %s', (destination, suffix) => {
-        expect(platformSuffixForDestination(destination)).toBe(suffix);
-    });
-    // The default matters: an unrecognised or empty destination must not send the
-    // resolver looking in a directory nothing built into.
-    test('an unreadable destination falls back to iOS rather than to nothing', () => {
-        expect(platformSuffixForDestination('')).toBe('-iphonesimulator');
-    });
-});
-describe('runnableAppProducts', () => {
-    test('reads the application bundles a scheme builds', () => {
-        expect(runnableAppProducts(schemeXml(['MyApp.app']))).toEqual(['MyApp.app']);
-    });
-    // A scheme can carry several .app entries that are compatibility testers in
-    // other containers, beside the one product it really builds. "Mentions an
-    // app" would pick just as badly as a directory scan does.
-    test('ignores an entry the scheme lists but does not build', () => {
-        const xml = schemeXml(['MyApp.app'], ['APITester.app', 'ObjCAPITester.app']);
-        expect(runnableAppProducts(xml)).toEqual(['MyApp.app']);
-    });
-    test('ignores a product that is not an application bundle', () => {
-        expect(runnableAppProducts(schemeXml(['MyLib.framework', 'MyApp.app']))).toEqual(['MyApp.app']);
-    });
-    // No evidence, which the caller must not read as "builds no app".
-    test.each([
-        ['a file that could not be read', null],
-        ['a scheme with no build action', '<?xml version="1.0"?><Scheme></Scheme>'],
-    ])('%s yields nothing rather than an answer', (_label, xml) => {
-        expect(runnableAppProducts(xml)).toEqual([]);
-    });
-});
-describe('chooseAppProduct', () => {
-    const IOS = 'generic/platform=iOS Simulator';
-    // The defect, in one assertion.
-    test('takes the scheme’s own app over a companion built beside it', () => {
-        const built = [
-            app('Debug-watchsimulator', 'Companion Watch App.app'),
-            app('Debug-iphonesimulator', 'MyApp.app'),
-        ];
-        expect(chooseAppProduct(built, ['MyApp.app'], IOS)?.name).toBe('MyApp.app');
-    });
-    // And it must not depend on scan order, which is the property the old code
-    // had no opinion about at all.
-    test('takes it whichever order the products were found in', () => {
-        const built = [
-            app('Debug-iphonesimulator', 'MyApp.app'),
-            app('Debug-watchsimulator', 'Companion Watch App.app'),
-        ];
-        expect(chooseAppProduct(built, ['MyApp.app'], IOS)?.name).toBe('MyApp.app');
-    });
-    // The single-target shape, which must not regress.
-    test('takes the only app there is', () => {
-        const built = [app('Debug-iphonesimulator', 'Contributions.app')];
-        expect(chooseAppProduct(built, ['Contributions.app'], IOS)?.name).toBe('Contributions.app');
-    });
-    // Absence of evidence is not evidence: a project with no shared scheme is
-    // ordinary, and those builds worked before this resolver existed.
-    test('still resolves an app when the scheme says nothing', () => {
-        const built = [
-            app('Debug-watchsimulator', 'Watch.app'),
-            app('Debug-iphonesimulator', 'MyApp.app'),
-        ];
-        expect(chooseAppProduct(built, [], IOS)?.name).toBe('MyApp.app');
-    });
-    test('falls back to any platform when none matches the destination', () => {
-        const built = [app('Debug-maccatalyst', 'MyApp.app')];
-        expect(chooseAppProduct(built, [], IOS)?.name).toBe('MyApp.app');
-    });
-    // The scheme outranks the platform directory, not the other way round: a
-    // watchOS-only scheme built for watchOS still gets its own product.
-    test('honours the scheme when the destination is the companion’s', () => {
-        const built = [
-            app('Debug-iphonesimulator', 'MyApp.app'),
-            app('Debug-watchsimulator', 'Watch.app'),
-        ];
-        const watch = 'generic/platform=watchOS Simulator';
-        expect(chooseAppProduct(built, ['Watch.app'], watch)?.name).toBe('Watch.app');
-    });
-    test('has no answer when nothing was built', () => {
-        expect(chooseAppProduct([], ['MyApp.app'], IOS)).toBeNull();
-    });
-});
-/**
- * The script the step actually ships, run against a real tree.
- *
- * The rules above are a description of what should happen; this is the thing
- * that happens. A resolver that is correct and unshippable — a syntax error, a
- * heredoc that swallows a character, a path assumption that only holds in the
- * unit test — passes every assertion above and delivers the watch app.
- */
-describe('the resolver script, as the build machine runs it', () => {
-    let root;
-    beforeEach(() => {
-        root = mkdtempSync(join(tmpdir(), 'cibuild-app-product-'));
-    });
-    afterEach(() => {
-        rmSync(root, { recursive: true, force: true });
-    });
-    const products = () => join(root, 'build', 'DerivedData', 'Build', 'Products');
-    function builtApp(platform, name) {
-        const dir = join(products(), platform, name);
-        mkdirSync(dir, { recursive: true });
-        writeFileSync(join(dir, 'Info.plist'), '<plist/>\n');
-    }
-    /** A shared scheme where Xcode puts one, inside the project bundle. */
-    function sharedScheme(project, name, xml) {
-        const dir = join(root, project, 'xcshareddata', 'xcschemes');
-        mkdirSync(dir, { recursive: true });
-        writeFileSync(join(dir, `${name}.xcscheme`), xml);
-    }
-    function resolve(scheme, destination = 'generic/platform=iOS Simulator') {
-        const script = join(root, 'resolver.cjs');
-        writeFileSync(script, APP_PRODUCT_RESOLVER_SOURCE);
-        try {
-            return execFileSync(process.execPath, [script, products(), join(root, 'MyApp.xcodeproj'), scheme, destination], { encoding: 'utf-8' });
-        }
-        catch {
-            return '';
-        }
-    }
-    test('exports the app under test, not the watch companion beside it', () => {
-        builtApp('Debug-watchsimulator', 'MyApp Watch App.app');
-        builtApp('Debug-iphonesimulator', 'MyApp.app');
-        sharedScheme('MyApp.xcodeproj', 'MyApp', schemeXml(['MyApp.app']));
-        expect(resolve('MyApp')).toBe(join(products(), 'Debug-iphonesimulator', 'MyApp.app'));
-    });
-    test('exports the only app of a single-target project', () => {
-        builtApp('Debug-iphonesimulator', 'Contributions.app');
-        sharedScheme('MyApp.xcodeproj', 'MyApp', schemeXml(['Contributions.app']));
-        expect(resolve('MyApp')).toBe(join(products(), 'Debug-iphonesimulator', 'Contributions.app'));
-    });
-    test('still resolves an app for a project with no shared scheme at all', () => {
-        builtApp('Debug-iphonesimulator', 'MyApp.app');
-        expect(resolve('MyApp')).toBe(join(products(), 'Debug-iphonesimulator', 'MyApp.app'));
-    });
-    test('reads a scheme shared by a sibling project in the same directory', () => {
-        builtApp('Debug-iphonesimulator', 'MyApp.app');
-        builtApp('Debug-watchsimulator', 'MyApp Watch App.app');
-        sharedScheme('Other.xcodeproj', 'MyApp', schemeXml(['MyApp.app']));
-        expect(resolve('MyApp')).toBe(join(products(), 'Debug-iphonesimulator', 'MyApp.app'));
-    });
-    // Nothing built is the caller's guard to report, not this script's to guess
-    // at: it must say nothing rather than print a path that does not exist.
-    test('prints nothing when the build produced no app', () => {
-        mkdirSync(products(), { recursive: true });
-        expect(resolve('MyApp')).toBe('');
-    });
-    test('prints nothing when there is no Products directory', () => {
-        expect(resolve('MyApp')).toBe('');
-    });
-});
-//# sourceMappingURL=xcode-app-product.test.js.map

package/dist/src/yaml/steps/xcode-derived-data.test.d.ts

@@ -1,30 +0,0 @@
-/**
- * Products go under a derived data path, never into one flat directory.
- *
- * `CONFIGURATION_BUILD_DIR` overrides the per-configuration/per-platform
- * product separation xcodebuild provides under
- * `DerivedData/Build/Products/<config>-<platform>/`, flattening every target in
- * the graph into a single directory. Two build tasks for the same target then
- * declare the same absolute output path and xcodebuild refuses the entire build
- * with "Multiple commands produce". The notes it prints name the SAME target
- * twice, which is the tell: one target built twice into one directory, not two
- * packages colliding on a name.
- *
- * Measured 2026-09-09 on the iOS corpus rows, all on the template's must-pass
- * "Build App" step: 16 collisions on jellyfin/Swiftfin, 266 on
- * Automattic/pocket-casts-ios, 425 on home-assistant/iOS.
- *
- * A fourth row failed differently for the same reason. CocoaPods derives
- * `PODS_CONFIGURATION_BUILD_DIR` from `BUILD_DIR`, which `CONFIGURATION_BUILD_DIR`
- * does NOT override — so pod products land in the flat directory while every
- * generated copy-resources script and linker search path still points into
- * DerivedData. shenruisi/Stay reported "Resource SDWebImage.bundle not found.
- * Run pod install" for a bundle that had been built two directories away.
- *
- * Proved by control on a runner guest, same repo and image and flags with only
- * this setting differing: `CONFIGURATION_BUILD_DIR` reproduced the collision and
- * exit 65 with no .app, `-derivedDataPath` reached BUILD SUCCEEDED in 2m06s and
- * left both `Debug` and `Debug-iphonesimulator` under Products.
- */
-export {};
-//# sourceMappingURL=xcode-derived-data.test.d.ts.map

package/dist/src/yaml/steps/xcode-derived-data.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"xcode-derived-data.test.d.ts","sourceRoot":"","sources":["../../../../src/yaml/steps/xcode-derived-data.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG"}