简体   繁体   English

无法在Ad-Hoc模式下编译iOS-App(Xamarin.iOS)

[英]Can't compile iOS-App in Ad-Hoc mode (Xamarin.iOS)

So basically I'm following this official Xamarin guide to release my app in the AppStore. 所以基本上我正在遵循这个官方Xamarin指南在AppStore中发布我的应用程序。

However no matter what I try (changing signing profiles, different build options) the solution-process crashes every time after 1-2 minutes with different errors that don't explain what exactly went wrong (signing error, user aborted?!, etc.). 然而,无论我尝试什么(更改签名配置文件,不同的构建选项),解决方案进程在1-2分钟后每次都会崩溃,并且不能解释究竟出错的错误(签名错误,用户中止?等等)。 )。

After the error is shown I always have to reconnect to the Mac. 显示错误后,我总是必须重新连接到Mac。 What could be the problem? 可能是什么问题呢?

EDIT: 编辑:

Tool exited with code: 1. Output: CSSM_SignData returned: 800108E6 /Users/metadokentwicklung/Library/Caches/Xamarin/mtbs/builds/mWIDAS_iOS/806c20450998d745a5c8df0e4928100f/bin/iPhone/Ad-Hoc/mWIDAS_iOS.app: errSecInternalComponent mWIDAS_iOS 工具退出代码:1。输出:CSSM_SignData返回:800108E6 /Users/metadokentwicklung/Library/Caches/Xamarin/mtbs/builds/mWIDAS_iOS/806c20450998d745a5c8df0e4928100f/bin/iPhone/Ad-Hoc/mWIDAS_iOS.app:errSecInternalComponent mWIDAS_iOS

I tried the publish profiles (Ad-Hoc,AppStore,automatic) and provisioning profile. 我尝试了发布配置文件(Ad-Hoc,AppStore,自动)和配置文件。

Okay solved the problem myself a few days ago. 好几天前我自己解决了这个问题。 Dumb mistake on my behlaf. 我的behlaf上的愚蠢错误。

I use the same monitor for the Mac Mini and the Windows PC so I didn't see the popup on the Mac prompting me to accept the use of the keyfile. 我为Mac Mini和Windows PC使用相同的显示器,所以我没有看到Mac上的弹出窗口提示我接受使用密钥文件。

After I agreed to it everything worked like a charm. 在我同意之后,一切都像魅力一样。

I resolved this issue by: 我解决了这个问题:

  1. Cleaning my solution 清理我的解决方案
  2. Closing VS4Mac 关闭VS4Mac
  3. Shut down Macbook Pro 关闭Macbook Pro
  4. Start Macbook Pro 启动Macbook Pro
  5. Reopen my solution 重新打开我的解决方案
  6. Build iOS head project (I am working in Xamarin.Forms) 构建iOS头项目(我在Xamarin.Forms工作)

And it built successfully this time. 它这次建成了。 I am noticing lots of issues from Windows VS are creeping into VS4Mac by each update. 我注意到Windows VS的许多问题都是通过每次更新进入VS4Mac。 Not sure why this was happening but that resolved my issue 不知道为什么会这样,但这解决了我的问题

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM