All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: member graysky <graysky@archlinux.us>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: TestFlight is no longer accepting testers ... new link needed?
Date: Fri, 22 Mar 2019 13:48:23 -0600	[thread overview]
Message-ID: <CAHmME9r9k6iHgGRnKh8=aa-D-uHApLGc_LdqSnZu38V_NqO2HA@mail.gmail.com> (raw)
In-Reply-To: <CAO_nJAYPMoBNaKqNW10TRQSKA2EV_-9XqOhJmPmNVm4OuedOAw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 814 bytes --]

Apple took it down because the required device capability key conflicted
with an iPad in their test flight program, at exactly the same time the
main version was approved for the store. Interestingly the required device
capability key contained an erroneous entry "armv7", which we don't
actually require. So that's trivial to remediate, and the fix is already in
the repo. But it is interesting this was explicitly flagged for the first
time as part of their test program: does that mean they're working on a new
iPad chip that is armv8-only? It wouldn't surprise me.

On Fri, Mar 22, 2019, 13:25 John <graysky@archlinux.us> wrote:

> Is TestFlight for the iOS app no longer active?  Looking to get the
> latest build of the iOS client in hopes it is more robust for me (I
> see 0.0.20190319-5 a few days ago).
>

[-- Attachment #1.2: Type: text/html, Size: 1187 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

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

      reply	other threads:[~2019-03-22 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 19:24 TestFlight is no longer accepting testers ... new link needed? John
2019-03-22 19:48 ` Jason A. Donenfeld [this message]

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='CAHmME9r9k6iHgGRnKh8=aa-D-uHApLGc_LdqSnZu38V_NqO2HA@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=graysky@archlinux.us \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.