Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Periphery scan fails when target's Supported Platform differs from main app target #882

Open
justTil opened this issue Feb 11, 2025 · 0 comments

Comments

@justTil
Copy link

justTil commented Feb 11, 2025

When using Periphery in Xcode using the aggregated target, the Build Setting > Supported Platforms has to be the same as your main build platforms.

F.e. if your main target only iOS and you have macOS selected in periphery target, then it will crash and give an error similar to this:

Building ProjectName... error: Shell command 'xcodebuild -project '/pahtToProject/ProjectName.xcodeproj' 
-scheme 'ProjectName.xcodeproj' -parallelizeTargets -derivedDataPath '/caches/com.github.peripheryapp/DerivedData-....' 
-quiet build-for-testing CODE_SIGNING_ALLOWED="NO" ENABLE_BITCODE="NO" 
DEBUG_INFORMATION_FORMAT="dwarf" COMPILER_INDEX_STORE_ENABLE="YES" INDEX_ENABLE_DATA_STORE="YES"' 
returned exit status '65': ld: building for 'iOS', but linking in dylib 

(/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/Versions/A/XCTest) built for 'zippered(macOS/Catalyst)' clang: error: linker command failed with exit code 1 (use -v to see invocation)

Solution: Set the same supported platforms and maybe add this step/checkup to the documentation please.
Image

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

No branches or pull requests

1 participant