From 7511f2395a8bff28cb31dc96e85d047ff72d84dc Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Mon, 26 Sep 2022 11:37:32 +0000 Subject: [PATCH] Update content of files --- .../core.telegram.org/reproducible-builds.html | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/data/web/core.telegram.org/reproducible-builds.html b/data/web/core.telegram.org/reproducible-builds.html index 5c248aeb38..e2d052f195 100644 --- a/data/web/core.telegram.org/reproducible-builds.html +++ b/data/web/core.telegram.org/reproducible-builds.html @@ -161,7 +161,7 @@ Otherwise, something went wrong.

To provide a stable and easily reproducible environment, Telegram iOS builds are compiled on a virtual machine. Parallels is used to verify the builds.

-

Due to recent changes introduced in XCode 14 by Apple, the instruction below doesn't work at the moment. We will update this page as soon as Apple resolves the issue.

+

Due to recent changes introduced in XCode 14 by Apple, the instruction below doesn't work at the moment. We will update this page as soon as Apple resolves the issue. Read more about the issue

Step 1. Install the Parallels virtual machine

Parallels can be obtained here, it features a fully-functional trial version.

@@ -416,8 +416,18 @@ BAZEL="$HOME/bazel/bazel" sh buildbox/build-telegram.sh verify<

  • If the gradle version used in the Dockerfile is not available anymore and building of the Docker image fails, wait for a Dockerfile update or update manually to lastest available version.

    • -

    …

    -

    We will update this section with information on overcoming other common issues.

    +

    Troubleshooting: iOS

    +

    Due to recent changes introduced in XCode 14 by Apple, it is currently not possible to create reproducible builds for iOS using tools officially supported by Apple. We will update this page as soon as Apple resolves the issue.

    +

    To confirm the issue for yourself, follow these steps:

    +
      +
    1. Unzip link-issue.zip
      2. +
    2. sh test-link.sh
      3. +
    3. Compare link1.output and link.output. Specifically:
      4. +
    +