blocks|key|2930680|text|找到了解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2930681|2930682|+"Objective-C+Bridging+Header“设置(又称SWIFT_OBJC_BRIDGING_HEADER)必须设置在目标级别，而不是项目级别。请确保删除项目级别的设置值。|unordered-list-item|offset|length|style|CODE|2930683|2930684|(对我来说，它似乎是一个Xcode错误，因为我不知道它为什么要修复它)。|2930685|entityMap^0|0|0|Z|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@$F|R|G|S|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Found a solution:

<ul>
<li>The "Objective-C Bridging Header" setting (aka <code>SWIFT_OBJC_BRIDGING_HEADER</code>) must be set at the Target level, and NOT the Project level. Be sure to delete the setting value at the Project level.</li>
</ul>

(to me, it seems like an Xcode bug, since I don't know why it fixes it).

blocks|key|142884|text|我也有同样的问题。例如，我将所有的导入从#import+"HMSegmentedControl.h"更改为#import+<HMSegmentedControl/HMSegmentedControl.h>。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|142885|entityMap^0|K|U|1H|1D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I have the same issue. I changed all my imports from 
<code>#import "HMSegmentedControl.h"</code> to <code>#import &lt;HMSegmentedControl/HMSegmentedControl.h&gt;</code> for example.

blocks|key|2930716|text|我必须在用户头搜索路径中添加我的lib目录：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2930717|​|2930718|📷|atomic|2930719|2930720|在我的示例中，lib目录包含.a-library文件和一些头文件。这些都包含在桥接头文件中。然而，swift编译器找不到它们。只有当我将${PROJECT_DIR}/lib添加到用户头搜索路径时，它才构建测试目标。|2930721|(我在Mavericks+10.9.5上使用Xcode+6.2+)|2930722|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/42655ad165adc5098b5881b7307848ac.png|imageAlt^0|G|3|0|0|0|1|0|0|0|7|3|E|2|1W|I|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|K|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1E|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W|X|-4]]]]

I had to add my <code>lib</code> directory in User Header Search Paths:

<img src="https://i.stack.imgur.com/RXxde.png" alt="test target settings - user header search path">

In my case the <code>lib</code> directory contains the <code>.a</code>-library file and some header files. These are included in the bridging header file. However, the swift compiler wouldn't find them. Only when I added <code>${PROJECT_DIR}/lib</code> to the User Header Search Path it built the test target.

(I am using Xcode 6.2 on Mavericks 10.9.5)

blocks|key|145240|text|我们遇到了相同的错误消息，但原因完全不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145241|设置：|145242|145243|应用程序目标，所有Obj-C代码|unordered-list-item|145244|单元测试目标，具有单个快速测试用例&一个引用应用程序代码|145245|的桥接头|145246|当我们在清理(或在队友的机器上)之后添加第二个快速测试用例时，我们在构建单元测试目标时看到了这个错误。|145247|通过向单元测试目标添加一个虚拟Obj-C类修复了此问题。|145248|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

We encountered the same error message, with a completely different cause.

Setup:

<ul>
<li>App target, all Obj-C code</li>
<li>Unit Test target with a single swift test case &amp; a bridging header referring to app code</li>
</ul>

When we added the second swift test case, after a clean (or on a team mate's machine), we saw this error when building the unit test target.

It was fixed by adding a dummy Obj-C class to the unit test target.

blocks|key|144020|text|如果使用cocoapods，请尝试通过运行以下命令重新安装pods。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|144021|pod+install|code-block|syntax|javascript|144022|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If using cocoapods, try reinstalling the pods by running the following command.

<pre><code>pod install
</code></pre>

blocks|key|145419|text|使用Cocoapods安装库CocoaImageHashing时出现此错误。问题是搜索路径是错误的。因此，在目标级别，在生成设置公共搜索路径和标题搜索路径中，路径对应于不存在的文件夹，例如，当文件夹结构Headers/+->+/不存在时，路径为"${PODS_ROOT}/Headers/Public/CocoaImageHashing"，。我添加了路径${PODS_ROOT}/CocoaImageHashing，错误消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145420|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This error appeared when installing with Cocoapods the library CocoaImageHashing. 
The problem was that the search paths were wrong. So at the Target level, in Build Settings -> Search Paths -> Header Search Paths, the paths were corresponding to non existing folders, for example "${PODS_ROOT}/Headers/Public/CocoaImageHashing", when the folder structure Headers/Public/ did not exist.
I added the path ${PODS_ROOT}/CocoaImageHashing and the error disappeared.

blocks|key|2931286|text|在添加/重命名当前配置后，这种情况发生在我身上，这是有意义的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2931287|每个配置都使用由cocoapods生成的配置集，因此这些配置需要匹配。|2931288|因此，如果您添加/重命名配置，这些配置将需要使用正确的配置集，为此，运行pod+install可以做到这一点。|offset|length|style|CODE|2931289|entityMap^0|0|0|10|B|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

This happened to me after adding/renaming current configurations and it makes sense.

Every configuration makes use of Configurations Set generated by cocoapods so these 
things needs to match.

So if you add/rename configurations, these will need to use the right configuration sets, and for that running <code>pod install</code> will do it.

blocks|key|2930754|text|好吧，这有点奇怪，但我猜你必须在你的测试目标的“复制包资源”阶段添加一个资源，让它从你的主应用目标加载所有的头文件。在我的例子中，我添加了main.storyboard，它会处理这个错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2930755|​|2930756|📷|atomic|2930757|2930758|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e8f6abeb5b0f7662d272669083d0fb9d.png|imageAlt^0|1X|F|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|K|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

Well its little strange but I guess you have to add a resource to your "Copy Bundle Resources" phase of your test target to make it load all headers from your main app target. In my case, I added <code>main.storyboard</code> and it took care of the error.

<img src="https://i.stack.imgur.com/iRa7V.png" alt="enter image description here">

blocks|key|2931023|text|这在某种程度上为我做了这个把戏：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2931024|2931025|清理项目|unordered-list-item|2931026|清理构建文件夹|2931027|重启Xcode|2931028|2931029|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

This somehow did the trick for me:

<ul>
<li>Clean project</li>
<li>Clean build folder</li>
<li>Restart Xcode</li>
</ul>

blocks|key|144128|text|如果对任何人都有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|144129|在我的例子中，我添加的obj-c文件有一个引用文件夹(xcode中的蓝色文件夹)，但是头文件找不到它们。只需添加文件，而不是文件夹，从finder到xcode并解决。|144130|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If helps anyone. 

In my case my obj-c files were added has a reference folder (the blue folders in xcode) and the header couldn't find them.
Just added the files, not the folder, from the finder to xcode and solved.

blocks|key|2931178|text|(2017年5月27日更新)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2931179|Xcode+8.+Swift项目-导入Objective+C.|offset|length|style|BOLD|2931180|要知道的事情：|2931181|2931182|桥接头文件必须保存在项目的文件夹中。(即，不是保存在与保存.xcodeproj相同的级别，而是更低级别的文件夹中，所有快速和客观的c文件都保存在文件夹中)。它仍然可以在顶层找到文件，但是它不能正确地链接和导入Objective+C文件到桥接头文件中，|ordered-list-item|2931183|桥接头文件可以被命名为任何名称，只要它是一个.h头文件|2931184|请确保构建设置>+Swift编译器-常规>+Objective+C桥接头中的路径正确地指向你的桥接头文件，如果你仍然得到“找不到”，尝试首先清空你的桥接头文件并擦除你当前在那里写入的任何导入。确保可以首先找到桥接头文件，然后开始向该文件添加objective+c导入。出于某些原因，它会返回同样的“找不到”错误，即使它被找到了，但它不喜欢导入你的尝试由于某种原因你不应该#|2931185|+"MyBridgingHeaderFile.h“在你的任何目标C文件。这也会导致|2931186|出现"file+not+found“错误|2931187|entityMap^0|0|0|V|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|W|$]]

(Updated as of May 27, 2017)

Xcode 8. Swift Project - importing Objective C. 

Things to know:

<ol>
<li>Bridging header file MUST be saved within the project's folder. (i.e. not saved at the same level that .xcodeproj is saved, but instead one level further down into the folders where all your swift and objective c files are saved). It can still find the file at the top level, but it will not correctly link and be able to import Objective C files into the bridging header file</li>
<li>Bridging header file can be named anything, as long as it's a .h header file</li>
<li>Be sure the path in Build Settings > Swift Compiler - General > Objective C Bridging Header is correctly pointing to you bridging header file that you made</li>
<li>IMPORTANT: if you're still getting "not found", try to first empty your bridging header file and erase any imports you currently have written there. Be sure that the bridging header file can be found first, then start to add objective c imports to that file. For some reason, it will kick back the same "not found" error even if it is found but it doesn't like the import your trying for some reason</li>
<li>You should not #import "MyBridgingHeaderFile.h" in any of your objective C files. This will also cause a "file not found" error</li>
</ol>

blocks|key|143933|text|我也有同样的问题。对我来说，原因是我对我的App和我的Today扩展都使用了相同的桥头。我的Today扩展不包括Parse，但因为它是在桥头中定义的，所以它试图查找它。我为我的Today扩展创建了一个新的桥头，错误消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|143934|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem. For me the reason was that I was using the same bridging-header for both my App and my Today Extension. My Today Extension does not include Parse, but because it was defined in the bridging-header it was trying to look for it. I created a new bridging-header for my Today Extension and the error dissapeared.

blocks|key|145307|text|我的框架之前是工作的，然后突然停止工作，这些答案对我来说都不起作用。我在构建阶段>将二进制文件链接到库中删除了框架，并重新添加了它。又开始工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145308|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My framework was working before and suddenly stopped working, and none of these answers were working for me. I removed the framework in Build Phases > Link Binary With Libraries, and re-added it. Started working again.

blocks|key|142959|text|我遇到了一个问题，花了2个小时才找到。我的环境如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|142960|cocoapod+0.39.0|142961|swift+2.x|142962|XCode+7.3.1|142963|步骤：|142964|导入项目路径：project_name/project_name/your_bridging_header.h|offset|length|style|BOLD|142965|In+Swift段在生成设置中，Objective-C桥接标头应为：project_name/your_bridging_header.h|unordered-list-item|142966|
|142967|In+your_bridging_header.h，将所有声明从.h更改为#导入正在使用的类中的|142968|142969|+your_3rd_party.声明导入your_3rd_party|142970|142971|entityMap^0|0|0|0|0|0|7|1C|0|Y|Z|0|0|3|M|W|2|11|B|0|0|1|E|I|G|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@$L|18|M|19|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1A|8|@$L|1B|M|1C|N|O]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|R|7|1E|8|@$L|1F|M|1G|N|O]|$L|1H|M|1I|N|O]|$L|1J|M|1K|N|O]]|9|@]|A|$]]|$1|W|3|T|5|6|7|1L|8|@]|9|@]|A|$]]|$1|X|3|Y|5|R|7|1M|8|@$L|1N|M|1O|N|O]|$L|1P|M|1Q|N|O]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|11|$]]

I had an issue and fixed it after spending 2 hours to find. My environment as below:

cocoapod 0.39.0

swift 2.x

XCode 7.3.1

Steps:

<ol>
<li>project path: project_name/project_name/your_bridging_header.h</li>
<li>In Swift section at Build Setting, Objective-C Bridging Header should be: project_name/your_bridging_header.h</li>
<li>In your_bridging_header.h, change all declarations from .h to #import </li>
<li>In class which is being used your_3rd_party. Declare import your_3rd_party</li>
</ol>

blocks|key|141902|text|如果您使用的是Cocoapods，请尝试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141903|141904|退出Xcode|ordered-list-item|141905|pod+deintegrate|offset|length|style|CODE|141906|pod+install|141907|141908|对我来说，这解决了一个奇怪的问题。|141909|entityMap^0|0|0|0|0|F|0|0|B|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@$H|W|I|X|J|K]]|9|@]|A|$]]|$1|L|3|M|5|E|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|R|$]]

If you are using Cocoapods, try:
<ol>
<li>Quit Xcode</li>
<li><code>pod deintegrate</code></li>
<li><code>pod install</code></li>
</ol>
For me, this solved the weird issue.

blocks|key|2718439|text|我刚刚复制了一个现有的方案，并在项目中添加了另一个配置。我必须将具有相同名称的配置添加到框架的项目中，以便它也能在相同的DerivedData/($AppName)/Build/Products/($CONFIGURATION_NAME)文件夹中构建。否则，无法创建.framework文件，因此无法导入。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2718440|entityMap^0|1O|1N|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had just duplicated an existing scheme and added another configuration to the project. I had to add a configuration with the same name to the framework's project in order for it to also build in the same <code>DerivedData/($AppName)/Build/Products/($CONFIGURATION_NAME)</code> folder. Otherwise the .framework file doesn't get created and therefore can't be imported.

blocks|key|2931053|text|我今天在我的Swift项目中尝试使用Objective-C编写的pod时遇到了同样的问题，上面的解决方案似乎都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2931054|在我让use_frameworks!写的播客文件中。注释此行，然后再次运行pod+install为我解决了这个问题，错误也就消失了。|offset|length|style|CODE|2931055|entityMap^0|0|3|F|11|B|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

I ran into the same issue today when trying to use a pod written in Objective-C in my Swift project, none of the above solutions seemed to work. 

In the podfile I had <code>use_frameworks!</code> written. Commenting this line and then running <code>pod install</code>again solved this issue for me and the error went away.

blocks|key|2718589|text|我也遇到过类似的问题，只有一个解决方案适合我。我尝试了所有建议的方法，我知道我的桥接头设置得很好，因为我有一些其他的库在工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2718590|当我在没有Cocoapods的情况下将库(拖放)复制到项目中时，只有在那之后我才能正确地导入头文件。|2718591|我用的是facebook/Shimmer库。|2718592|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had similar problem and only one solution worked out for me. I tried everything suggested, and I knew that I set my bridging header fine, because I had some other lib working.

When I copied library (drag and drop) into the project, without Cocoapods, only after that I could import headers without errors.

I used facebook/Shimmer library.

blocks|key|143115|text|我在pods上也遇到过类似的问题。基本上，在尝试运行我的UI测试时，Xcode抱怨缺少pod。对此的解决方案比上面描述的任何解决方案都简单得多：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|143116|143117|转到项目文件(main不是目标)|ordered-list-item|143118|单击"Info“选项卡(最左侧)|143119|为UI测试目标设置正确的pod配置(+"Deployment+target”下的“Configurations”部分)|143120|143121|工作中！|143122|我在一个线程中找到了它：https://github.com/CocoaPods/CocoaPods/issues/2695|offset|length|143123|听起来有点像可可豆荚的bug，但我知道为什么它可能是一个棘手的案例。|143124|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/CocoaPods/CocoaPods/issues/2695^0|0|0|0|0|0|0|0|C|1E|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@$O|18|P|19|1|1A]]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I had a similar issue with pods. Basically trying to run my UI tests, Xcode complained about missing pods. Solution to this was much simpler than any described above:

<ol>
<li>go to project file (main not a target) </li>
<li>click on the "Info" tab (most left) </li>
<li>set proper pod configuration for UI tests target
("Configurations" section right under "Deployment Target")</li>
</ol>

Working!

I found it in a thread: <a href="https://github.com/CocoaPods/CocoaPods/issues/2695" rel="nofollow noreferrer">https://github.com/CocoaPods/CocoaPods/issues/2695</a>

Sounds a bit like a bug for cocoa pods but I can see reasons why it might be tricky case.

blocks|key|145474|text|在我的情况下，我不得不退出模拟器...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145475|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I just had to quit the simulator...

blocks|key|2931247|text|清理项目，清理构建文件夹，重新启动Xcode。我只是删除了goto+>+Build+Settings+>+Search+the+keyword中的路径。Swift编译器-通用->+Objective-C桥头为我工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2931248|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Clean project,Clean build folder,Restart Xcode. i just remove path at project goto > Build Settings > Search the keyword. Swift Compiler - General -> Objective-C Bridging header worked for me.

blocks|key|141832|text|2019年8月|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|141833|在我的例子中，我想在来自相同目标的Objective-C头文件中使用Swift协议，为此，我需要使用Swift协议的转发声明来在Objective-C接口中引用它。这对于在Objective-C头文件中使用Swift类也是有效的。要使用转发声明，请参阅在使用转发声明的Objective-C标头中包含Swift类的docs中的以下示例|141834|//+MyObjcClass.h
@class+MySwiftClass;+//+class+forward+declaration
@protocol+MySwiftProtocol;+//+protocol+forward+declaration

@interface+MyObjcClass+:+NSObject
-+(MySwiftClass+*)returnSwiftClassInstance;
-+(id+<MySwiftProtocol>)returnInstanceAdoptingSwiftProtocol;
//+...
@end|code-block|syntax|javascript|141835|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/documentation/swift/imported_c_and_objective-c_apis/importing_swift_into_objective-c^0|0|7|0|4D|4|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|I|5|J|7|11|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

August 2019

In my case I wanted to use a Swift protocol in an Objective-C header file that comes from the same target and for this I needed to use a forward declaration of the Swift protocol to reference it in the Objective-C interface. The same should be valid for using a Swift class in an Objective-C header file. To use forward declaration see the following example from the <a href="https://developer.apple.com/documentation/swift/imported_c_and_objective-c_apis/importing_swift_into_objective-c" rel="nofollow noreferrer">docs</a> at Include Swift Classes in Objective-C Headers Using Forward Declarations:

<pre><code>// MyObjcClass.h
@class MySwiftClass; // class forward declaration
@protocol MySwiftProtocol; // protocol forward declaration

@interface MyObjcClass : NSObject
- (MySwiftClass *)returnSwiftClassInstance;
- (id &lt;MySwiftProtocol&gt;)returnInstanceAdoptingSwiftProtocol;
// ...
@end
</code></pre>

I have a Swift project for which I'm trying to import ObjC-based frameworks. The framework is located in a directory under the project's path and is referenced by the project in Xcode. It's also added to the "Link Binary with Libraries" in the project's 'Build Phases' page.

However, for some reason, I can't seem to include the framework in the Bridging-Header file. I get the following error:

<pre><code>BridgingHeader.h:5:9: error: 'Parse/Parse.h' file not found
#import &lt;Parse/Parse.h&gt;
 ^
&lt;unknown&gt;:0: error: failed to import bridging header 'BridgingHeader.h'
</code></pre>

Things I've checked:

<ol>
<li>The "Install Objective-C Compatibility Header" is set to "YES".</li>
<li>The Header Search Paths includes the path to the frameworks.</li>
</ol>

I'm sure I'm missing something, so if anyone has any clues, that would be great.

Getting "file not found" in Bridging Header when importing Objective-C frameworks into Swift project

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我有一个Swift项目，我正在尝试为其导入基于ObjC的框架。该框架位于项目路径下的目录中，并由Xcode中的项目引用。它还被添加到项目的“构建阶段”页面中的"Link Binary with Libraries“中。但是，由于某些原因，我似乎不能将框架包含在桥头文件中。我得到以下错误：BridgingHeader.h:5:9: error: 'Parse/Parse.h' file not fo

问将Objective-C框架导入Swift项目时，桥接头中出现“找不到文件”
EN

回答 22

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Objective-C框架导入Swift项目时，桥接头中出现“找不到文件”EN

回答 22

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Objective-C框架导入Swift项目时，桥接头中出现“找不到文件”
EN