Unable to do refactoring on my Swift file in Xcode 9

Question

I am using Xcode 9 and I am trying to do Refactoring on my Swift based file but every time I am getting below error:

Refactoring engine ranges didn't match initial ranges

Why isn't it matching the initial range?

13.3! It's the bug that keeps on giving. (I tried to rename; was told this was an illegal re-declaration, undid the rename, deleted the other file, and got the error. Building did nothing. After restarting, I opened the file... with the new name already in place.) — green_knight, Apr 22 '22 at 18:34
Apple should literally outsource creating the IDE to Jetbrains! — Darshan, Mar 24 '23 at 07:26

score 29 · Answer 1 · edited Jun 28 '20 at 09:41

29

Workaround: Restart Xcode.

This has not been resolved yet as of January 2018 (Xcode 9.2).

edited Jun 28 '20 at 09:41

Cœur

37,241
25
195
267

answered Jan 06 '18 at 18:49

Cannoliopsida

3,044
5
36
61

1

In Xcode 9.2, close the project and open it again (don't have to restart Xcode). Worked for me – auspicious99 May 08 '18 at 09:38
1

I think clearing out derived data will make the indexing working once again and you shouldn't need to restart Xcode... Altought paradox is that restarting Xcode is faster :D – Dominik Bucher Dec 14 '18 at 09:16

score 25 · Answer 2 · edited Jan 07 '20 at 21:34

25

Build your project (Command ⌘ + B) and it will fix the error. After doing it, I could rename my file successfully.

edited Jan 07 '20 at 21:34

shim

9,289
12
69
108

answered Jan 07 '20 at 19:41

Jose Antonio

376
4
6

1

This works for me with XCode 13.3 (13E113). – Alain Apr 12 '22 at 07:20
1

Restarting Xcode didn't work for me, but this did. Xcode 13.3 (13E113) – charmingToad May 12 '22 at 00:55

manman · Answer 3 · 2018-09-09T00:18:05.460

Update For some reason, it's not happening for me anymore. I noticed also whenever I don't let indexing finishes before trying to start doing a refactor or tap on refactor many times, still see the error, but not permanent anymore.

I asked an engineer at WWDC 2018 about this issue. This issue was happening for me in only one project in my workspace. Other projects in the same workspace works fine. At the moment, there's no solution to this issue. If you want to help Apple to fix this, you can close your Xcode and run following command in terminal:

SOURCEKIT_SERVICE_LOG=3 /Applications/Xcode.app/Contents/MacOS/Xcode 2>&1 | tee /tmp/sk-log.txt

And then try to reproduce the issue and send them the log file (/tmp/sk-log.txt) so they can narrow it down and hopefully fix it in future Xcode versions.

Notice This is project related issue and won't be fixed with OS updates, Xcode updates, or any number of restarting applications, at least the one that I'm having.

axunic · Answer 4 · 2018-08-31T09:37:36.380

I have Xcode's project created using Xcode8 long time ago. For some reason I have to upgrade to Xcode9 (9.4.1 exactly). Then I experienced that error only on that old project, not the new one created using Xcode9.

So i think that error related to project issue. So I decided to compare the settings between old and new one. There are some differences, and after several tries, by changing Optimization Level for Debug solved refactor issue.

In project editor, select your Target, Build Settings
Set Optimization Level (Debug) = No optimization [-Onone]
Delete DerivedData folder related to your project in /Users/YourMacUsername/Library/Developer/Xcode/DerivedData
Clean project shiftcommandk.
Build project commandb.

I am using Xcode 12.4 and this solved my issue. – Jake A. Apr 03 '21 at 05:53 — Jake A., Apr 03 '21 at 05:53

score 4 · Answer 5 · answered Aug 01 '19 at 05:43

4

I have the same issue in Xcode 10.3. Refactoring didn't work when I right clicked → refactor → rename on the class name in the class definition. However it did work when I did the same somewhere in code where I use that class.

answered Aug 01 '19 at 05:43

WalterBeiter

2,021
3
23
48

Have you made a feedback on http://feedbackassistant.apple.com ? – Cœur Jun 28 '20 at 09:24

score 3 · Answer 6 · answered Jan 10 '20 at 00:52

3

Product -> Clean Build Folder -> Quit Xcode -> Reopen Project -> Build

answered Jan 10 '20 at 00:52

Richard Poutier

207
2
10

score 2 · Answer 7 · answered Sep 19 '18 at 19:44

2

I update to Xcode 10 and finally refactoring now it works again after a year without refactoring

answered Sep 19 '18 at 19:44

pableiros

14,932
12
99
105

1

Just got one in Xcode 10. :-) But I believe it is a limitation in Xcode to do refactoring without actually building it. For my case. I rebuilt it then that error is gone when I tried to refactor. – Paul Sep 29 '18 at 13:42
@Paul same was for me – pableiros Sep 29 '18 at 17:18
@Paul Add another instance in Xcode 10 - all well after clean/rebuild. – green_knight Dec 04 '18 at 20:01
1

@Paul And another on Xcode 13.2. It seems the "ranges" refer to the build targets (e.g. iPhone 13 Pro) – Collierton Dec 21 '21 at 19:30

score 2 · Answer 8 · answered Apr 25 '21 at 06:10

I am on Mac M1 and using Xcode Version 12.5 beta 3.
I was facing the same issue when trying to rename ViewController.
Before renaming it, I moved it to a new group, and my code was in a running state. Not sure if that was the reason for the issue.
But I restarted the Xcode and the issue was resolved for me.

score 0 · Answer 9 · answered Aug 01 '18 at 17:44

0

I was experiencing the exact same issue. It turned out that I had my build configuration set to Release mode. Changing it to Debug, cleaning build folder and recompiling fixed the issue for me.

answered Aug 01 '18 at 17:44

user3001830

1

score 0 · Answer 10 · answered Sep 08 '21 at 20:28

0

Remove `DerivedData`

This worked for me for this error and other kind of refactoring errors.

Close Xcode
Remove DerivedData:

rm -rf ~/Library/Developer/Xcode/DerivedData

answered Sep 08 '21 at 20:28

Pedro Trujillo

1,559
18
19

score 0 · Answer 11 · answered Nov 28 '22 at 04:44

0

I experienced this on a Mac M1, using Xcode Version 14.1 (14B47b).

This helped: Clean project: shift-command-k. Build project: command-b.

answered Nov 28 '22 at 04:44

bravestLimit

33
1
9

score 0 · Answer 12 · answered Feb 28 '23 at 14:12

0

Xcode 14.2: New project and tried to refactor the name of the ViewController and got the rename error pop up. Saved the the project and did a build. Refactoring the file name worked after that.

answered Feb 28 '23 at 14:12

Bob Taylor

61
1
5

Tamara Andonovska · Answer 13 · 2023-05-25T10:13:40.867

In case none of the above works (usually does for me too, except for this one time when it didn't), this is what worked for me:

I remove reference of the file (but still keep the actual file). Remove reference window option
I open the folder where I have the file I previously removed and I drag and drop the file in the same place I needed it to be. Make sure Copy items if needed in unselected. Drag-and-drop window option
Clean build folder and Build.
Wait for indexing to finish.
Refactor.

Note: I'm using Xcode 14.3

score 0 · Answer 14 · answered May 25 '23 at 13:58

None of the below worked for me. But I could do it. This is my solution.

My case was like:

variable = [self functionName];

and "functionName" failed to refactor > rename. What I did is took this function call in brackets like this:

variable = ([self functionName]);

After that I could rename this function.

Unable to do refactoring on my Swift file in Xcode 9

14 Answers14

Remove DerivedData

Remove `DerivedData`