wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: WireGuard removed from Google Play Store, rectification in progress
Date: Wed, 16 Oct 2019 10:48:21 +0200	[thread overview]
Message-ID: <CAHmME9rcxwHNwT33cQzP6pGf64YG1Sz5iJtjQcOyFGanQf-CMg@mail.gmail.com> (raw)

Hi,

After waiting several days for Google to review our app -- apparently
the process is manual now and they're quite backed up -- I was
delighted to learn this morning that the app was approved. Then, 20
minutes later, I received a letter saying that the entire app listing,
not just the latest version, has been removed and delisted from the
Play Store.

They said it was because we're in violation of their "Payments
Policy", presumably because we have a link inside the app that opens
the user's web browser to wireguard.com/donations/ . I appealed using
their website appeal form. Thirty minutes later (was this automated,
unlike the manual app review process?), I received a rejection of the
appeal.

I immediately made this commit --
https://git.zx2c4.com/wireguard-android/commit/?id=f0bab44b4a17b65e9f7e718a9ba9b2bc37041268
-- and uploaded a new version. We're now waiting for a new, presumably
manual, review of the app. Until then, it is entirely unavailable on
the Play Store.

Sorry for the inconvenience. I'm sure many users are just as annoyed
as I am. In the interim, luckily F-Droid has our app:
https://f-droid.org/en/packages/com.wireguard.android/

I'll send an update once we're reinstated on the Play Store.

Regards,
Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-10-16  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  8:48 Jason A. Donenfeld [this message]
2019-10-16 20:12 ` WireGuard removed from Google Play Store, rectification in progress Jason A. Donenfeld

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=CAHmME9rcxwHNwT33cQzP6pGf64YG1Sz5iJtjQcOyFGanQf-CMg@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).