[FIX] TestFlight Deploy CI의 tuisttool OS 불일치 수정 - #108
Merged
Conversation
macOS 26 기준으로 빌드·커밋된 tuisttool 바이너리가 macos-15 러너에서 로드 실패(exit 134)하므로, 각 잡에서 TuistTool.swift를 소스로 재컴파일
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
1 participant
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.
무엇을 / 왜
PR #107 머지 후
TestFlight Deploy워크플로우의test잡이Generate project스텝에서 exit code 134로 실패했습니다.원인: 레포에 커밋된
tuisttool바이너리가 로컬 macOS 26.0 기준으로 빌드되어 있어,macos-15러너에서 dyld 로드에 실패합니다.```
dyld: Library not loaded: /usr/lib/swift/libswift_DarwinFoundation2.dylib
Referenced from: .../tuisttool (built for macOS 26.0 which is newer than running OS)
Abort trap: 6 ./tuisttool install
```
변경 사항
test·deploy두 잡의Setup mise & tuist직후에swiftc TuistTool.swift -o tuisttool재컴파일 스텝 추가test잡의Generate project,deploy잡의Install dependencies,fastlane/Fastfile의./tuisttool generate세 사용처를 모두 커버To Reviewer
tuisttool은TuistTool.swift를 컴파일한 바이너리라 소스에서 그대로 재빌드해도 동작이 동일합니다. 로컬에서 단독 컴파일이 성공함을 확인했습니다..gitignore처리하거나 on-demand 컴파일 래퍼로 전환하면 좋겠습니다. 이번 PR에서는 CI 복구에 범위를 한정했습니다.TestFlight Deploy실행 또는workflow_dispatch수동 실행으로test잡 통과를 확인하면 됩니다.