MacDownApp / MacDownApp/macdown
Build failed in Xcode 10.1
- Dominant language
- Rich Text Format
- Stars
- 9.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Showing Recent Messages
``` Cycle inside MacDown; building could produce unreliable results.
Cycle details:
→ That command depends on command in Target 'MacDown': script phase “[CP] Embed Pods Frameworks”
→ Target 'MacDown' has copy command from '/Users/brian.tully/Library/Developer/Xcode/DerivedData/MacDown-gxwdfssocsvkvufuhhdvwuydzcpv/Build/Products/Debug/macdown' to '/Users/brian.tully/Library/Developer/Xcode/DerivedData/MacDown-gxwdfssocsvkvufuhhdvwuydzcpv/Build/Products/Debug/MacDown.app/Contents/SharedSupport/bin/macdown'
○ Target 'MacDown' has compile command with input '/Users/brian.tully/Sites/macdown/MacDown/Images.xcassets'
○ That command depends on command in Target 'MacDown': script phase “[CP] Copy Pods Resources”
```
Contributor guide
Research direction
The report is limited to an Xcode 10.1 build log for target MacDown; begin by reproducing the build and inspect the “[CP] Embed Pods Frameworks” and “[CP] Copy Pods Resources” phases named in the cycle. Done means the MacDown target builds without the reported dependency cycle or unreliable-results warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, objective-c
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100