@bacons/apple-targets 0.1.8 → 0.1.10

package/README.md

@@ -11,48 +11,47 @@ An experimental Expo Config Plugin that generates native Apple Targets like Widg
 
 > This plugin requires at least CocoaPods 1.16.2, Xcode 16, and Expo SDK +52.
 
-Run the following command in your Expo project:
+1. Run `npx create-target` in your Expo project to generate an Apple target.
+2. Select a target to generate, I recommend starting with a `widget` (e.g. `npx create-target widget`). This will generate the required widget files in the root `/targets` directory, install `@bacons/apple-targets`, and add the Expo Config Plugin to your project.
+3. If you already know your Apple Team ID, then set it under the `ios.appleTeamId` property in your `app.json`. You can find this in Xcode under the Signing & Capabilities tab and set it later if needed.
+4. Run `npx expo prebuild -p ios --clean` to generate the Xcode project.
+5. You can now open your project in Xcode (`xed ios`) and develop the widget inside the `expo:targets/<target>` folder.
+6. When you're ready to build, select the target in Xcode and build it.
 
-```
-npx create-target
-```
+### How it works
 
-Select a target to generate, I recommend starting with a `widget`.
+The root `/targets` folder is magic, each sub-directory should have a `expo-target.config.js` file that defines the target settings. When you run `npx expo prebuild --clean`, the plugin will generate the Xcode project and link the target files to the project. The plugin will also generate an `Info.plist` file if one doesn't exist.
 
-This will generate the required widget files in the `targets` directory.
+The Config Plugin will link the subfolder (e.g. `targets/widget`) to Xcode, and all files inside of it will be part of the target. This means you can develop the target inside the `expo:targets` folder and the changes will be saved outside of the generated `ios` directory.
 
-Ensure the `ios.appleTeamId` property is set in your `app.json`, then run `npx expo prebuild -p ios --clean` to generate the Xcode project.
+The root `Info.plist` file in each target directory is not managed and can be freely modified.
 
-You can now open Xcode and develop the widget inside the `expo:targets` folder. When you're ready to build, run:
+Any files in a top-level `target/{name}/assets` directory will be linked as resources of the target. This rule was added to support Safari Extensions.
 
-### Manual usage
+### Entitlements
 
-- Add targets to `targets/` directory with an `expo-target.config.json` file.
-- If you don't have an `Info.plist`, it'll be generated on `npx expo prebuild`. This may be changed in the future so if you have an `Info.plist` it'll be used, otherwise, it'll be generated.
-- Any files in a top-level `target/*/assets` directory will be linked as resources of the target. This was added to support Safari Extensions.
-- A single top-level `*.entitlements` file will be linked as the entitlements of the target. This is not currently used in EAS Capability signing, but may be in the future.
-- All Swift files will be linked as build sources of the target. There is currently no support for storyboard or `.xib` files because I can't be bothered.
-- All `*.xcassets` files will be linked as resources, and accessible in the targets. If you add files outside of Xcode, you'll need to re-run `npx expo prebuild` to link them.
-- In Expo SDK +52, set the `ios.appleTeamId`, for SDK 51 and below, set the `appleTeamId` prop in the Config Plugin in `app.config.js`:
+If the `expo-target.config` file defines an `entitlements: {}` object, then a `generated.entitlements` will be added. Avoid using this file directly, and instead update the `expo-target.config.js` file. If the `entitlements` object is not defined, you can manually add any top-level `*.entitlements` file to the target directory—re-running `npx expo prebuild` will link this file to the target as the entitlements file. Only one top-level `*.entitlements` file is supported per target.
 
-```json
-{
-  "plugins": [
-    [
-      "@bacons/apple-targets",
-      {
-        "appleTeamId": "XXXXXXXXXX"
-      }
-    ]
-  ]
-}
-```
+Some targets have special entitlements behavior:
+
+- App Clips (`clip`) automatically set the required `com.apple.developer.parent-application-identifiers` to `$(AppIdentifierPrefix)${config.ios.bundleIdentifier}`
+- Targets that can utilize App Groups will automatically mirror the `ios.entitlements['com.apple.security.application-groups']` array from the `app.json` if it's defined. This can be overwritten by specifying an `entitlements['com.apple.security.application-groups']` array in the `expo-target.config.js` file.
+
+### Development
+
+Any changes you make outside of the `expo:targets` directory in Xcode are subject to being overwritten by the next `npx expo prebuild --clean`. Check to see if the settings you want to toggle are available in the Info.plist or the `expo-target.config.js` file.
+If you modify the `expo-target.config.js` or your root `app.json`, you will need to re-run `npx expo prebuild --clean` to sync the changes.
+
+You can use the custom Prebuild template `--template node_modules/@bacons/apple-targets/prebuild-blank.tgz` to create a build without React Native, this can make development a bit faster since there's less to compile.
+
+## Target config
 
-## `expo-target.config.js`
+The target config can be a `expo-target.config.js`, or `expo-target.config.json` file.
 
 This file can have the following properties:
 
 ```js
+/** @type {import('@bacons/apple-targets/app.plugin').Config} */
 module.exports = {
   type: "widget",
 
@@ -67,7 +66,7 @@ module.exports = {
   icon: "../assets/icon.png",
   // Can also be a URL
   frameworks: [
-    // Frameworks without the extension, these will be added to the target.
+    // Frameworks with or without the `.frameworks` extension, these will be added to the target.
     "SwiftUI",
   ],
   entitlements: {
@@ -84,26 +83,16 @@ module.exports = {
   // Optional bundle identifier for the target. Will default to a sanitized version of the root project bundle id + target name.
   // If the specified bundle identifier is prefixed with a dot (.), the bundle identifier will be appended to the main app's bundle identifier.
   bundleIdentifier: ".mywidget",
-};
-```
 
-You can also use `.js` with the typedoc for autocomplete:
-
-```js
-/** @type {import('@bacons/apple-targets').Config} */
-module.exports = {
-  type: "watch",
-  colors: {
-    $accent: "steelblue",
-  },
-  deploymentTarget: "9.4",
+  // Should the release build export the JS bundle and embed. Intended for App Clips and Share Extensions where you may want to use React Native.
+  exportJs: false,
 };
 ```
 
-Finally, you can return a function that accepts the Expo Config and returns a target function for syncing app groups:
+You can also return a function that accepts the Expo Config and returns a target function for syncing entitlements and other values:
 
 ```js
-/** @type {import('@bacons/apple-targets').ConfigFunction} */
+/** @type {import('@bacons/apple-targets/app.plugin').ConfigFunction} */
 module.exports = (config) => ({
   type: "widget",
   colors: {
@@ -192,7 +181,7 @@ The name of the target must match the name of the target directory.
 > I wrote a blog about this one and used it in production. Learn more: [Expo x Apple Widgets](https://evanbacon.dev/blog/apple-home-screen-widgets).
 
 ```js
-/** @type {import('@bacons/apple-targets').Config} */
+/** @type {import('@bacons/apple-targets/app.plugin').Config} */
 module.exports = {
   type: "widget",
   icon: "../../icons/widget.png",
@@ -224,7 +213,7 @@ module.exports = {
 These show up in the share sheet. The icon should be transparent as it will be masked by the system.
 
 ```js
-/** @type {import('@bacons/apple-targets').Config} */
+/** @type {import('@bacons/apple-targets/app.plugin').Config} */
 module.exports = {
   type: "action",
   name: "Inspect Element",
@@ -269,7 +258,7 @@ Ensure `NSExtensionJavaScriptPreprocessingFile: "index"` in the Info.plist.
 Populate the Spotlight search results with your app's content.
 
 ```js
-/** @type {import('@bacons/apple-targets').Config} */
+/** @type {import('@bacons/apple-targets/app.plugin').Config} */
 module.exports = {
   type: "spotlight",
 };
@@ -308,9 +297,7 @@ The codesigning is theoretically handled entirely by [EAS Build](https://docs.ex
 
 You can also manually sign all sub-targets if you want, I'll light a candle for you.
 
-## Xcode parsing
-
-This plugin makes use of my proprietary Xcode parsing library, [`@bacons/xcode`](https://github.com/evanbacon/xcode). It's mostly typed, very untested, and possibly full of bugs––however, it's still 10x nicer than the alternative.
+> I haven't gotten App Clip codesigning to be fully automated yet. PRs welcome.
 
 ## Building Widgets
 
@@ -349,7 +336,7 @@ First, define your main App Group entitlement in your `app.json`:
 Second, define the same App Group in your target's `expo-target.config.js`:
 
 ```js
-/** @type {import('@bacons/apple-targets').ConfigFunction} */
+/** @type {import('@bacons/apple-targets/app.plugin').ConfigFunction} */
 module.exports = (config) => ({
   type: "widget",
   entitlements: {
@@ -402,6 +389,6 @@ let defaults = UserDefaults(suiteName:
 let index = defaults?.string(forKey: "myKey")
 ```
 
-## Using React Native in Targets
+## Xcode parsing
 
-I'm not sure, that's not the purpose of this plugin. I built this so I could easily build iOS widgets and other minor targets with SwiftUI. I imagine it would be straightforward to use React Native in share, notification, iMessage, Safari, and photo editing extensions, you can build that on top of this plugin if you want. Look at the App Clip example for a starting point.
+This plugin makes use of my proprietary Xcode parsing library, [`@bacons/xcode`](https://github.com/evanbacon/xcode). It's mostly typed, very untested, and possibly full of bugs––however, it's still 10x nicer than the alternative.

package/app.plugin.d.ts

@@ -0,0 +1 @@
+export * from "./build/config-plugin";

package/build/config-plugin.js

@@ -6,16 +6,20 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.withTargetsDir = void 0;
 const glob_1 = require("glob");
 const path_1 = __importDefault(require("path"));
+const chalk_1 = __importDefault(require("chalk"));
 const withPodTargetExtension_1 = require("./withPodTargetExtension");
 const withWidget_1 = __importDefault(require("./withWidget"));
 const withXcparse_1 = require("./withXcparse");
+let hasWarned = false;
 const withTargetsDir = (config, _props) => {
     var _a;
-    const { appleTeamId = (_a = config === null || config === void 0 ? void 0 : config.ios) === null || _a === void 0 ? void 0 : _a.appleTeamId, root = "./targets", match = "*", } = _props || {};
-    if (!appleTeamId) {
-        throw new Error(`You must specify an \`appleTeamId\` in your app config to use the \`withTargetsDir\` plugin.`);
-    }
+    let { appleTeamId = (_a = config === null || config === void 0 ? void 0 : config.ios) === null || _a === void 0 ? void 0 : _a.appleTeamId } = _props || {};
+    const { root = "./targets", match = "*" } = _props || {};
     const projectRoot = config._internal.projectRoot;
+    if (!appleTeamId && !hasWarned) {
+        hasWarned = true;
+        console.warn((0, chalk_1.default) `{yellow [bacons/apple-targets]} Expo config is missing required {cyan ios.appleTeamId} property. Find this in Xcode and add to the Expo Config to correct. iOS builds may fail until this is corrected.`);
+    }
     const targets = (0, glob_1.sync)(`${root}/${match}/expo-target.config.@(json|js)`, {
         // const targets = globSync(`./targets/action/expo-target.config.@(json|js)`, {
         cwd: projectRoot,

package/build/target.d.ts

@@ -1,6 +1,7 @@
 import { PBXNativeTarget, XcodeProject } from "@bacons/xcode";
 export type ExtensionType = "widget" | "notification-content" | "notification-service" | "share" | "intent" | "bg-download" | "intent-ui" | "spotlight" | "matter" | "quicklook-thumbnail" | "imessage" | "clip" | "watch" | "location-push" | "credentials-provider" | "account-auth" | "action" | "safari" | "app-intent" | "device-activity-monitor";
 export declare const KNOWN_EXTENSION_POINT_IDENTIFIERS: Record<string, ExtensionType>;
+export declare const SHOULD_USE_APP_GROUPS_BY_DEFAULT: Record<ExtensionType, boolean>;
 export declare function getTargetInfoPlistForType(type: ExtensionType): string;
 export declare function productTypeForType(type: ExtensionType): "com.apple.product-type.application.on-demand-install-capable" | "com.apple.product-type.application" | "com.apple.product-type.extensionkit-extension" | "com.apple.product-type.app-extension";
 export declare function needsEmbeddedSwift(type: ExtensionType): boolean;

package/build/target.js

@@ -3,7 +3,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.getAuxiliaryTargets = exports.getMainAppTarget = exports.isNativeTargetOfType = exports.getFrameworksForType = exports.needsEmbeddedSwift = exports.productTypeForType = exports.getTargetInfoPlistForType = exports.KNOWN_EXTENSION_POINT_IDENTIFIERS = void 0;
+exports.getAuxiliaryTargets = exports.getMainAppTarget = exports.isNativeTargetOfType = exports.getFrameworksForType = exports.needsEmbeddedSwift = exports.productTypeForType = exports.getTargetInfoPlistForType = exports.SHOULD_USE_APP_GROUPS_BY_DEFAULT = exports.KNOWN_EXTENSION_POINT_IDENTIFIERS = void 0;
 const plist_1 = __importDefault(require("@expo/plist"));
 exports.KNOWN_EXTENSION_POINT_IDENTIFIERS = {
     "com.apple.message-payload-provider": "imessage",
@@ -26,12 +26,37 @@ exports.KNOWN_EXTENSION_POINT_IDENTIFIERS = {
     "com.apple.deviceactivity.monitor-extension": "device-activity-monitor",
     // "com.apple.intents-service": "intents",
 };
+// An exhaustive list of extension types that should sync app groups from the main target by default when
+// no app groups are specified.
+exports.SHOULD_USE_APP_GROUPS_BY_DEFAULT = {
+    share: true,
+    "bg-download": true,
+    clip: true,
+    widget: true,
+    "account-auth": false,
+    "credentials-provider": false,
+    "device-activity-monitor": false,
+    "app-intent": false,
+    "intent-ui": false,
+    "location-push": false,
+    "notification-content": false,
+    "notification-service": false,
+    "quicklook-thumbnail": false,
+    action: false,
+    imessage: false,
+    intent: false,
+    matter: false,
+    safari: false,
+    spotlight: false,
+    watch: false,
+};
 // TODO: Maybe we can replace `NSExtensionPrincipalClass` with the `@main` annotation that newer extensions use?
 function getTargetInfoPlistForType(type) {
+    // TODO: Use exhaustive switch to ensure external contributors don't forget to add this.
     if (type === "watch") {
         return plist_1.default.build({});
     }
-    if (type === "action") {
+    else if (type === "action") {
         return plist_1.default.build({
             NSExtension: {
                 NSExtensionAttributes: {
@@ -93,7 +118,7 @@ function getTargetInfoPlistForType(type) {
             },
         });
     }
-    if (type === "account-auth") {
+    else if (type === "account-auth") {
         return plist_1.default.build({
             NSExtension: {
                 NSExtensionPointIdentifier,
@@ -105,7 +130,7 @@ function getTargetInfoPlistForType(type) {
             },
         });
     }
-    if (type === "credentials-provider") {
+    else if (type === "credentials-provider") {
         return plist_1.default.build({
             NSExtension: {
                 NSExtensionPointIdentifier,
@@ -113,7 +138,7 @@ function getTargetInfoPlistForType(type) {
             },
         });
     }
-    if (type === "notification-service") {
+    else if (type === "notification-service") {
         return plist_1.default.build({
             NSExtension: {
                 NSExtensionAttributes: {

package/build/withWidget.js

@@ -8,21 +8,51 @@ const plist_1 = __importDefault(require("@expo/plist"));
 const fs_1 = __importDefault(require("fs"));
 const glob_1 = require("glob");
 const path_1 = __importDefault(require("path"));
+const chalk_1 = __importDefault(require("chalk"));
 const withIosColorset_1 = require("./colorset/withIosColorset");
 const withImageAsset_1 = require("./icon/withImageAsset");
 const withIosIcon_1 = require("./icon/withIosIcon");
 const target_1 = require("./target");
 const withEasCredentials_1 = require("./withEasCredentials");
 const withXcodeChanges_1 = require("./withXcodeChanges");
-let hasWarned = false;
+function memoize(fn) {
+    const cache = new Map();
+    return ((...args) => {
+        const key = JSON.stringify(args);
+        if (cache.has(key)) {
+            return cache.get(key);
+        }
+        const result = fn(...args);
+        cache.set(key, result);
+        return result;
+    });
+}
+const warnOnce = memoize(console.warn);
+const logOnce = memoize(console.log);
+function createLogQueue() {
+    const queue = [];
+    const flush = () => {
+        queue.forEach((fn) => fn());
+        queue.length = 0;
+    };
+    return {
+        flush,
+        add: (fn) => {
+            queue.push(fn);
+        },
+    };
+}
+// Queue up logs so they only run when prebuild is actually running and not during standard config reads.
+const prebuildLogQueue = createLogQueue();
 function kebabToCamelCase(str) {
     return str.replace(/-([a-z])/g, function (g) {
         return g[1].toUpperCase();
     });
 }
 const withWidget = (config, props) => {
-    // TODO: Magically based on the top-level folders in the `ios-widgets/` folder
     var _a, _b, _c, _d, _e, _f, _g, _h, _j;
+    prebuildLogQueue.add(() => warnOnce((0, chalk_1.default) `\nUsing experimental Config Plugin {bold @bacons/apple-targets} that is subject to breaking changes.`));
+    // TODO: Magically based on the top-level folders in the `ios-widgets/` folder
     if (props.icon && !/https?:\/\//.test(props.icon)) {
         props.icon = path_1.default.join(props.directory, props.icon);
     }
@@ -37,21 +67,49 @@ const withWidget = (config, props) => {
         cwd: widgetFolderAbsolutePath,
     });
     if (entitlementsFiles.length > 1) {
-        throw new Error(`Found multiple entitlements files in ${widgetFolderAbsolutePath}`);
+        throw new Error(`[bacons/apple-targets][${props.type}] Found more than one '*.entitlements' file in ${widgetFolderAbsolutePath}`);
     }
     let entitlementsJson = props.entitlements;
-    // Apply default entitlements that must be present for a target to work.
-    function applyDefaultEntitlements(entitlements) {
-        if (props.type === "clip") {
-            entitlements["com.apple.developer.parent-application-identifiers"] = [
-                `$(AppIdentifierPrefix)${config.ios.bundleIdentifier}`,
-            ];
-            // NOTE: This doesn't seem to be required anymore (Oct 12 2024):
-            // entitlements["com.apple.developer.on-demand-install-capable"] = true;
-        }
-        return entitlements;
-    }
     if (entitlementsJson) {
+        // Apply default entitlements that must be present for a target to work.
+        const applyDefaultEntitlements = (entitlements) => {
+            var _a, _b, _c, _d;
+            if (props.type === "clip") {
+                entitlements["com.apple.developer.parent-application-identifiers"] = [
+                    `$(AppIdentifierPrefix)${config.ios.bundleIdentifier}`,
+                ];
+                // NOTE: This doesn't seem to be required anymore (Oct 12 2024):
+                // entitlements["com.apple.developer.on-demand-install-capable"] = true;
+            }
+            const APP_GROUP_KEY = "com.apple.security.application-groups";
+            const hasDefinedAppGroupsManually = APP_GROUP_KEY in entitlements;
+            if (
+            // If the user hasn't manually defined the app groups array.
+            !hasDefinedAppGroupsManually &&
+                // And the target is part of a predefined list of types that benefit from app groups that match the main app...
+                target_1.SHOULD_USE_APP_GROUPS_BY_DEFAULT[props.type]) {
+                const mainAppGroups = (_b = (_a = config.ios) === null || _a === void 0 ? void 0 : _a.entitlements) === null || _b === void 0 ? void 0 : _b[APP_GROUP_KEY];
+                if (Array.isArray(mainAppGroups) && mainAppGroups.length > 0) {
+                    // Then set the target app groups to match the main app.
+                    entitlements[APP_GROUP_KEY] = mainAppGroups;
+                    prebuildLogQueue.add(() => {
+                        logOnce((0, chalk_1.default) `[${widget}] Syncing app groups with main app. {dim Define entitlements[${JSON.stringify(APP_GROUP_KEY)}] in the {bold expo-target.config} file to override.}`);
+                    });
+                }
+                else {
+                    config_plugins_1.WarningAggregator.addWarningIOS(`ios.entitlements["${APP_GROUP_KEY}"]`, `[${props.type}] Apple target may require the App Groups entitlement but none were found in the Expo config.\nExample:\n${JSON.stringify({
+                        ios: {
+                            entitlements: {
+                                [APP_GROUP_KEY]: [
+                                    `group.${(_d = (_c = config.ios) === null || _c === void 0 ? void 0 : _c.bundleIdentifier) !== null && _d !== void 0 ? _d : `com.example.${config.slug}`}`,
+                                ],
+                            },
+                        },
+                    }, null, 2)}`);
+                }
+            }
+            return entitlements;
+        };
         entitlementsJson = applyDefaultEntitlements(entitlementsJson);
     }
     // If the user defined entitlements, then overwrite any existing entitlements file
@@ -60,11 +118,15 @@ const withWidget = (config, props) => {
             "ios",
             async (config) => {
                 var _a;
+                const GENERATED_ENTITLEMENTS_FILE_NAME = "generated.entitlements";
                 const entitlementsFilePath = (_a = entitlementsFiles[0]) !== null && _a !== void 0 ? _a : 
                 // Use the name `generated` to help indicate that this file should be in sync with the config
-                path_1.default.join(widgetFolderAbsolutePath, `generated.entitlements`);
+                path_1.default.join(widgetFolderAbsolutePath, GENERATED_ENTITLEMENTS_FILE_NAME);
                 if (entitlementsFiles[0]) {
-                    console.log(`[${widget}] Replacing ${path_1.default.relative(widgetFolderAbsolutePath, entitlementsFiles[0])} with entitlements JSON from config`);
+                    const relativeName = path_1.default.relative(widgetFolderAbsolutePath, entitlementsFiles[0]);
+                    if (relativeName !== GENERATED_ENTITLEMENTS_FILE_NAME) {
+                        console.log(`[${widget}] Replacing ${path_1.default.relative(widgetFolderAbsolutePath, entitlementsFiles[0])} with entitlements JSON from config`);
+                    }
                 }
                 fs_1.default.writeFileSync(entitlementsFilePath, plist_1.default.build(entitlementsJson));
                 return config;
@@ -80,10 +142,7 @@ const withWidget = (config, props) => {
     (0, config_plugins_1.withDangerousMod)(config, [
         "ios",
         async (config) => {
-            if (!hasWarned) {
-                hasWarned = true;
-                console.warn("You're using an experimental Config Plugin that is subject to breaking changes and has no E2E tests.");
-            }
+            prebuildLogQueue.flush();
             fs_1.default.mkdirSync(widgetFolderAbsolutePath, { recursive: true });
             const files = [
                 ["Info.plist", (0, target_1.getTargetInfoPlistForType)(props.type)],
@@ -179,6 +238,7 @@ const withConfigColors = (config, props) => {
             });
         });
     }
+    // TODO: Add clean-up maybe? This would possibly restrict the ability to create native colors outside of the Expo target config.
     return config;
 };
 exports.default = withWidget;

package/build/withXcodeChanges.js

@@ -634,7 +634,7 @@ function createConfigurationListForType(project, props) {
     }
 }
 async function applyXcodeChanges(config, project, props) {
-    var _a, _b;
+    var _a;
     const mainAppTarget = (0, target_1.getMainAppTarget)(project);
     // Special setting for share extensions.
     if ((0, target_1.needsEmbeddedSwift)(props.type)) {
@@ -653,20 +653,11 @@ async function applyXcodeChanges(config, project, props) {
         console.log(`Target "${targetToUpdate.props.productName}" already exists, updating instead of creating a new one`);
     }
     const magicCwd = path_1.default.join(config._internal.projectRoot, "ios", props.cwd);
-    let developmentTeamId = (_b = props.teamId) !== null && _b !== void 0 ? _b : mainAppTarget.getDefaultBuildSetting("DEVELOPMENT_TEAM");
-    if (!developmentTeamId) {
-        console.error("Couldn't find DEVELOPMENT_TEAM in Xcode project and none were provided in the Expo config. Using placeholder value.");
-        // Using a placeholder gives users a chance to see the value in Xcode.
-        developmentTeamId = "XXXXXXXXXX";
-        // throw new Error(
-        //   "Couldn't find DEVELOPMENT_TEAM in Xcode project and none were provided in the Expo config."
-        // );
-    }
     function applyDevelopmentTeamIdToTargets() {
         var _a, _b;
         var _c, _d, _e;
         // Set to the provided value or any value.
-        const devTeamId = developmentTeamId ||
+        const devTeamId = props.teamId ||
             project.rootObject.props.targets
                 .map((target) => target.getDefaultBuildSetting("DEVELOPMENT_TEAM"))
                 .find(Boolean);

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@bacons/apple-targets",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "Generate Apple Targets with Expo Prebuild",
   "main": "build/ExtensionStorage.js",
   "types": "build/ExtensionStorage.d.ts",
   "files": [
     "app.plugin.js",
+    "app.plugin.d.ts",
     "build",
     "ios",
     "expo-module.config.json",