Symbol not found: _$sSo22CLLocationCoordinate2DVSE12CoreLocationMc when building for visionOS 2.5 with Xcode 16.3

Question

Created May ’25

Replies 2

Boosts 0

Participants 2

Hello, I'm encountering a runtime crash when building my visionOS app with Xcode 16.3 for visionOS 2.5. Our existing AppStore/Testflight app is also instantly crashing on visionOS 2.5 when opened but works fine on e.g visionOS 2.4. The app builds successfully but crashes on launch with this symbol lookup error (slightly adjusted because the forum complained regarding sensitive data):

Symbol not found: _$sSo22CLLocationCoordinate2DVSE12CoreLocationMc
  Referenced from: <XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX> /private/var/containers/Bundle/Application/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/MyApp.app/MyApp.debug.dylib
  Expected in: <XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX> /usr/lib/swift/libswiftCoreLocation.dylib
dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture:/usr/lib/libViewDebuggerSupport.dylib

I've already implemented my own Codable conformance for CLLocationCoordinate2D:

extension CLLocationCoordinate2D: Codable {
    // implementation details...
}

This worked fine on previous visionOS/Xcode versions. Has anyone encountered this issue or found a solution? System details:

macOS version: 15.3.2
Xcode version: 16.3
visionOS target: 2.5

Thank you!

Boost

Answer 1

kallipigous OP

May ’25

it's just started for me too. Did you ever find a solution?

0

Answer 2

kallipigous OP

May ’25

Mine is fixed. It seems to be because apple suddenly generated their own version of codable for CLLocationCoordinate2D and this was conflicting. Examining CLLocationCoordinate2D showed that it was now marked as codable in the documentation. I removed my codable extension but it still didn't like it. but when I updated Xcode to the latest release version it went back to being non codable and everything is fine again.

0