-
Hello. I am getting this error
And I am not sure how to proceed. I am using Sparkle through SPM, and I generate the appcast with ./generate_appcast seemingly without issues. If I run sign_update it seems to verify properly too.
I am archiving the app through Xcode, then I just export it and place the .app file in a .zip file and run the ./generate_appcast. After this I upload the files to my web server. Then I try to update from a lower version and I get that error. The last lines in console is
Similar threads #2252 and #2174. Neither seems to work for me, although I am not sure how to verify the cache thing he mentions. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
There aren't any useful error logs pasted here. There should be more descriptive logs under your app's process name, or under Autoupdate process. You can grab the last five minutes of the logs via It could also potentially be an apple code signing issue. If it's an EdDSA signing issue then maybe the archive Sparkle is downloading isn't the same (eg a server caching issue). But this is pretty speculative until seeing useful error information. |
Beta Was this translation helpful? Give feedback.
-
Thank you! I was able to find more details there that solved the issue. The error I had was
The older 0.5 version was not sent through the notarization step, while the newer versions were, so I guess that was one difference. I also played around a lot with eg. tar vs zip, and so on. So that might have been another issue. Solution So I made two new updates in exactly the same way (archive -> notarize -> tar -> generate appcast) and then the update succeeded. Much appreciated! |
Beta Was this translation helpful? Give feedback.
Thank you! I was able to find more details there that solved the issue.
The error I had was