Skip to content

docs: explain how to keep Necto out of Release builds - #47

Merged
heoblitz merged 1 commit into
mainfrom
docs/exclude-necto-from-release
Nov 16, 2026
Merged

heoblitz merged 1 commit into
mainfrom
docs/exclude-necto-from-release

Conversation

@heoblitz

Copy link
Copy Markdown
Collaborator

Summary

Resolves #44.

Swift Package Manager links a package product in every build configuration, so Necto's code and panel bundles stay in a Release app even when every call is under #if DEBUG. The setup guide said EXCLUDED_SOURCE_FILE_NAMES does not help, which left a separate distribution target as the only option. That is heavy for an app with extensions and app groups.

Setting Excluded Source File Names to Necto* for the Release configuration of the app target does remove them. The guide, in English and Korean, now describes the setting, notes that the pattern also matches the app's own Necto* files, and shows how to inspect a Release app. A separate target stays as the fallback.

Test Plan

Built a minimal app that depends on NectoSDK, NectoEventsPlugin, NectoFilesPlugin, NectoProcessMetricPlugin, NectoUIControlPlugin and NectoURLSessionCapturePlugin, with every Necto import and call under #if DEBUG. Both builds were clean Release builds for iphoneos with CODE_SIGNING_ALLOWED=NO on Xcode 27.0.

Without the setting Necto* excluded
Necto_*.bundle in the app 5 0
nm -U | grep -ci necto on the main binary 6042 0
Private entry point strings 9 0
Main binary size 1,739,528 bytes 74,608 bytes

Not verified: a Tuist project, an archive build, and an app whose extension also links Necto. The fixture was a plain Xcode project. No check in the repository covers the documentation text.

The setup guide said that excluding calls does not remove the package and
that EXCLUDED_SOURCE_FILE_NAMES does not help, which left a separate
distribution target as the only way to keep Necto out of an App Store build.

Setting Excluded Source File Names to Necto* for the Release configuration of
the app target does drop the package's object files and resource bundles. The
guide now describes that setting, what else the pattern matches, and how to
inspect a Release app for what remains. A separate target stays as the
fallback for setups where the setting does not apply.
@heoblitz
heoblitz merged commit c29c0e6 into main Nov 16, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

iOS: a way to keep Necto out of Release builds without a separate app target

1 participant