Help with: "Autoupdate Error: Timeout: agent connection was never initiated (null) (URL (null))" #2159
-
I've been using Sparkle 2 for a while with my Sandboxed app. Today I made a new release. I updated files and tested from my computer (works), but I have a user where this update is reptatditly failing with the following error:
Does this ring a bell for anyone? My computer is macOS 12.3.1, while their computer is 11.6.6, I don't know if that is making the difference or not. Update A little more information... the update does work on their computer from Guest User account. Update 2 And now it is working in their account (after the logout and log back in). So working, but would still be interesting to have an idea on the underlying problem. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
For some reason the XPC connection from the progress/agent tool ( |
Beta Was this translation helpful? Give feedback.
-
Thanks for taking a look. Here's the more complete log that the user sent to me in case it helps.
|
Beta Was this translation helpful? Give feedback.
-
Likely a performance issue. |
Beta Was this translation helpful? Give feedback.
-
Ok, thanks again for talking a look. I'll report back if I keep seeing this, but so far it's only been this one time. |
Beta Was this translation helpful? Give feedback.
-
On my machine |
Beta Was this translation helpful? Give feedback.
-
I made a change that specifies the |
Beta Was this translation helpful? Give feedback.
For some reason the XPC connection from the progress/agent tool (
Updater.app
) to theAutoupdate
installer was never established. It would be interesting to see if there were logs showingUpdater
process was started in any way (if you have those). I suppose since a logout/reboot fixes it, libxpc/launchd or something could be involved in such a way. Since it's not reproducible anymore it's hard to dive deeper with just the given info available :(. This code probably hasn't really changed much since Sparkle 2 beta ~2016 and this is the first report of this error I'm aware of.