You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could not read contents of `/var/folders/cl/8cgpg37n5cl78pjkbpgml94w0000gn/T/jazzy20190128-87912-1r7txvvMapboxNavigation-Documentation/build/Release-iphoneos/MapboxDirections.swift`
Could not parse `MapboxDirections.swift`. Please open an issue at https://github.com/jpsim/SourceKitten/issues with the file contents.
CocoaPods places the pod’s downloaded framework inside a MapboxDirections.swift directory. jazzy passes the framework root’s path to xcodebuild as an include directory (-I). But the “.swift” suffix in the directory name causes SourceKitten to detect the folder as a Swift file:
Oops, you were right, the isFile helper is incorrect and also returns true for directories. Your fix at #575 looks good at a glance, we just have to figure out why it's failing CI.
The Mapbox Navigation SDK for iOS runs
jazzy
passing in this podspec as--podspec
. Among the errors we’re working through in mapbox/mapbox-navigation-ios#1795 is this one caused by the dependency on the MapboxDirections.swift pod:CocoaPods places the pod’s downloaded framework inside a MapboxDirections.swift directory. jazzy passes the framework root’s path to
xcodebuild
as an include directory (-I
). But the “.swift” suffix in the directory name causes SourceKitten to detect the folder as a Swift file:SourceKitten/Source/SourceKittenFramework/String+SourceKitten.swift
Lines 453 to 455 in 4a0f386
So then
sourcekitten doc
fails becauseModule.docs
thinks it needs to parse a “MapboxDirections.swift” file for documentation:SourceKitten/Source/SourceKittenFramework/Module.swift
Line 81 in 4a0f386
SourceKitten/Source/SourceKittenFramework/File.swift
Lines 64 to 69 in 4a0f386
/cc @JThramer
The text was updated successfully, but these errors were encountered: