WatchKit error - unable to find interface controller class '' to instantiate

Question

Whenever I make any connections in my subclass of WKIInterfaceController I get error WatchKit error - unable to find interface controller class 'myClass' to instantiate and a activity indicator showing in simulator and the view does not load. Disconnect all conections and the view displays correctly but still get the error

Tried

Unable to find interface controller class 'InterfaceController' to instantiate

WatchKit: unable to find interface controller class

WatchKit reloadRootControllersWithNames causing error, with pageController or after push/pop

Two links suggests a bug, If it is a bug this would surely not be present on the release version of XCode and everyone would experience the same behaviour rendering watcKit all but useless?

There are many many bugs in the XCode release version!! XD – Josh Feb 02 '16 at 15:36 — Josh, Feb 02 '16 at 15:36

score 42 · Answer 1 · answered Apr 27 '15 at 19:11

42

I solved this issue by:

1) deleting trouble-making InterfaceController file and creating it again in the folder for WatchKit Extension in the project (not just in a group in Project navigator). By default xcode gives you Watch App folder - you have to change it.

2) setting class in Interface Builder so that module was set to ProjectName_WatchKit_Extension

If module is not set - xcode won't be able to find your class

answered Apr 27 '15 at 19:11

Aleksandr Shcherbakov

759
1
6
16

This was my issue, Module wasn't set for some odd reason. Using the new Xcode 7. – Ruben Martinez Jr. Jun 13 '15 at 18:32
2

This was also my issue, however I didnt get how to change the module with your description. The module option is found in the Interface Builder, right panel, the third tab, right below the Class option. – Juan Haladjian Apr 26 '16 at 18:02
1

Part 2 was the solution for me. I had replaced an ObjC file with a Swift file, and of course Swift files need a module. – lewis Dec 11 '18 at 15:31
What in case when you have multiple targets for WatchKit/WatchKitExtensions? I can put there only one module, but I have 4 different targets for WatchKit/WatchKitExtensions (together 8 targets). – Ariel Bogdziewicz May 06 '19 at 10:00
Ok, I solved it for multiple targets by WatchKitTargetApp[1-N] -> Build Settings -> Interface Builder Storyboard Compiler -> Default Module must be set to WatchKitExtensionModule[1-N] and in Storyboard you have to check Inherit Module From Target. – Ariel Bogdziewicz May 06 '19 at 10:21
I renamed the target and failed to update the module field in Storyboard. Thanks. – Friendtam May 17 '19 at 11:54

score 25 · Accepted Answer · answered Mar 19 '15 at 11:06

25

For anyone else who has this. The class must be set to the correct target membership ie yourApp WatchKit Extension rather than yourApp WatchKit App when creating your class. It can also be edited in Target membership in interface builder.

answered Mar 19 '15 at 11:06

JSA986

5,870
9
45
91

score 16 · Answer 3 · answered Mar 18 '15 at 23:20

16

I was having same issues after the recent 8.2 release. I had to go to each one of my InterfaceControllers and adjust its custom class module to whatever was shown as an option or "none".

answered Mar 18 '15 at 23:20

devone

293
3
10

1

This was a big help for me... same issue and nothing else worked, thanks! – GarySabo Jul 24 '15 at 21:30
2

I had this issue after copying an InterfaceController from an existing project into the current project. Fixed by changing the module back to none/empty. Thanks. – mumush Aug 03 '15 at 06:50

score 12 · Answer 4 · answered Dec 05 '16 at 09:05

12

After adding new Interface controller in WatchOS, above issue is occurred due to wrong

"Module Name in Custom Class" :-

After changing the module to extension above issue is resolved.

answered Dec 05 '16 at 09:05

Shrawan

7,128
4
29
40

1

Thanks for putting in the images! I absorb images a lot quicker that way. – Jacksonkr Feb 08 '18 at 20:09

score 2 · Answer 5 · edited May 23 '17 at 12:02

2

In my case I renamed Watch Kit Extension to WatchKitExtension, and it was running succesfully on simulator, but failed to run after full project clean.
Thanks to https://stackoverflow.com/a/29904047/104170.
In order to make it work I just needed to specify correct module in my .storyboard file

edited May 23 '17 at 12:02

Community

1
1

answered Jun 11 '15 at 17:59

tt.Kilew

5,954
2
33
51

Kamani Jasmin · Answer 6 · 2018-09-28T18:57:08.053

2

1. select your WKInterfaceController
2. select Inherit Module From Target

edited Sep 28 '18 at 18:57

answered Jul 15 '18 at 13:46

Kamani Jasmin

691
8
11

score 2 · Answer 7 · edited Feb 18 '19 at 05:48

2

The problem here is that we set the module for the interface controllers incorrectly. Since those controllers belong to Watch Extension target, we can find the product module as below

Image to show how to find the product module name

image to show how to find the product module name

Once we have the module name, just go ahead and set it for each interface controller

image to show how to set the product name

image to show how to set the product name

edited Feb 18 '19 at 05:48

kenlukas

3,616
9
25
36

answered Feb 18 '19 at 03:25

kyhai

21
3

score 1 · Answer 8 · answered Jan 22 '16 at 07:27

1

When you create your glance interface controller, be sure to add it to the the Watch App Extension. This was my problem.

answered Jan 22 '16 at 07:27

VaporwareWolf

10,143
10
54
80

score 1 · Answer 9 · answered Jan 28 '16 at 00:05

1

You need to verify the view controller is in your compile source here: Select Project > Select Watchkit Extension Target > Build Phases > Compile Sources

answered Jan 28 '16 at 00:05

zaolian

1,187
3
11
21

This has already been answered correctly and marked as correct "class must be set to the correct target membership" it is not a compile resources issue – JSA986 Jan 28 '16 at 10:17
@JSA986 Thanks for the comment! I ran into the problem and the above correct answer was not detailed enough for me to solve it. It tells me Why, but not How. Thus I think writing the steps here might be useful to people new to iOS development. – zaolian Jan 28 '16 at 17:30

score 1 · Answer 10 · answered Feb 02 '16 at 15:41

1

Clicking in my Watch storyboard > Interface controller Scene > Identity Inspector (the middle icon, from the 5 icons that appear on the menu at the right of Xcode) > Set Module to "[YourProjectName]Extension" worked for me!

answered Feb 02 '16 at 15:41

Josh

6,251
2
46
73

If yourprojectname is a name with spaces is it then for example literally Foo LooExtension of how is it? – user1007522 Sep 21 '16 at 10:45
I am not sure... @user1007522 – Josh Sep 21 '16 at 14:17

score 1 · Answer 11 · answered Aug 03 '16 at 08:25

1

Just look target for both class and interface. It should be set to Extension that's all

answered Aug 03 '16 at 08:25

Ali

514
5
16

Actually Inteface.storyboard should be in Watch App target, not in Extension. – kelin Dec 07 '22 at 12:41

score 1 · Answer 12 · answered Sep 23 '16 at 14:25

1

I solved it by setting Module to Watch_Extension

answered Sep 23 '16 at 14:25

rgreso

496
1
7
19

score 0 · Answer 13 · answered Oct 27 '15 at 23:42

0

Make sure you make the new Class member of the EXTENSIONS while you are creating the class.

answered Oct 27 '15 at 23:42

kavehmb

9,822
1
19
22

score 0 · Answer 14 · answered Nov 10 '15 at 10:14

0

I fixed it by clearing the module name in the storyboard for that specific interface class. (Which is a objective-c class).

answered Nov 10 '15 at 10:14

basvk

4,437
3
29
49

score 0 · Answer 15 · answered May 23 '19 at 16:39

0

Just drove myself nuts over this for a couple of hours. Followed all the suggestions here, no luck.

What ended up for me is what I should have done in the first place - I cleaned the build folder.

Product > Clean Build Folder

answered May 23 '19 at 16:39

swiftyboi

2,965
4
25
52

score 0 · Answer 16 · answered Sep 25 '19 at 15:25

0

Make sure the module name in storyboard is same as .appex file under tagerts/XXX WatchKit App General Tab -> Frameworks, Libraries, and Embedded Content.

answered Sep 25 '19 at 15:25

Evan

1,152
1
11
18

Developersian · Answer 17 · 2020-04-30T07:46:26.473

the accepted answer didn't work for me.

I did answer it completely In this post: https://stackoverflow.com/a/61517773/7345611

but I did put the part related to this question here:

The best approach that worked for me is:

go to interface.storyboard located at left navigator pane in Xcode
select the yellow circle on top of a interfaceController
go to it's identity inspector
in class section, reassign your class to that interfaceController by retyping the class name and hitting enter which Xcode will updates the module section under it automatically. (all your problem lie in Module Section where Module still has the old name assigned to it)
do the same process for all interfaceControllers and customClasses(if you have any) and everything that you assigned a class to it before.

now the app should run as expected.

WatchKit error - unable to find interface controller class '' to instantiate

17 Answers17

Linked