Question 130909 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode 13.3 magically changing a function call into a property access

Overnight, my Xcode got updated to 13.3. Since then, I am getting an error while compiling.

I have a method, which is now called xxxxasdfxxxx(). It appears in the last line of an if statement. For example:

       if  let state = ...,
            let field = state....,
            !field.xxxxasdfxxxx()
        {
        }

Whenever I compile, the code magically changes from a method to a property. So the above code suddenly looks like:

        if  let state = ...,
            let field = state....,
            !field.xxxxasdfxxxx {

Note, it is even moving the opening brace as well. I do not know if that is relevant.

This is a breaking change and I have no idea why it is doing it. Obviously the name of the function is not important as I have changed it several times. Interestingly, I have a piece of identical code in another part of the project that is not being magically changed.

Does anyone have an idea as to why this might be happening and how to get around it?

Tags:

3

Answers


  1. 0

    I had the same problem with Xcode 13.3 and I don’t know what is causing that. But I found a solution that worked for me and made possible to build the application without further problems.

    Just remove the ! from de method’s call and use == false instead as follows:

                if  let state = ...,
            let field = state....,
            field.xxxxasdfxxxx == false {
    Login or Signup to reply.
  2. 0

    This appeared to be happening to me as well. Setting the values == false did seem to work, but we had too many instances to change. After looking into it, it seemed perhaps it was our SwiftLint instance. Sure enough, updating SwiftLint to the latest release (0.47.0) fixed the issue. I’d recommend Double check your linters if you have any installed.

    Login or Signup to reply.
  3. 0

    I had the same problem with Xcode 13.4 and I solved it updating SwiftLint using this command line: brew upgrade swiftlint

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search