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
Which Xcode version are you using (check xcodebuild -version)? Xcode 14.0; Build version 14A309
I have several files with clear violations of the rule (that I added myself, just to make 100% sure), but this is the output I get from running swiftlint:
Analyzing Swift files in current working directory
Analyzing '<FILENAME_1.swift' (1/596)
sourcekit: [1:getCursorInfo:10755: 0.0000] error creating ASTInvocation: error: unknown argument: '-use-frontend-parseable-output'
Could not get cursor info
sourcekit: [1:getCursorInfo:10759: 0.0004] error creating ASTInvocation: error: unknown argument: '-use-frontend-parseable-output'
Could not get cursor info
....
sourcekit: [1:getCursorInfo:11067:21.6235] error creating ASTInvocation: error: unknown argument: '-use-frontend-parseable-output'
Could not get cursor info
sourcekit: [1:getCursorInfo:11071:21.6237] error creating ASTInvocation: error: unknown argument: '-use-frontend-parseable-output'
Could not get cursor info
sourcekit: [1:getCursorInfo:11075:21.6238] error creating ASTInvocation: error: unknown argument: '-use-frontend-parseable-output'
Could not get cursor info
Done analyzing! Found 0 violations, 0 serious in 596 files.
Closest issue I could find was this one when Xcode 12 came out
The text was updated successfully, but these errors were encountered:
New Issue Checklist
Describe the bug
When applying the rule
unused_import
, the swiftlint analyzer chokes then reports no errors, even though there clearly are errors in the code.Complete output when running SwiftLint, including the stack trace and command used
Environment
xcodebuild -version
)? Xcode 14.0; Build version 14A309I have several files with clear violations of the rule (that I added myself, just to make 100% sure), but this is the output I get from running swiftlint:
Closest issue I could find was this one when Xcode 12 came out
The text was updated successfully, but these errors were encountered: