Sparkle

Double-authentication causes installation failure.

Bug #228475 reported by Andy Matuschak
2
Affects Status Importance Assigned to Milestone
Sparkle
Confirmed
Medium
Unassigned

Bug Description

1. Try to update an app without write access.
2. Get authentication prompt; cancel.
3. Check for updates again and authorize this time.
4. Note that Sparkle fails to copy the new app in place but still trashes the old one.

See original description
Andy Matuschak (andymatuschak)
description: updated
Changed in sparkle:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Catfish_Man (catfish-man) wrote :

I think this may be due to OSX auto-renaming duplicate files as they're put into NSTemporaryDirectory. I had updates with 1-5 appended to the name after some failed testing.

Revision history for this message
Andy Matuschak (andymatuschak) wrote :

Sparkle actually does the auto-renaming bit. It's in [SUBasicUpdateDriver download:decideDestinationWithSuggestedFilename:]

Revision history for this message
Andy Matuschak (andymatuschak) wrote :

I still can't for the life of me figure out why this happens. Security.framework is inscrutable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.