Hi @tsabend, this is a very nice tool, thanks for sharing it.
I run it on my day job Xcode project, which uses Carthage to resolve dependencies, and got a crash.
I think it was due to the fact that we are using a project called Reachability.swift, which Carthage fetches into a folder with the same name, including the .swift part. fus then tries to read the content of what it thinks it's the filed Reachability.swift, but that's actually a folder.
This PR does not fix the issue that results in that crash, but just quickly works around it by excluding the Carthage folder, the same way that the Pods one is already excluded.
I think this is an acceptable workaround for the time being, given that it mimics an already existing behaviour.
Hi @tsabend, this is a very nice tool, thanks for sharing it.
I run it on my day job Xcode project, which uses Carthage to resolve dependencies, and got a crash.
I think it was due to the fact that we are using a project called Reachability.swift, which Carthage fetches into a folder with the same name, including the
.swift
part.fus
then tries to read the content of what it thinks it's the filedReachability.swift
, but that's actually a folder.This PR does not fix the issue that results in that crash, but just quickly works around it by excluding the Carthage folder, the same way that the Pods one is already excluded.
I think this is an acceptable workaround for the time being, given that it mimics an already existing behaviour.