Why does my archived Swift app seem to look at the wrong path?

Question

I have XCode 10.2, and have tried Swift 4 & Swift 4.2. My desktop app runs fine from XCode, but crashes when I try to run it after archive.

I get this:

Termination Reason: DYLD, [0x4] Symbol missing

Application Specific Information: dyld: launch, loading dependent libraries

Dyld Error Message: Symbol not found: _$SBOWV Referenced from: /Users/USER/Desktop//My App.app/Contents/MacOS/../Frameworks/Alamofire.framework/Versions/A/Alamofire Expected in: /usr/lib/swift/libswiftCore.dylib in /Users/USER/Desktop//My App.app/Contents/MacOS/../Frameworks/Alamofire.framework/Versions/A/Alamofire

The weird thing I notice offhand is that it thinks my path is /Users/USER/Desktop/*/Live Canvas.app/Contents/MacOS/My App. That is certainly the wrong folder - I'm not sure if that's meant as a placeholder or it thinks that's my literal, incorrect path.

I also looked at Xcode 10 Archived App Doesn't Run on Macs with Xcode 9 or Earlier Installed: DYLD, [0x4] Symbol missing? and set Always Embed Swift Standard Libraries to Yes for both Project and Target. The other question also doesn't appear to have path weirdness.

I should note that I have Swift 5 on my machine as well, however I'm on Mojave 10.14.4 so it shouldn't be an issue per https://support.apple.com/kb/DL1998?locale=en_US. It won't even let me install that because my OS is the right version.

What do you mean by *"My desktop app runs fine in emulator"*? There is no macOS emulator. — rmaddy, Apr 29 '19 at 17:10
@rmaddy Sorry, I hit cmd+R to run the app from XCode - what's the right term there? — Dave Stein, Apr 29 '19 at 17:12
That actually runs your app on your Mac. No emulator involved. — rmaddy, Apr 29 '19 at 17:17
Similar to https://stackoverflow.com/questions/52452236/xcode-10-archived-app-doesnt-run-on-macs-with-xcode-9-or-earlier-installed-dyl — matt, Apr 29 '19 at 17:29
@matt I have that setting already marked to "yes" for my target. will update for project and try again — Dave Stein, Apr 29 '19 at 17:55

score 0 · Answer 1 · answered Apr 30 '19 at 15:39

0

I downgraded from XCode 10.2 -> 10.1. Problem solved.

answered Apr 30 '19 at 15:39

Dave Stein

8,653
13
56
104

That is a workaround but I don't see how it answers the question. What we're looking for here are _causes_ and _solutions_. You're just avoiding the issue. If there is a bug in Xcode 10.2 it needs to be reported to Apple. If there isn't, you're doing something wrong and we need to know what it is. – matt Apr 30 '19 at 16:03
Yeah I usually go back and report bugs and post here. I just need to get something out and then can come back to this. You are right though. – Dave Stein Apr 30 '19 at 16:07

Why does my archived Swift app seem to look at the wrong path?

1 Answers1