ios Xcode 4.4 错误 - 等待应用程序启动超时

Xcode 4.4 error - Timed out waiting for app to launch

提问by notsoux

yesterday I installed Xcode 4.4.

昨天我安装了 Xcode 4.4。

I'm working on a project which needs to run on ios 4.1 upwards, supporting iOS device with camera. Until I installed Xcode 4.4 everything went well, and I can test app on iphone 3gs and 4s. After I installed Xcode 4.4 I was unable to test app on iphone 3gs, and everytime I try to do it, xcode shows me that message: - Could not lauch "appname". timed out for app to lauch -

我正在开发一个需要在 ios 4.1 以上运行的项目，支持带摄像头的 iOS 设备。直到我安装 Xcode 4.4 一切顺利，我可以在 iphone 3gs 和 4s 上测试应用程序。安装 Xcode 4.4 后，我无法在 iphone 3gs 上测试应用程序，每次我尝试这样做时，xcode 都会向我显示该消息： -无法启动“appname”。应用程序启动超时 -

Does someone have any idea how to get rid of that error?

有人知道如何摆脱该错误吗？

回答by Vinzzz

I had a similar issue when trying to debug an App with Ad-Hoc provisioning... Check which provisioning you're using, it seems ad-hoc provisioning cannot be used for debugging.

我在尝试使用 Ad-Hoc 配置调试应用程序时遇到了类似的问题...检查您正在使用哪个配置，似乎临时配置不能用于调试。

EDITIn fact, it seems only developmentprovisioning profiles are Ok for debugging

编辑事实上，似乎只有开发配置文件才能进行调试

回答by bearMountain

For me:
Under Edit Scheme
For the Runconfiguration
On the Infotab
For Build Configuration
I had Releaseselected

对于我：
在Edit Scheme
对于Run配置下
在Info选项卡上
为Build Configuration
我Release选择了

But, it needs to be on Debugto run locally on a device.

但是，它需要Debug在设备上本地运行。

回答by B.M. Lam

I had a similar issue. In my case the reason was that I changed the setting for Launch ( xcode -> product -> Edit Scheme) to Wait and forgot about it.

我有一个类似的问题。就我而言，原因是我将 Launch ( xcode -> product -> Edit Scheme) 的设置更改为 Wait 并忘记了它。

When I changed the setting back to Automatic, the app will launch as usual.

当我将设置改回自动时，应用程序将照常启动。

回答by B.M. Lam

I also had same problem. I deleted old provisioning & distribution profiles from the testing devices and installed the modified profiles. The date of these provisioning profiles matter. The error timedout got solved.

我也有同样的问题。我从测试设备中删除了旧的配置和分发配置文件并安装了修改后的配置文件。这些配置文件的日期很重要。错误超时得到解决。

回答by Mann

It is issue of Provisioning profile. I was using Distribution Provisioning Profile. Changed back to Development Provisioning profile from Developer portal and used that, Solved the issue.

这是供应配置文件的问题。我正在使用分发配置文件。从开发人员门户改回开发供应配置文件并使用它，解决了问题。

回答by edaype

This worked for me on XCode 4.6 iOS 6.1.2

这在 XCode 4.6 iOS 6.1.2 上对我有用

• Open Organizer
• Select your device from the left
• Add to Portal
• Enter you Developer credentials
• Close Organizer and in the project file under your target select "Build Settings" -> "Code Signing Identity" pick the profile "iOS Team Provisioning Profile"
• Clean and run.

• 打开组织者
• 从左侧选择您的设备
• 添加到门户
• 输入您的开发人员凭据
• 关闭 Organizer 并在目标下的项目文件中选择“Build Settings”->“Code Signing Identity”选择配置文件“iOS Team Provisioning Profile”
• 清洁并运行。

回答by Matthew Velie

Remove the app from the device/simulator and try again, should work. Looks to be a bug in xcode.

从设备/模拟器中删除应用程序并重试，应该可以工作。看起来是 xcode 中的一个错误。

回答by SachinVsSachin

I had same problem now I resolved it ..

我遇到了同样的问题，现在我解决了..

Follow these step to sort out the problem.

请按照以下步骤解决问题。

Step:1Go to xcode folder like this

步骤：1像这样转到 xcode 文件夹

Step2:Reach to folder xcode->DerivedData

步骤 2：到达文件夹 xcode->DerivedData

Step3:Delete all folder inside of DerivedData

Step3：删除DerivedData里面的所有文件夹

It will work for you Thanks

它会为你工作谢谢

回答by mojuba

In my case the cause turned out to be the launch daemon being unable to load the app icons and crashing. Even though it didn't look like a crash - the device and the OS were becoming very slow or totally unresponsive. I figured this by analysing the crash logs. (My icons were too large - about 2,500x2,500 - I simply forgot to reduce their sizes properly before adding them to resources). Hope this helps someone.

在我的情况下，原因是启动守护程序无法加载应用程序图标并崩溃。即使它看起来不像是崩溃 - 设备和操作系统变得非常缓慢或完全没有响应。我通过分析崩溃日志发现了这一点。（我的图标太大了 - 大约 2,500x2,500 - 我只是忘记在将它们添加到资源之前正确减小它们的大小）。希望这可以帮助某人。

回答by FunkyMonkey

I tried all solution above with no success. But when I did complete cleanup of my iPhone 4S with iOS 7 this problem never occurred again.

我尝试了上述所有解决方案，但没有成功。但是当我用 iOS 7 彻底清理我的 iPhone 4S 时，这个问题再也没有发生过。