问题描述
我一直在对更新错误！"进行故障排除.现在与Sparkle合作了几天，但进展甚微.我尽可能地根据工作样本对appcast进行建模，但我无法使其正常工作.最后，我决定使用我的应用程序中的示例appcast进行测试:
I have been troubleshooting an 'Update Error!' for a few days now with Sparkle and have made little progress. I modeled my appcast after a working sample as closely as I could but I couldn't get it to work. Finally, I just decided to use the sample appcast in my app to test:
http://sparkle-project.org/files/sparkletestcast.xml
当我将其用作SUFeedURL时，它会起作用.因此，我将该XML的内容复制并粘贴到了服务器上的文件中，这是行不通的.仔细看一下diff，唯一的区别是sparkle:dsaSignature，我没有有效的值.
When I put that as my SUFeedURL, voila, it works. So I copied and pasted the contents of that XML to the file on my server and it doesn't work. Looking over the diff closer, the only material difference is the sparkle:dsaSignature, which I don't have a valid value for.
通读文档，但是，我的印象是，我只需要如果我自己不使用证书签署应用程序，请处理dsaSignature的内容.部署此应用程序的版本时，是从Xcode导出它并用我的开发人员身份对其进行签名，然后将其压缩并放在服务器上.
Reading over the documentation, however, I got the impression that I only needed to deal with the dsaSignature stuff if I am not signing the app myself with my certificate. When I am deploying the build of this app, I am exporting it from Xcode and signing it with my dev identity, and then zipping it up and putting it on the server.
如果我自己对应用程序进行签名，我是否需要在应用程序广播中使用sparkle:dsaSignature字段?我不知道为什么这不起作用.
Do I need the sparkle:dsaSignature field in my appcast if I am signing the app myself? I can't figure out why this isn't working.
推荐答案
WOW.只是...哇.我的SUFeedURL以www而不是http://www开头.那是导致坠机的原因，并且花费了数小时的头部挠曲才能追踪到.希望这对以后的人有所帮助.
WOW. Just...wow. My SUFeedURL started with www, not http://www. That was causing the crash and took several hours of head scratching to track down. Hopefully this helps someone in the future.
这篇关于我的Sparkle应用广播是否需要sparkle:dsaSignature字段才能有效?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！