Closed luckman212 closed 2 years ago
Nice catch. That’s something which should be addressed in the MacUpdater CLI. It won’t affect the Workflow because it handles updates, not the scanning (that should be left to MacUpdater’s scheduling). If you contact MacUpdater, which I guess you might’ve done already, someone will take a look. Though it seems like a low priority issue, I imagine it doesn’t happen often.
Thank you for the concern.
Sure, I just reported it via email to support. Thanks @vitorgalvao
thanks for the bug report. we've addressed this now and the fix will be in the next public release of #MacUpdater (build number > 13887)
can't say if there will be another 2.2.2 build or if the next release will already be version 2.3
Hi @vitorgalvao
I started using
/Applications/MacUpdater.app/Contents/Resources/macupdater_client scan
in some automation scripts. I didn't know about this CLI!One problem, as I was testing, obviously I was running the
scan
parameter more often than normal, so I hit this:The problem here is, even after clicking OK, the
macupdater_client
process does not exit, so the script hangs indefinitely. I imagine this could/would affect the Alfred workflow as well.