Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sparkle: Completely broken? #802

Closed
bdkjones opened this issue Apr 29, 2016 · 11 comments
Closed

Sparkle: Completely broken? #802

bdkjones opened this issue Apr 29, 2016 · 11 comments

Comments

@bdkjones
Copy link
Contributor

Hi guys. I'm pretty sure Sparkle has just stranded tens of thousands of users of my app and I'm a little frustrated.

A couple months ago, I shipped an update to my app that included the then-current version of Sparkle: 1.13.1.

The version of my app was 2.7.1. Today, I shipped an update for version 2.8 and updated my appcast.xml file with the following entry:

<item>
            <title>Version 2.8</title>
            <sparkle:releaseNotesLink>https://incident57.com/codekit/sparkleversionhistory.html</sparkle:releaseNotesLink>
            <pubDate>Friday, 29 April 2016 18:15:00 -0700</pubDate>
            <enclosure url="https://incident57.com/codekit/files/codekit-19120.zip" sparkle:version="19120" sparkle:shortVersionString="2.8" length="52007267" type="application/octet-stream"/>
            <sparkle:minimumSystemVersion>10.8</sparkle:minimumSystemVersion>
        </item>

However, when I check for updates in 2.7.1, Sparkle reports that the latest version of my app that is available is 2.7.1. I have verified that the correct XML file is being downloaded.

What's going on here? And PLEASE tell me I can fix it...

@bdkjones
Copy link
Contributor Author

Sparkle is not logging anything to console.app when I check for updates.

This really doesn't look good, guys. I'm incredibly worried that I've now shipped a version of my app that I can never update because Sparkle is silently failing. What can I provide to figure out what's going on?

@bdkjones
Copy link
Contributor Author

My app is signed with a valid Apple Developer Certificate and as you can see in my item entry above, I'm delivering the download and release notes via https. Additionally, the old version of my app (2.7.1) and the new version both have NSAllowsArbitraryLoads set to YES, which allows using HTTP connections.

@kornelski
Copy link
Member

kornelski commented Apr 29, 2016

Sparkle reports user-friendly version 2.7.1 to the user, but checks against sparkle:version="19120" you've specified. Is that 19120 higher than your CFBundleVersion in the old app?

@bdkjones
Copy link
Contributor Author

Yes. The old app is 19115.

Sent from my iPhone

On Apr 29, 2016, at 12:37, Kornel notifications@github.com wrote:

Sparkle reports user-friendly version to the user, but checks against sparkle:version="19120" you've specified. Is that higher than your CFBundleVersion in the old app?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

@kornelski
Copy link
Member

I'm looking into it

@bdkjones
Copy link
Contributor Author

If you'd like, the old version (2.7.1) of my app is available at http://incident57.com/codekit/files/codekit-19115.zip

The new version is http://incident57.com/codekit/files/codekit-19120.zip

The location of the appcast.xml file and related resources is in the item entry above. Thanks for the help!

@bdkjones
Copy link
Contributor Author

Do you think there's any hope of fixing the problem from where I am, or do I need to start looking at how to contact my customers and let them know they need to manually update to the latest release of my app?

@zorgiepoo
Copy link
Member

Is the appcast on your server up to date? Going to https://incident57.com/codekit/appcast/ck2appcast.xml , I don't see the entry for 2.8

@bdkjones
Copy link
Contributor Author

@zorgiepoo What's your physical location in the world? When I visit that URL I get the updated XML with the 2.8 item. That's the very first thing I checked, before I opened this issue. I will re-verify, but I currently don't have any caching enabled on my server so it should not be serving an old version to anyone.

@zorgiepoo
Copy link
Member

U.S. EST. It's not serving the new version for me then.

@bdkjones
Copy link
Contributor Author

@zorgiepoo You're right. When I access the URL through my VPN, I get a different version of the file depending on what location I'm accessing from. There's something funky going on with caching at my hosting provider.

You know, I TRY not look like a moron before I open an issue on GitHub and, invariably, I look like a moron every time I open an issue on GitHub. This really WAS the first thing I checked when the problem appeared. I'll see what the heck is going on with my hosting provider and that will clear this up, I'm sure.

Sorry for the false alarm; just a stressful few hours. In my next life, I will choose literally any other career than software development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants