Hi, I’m the maintainer of the pipeline this is happening on.
Regarding your question: both the sonar scanner and SwiftLint are run as part of the same gitlab pipeline, albeit in different jobs (and docker containers). Both jobs show the same commit being checked out.
What I find most interesting is that the line number the scanner reports in the exception doesn’t actually appear in the JSON that SwiftLint outputs. In some cases (like the one posted here), the JSON being imported doesn’t even mention that file (AppLaunchCoordinator.swift).
I noticed that the JSON used absolute paths for source files so I tried switching to the generic SonarQube format instead, for which SwiftLint uses relative paths. Today the issue occurred even with that format, though.
Is there any more info we can provide that could help?