menu update option grays out after update check

Asked by ptfigg

Two questions:

I was previously running ver. 1.1. Now running ver.1.5.

Clicking the Check for Updates menu option seems to work only once per application session. The menu option grays out after the option is clicked. It returns to an active state when the application is re-launched.

What is the proper way to update the framework to ver 1.5? Should I simply delete the previous version in my app. bundle and start from scratch?

thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
ptfigg
Solved:
Last query:
Last reply:
Revision history for this message
Andy Matuschak (andymatuschak) said :
#1

1. You mean if you click Remind Me Later, you can't check for updates again? That's really, really weird and shouldn't be happening. Are you running with any particular localization? I'm guessing it's happening because there are still some fragments of the old framework somewhere. Check the console—there should be some output of what's going on.

2. You should delete the old Sparkle.framework and replace it with the new one. Then *clean* your project and rebuild.

Let me know if that works, or, if it doesn't, what's in the console after the window closes the first time.

Revision history for this message
ptfigg (ptfigg) said :
#2

Thanks Andy,

I referring to the basic "Check For Updates" menu option that I implemented and connected to the Updater Controller class. After launching the application I can click that menu option and Sparkle returns update availability status as normal. From that point on the Check for Updates menu option is grayed out and only available if I quit and re-launch.

I deleted ver. 1.1 and replaced it with the new bundle, cleaned and rebuild. No luck. If I revert back to 1.1 things function normally.

I'm not sure wht's going on ;)

thaks again.

-ptfigg.

Revision history for this message
Andy Matuschak (andymatuschak) said :
#3

Oh, okay. So you've linked the menu item to -checkForUpdates: in the SUUpdater? Is there any output in the console? Can you upload a copy of the app somewhere?

Revision history for this message
ptfigg (ptfigg) said :
#4

Yes I'm linked up in the menu item and there's no output in the console.

I built a simple test project and added 1.5 - the menu item functions normally after multiple clicks.

What worries me is I'm experiencing the same problematic behavior on three separate apps that I am currently developing, all previously running 1.1 with no problem.

Is it possible I'm missing something while attempting to upgrade?

thanks.

-ptfigg.

Revision history for this message
Andy Matuschak (andymatuschak) said :
#5

Possibly! Try deleting your preferences file; it might be a problem with preference migration. In the meantime, could you email me a copy of the app with 1.5 or otherwise post it somewhere so I can try to debug?

Revision history for this message
ptfigg (ptfigg) said :
#6

Thanks Andy.

Let me try deleting the preference file.

I assume you need the source project to debug?

-ptfigg.

Revision history for this message
Andy Matuschak (andymatuschak) said :
#7

I shouldn't actually, if it's Sparkle's fault.

Revision history for this message
ptfigg (ptfigg) said :
#8

Andy,

I think I may be off track here.

Question:

Does the new version gray out the menu item after a single check for updates click if there are no updates available, and then make itself available once again during subsequent application launches?

I ask because the test application is now behaving in this manner as well.

Run this:

http://www.pfiggmsc.com/ptfiggSparkletest.zip

Thanks again.

ptfigg.

Revision history for this message
Andy Matuschak (andymatuschak) said :
#9

Nope, it really shouldn't, but I think you've just produced a test case which shows that it does. Let me see if I can reproduce.

Revision history for this message
Andy Matuschak (andymatuschak) said :
#10

Congrats, you found a bug: https://bugs.launchpad.net/sparkle/+bug/236694 :D It's now fixed.

It only affected user-initiated update checks when no update was available, though. Does that cover the entirety of your problem?

Revision history for this message
ptfigg (ptfigg) said :
#11

Yes Andy, that is correct. Everything else appears to function as expected.

Thanks.

-ptfigg.

Revision history for this message
ptfigg (ptfigg) said :
#12

I'll close out the thread.

Thanks again.

-ptfigg.