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 00:53:01 +0100	[thread overview]
Message-ID: <CAHmME9pZq6pMV9W2EiYRP_mOLkQXVDpdB83kEFsiuhEH807bzA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qCRWXMVjuz6g6M0wMvhj9v90sTkHNOFCr+Jht-rUNFoQ@mail.gmail.com>

Hi again,

On Thu, Dec 17, 2020 at 10:53 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> However, they rejected the iOS update, due to the link in the version
> info window to https://www.wireguard.com/donations/ that we've had on
> there for two years. You can see their rejection here:
> https://data.zx2c4.com/apple-asks-me-to-remove-donation-link-from-app.png
> https://data.zx2c4.com/the-screenshot-that-apple-provided.png
>
> Not wanting to hold up getting this fix deployed, I quickly removed
> the link and resubmitted to the App Store:
> https://git.zx2c4.com/wireguard-apple/commit/?id=a4fc0f64b8bca8afae5abab37b81ba0b45836975
>
> So now the process of getting that fix deployed on iOS starts from the
> beginning again. It could take another 24 hours. It could take a full
> month. The process is opaque, and try as I may, I don't know what else
> I can do to get the fix out faster.

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. My experience with Apple
here is that if you respond to their rejection with anything at all,
you automatically get put in a bin of at least a week wait time. I
hope that doesn't happen here. But, anyway, another day has gone by,
and we're still waiting on Apple to ship the fix to you all.

My response to them was:

> Hi,
>
> Looking at that screenshot, I think you might have tested the old build. The
> one I submitted is build 21, which removes the donation link, rather than
> build 20. But in the screenshot you've attached, it shows "(20)" and it also
> shows the donation link. So that leaves me pretty confused about what's
> going on. The link is definitely gone in build 21, and I definitely
> submitted build 21, and looking again at my build submission, it says build
> 21.
>
> Attached is a photo of build 21 running from Test Flight on my iPhone.
> Notice how the build number says 21 and the donation link is gone.
>
> Could you take another look?
>
> Thanks,
> Jason

I hope this gets cleared up soon. Maybe I'll watch Terry Gilliam's
Brazil on repeat while waiting.

Jason

  parent reply	other threads:[~2020-12-18 23:53 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 [this message]
2020-12-19  0:11       ` Jacob Lambert
2020-12-19 10:40       ` Jason A. Donenfeld
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=CAHmME9pZq6pMV9W2EiYRP_mOLkQXVDpdB83kEFsiuhEH807bzA@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).