Swift Protocol Analysis

Rules and Languages Report False-positive / False-negative...
,
1

  • What language is this for? Swift

  • Which rule? swift:S2962 and swift:S4144

  • Why do you believe it’s a false-positive/false-negative? Fields within a protocol must be defined with get/set.

  • Are you using: SonarQube Cloud

    • How can we reproduce the problem? Give us a self-contained snippet of code (formatted text, no screenshots)

      protocol Foo {

      var bar: String { get set }

      var bar2: String { get set }
      }

Has something changed around how analysis is performed? Our issues jumped from 115~ to over 700 between two runs:

Screenshot 2025-12-19 at 15.40.29
Screenshot 2025-12-19 at 15.40.291872×1068 33.9 KB

2

Hi,

In fact, we released a completely re-written Swift analyzer.

I’m going to flag this for the language experts.

 
Ann

6

Hello @LewisOxbury ,

First of all thank you for the feedback.

FYI fixes for the false-positives in swift:S2962 and swift:S4144 will be deployed to SonarQube Cloud next week.

1 Like
10

After our update to SonarQube Server 2026.1.0.119033, we receive exactly the same issue from rule S4144 on these code blocks, when using { get } in a protocol:

Update this function so that its implementation is not identical to getter on line X

Can you confirm in which Server version this was fixed, or if this regressed?

I also had a look at the release logs, and found SONAR-27277 which promises some improvements in the next update but without any information at all…

Thanks!

11

Hi @Nef10,

This was fixed in late January. That means it’s included in the next release of SonarQube Server, so if you pick up 2026.2.1 you should get the fix.

 
HTH,
Ann

12

Hello @Nef10

The fix for this issue made into SonarQube Server 2026.2,
and then was also backported to SonarQube Server 2026.1.2 LTA

1 Like
13

Thanks, after updating the server to => 2026.1.2 it’s fixed for me.

2 Likes