blocks|key|889652|text|我解决了这个问题，做了一个简单明了的项目：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|889653|产品->清洁。|unordered-list-item|889654|窗口->项目->选择项目并删除派生数据。|889655|关闭XCode。|889656|重新开始项目。|889657|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

I solved this problem doing tipical project clean steps:

<ul>
<li>Product -> Clean. </li>
<li>Window -> Projects -> Select your project and
delete derived data. </li>
<li>Close XCode. </li>
<li>Reopen project.</li>
</ul>

blocks|key|971180|text|我遇到了这个问题，并在日志中注意到了这一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971181|-[MIBundle+pluginKitBundlesSkippingPlatformValidation:withError:]:+Ignoring+plugin+at+(path+to+my+app+extension)+because+it+doesn't+work+on+this+OS+version|code-block|syntax|javascript|971182|为我的扩展更新“生成设置”中的部署目标版本修复了这个问题。|971183|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I encountered this issue and noticed this in the log:

<pre><code>-[MIBundle pluginKitBundlesSkippingPlatformValidation:withError:]: Ignoring plugin at (path to my app extension) because it doesn't work on this OS version
</code></pre>

Updating the Deployment Target version in Build Settings for my extension fixed this.

blocks|key|1725310|text|奇怪的是，将我的项目的根文件夹重命名为其他东西对我来说很有好处。可能是因为某些具有文件夹现有名称的xcode缓存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725311|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|$]]

Very strangely, renaming the root folder of my project to something else did the trick for me. Probably some caching of xcode somewhere with the existing name of the folder was the reason.

blocks|key|889686|text|我在做共享扩展的时候也遇到了同样的问题。这里提出的解决办法对我都没有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|889687|我关心调试和日志记录。我无法调试和/或记录。起初，我认为扩展不起作用，但我运行了一个测试，并验证了它实际上正在执行，但由于某种原因，我无法调试或记录。|889688|我能想到的最好的方法是手动附加调试器，在我想要记录的地方添加断点，编辑断点，添加操作来记录，然后在评估后继续。以下是这样做的步骤：|889689|将活动方案设置为所需的扩展(从顶部栏或从Product/Scheme/Choose-Your-Scheme+)|ordered-list-item|offset|length|style|CODE|889690|Debug/Attach+to+Process+by+ID+or+Name...。然后键入扩展名或其包id。|889691|添加要添加日志的断点。编辑断点。添加操作(日志消息)并输入所需的日志。检查Automatically+continue+after+evaluating+the+actions。|889692|这里，你可以找到我没有答案的问题。|889693|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/q/54443613/1051589^0|0|0|0|K|X|0|0|14|0|11|1F|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|13|8|@$I|14|J|15|K|L]]|9|@]|A|$]]|$1|M|3|N|5|H|7|16|8|@$I|17|J|18|K|L]]|9|@]|A|$]]|$1|O|3|P|5|H|7|19|8|@$I|1A|J|1B|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1C|8|@]|9|@$I|1D|J|1E|1|1F]]|A|$]]|$1|S|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I had the same issue when I was working on a share extension. None of the suggested solutions here worked for me.

I cared for debugging and logging. I wasn't able to debug and/or log. I thought at first that the extension wasn't working, but ran a test and verified it was actually executing but for some reason I wasn't able to debug or log.

The best I was able to come up with is to manually attach a debugger, add breakpoints where I wanted to log, edited the breakpoints and added actions to log and continue after evaluation. The following is the steps to do so:

<ol>
<li>Set the active scheme to the extension you want (from the top bar, or from <code>Product/Scheme/Choose-Your-Scheme</code></li>
<li><code>Debug/Attach to Process by ID or Name...</code>. Then type the name of the extension or its bundle id.</li>
<li>Add breakpoints where you wanted to add logs. Edit the breakpoint. Add action (Log Message) and enter the log you want. Check <code>Automatically continue after evaluating the actions</code>.</li>
</ol>

<a href="https://stackoverflow.com/q/54443613/1051589">Here</a> you can find my unanswered question.

blocks|key|1725358|text|我在iOS+13上通过XCode+11+Beta+4测试Cordova应用程序时遇到了同样的问题。通过遗留系统构建解决了这个问题(文件>工作区设置)。>构建系统>遗产构建系统)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725359|希望它能帮上忙|1725360|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|$]]

I ran into the same issue while testing a Cordova app on iOS 13 via XCode 11 Beta 4. 
Building via the legacy system solved it (File > Workspace Settings... > Build System > Legacy Build System).

Hope it helps

blocks|key|971285|text|在Xcode+11+beta+5中，我也犯了同样的错误。我无法安装这个应用程序。我甚至把应用程序上传到，然后尝试用TestFlight进行安装，但是被下载后应用程序没有安装，非常奇怪。没有来自App连接的错误。通过使用模拟器运行应用程序，我发现了这个问题。在模拟器上运行这个应用程序之后，Xcode给了我一个详细的错误消息。在我的例子中，我有多个框架，具有相同的Bundle+In。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971286|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 Xcode 11 beta 5, I had the same error. I couldn't install the app. I even uploaded the app to App Store Connect, then tried to install with TestFlight, but the app failed to install after being downloaded, very weird. No error from App Store Connect. I found the issue by running the app with the Simulator. After running the app on the Simulator, Xcode gave me a detailed error message. In my case, I had multiple frameworks with the same Bundle IDs.

blocks|key|889732|text|我也犯了同样的错误，但是上面的解决方案对我都没有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|889733|在我的例子中，我使用的是一个免费的苹果开发者帐户，并在尝试安装第四个应用程序后发现了这个错误。免费帐户的安装限制为3。我删除了我已经拥有的3个应用程序中的一个，安装工作如愿。|889734|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|$]]

I had this same exact error, but none of the above solutions worked for me. 

In my case, I am using a free Apple developer account and got this error after trying to install a 4th app. The install limit for free accounts is 3. I deleted one of the 3 apps I already had and the installation worked as expected.

blocks|key|971318|text|在我的例子中，我使用了带有iOS+13+beta版的Xcode+11+GM种子，并且由于“自动”失败，我已经将代码签名到手动(分发)。我让我的团队代理允许我的用户"Admin“角色，进入Apple+Developer的门户并编辑”无效“配置文件以选中复选框，明确提到"Xcode+11”。在我下载了个人资料后，我的团队代理将我的角色放回“成员”，一切都进行得很顺利。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971319|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 was using Xcode 11 GM seed with iOS 13 beta, and I had code signing to manual (distribution) since the "Automatic" was failing.
I had my team agent allow my user "Admin" role, went into the Apple Developer's portal and edited the "invalid" provisioning profiles to check the checkbox explicitly mentioning "Xcode 11".
After I downloaded the profile my team agent put back my role to "member" and all went well.

blocks|key|971324|text|对我来说，这个问题与迦太基一起下载的阿拉莫火图书馆有关。确保选择“不要嵌入”并让迦太基复制图书馆。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971325|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|$]]

For me the issue was related to Alamofire library that was downloaded with Carthage. Ensure to select "Do not embed" and let Carthage to copy the Library.

blocks|key|1725439|text|我通过构建设置>代码签名标识>调试来修正我的设置。确保您有适当的“开发证书”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725440|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 fixed mine by going to Build Settings > Code Signing Identity > Debug. Make sure you have the appropriate "development certificate".

blocks|key|971389|text|这是一个代码签名问题。Xcode+11要求您将"Apple+Development“证书添加到您的开发配置文件中，这些配置文件将自动添加到您的证书和配置文件中。将该证书添加到您的配置文件中，重新下载您的开发配置文件和vwala。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971390|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 is a code signing issue. Xcode 11 requires you to add the "Apple Development" certificate to your development provisioning profile that they automatically added to your certificates and profiles. Add that certificate to your profile, redownload your development profile and vwala.

blocks|key|1725477|text|对于IOS+13，当使用Xcode-beta安装应用程序时，唯一起作用的是重新启动连接到计算机的电话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725478|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|$]]

For IOS 13 when installing the app with Xcode-beta the only thing that worked was to restart the phone connected to the computer

blocks|key|971427|text|在Xcode窗口的顶部，在“运行/停止”旁边单击应用程序图标，然后选择“管理方案”。确保运行和测试使用构建配置“调试”。Xcode将这些更改为"release“。别问我为什么！使用Xcode+v+11+(11a420a)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971428|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 the top of the Xcode window, next to run/stop click on your app icon, and select manage schemes. Make sure run and test uses the build configuration "Debug". Xcode changed these to "release". Do not ask me why! Using Xcode v 11 (11a420a)

blocks|key|971456|text|我也犯了同样的错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971457|无法找到已安装的应用程序安装声称已成功，但无法在设备上找到应用程序。bundleId+=+(+MY_BUNDLE_ID+)“但用MY_BUNDLE_ID代替"null|blockquote|971458|在Xcode11更新后，我得到了这个错误|971459|解决方案：|offset|length|style|BOLD|971460|我的项目和ProjectTests有不同的开发团队。项目有业主团队，ProjectTests有个人团队|971461|我也没有机会通过Xcode接口将团队更改为所有者。因此，我在构建设置-只是进入我的团队(自动管理证书也启用)。|971462|是的，它在Xcode+UI+(红色标签)中看起来是个错误，但是能够安装在实际的设备上。|971463|entityMap^0|0|0|0|0|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|W|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|X|8|@$I|Y|J|Z|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|11|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|12|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|T|$]]

I got the same error:

<blockquote>
 Could not locate installed application Install claimed to have
 succeeded, but application could not be found on device. bundleId =
 (MY_BUNDLE_ID)" but with MY_BUNDLE_ID instead "null
</blockquote>

I got this error after Xcode11 update

Solution: 

My Project and ProjectTests had different developments team.
Project had Owner Team, ProjectTests had Personal Team

And I had't opportunity to change team to owner's by Xcode interface. So I make it in build settings - just entered my team (automate manage certificates enabled too).

Yes, its look an error in Xcode UI (red label), but was able to install on real devices.

blocks|key|889801|text|对我来说，它是更新Xcode项目到所需的升级，在更新后，它运行良好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|889802|只需发出Navigator+(按命令%2B+5)+>查找缺少的项目更改并更新它。|889803|我在Xcode+11+beta版本中运行我的代码，所以有东西坏了，在将它更新到所需的设置之后，它恢复了正常。|889804|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|$]]

For me it was updating Xcode project to the required upgrade, after updating it worked fine.

Just go to Issue Navigator (press command + 5) > look for missing project changes and update it. 

I was running my code in Xcode 11 beta version, so there something got broken, after updating it to required settings it went back to normal.

blocks|key|971482|text|Xcode+11+(11a420+A)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|971483|我遇到了类似的问题，尝试了以上所有的解决方案(eg.changing到遗留、清洁和构建等).但最终的解决方案是使用我使用的外部框架，我通过将选项更改为Embed+&将从嵌入改为签名，从而解决了这一问题。不确定这可能是Xcode问题|971484|entityMap^0|0|J|0|23|8|2C|6|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

Xcode 11 (11a420a)

I faced a similar issue, tried all the above solutions(eg.changing to legacy, clean and build, etc.) ... but ultimately the solution was with the external framework I used, I solved this by changing the option to Embed &amp; Sign from Embed without Signing ..... Not sure this might be Xcode issue

blocks|key|889814|text|修正了我的。这是因为在构建阶段没有复制Alamofire框架(通过Carthage)+(以前在Xcode中的嵌入式库部分)，但是现在它已经消失了，选择嵌入类型无效)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|889815|脚本体是：/usr/local/bin/carthage+copy-frameworks，输入文件的路径是$(SRCROOT)/Carthage/Build/iOS/Alamofire.framework，输出文件的路径是$(BUILT_PRODUCTS_DIR)/$(FRAMEWORKS_FOLDER_PATH)/Alamofire.framework。|offset|length|style|CODE|889816|希望这有助于或者让你找到你的解决方案。|889817|entityMap^0|0|5|13|1H|1D|33|1V|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|K|$]]

Fixed mine. Was caused by Alamofire framework (via Carthage) not being copied during build phase (used to be in Embedded libraries section in Xcode before, but it's gone now and choosing embedding type didn't work).

The script body is: <code>/usr/local/bin/carthage copy-frameworks</code>
The paths are <code>$(SRCROOT)/Carthage/Build/iOS/Alamofire.framework</code> for input files and <code>$(BUILT_PRODUCTS_DIR)/$(FRAMEWORKS_FOLDER_PATH)/Alamofire.framework</code> for output ones.

Hope this helps or lets you find your solution.

blocks|key|889819|text|在我的例子中，这个问题是使用控制台日志在日志中发现的，我在云中看到了来自installd进程的一个错误，说我的plist.info文件有问题。它并没有说出确切的内容，但修复了我的plist文件解决了它。在我的例子中，我有3个plist文件(iPhone、watch和watch扩展名)，问题是我的watch+plist.info文件(我意外地添加了NSLocationAlwaysUsageDescription，解决了这个问题)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|889820|entityMap^0|10|8|1J|A|44|G|4U|W|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

In my case the issue was found using the console log
going through the logs I cloud see an error from the <code>installd</code> process saying there was something wrong with my <code>plist.info</code> file.
It did not say what exactly
But fixing my plist file solved it.
In my case I had 3 plist files (iPhone, watch, and watch extension), the problem was my <code>watch plist.info</code> file (I added the <code>NSLocationAlwaysUsageDescription</code> accidentally, removing this solved the problem).

blocks|key|971538|text|对我来说，我有一个构建阶段脚本，目的是将模拟器架构从应用程序中剥离出来(当它发布到app时)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971539|我读过一篇文章，建议为模拟器构建更好的错误细节，并发现脚本在每个构建上都在运行，所以我把它改为“只在安装时运行脚本”，这似乎解决了我的问题。|971540|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|$]]

For me it was that I had a build phase script that was intended to strip simulator architectures from the app (for when it's published to the App Store).

I'd read a suggestion that building for the simulator would give better error details and found that the script was running on every build so I switched it to 'run script only when installing' and that seems to have resolved the issue for me.

blocks|key|971561|text|在选择"iPhone分发“配置配置文件/签名证书时，我看到了这个错误--当我切换到"iPhone+Developer”时，它被清除了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971562|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 was seeing this error with an "iPhone Distribution" provisioning profile / signing certificate selected - it cleared up when I switched to "iPhone Developer"

blocks|key|971573|text|我也有这个问题。如果有人不能用另一个答案来解决这个问题，并且在他的应用程序中使用一个框架，我的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971574|我使用了一个框架(tesseract)，但是没有签名，所以我不能使用这个应用程序，但是Xcode没有意识到这个问题。要解决这个问题，请转到您的项目文件中，将框架的“嵌入”选项更改为embed&sign。|971575|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|$]]

I also had this problem. If anyone couldn't solve it with another answer and uses a framework in his app, my solution:

I used a framework (tesseract), but didn't sign it, so I couldn't use the app, but Xcode didnt recognize the problem. To solve this, go to your project file, to general and change the "embed" option for your frameworks to embed&amp;sign.

blocks|key|1725779|text|迦太基工作溶液|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1725780|转到Project+General+->+Frameworks,+Libraries,+and+Embedded+Content并将框架更改为Do+Not+Embed+(在我的例子中，Do+Not+Embed就是问题所在)|ordered-list-item|CODE|1725781|​|1725782|📷|atomic|1725783|1725784|转到Build+Phases，选择%2B+New+Run+Scrip+Phase，为脚本shell插入/usr/local/bin/carthage+copy-frameworks，为Input+files添加$(SRCROOT)/Carthage/Build/iOS/Alamofire.framework插入/usr/local/bin/carthage+copy-frameworks|1725785|1725786|1725787|1725788|现在它应该起作用了|1725789|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/8e24660af7d32fc259b401f759d25619.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/85c351e942c2dcf6363791001349c96a.png^0|0|7|0|A|7|L|17|1Z|C|2K|C|0|0|0|1|0|0|0|2|C|H|1|J|J|1D|13|2I|B|2V|1D|4A|13|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1A|8|@$9|1B|A|1C|B|I]|$9|1D|A|1E|B|I]|$9|1F|A|1G|B|I]|$9|1H|A|1I|B|I]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1J|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1K|8|@]|D|@$9|1L|A|1M|1|1N]]|E|$]]|$1|O|3|K|5|6|7|1O|8|@]|D|@]|E|$]]|$1|P|3|Q|5|H|7|1P|8|@$9|1Q|A|1R|B|I]|$9|1S|A|1T|B|I]|$9|1U|A|1V|B|I]|$9|1W|A|1X|B|I]|$9|1Y|A|1Z|B|I]|$9|20|A|21|B|I]|$9|22|A|23|B|I]]|D|@]|E|$]]|$1|R|3|K|5|6|7|24|8|@]|D|@]|E|$]]|$1|S|3|M|5|N|7|25|8|@]|D|@$9|26|A|27|1|28]]|E|$]]|$1|T|3|K|5|6|7|29|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|2A|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|2B|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13|14|-4]]|15|$5|Z|10|11|E|$12|16|14|-4]]]]

CARTHAGE WORKING SOLUTION

<ol>
<li>Go to Project <code>General</code> -> <code>Frameworks, Libraries, and Embedded Content</code> and change framework as <code>Do Not Embed</code> (in my case Alamofire.framework was the problem)</li>
</ol>

<a href="https://i.stack.imgur.com/Ex2Cn.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Ex2Cn.png" alt="enter image description here"></a>

<ol start="2">
<li>Go to <code>Build Phases</code>, select <code>+</code> <code>New Run Scrip Phase</code>, insert <code>/usr/local/bin/carthage copy-frameworks</code>for the script shell, and for the <code>Input files</code> add <code>$(SRCROOT)/Carthage/Build/iOS/Alamofire.framework</code></li>
</ol>

<a href="https://i.stack.imgur.com/DHrZj.png" rel="noreferrer"><img src="https://i.stack.imgur.com/DHrZj.png" alt="enter image description here"></a>

Now it should work

blocks|key|971717|text|我通过在“签名和功能”屏幕中勾选“自动管理签名”来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971718|这里列出的其他解决方案对我都没有用。|971719|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|$]]

I've solved the problem by ticking the "Automatically manage signing" in the "Signing &amp; Capabilities" screen.

None of the other solutions listed here worked for me.

blocks|key|889892|text|在我的例子中，我刚刚将显示名称从Something重命名为something。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|889893|我被迫返回到我的设备上运行。|889894|配置：Xcode+11.0，iOS+13.1.2|blockquote|889895|entityMap^0|B|4|G|9|T|9|0|0|3|A|E|A|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|D]|$9|S|A|T|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|U|8|@]|E|@]|F|$]]|$1|I|3|J|5|K|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|E|@]|F|$]]|$1|L|3|-4|5|6|7|10|8|@]|E|@]|F|$]]]|M|$]]

In my case, I just renamed Display Name from <code>Something</code> to <code>something</code>.

I'm forced to revert back to run on my device.

<blockquote>
 Config: Xcode 11.0, iOS 13.1.2
</blockquote>

blocks|key|971755|text|解决方案#101-旧实例需要从设备中删除|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|971756|在我的iOS+13设备上使用Xcode+11.1运行时遇到了这个问题，Mac最近更新为Catalina，并希望它与this.....but+no有关。|971757|解决办法要简单得多..。|971758|我从设备中删除了一个非常老的应用实例(长时间按住，当然按x键)。从XC重新旋转的构建和所有的工作很好！|971759|看起来这个问题有各种各样的正确答案，我的答案是这个，希望它能帮助到其他人。|971760|entityMap^0|9|8|0|E|A|17|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|Z|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|O|$]]

Solution #101 - Old instance needed deleted from device

Encountered this issue when running on my iOS 13 device, using Xcode 11.1, Mac OS recently updated to Catalina and expected it to have something to do with this.....but no.

Solution was much simpler....

I deleted a very old instance of the app from within the device, (long hold, press the x of course). Re-spun the build from XC and all worked fine!

Looks like there's various correct answers to this one, mine was this and may it help someone else.

blocks|key|971817|text|尝试将frameworks+target更改为13.0，将Project+Target更改为iOS+9.0|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|971818|为了在我的Xcode版本11.0中修复它，问题是框架、目标和项目目标。|971819|​|971820|📷|atomic|971821|971822|971823|971824|971825|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/6e02b8022d593f0dfb509cc09052fc96.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/dccc92d5ded34753d96ab4abdcfc2482.png^0|3|H|T|E|0|0|0|0|1|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|M|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|N|3|I|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|K|5|L|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|P|3|I|5|6|7|1I|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X|Y|-4]]|Z|$5|T|U|V|E|$W|10|Y|-4]]]]

Try to change the <code>frameworks target</code> to 13.0 and <code>Project Target</code> to iOS 9.0

To fix it in my Xcode Version 11.0 for me the issue was frameworks target and project target.

<img src="https://i.stack.imgur.com/mHmUr.png" alt="">

<img src="https://i.stack.imgur.com/8E6Zh.png" alt="">

blocks|key|891623|text|我终于找到了解决办法(至少对我来说是这样)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|891624|我面临着这个问题(不知从哪里冒出来)，也许是开发/生产证书的问题。我有一个关于“签名和功能”的手动配置，所以当我切换到自动时，只需修复这个问题。(对不起，我的英语很差)|891625|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|$]]

I Finally found a fix (at least to me)

I was with facing this problem (that appears from nowhere) and maybe is some issue with the Dev/Production certificate. I have a Manual config on "signing &amp; Capabilities" so when I switch to Automatic just fix the problem.
(sorry for my bad english)

blocks|key|1726004|text|在我的例子中，这是一个代码签名问题(我使用手动代码签名)。我不得不从iOS+Distribution切换到iOS+Developer以获得Any+iOS+SDK键：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1726005|​|1726006|📷|atomic|1726007|1726008|并选择符合条件的开发供应配置文件。|1726009|Xcode+11|1726010|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/fac69bfe02b552eccb81da711a5c3b47.png|imageAlt^0|Y|G|1H|D|1X|B|0|0|0|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|K|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1B|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1C|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W|X|-4]]]]

It was a code signing issue in my case (I use manual code signing). I had to switch from <code>iOS Distribution</code> to <code>iOS Developer</code> for <code>Any iOS SDK</code> key:

<a href="https://i.stack.imgur.com/SvYXZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SvYXZ.png" alt="Code signing issue"></a>

and also select an eligible development provisioning profile.

Xcode 11

blocks|key|889965|text|最近，当我更新到Xcode+11时，我遇到了这种情况；如果您正在设备上进行测试，请转到"Build“，然后将所有内容更改为"iOS+Developer”中的“代码签名标识”。这应该能解决问题。然后，一旦您准备好启动，请确保设置了iOS分发。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|889966|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 this happen to me just recently when I updated to Xcode 11; if you are testing on a device, go to "Build Settings", then change everything to "iOS Developer" under "Code Signing Identity". This SHOULD fix the issue. Then once you're ready to launch, make sure you have iOS Distribution set up.

blocks|key|971923|text|在我注意到benchuk使用控制台找出他有问题的原因之前，我尝试了这个问题的几乎每一个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971924|我在控制台中搜索了installd，发现我添加到我的项目中的"fat“框架实际上已经签署了。|offset|length|style|CODE|971925|该签名与应用程序的其他部分不匹配，导致安装失败。|971926|知道出了什么问题后，我可以简单地删除签名：|971927|codesign+--remove-signature+Some.framework|971928|entityMap^0|0|9|8|0|0|0|0|16|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

I tried almost every single answer to this question before I noticed benchuk used the Console to figure out why he had a problem.

I had a look in the Console searching for <code>installd</code> and found that the "fat" Framework I had added to my project was actually signed.

The signature did not match the rest of the app which caused the installation to silently fail.

Knowing what was wrong, I could simply remove the signature:

<code>codesign --remove-signature Some.framework</code>

blocks|key|971930|text|因为Siri扩展了我的项目。在“构建阶段”“嵌入应用程序扩展”中，删除xxxSiriExtension.appex构建并重新添加它。它解决了我的项目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|971931|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|$]]

It caused on my project because of Siri Extension. In "Build Phases" "Embed App Extension" remove xxxSiriExtension.appex build and add it again. It solved on my project

blocks|key|1726103|text|当我试图在设备上安装我们的应用程序时，我也遇到了类似的错误。由于各种原因，我们最近更换了这个应用程序的团队，显然，一些标识符没有被更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1726104|如果是这样的话，请访问Apple门户并找到您的团队标识符。他们长得像这样。NXD2KNAXM。|ordered-list-item|offset|length|style|CODE|1726105|打开yourproject.xcodeproj/project.pbxproj文件，只需搜索-用新标识符替换旧标识符。|1726106|这种方法确实是犹太人聚居区，但对我来说很管用。|1726107|entityMap^0|0|11|9|0|2|11|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@$E|Q|F|R|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|S|8|@$E|T|F|U|G|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|N|$]]

I was getting a similar error when trying to install our app on device. We have recently switched teams for the app for various reasons, and apparently, some identifiers had not been changed. 

<ol>
<li>If this is the case for you, go to Apple Developer portal and find your team identifiers. They look something like this. <code>NXD2KNAXM</code>. </li>
<li>Open your <code>yourproject.xcodeproj/project.pbxproj</code> file and simply search-replace the old identifier with the new identifier. </li>
</ol>

The approach is really ghetto, but it worked for me.

blocks|key|972045|text|我面临着同样的问题，我的代码没有其他答案中提到的任何问题(使用相同捆绑标识符的框架、遗留系统等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|972046|我的解决方案是先安装应用程序作为侧加载，然后以正常方式运行应用程序(Cmd%2BR).|offset|length|style|BOLD|972047|首先，对你的项目做一个IPA+(有很多方法可以做到这一点，我是通过压缩名为Payload的具有应用程序文件的文件夹来实现的。您可以选择其他方式，您所需要的只是一个IPA文件)。|972048|接下来，在Xcode中打开设备和模拟器(Cmd%2BShift%2B2)。|972049|​|972050|📷|atomic|972051|972052|现在，单击安装应用程序部分中的小加号按钮(%2B)，您将被要求选择IPA。选择您的IPA，它将安装在设备上。|972053|现在设备上存在给定包标识符的应用程序，您的运行命令将按预期工作。|972054|只要点击Cmd%2BR，您的项目就会在设备上运行。|972055|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/9f2d46880481bab8c89c28d3e5474de9.png|imageAlt^0|0|0|15|0|0|0|0|0|1|0|0|0|0|0|W|0|0|N|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1B|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|Q|3|M|5|6|7|1H|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1I|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14|15|-4]]]]

I faced the same issue and my code was not having any of the issues mentioned in other answers (frameworks using same bundle identifiers, legacy system etc). 

My solution was to install the app first as side load, and then running the app in normal way (Cmd+R). 

First, make an IPA of your project (there are many ways to do this, I made it by compressing folder named Payload having app file. You may choose other ways, all you need is an IPA file).

Next, open devices and simulators (Cmd+Shift+2) in Xcode.

<a href="https://i.stack.imgur.com/3Zo0R.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3Zo0R.png" alt="enter image description here"></a>

Now click on the small plus button (+) in the INSTALLED APPS section, and you would be asked to select the IPA. Select your IPA, and it will be installed on the device.

Now that an application of given bundle identifier is existing on the device, your run command would work as expected. 

Simply hit Cmd+R, and your project would run on the device.

blocks|key|1726249|text|这已经在Xcode+11.2中得到了解决。使用Xcode+11.2，您现在应该得到一个错误，该错误指示应用程序安装失败，而不是错误指示它已安装但未能启动。此错误还应包含有关安装失败的一些详细信息。如果细节不够充分，我建议将目标对准模拟器设备，而不是真正的设备，因为那样会产生更高的保真度错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1726250|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/documentation/xcode_release_notes/xcode_11_2_release_notes?language=objc^0|4|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This has been addressed in <a href="https://developer.apple.com/documentation/xcode_release_notes/xcode_11_2_release_notes?language=objc" rel="nofollow noreferrer">Xcode 11.2</a>. With Xcode 11.2, you should now get an error that indicates that the app failed to install rather than an error that indicates that it installed but failed to launch. The error should also contain some details as to why the install failed. If the details are insufficient, I suggest targeting a simulator device instead of a real device as that should produce a higher fidelity error.

blocks|key|972149|text|试试这个，这个解决方案对我有用。仅在安装选项时在嵌入应用程序扩展下在构建阶段目标设置下启用副本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|972150|首先，尝试在模拟器上执行app，这样也会在模拟器上抛出一些错误。|972151|​|972152|📷|atomic|972153|972154|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3802e25d18122dfd370b663cb4c8c8ed.png|imageAlt^0|K|S|0|0|W|0|0|1|0|0|1|0|1|0|0|0|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|M|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U|V|-4]]]]

Try this, this solution works for me. Enable Copy only when installing option under Embed App Extensions in BUILD Phases targer settings. 

First try to Execute app on simulator, so that this will also throw some error on simulators too.

<a href="https://i.stack.imgur.com/9w8gP.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/9w8gP.png" alt="enter image description here"></a>

blocks|key|890117|text|XCode+11.1，Swift+5.+问题：版本号在XCode中为空！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|890118|此错误背后可能有多种原因。|890119|对我来说，这是因为构建号在XCode中是空的。看看你是否也发生了同样的事。|890120|entityMap^0|K|3|0|0|9|9|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

<h2>XCode 11.1, Swift 5. Issue: Build Number was empty in XCode !!!</h2>
There could be multiple reasons behind this error.
For me it was because build number was empty in XCode. Check if the same happend for you.

blocks|key|891809|text|这个问题也有这么多被否决的答案，但没有一个对我的案子有用。对我来说，我无法在模拟器或设备中运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|891810|我又来了deintegrate+pod和install，这是工作。清洁项目和|offset|length|style|CODE|891811|pod+deintegrate
pod+install|code-block|syntax|javascript|891812|希望这能帮到一个人|891813|entityMap^0|0|4|B|K|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

This question have so many upvoted answer as well but none worked for my case. For me i am not able to run in simulator or device.

I just <code>deintegrate</code> pod and <code>install</code> again and it's work. Clean the project and

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

Hope this will help some one

blocks|key|1726308|text|请检查您的所有项目目标，如用projectnameTests登录same.account|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1726309|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|$]]

Please check your all project target like projectnameTests signing in with same.account

blocks|key|972232|text|当您试图使用are的供应配置文件在设备上运行are时，就会发生这种情况。确保您正在使用Development或Adhoc+Profiles运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|972233|另一个原因可能是，您可以为IPA生成运行一些架构剥离脚本。检查这是否引发了任何错误。|972234|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|$]]

This happens when you are trying to run App on device using Provisioning Profiles for App Store. Make sure you are running using Development or Adhoc Profiles.

Another reason for this could , you could running some architecture stripping script for IPA generation. Check if this is throwing any errors.

blocks|key|1726380|text|当我删除这个应用程序的一个旧实例时，我遇到了这个问题，当时我正试图在构建完成之前运行它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1726381|解决方案是简单地构建并再次运行项目。|offset|length|style|BOLD|1726382|entityMap^0|0|8|9|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]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I got this issue when I deleted an old instance of the app I was trying to run right before my build would've finished.

The solution is to simply build and run the project again.

blocks|key|1726468|text|您不能使用应用商店分发证书从Xcode构建到您的设备。您只能从TestFlight或apps安装由苹果签署的应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1726469|原因是因为这个由发行证书构建的应用程序可以安装在任何设备上，这对苹果来说是一个很大的不可以。|1726470|当我故意尝试测试Xcode的发布过程时，我遇到了这个问题。我想看看我的应用程序扩展的配置文件是否有正确的权限，但从架构的角度来看，这是不可能的。|1726471|当你从应用商店下载应用程序时会发生什么？|1726472|你只需安装它。没有提示信任开发团队。|1726473|当您从Xcode+(与您的开发或企业供应配置文件一起)安装一个应用程序时，或者从您的企业分发服务(例如AppCenter)或其他服务中下载它以交付给企业用户，会发生什么情况？|1726474|您得到一个开发团队不受信任的提示，您需要手动信任它：|1726475|​|1726476|📷|atomic|1726477|1726478|因此，与Apple发行证书签署的应用程序不会提示用户使用该消息，因此苹果不希望允许该ipa在每台设备上自由安装并攻击用户信息！|CODE|1726479|还可以看到另一个类似的答案：这里和这里|1726480|entityMap|0|LINK|mutability|MUTABLE|url|https://support.apple.com/en-us/HT204460|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/e40cdc95734d26167251ac86c9ddc730.jpg|imageAlt|2|https://stackoverflow.com/a/27567726/5175709|3|https://stackoverflow.com/questions/18913676/xcode-failed-to-get-the-task-for-process^0|5|6|0|0|0|0|0|0|E|2|0|0|0|0|1|1|0|0|16|3|0|E|2|2|H|2|3|0^^$0|@$1|2|3|4|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1N|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1O|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1P|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1R|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1S|8|@]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|R|3|S|5|6|7|1W|8|@]|D|@]|E|$]]|$1|T|3|U|5|V|7|1X|8|@]|D|@$9|1Y|A|1Z|1|20]]|E|$]]|$1|W|3|S|5|6|7|21|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|22|8|@$9|23|A|24|B|Z]]|D|@]|E|$]]|$1|10|3|11|5|6|7|25|8|@]|D|@$9|26|A|27|1|28]|$9|29|A|2A|1|2B]]|E|$]]|$1|12|3|-4|5|6|7|2C|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]|1A|$5|1B|16|1C|E|$1D|1E|1F|-4]]|1G|$5|15|16|17|E|$18|1H]]|1I|$5|15|16|17|E|$18|1J]]]]

tl;dr You can NOT build from Xcode to your device with a App Store Distribution certificate. You can only install apps signed by Apple from TestFlight or App Store.
<hr />
The reason is because that app built with distribution certificates can be installed on any device and that's a big no no for Apple.
I ran into this issue when I was purposely trying to test my release process from Xcode. I wanted to see if the provisioning profiles of my app extensions were having the correct entitlements, but turns out that's impossible from an architectural perspective.
<h2>What happens when you download an app from app store?</h2>
You just install it. No prompts to trust the developer team.
<h2>What happens when you install an app from Xcode (with your development or Enterprise Provisioning profile) or if you download it from your Enterprise Distribution Service (e.g. AppCenter) or some other service for delivering to Enterprise user?</h2>
You get a <a href="https://support.apple.com/en-us/HT204460" rel="nofollow noreferrer">prompt</a> that the developer team isn't trusted and you need to manually trust it:
<a href="https://i.stack.imgur.com/diBXol.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/diBXol.jpg" alt="enter image description here" /></a>
So Apps signed with App store distribution certs don't prompt users with that message, hence Apple does NOT want to allow that <code>ipa</code> to be freely installed on every device and hack users information!
Also see another similar answers <a href="https://stackoverflow.com/a/27567726/5175709">here</a> and <a href="https://stackoverflow.com/questions/18913676/xcode-failed-to-get-the-task-for-process">here</a>

Xcode gave me this message:

<blockquote>
 Could not locate installed application Install claimed to have
 succeeded, but application could not be found on device. bundleId =
 (null)
</blockquote>

I just started using pods.

How do I fix this?

Install claimed to have succeeded, but application could not be found on device

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Xcode给了我这个消息：无法找到已安装的应用程序安装声称已成功，但无法在设备上找到应用程序。bundleId = (null)我刚开始用豆荚。我该怎么解决这个问题？

问安装声称已成功，但在设备上找不到应用程序。
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安装声称已成功，但在设备上找不到应用程序。EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安装声称已成功，但在设备上找不到应用程序。
EN