Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard on macOS stopped working after 1.0.10 update
Date: Sat, 19 Dec 2020 11:40:14 +0100	[thread overview]
Message-ID: <CAHmME9owPe-HX=Lw28HzM7_cm0XqVZJOzVcHcfCgwXp-7GU+DQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pZq6pMV9W2EiYRP_mOLkQXVDpdB83kEFsiuhEH807bzA@mail.gmail.com>

Hey folks,

On 12/19/20, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> They rejected the submission with the donation link removed, citing
> the existence of the donation link in the old build and providing a
> screenshot of the old build, rather than the new build. I sent them a
> response pointing out that they reviewed the wrong build, looking at
> the old build rather than the new build, and I sent them a photo of
> the new build as installed from Test Fight.

Looks like we got lucky this time, and things are all set! 1.0.11
should now be available in the App Store. Hopefully this concludes the
saga with the recent updates, and things will be smooth sailing from
here on out. But as usual, please don't hesitate to send new bugs,
with redacted configs and logs.

Jason

  parent reply	other threads:[~2020-12-19 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 23:52 Glenn Schmidt
2020-12-17  1:43 ` Jason A. Donenfeld
2020-12-17  2:09   ` Glenn Schmidt
2020-12-17 21:53   ` Jason A. Donenfeld
2020-12-17 22:34     ` Nicolas CAPEYRON
     [not found]     ` <CAA6-MF8ZZ1eD+7wTfgzuGaiw8JPM+WiivJ0CxBja3-GZ=GXMaA@mail.gmail.com>
2020-12-18  9:19       ` Jason A. Donenfeld
2020-12-18 23:53     ` Jason A. Donenfeld
2020-12-19  0:11       ` Jacob Lambert
2020-12-19 10:40       ` Jason A. Donenfeld [this message]
2020-12-17 15:19 Nicolas CAPEYRON

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='CAHmME9owPe-HX=Lw28HzM7_cm0XqVZJOzVcHcfCgwXp-7GU+DQ@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --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).