Repository navigation
docs: explain how to keep Necto out of Release builds - #47
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 saidEXCLUDED_SOURCE_FILE_NAMESdoes 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 ownNecto*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,NectoUIControlPluginandNectoURLSessionCapturePlugin, with every Necto import and call under#if DEBUG. Both builds were clean Release builds foriphoneoswithCODE_SIGNING_ALLOWED=NOon Xcode 27.0.Necto*excludedNecto_*.bundlein the appnm -U | grep -ci nectoon the main binaryNot 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.