react-native-acoustic-connect-beta/plugin/build/withConnectIosSigning.d.ts

BETA: React native plugin for Acoustic Connect

import { type ConfigPlugin } from '@expo/config-plugins';
import type { ConnectPluginProps } from './withConnectNSE';
/**
 * Resolves the iOS signing team (Apple Team ID) for the host + push extensions.
 *
 * Priority:
 *  1. `iosDevelopmentTeam` plugin prop in app.json (explicit override)
 *  2. `Connect.iOSDevelopmentTeam` in `<projectRoot>/ConnectConfig.json`
 *
 * Returns `undefined` when neither source provides a real value (the placeholder
 * `YOUR_TEAM_ID` counts as unset). The mod is then a no-op — never a regression.
 */
export declare function resolveDevelopmentTeam(projectRoot: string, props: ConnectPluginProps): string | undefined;
/**
 * Expo Config Plugin mod that stamps `DEVELOPMENT_TEAM` onto every target's
 * build configuration in the generated Xcode project (host + ConnectNSE +
 * ConnectNCE), so all three sign consistently.
 *
 * Why this matters: the NSE mod injects the `aps-environment` entitlement, but
 * a CLI build (`expo run:ios` / `xcodebuild`) with no signing team falls back
 * to ad-hoc signing (`CODE_SIGN_IDENTITY = -`), which DROPS that entitlement —
 * so the OS issues no APNs token and push silently fails (CA-144135 §6). Setting
 * the team closes that loop on the prebuild path the SDK owns. Provisioning
 * itself still needs the developer's Apple ID in Xcode and
 * `-allowProvisioningUpdates` on the build (documented in the README).
 *
 * No-op when no team is configured (no regression for consumers who sign in the
 * Xcode GUI or via EAS, which manages the whole chain itself).
 *
 * Must run AFTER withConnectNSE / withConnectNCE so the extension targets exist.
 */
export declare const withConnectIosSigning: ConfigPlugin<ConnectPluginProps>;
export default withConnectIosSigning;
//# sourceMappingURL=withConnectIosSigning.d.ts.map