From: Alexander Burke <alex@alexburke.ca>
To: Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: macOS update logic needs improving
Date: Thu, 17 Dec 2020 11:34:33 +0100 [thread overview]
Message-ID: <F4FA02E0-62E2-4508-99FD-B917F8252346@alexburke.ca> (raw)
In-Reply-To: <Em6qFgnUJHoAWQmkBzNyZi4JA8DAd7Ylk0OANNRR1LVrZs8SzGAWkGCvyYj-jQPMTg3AV83_0oGW8Z40Uxm-KvseNM_CWXM9kQQLaOoOJPY=@protonmail.ch>
This is also the case on iOS for the same reason: because an app cannot be updated while it’s running, and while at least one tunnel is up the OS will not terminate the app.
> On 17 Dec 2020, at 05:25, Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch> wrote:
>
> Thank you for the recent efforts to bring macOS/iOS up to date.
>
> However there is a little bit of a problem with the logic for your macOS App Store updates.
>
> The update downloads fine, and *appears* to install, but the App Store app continues to show the update as available and installed.
>
> Further investigation shows that if Wireguard is running and/or open, the app will not actually be updated (App Store will roll back to the existing version).
>
> If Wireguard is quit, then the update will install OK.
>
> So you probably need to add some logic somewhere to detect and deal with open/running Wireguard (e.g. prompt user to exit).
next prev parent reply other threads:[~2020-12-17 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 10:25 Laura Smith
2020-12-17 10:33 ` Jason A. Donenfeld
2020-12-17 11:10 ` Laura Smith
2020-12-17 10:34 ` Alexander Burke [this message]
2020-12-17 10:38 ` Alexander Burke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F4FA02E0-62E2-4508-99FD-B917F8252346@alexburke.ca \
--to=alex@alexburke.ca \
--cc=n5d9xq3ti233xiyif2vp@protonmail.ch \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).