cannot find type in scope xcode 13

Question

Created Oct ’21

Replies 11

Boosts 5

Views 41k

Participants 17

I had many swift compiler errors of this type : "Cannot find type 'className' in scope" after passing from Xcode 12.5 to Xcode 13. And the error is always referred to Objective-C classes. The project is for an iOS 11 app for iPad.

The bridging-header is correctly set and the project with the same build-settings has never given this error before Xcode 13.

I'll try to clean the derived data folder without success. the strange thing is project compile successfully and I can run on simulator as well but after few second from a successful compilation on any swift files that use objective-c class is fired the swift compiler error.

Any idea? thanks

Answered by mrcdev in 696443022

I finally solved the problem removing all #import in bridging header of files contained in my pods libraries

Boost

Answer 1

Claude31 OP

Oct ’21

Could you post the code where you get the error message, as well as the needed context ?

0

Answer 2

mrcdev OP

Oct ’21

I add sample code and screen of the error, i hope is useful, PersonalEditorContentPageVC and QWidget are Objective-c classes.

class ContactViewController:PersonalEditorContentPageVC {
    var activeWidget:QWidget?
    var prevActiveWidget:QWidget?

Screenshot 2021-10-08 at 22.11.41.jpg

1

Answer 3

Helam OP

Oct ’21

I've got the same issue. In Xcode 13 only, I get "Cannot find X in scope" errors for all the objective-c stuff that i'm using in Swift, but the project still builds and runs successfully.

0

Answer 4

YShaw OP

Oct ’21

I've got the same issue. Is there any way to solve this issue?

0

Answer 5

OOPer OP

Oct ’21

@YShaw, the same error declaration would help very little solving your issue. You should better start your own thread with including enough info.

0

Answer 6

naveenfieldwire OP

Nov ’21

Same issue after upgrading to Xcode 13, Any fix ?

0

Answer 7

Duckbell OP

Nov ’21

Go to build settings and build after setting Precompile Bridging Header YES -> NO. You can show no errors. But codes defined by objec aren't recognized. It is not able to jump to definition.

9

Answer 8

mrcdev OP

Nov ’21

Accepted Answer

I finally solved the problem removing all #import in bridging header of files contained in my pods libraries

4

Answer 9

Ean16 OP

May ’22

I finally solved the problem with Product -> Clean Build Folder

8

Answer 10

Vinaykucoder OP

Aug ’22

I am seeing complier error on WKMediaCaptureType and WKPermissionDecision. I made sure WebKit is imported in WebViewDelegationHandler.swift file. Cannot find type 'WKMediaCaptureType' in scope. Cannot find type 'WKPermissionDecision' in scope. Any clue why it is happening. Thanks in advance!

0

Answer 11

dr2050 OP

Mar ’23

In my case, everything works but Xcode reports errors anyway. In this case, moving around the order of imports in the bridging header helped.

So it's not a real problem but you can solve it anyway.

4