<metaproperty="description"content="This page contains instructions for verifying that Telegram's open source code is exactly the same as the code that is used…">
<metaproperty="og:title"content="Reproducible Builds for iOS and Android">
<metaproperty="og:description"content="This page contains instructions for verifying that Telegram's open source code is exactly the same as the code that is used…">
<h1id="dev_page_title">Reproducible Builds for iOS and Android</h1>
<divid="dev_page_content"><p>This page contains instructions for verifying that Telegram's <ahref="https://telegram.org/apps#source-code">open source code</a> is exactly the same as the code that is used to build the apps that are available in the <ahref="https://telegram.org/dl/ios">App Store</a>, <ahref="https://telegram.org/dl/android">Google Play</a> and <ahref="https://telegram.org/android">directly</a> on the Telegram website.</p>
<p><strong>Warning:</strong> Telegram supports reproducible builds as of <ahref="https://telegram.org/blog/verifiable-apps-and-more"><strong>version 5.13</strong></a>. Bear in mind that, at this stage, the verification process should be considered <strong>experimental</strong>. We will be updating our apps and these instructions to make this process as straightforward as possible.</p>
<ul>
<li><ahref="#reproducible-builds-for-android">Telegram for Android</a></li>
<li><ahref="#reproducible-builds-for-ios">Telegram for iOS</a></li>
</ul>
<blockquote>
<p>Please read the relevant <strong>notes</strong> and <ahref="#troubleshooting">troubleshooting</a> section carefully.</p>
</blockquote>
<hr>
<divclass="blog_wide_image">
<ahref="/file/464001695/1/nxVa_f-qKS8.216020/9da7686ded6f1e7bef"target="_blank"><imgsrc="/file/464001785/3/GqL9jQg6ChI.76277/1377819b17eaa4dcce"srcset="/file/464001695/1/nxVa_f-qKS8.216020/9da7686ded6f1e7bef, 1200w"title="Builds Telegram verifiable are."alt="Dude in a jacket inspecting the hologram of a mechanical dog to verify it's built according to the blueprints provided."/></a>
</div>
<h2><aclass="anchor"name="reproducible-builds-for-android"href="#reproducible-builds-for-android"><iclass="anchor-icon"></i></a>Reproducible Builds for Android</h2>
<p>Docker can be obtained <ahref="https://www.docker.com/">here</a>. Once the installation is complete, log into your Docker account > Settings > Resources > Advanced and configure the amount of resources Docker may use:</p>
<p>We recommend using the maximum amount allowed by your system's hardware, in order to speed up the build time.</p>
<h3><aclass="anchor"name="step-2-confirm-which-version-you-have-installed-on-your-android"href="#step-2-confirm-which-version-you-have-installed-on-your-android"><iclass="anchor-icon"></i></a>Step 2. Confirm which version you have installed on your Android device</h3>
<p>You can find the <strong>version/build</strong> number and the source (website, Play Store, Huawei Store) at the bottom of the Settings page. Note that Telegram supports reproducible builds starting with version <strong>5.13</strong>.</p>
<p>Please make sure that you're using the correct <strong>version</strong> and <strong>build number</strong> of the version you want to check (and not the one from this example <imgclass="emoji"src="//telegram.org/img/emoji/40/F09F9888.png"width="20"height="20"alt="😈"/>). </p>
The part after the version number will help you know in which folder to look for the correct APK when you've finished [building the app (Step 4)](#step-4-build-the-app):
* “Direct” after version number means that the APK will be inside the “afat/standalone” folder.
* "Universal" after version number means that the APK will be inside the “afat/release” folder.
* If you have Android Version 6.0 or greater, your APK folder will have the “_SDK23” suffix.
* “arm64-v8a” - folder name will start with “arm64”.
* “armeabi-v7” - folder name will start with “armv7”.
<h3><aclass="anchor"name="step-3-obtain-the-source-code"href="#step-3-obtain-the-source-code"><iclass="anchor-icon"></i></a>Step 3. Obtain the source code</h3>
<p>Open Terminal, run the commands:<br><code>git clone https://github.com/DrKLO/Telegram.git $HOME/telegram-android</code><br><code>cd $HOME/telegram-android</code><br><code>git checkout release-{VERSION AND BUILD NUMBER FROM STEP 2}</code></p>
<p>For our <ahref="#step-2-confirm-which-version-you-have-installed-on-your-android">example</a>, the command would be:<br><code>git checkout release-5.13.0_1821</code></p>
<divclass="blog_wide_image">
<ahref="/file/464001840/1/5DrefLlg3vw.116770/8901e43605c30939d4"target="_blank"><imgsrc="/file/464001840/1/5DrefLlg3vw.116770/8901e43605c30939d4"title="Obtaining the source code"/></a>
</div>
<h3><aclass="anchor"name="step-4-build-the-app"href="#step-4-build-the-app"><iclass="anchor-icon"></i></a>Step 4. Build the app</h3>
<p>Open Terminal, run the commands:<br><code>cd $HOME/telegram-android</code><br><code>docker build -t telegram-build .</code></p>
<divclass="blog_wide_image">
<ahref="/file/464001202/1/UyO3_tLDRPg.35170/31865250522be6db86"target="_blank"><imgsrc="/file/464001202/1/UyO3_tLDRPg.35170/31865250522be6db86"title="Building the app"/></a>
</div>
<p><code>docker run --rm -v "$PWD":/home/source telegram-build</code></p>
<divclass="blog_wide_image">
<ahref="/file/464001691/2/SFreJq5OZ4U.34208/f69b83468ac2a07276"target="_blank"><imgsrc="/file/464001691/2/SFreJq5OZ4U.34208/f69b83468ac2a07276"title="Building the app"/></a>
<ahref="/file/464001014/116e8/0BQSMuzynOI.10222/1293c6fc237ab85f7e"target="_blank"><imgsrc="/file/464001014/116e8/0BQSMuzynOI.10222/1293c6fc237ab85f7e"title="Building the app"/></a>
<p><code>/apk/afat/standalone/app.apk</code>– used for direct downloads from telegram.org/android<br><code>/apk/afat/elease/app.apk</code>– the playstore version<br><code>/apk/afat/release/app-huawei.apk</code>– used exclusively for the Huawei store</p>
<p>Use the folder name from <ahref="#step-4-build-the-app">Step 4</a> to find the correct folder that holds the same APK as installed on your device. For example, for the Play Store version, the path to your APK will be:</p>
<p><code>$HOME/telegram-android/TMessagesProj/build/outputs/apk/afat/release/app.apk</code><br>Copy this APK to the root source directory by running this command in Terminal:<br><code>cp $HOME/telegram-android/TMessagesProj/build/outputs/apk/afat/release/app.apk $HOME/telegram-android/telegram_built.apk</code></p>
<ahref="/file/464001970/1/9nwL42h9lAU.32529/9b39cebcdb8c6daff7"target="_blank"><imgsrc="/file/464001970/1/9nwL42h9lAU.32529/9b39cebcdb8c6daff7"title="Copy the APK"/></a>
</div>
<h3><aclass="anchor"name="step-5-the-telegram-apk-installed-on-your-device"href="#step-5-the-telegram-apk-installed-on-your-device"><iclass="anchor-icon"></i></a>Step 5. The Telegram APK installed on your device</h3>
<p>You will need <ahref="https://developer.android.com/studio/releases/platform-tools.html#downloads">adb</a> for this step. </p>
<p>If you downloaded your APK <ahref="https://telegram.org/android"><strong>directly from Telegram's website</strong></a>, use the package name <code>org.telegram.messenger.web</code> in this step. To verify the <strong>Google Play APK</strong>, use <code>org.telegram.messenger</code>.</p>
</blockquote>
<p>Connect your device to the computer, open Terminal, run the commands:<br><code>adb shell pm path org.telegram.messenger</code></p>
<p>The output will look something like this:<br><code>package:/data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk</code><br>By using this information, pull the APK from your device to $HOME/telegram-android using command:<br><code>adb pull /data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk $HOME/telegram-android/telegram_store.apk</code></p>
<h3><aclass="anchor"name="step-6-compare-the-apks"href="#step-6-compare-the-apks"><iclass="anchor-icon"></i></a>Step 6. Compare the APKs</h3>
<p>To compare Direct and Huawei Store versions, open Terminal, run the commands:<br><code>cd $HOME/telegram-android</code><br><code>python apkdiff.py telegram_store.apk telegram_built.apk</code><br>If the APKs are the same, you will see<br><code>APKs are the same!</code></p>
<p>If your APKs don't match, please make sure that you chose <ahref="#step-2-confirm-which-version-you-have-installed-on-your-android">the correct code version</a> and <ahref="#step-4-build-the-app">the right SDK</a>.</p>
<p>Check out the <ahref="#troubleshooting">Troubleshooting</a> section first in case you run into trouble.</p>
<hr>
<h2><aclass="anchor"name="reproducible-builds-for-ios"href="#reproducible-builds-for-ios"><iclass="anchor-icon"></i></a>Reproducible Builds for iOS</h2>
<p>The verification process for iOS builds is, unfortunately, a lot more complex than for Android. The two main issues with Apple's current policies and infrastructure are as follows:</p>
<ol>
<li><p>Apple insists on using <strong>FairPlay</strong> encryption to “protect” even <strong>free</strong> apps from “app pirates” which makes obtaining the executable code of apps impossible without a jailbroken device. To solve this issue, Apple would simply need to allow submitting unencryptable binaries to the App Store. This would not affect security since the code would still be signed – and would enable anyone to check the integrity of apps supporting reproducible builds without endangering the integrity and security of their devices.</p>
</li>
<li><p>Building your own reproducible binaries is difficult because macOS doesn't support containers like Docker. If Apple followed in the footsteps of Linux (and even Microsoft!) and added container support, it would eliminate the need for steps 1-3 in the guide below.</p>
</li>
</ol>
<blockquote>
<p>As things stand now, you'll need a <strong>jailbroken device</strong>, at least <strong>1,5 hours</strong> and approximately <strong>90GB</strong> of free space to properly set up a virtual machine for the verification process.</p>
</blockquote>
<p>To provide a stable and easily reproducible environment, Telegram iOS builds are compiled on a virtual machine. Parallels is used to verify the builds.</p>
<p>Despite the compiler bugs introduced by Apple in <strong>Xcode 14</strong> (<ahref="#troubleshooting-ios">read more</a>), we were able to restore deterministic builds using manually crafted linker flags. Use the steps below to verify builds compiled with XCode 13 and below, <ahref="#ios-xcode-14">see here for XCode 14 instructions</a>.</p>
<h3><aclass="anchor"name="step-1-install-the-parallels-virtual-machine"href="#step-1-install-the-parallels-virtual-machine"><iclass="anchor-icon"></i></a>Step 1. Install the Parallels virtual machine</h3>
<p>Parallels can be obtained <ahref="https://www.parallels.com/">here</a>, it features a fully-functional trial version.</p>
<h3><aclass="anchor"name="step-2-install-the-latest-version-of-macos-big-sur"href="#step-2-install-the-latest-version-of-macos-big-sur"><iclass="anchor-icon"></i></a>Step 2. Install the latest version of macOS Big Sur</h3>
<p>To download an image that can be installed on the virtual machine, open the App Store, search for “Catalina” and click “View”.</p>
<divclass="blog_image_wrap">
<ahref="/file/464001442/2/kdNIHhlKvz4.940110/19c350a98ef2c2c164"target="_blank"><imgsrc="/file/464001442/2/kdNIHhlKvz4.940110/19c350a98ef2c2c164"title="Search for macOS Catalina on App Store > View"/></a>
<p>Search for macOS Catalina on App Store > View</p>
Choose “Download” and wait for the download to finish.
> If you were not using the latest version of the OS, your system may start updating instead. Please finish updating to download macOS Catalina.
When done, open Parallels and choose macOS Catalina:
<divclass="blog_image_wrap">
<ahref="/file/464001612/2/MX23LbMTi9s.387733/04fbf3e50047b87e99"target="_blank"><imgsrc="/file/464001612/2/MX23LbMTi9s.387733/04fbf3e50047b87e99"title="Select 'Install Windows or another OS' > Continue"/></a>
<p>Select 'Install Windows or another OS' > Continue</p>
<p>Before starting the installation, configure the virtual machine:</p>
<divclass="blog_image_wrap">
<ahref="/file/464001210/2/FVlrqHY_Vqw.231478/0167b02433bf413c67"target="_blank"><imgsrc="/file/464001210/2/FVlrqHY_Vqw.231478/0167b02433bf413c67"title="Enable checkbox 'Customize settings before installation'"/></a>
<p>Checkbox 'Customize settings before installation'</p>
</div>
<p>Change the name of the virtual machine to <code>macos11_Xcode12_5_1</code></p>
<divclass="blog_image_wrap">
<ahref="/file/464001398/1/SB22XXoAWTg.151444/8e479c26b30ceccc01"target="_blank"><imgsrc="/file/464001398/1/SB22XXoAWTg.151444/8e479c26b30ceccc01"title="Name VM as macos10_15_Xcode11_2"/></a>
<p>Name VM as macos10_15_Xcode12_2</p>
</div>
<p>Hardware > Processors: 2-4<br>Memory > 4GB may suffice but 8GB is recommended</p>
<divclass="blog_image_wrap">
<ahref="/file/464001494/1/_BIf-UvwS3Q.239110/d52cb48ec3d6e76e84"target="_blank"><imgsrc="/file/464001494/1/_BIf-UvwS3Q.239110/d52cb48ec3d6e76e84"title="At least 2 CPUs + 4 (8 recommended) GB Memory."/></a>
<p>At least 2 CPUs + 4 (8 recommended) GB Memory.</p>
<p>Your Apple ID is also not required, you can choose <strong>Set Up Later</strong>.</p>
<divclass="blog_image_wrap">
<ahref="/file/464001885/3/-EDysKEKxN4.872188/4fd018cdc5b1e9f3f4"target="_blank"><imgsrc="/file/464001885/3/-EDysKEKxN4.872188/4fd018cdc5b1e9f3f4"title="Skip Apple ID with 'Set Up Later'"/></a>
<p>Skip Apple ID with 'Set Up Later'</p>
</div>
<p>Use “telegram” for both the account name and password.</p>
<blockquote>
<p>Do not ever use the password “telegram” for <strong>anything</strong> else, it's cursed.</p>
</blockquote>
<divclass="blog_image_wrap">
<ahref="/file/464001994/1/uhQTRCzmHj0.805076/9fe8aaf3ade46b3bbf"target="_blank"><imgsrc="/file/464001994/1/uhQTRCzmHj0.805076/9fe8aaf3ade46b3bbf"title="Create a computer account with 'telegram' set both as account name and password"class="dev_page_image"/></a>
<p>Create a computer account with 'telegram' set both as account name and password</p>
</div>
<p>Now install Parallels tools from the menu bar:</p>
<divclass="blog_wide_image">
<ahref="/file/464001486/1/kvHNFzvxjA8.2491846/d75c7b01cb0d3e4115"target="_blank"><imgsrc="/file/464001486/1/kvHNFzvxjA8.2491846/d75c7b01cb0d3e4115"title="Install Parallels Tools using menu bar > Parallels icon > Actions > Install (Reinstall) Parallels Tools"/></a>
<p>Install Parallels Tools using menu bar > Parallels icon > Actions > Install (Reinstall) Parallels Tools...</p>
</div>
<p>After the system restarts, log in.<br>Open <strong>Terminal</strong> and run:<br><code>sudo visudo</code><br>Enter the password “telegram”</p>
<divclass="blog_wide_image">
<ahref="/file/464001603/1/syuA7Rk-n2Q.40736/a5e73335e5c7d3a36c"target="_blank"><imgsrc="/file/464001603/1/syuA7Rk-n2Q.40736/a5e73335e5c7d3a36c"title="Run Terminal on the VM, enter 'sudo visudo' > enter password (telegram)"/></a>
</div>
<p>Find this line at the end of the file:<br><code>%admin ALL=(ALL) ALL</code><br>Press “i” on your keyboard, add “NOPASSWD:”<br><code>%admin ALL=(ALL) NOPASSWD: ALL</code><br>Press Escape.<br>Type in “:wq”<br>Press Enter</p>
<divclass="blog_wide_image">
<ahref="/file/464001750/1/T6mMRrNkTUY.105833/6c491ac94ba52c30a0"target="_blank"><imgsrc="/file/464001750/1/T6mMRrNkTUY.105833/6c491ac94ba52c30a0"title="Press i to edit the highlighted string"class="dev_page_image"/></a>
<p>In the terminal, run:<br><code>sudo systemsetup -setcomputersleep Never</code></p>
<divclass="blog_wide_image">
<ahref="/file/464001368/3/4nNsEU8siSo.54459/fdccb77de26ce89c25"target="_blank"><imgsrc="/file/464001368/3/4nNsEU8siSo.54459/fdccb77de26ce89c25"title="sudo systemsetup -setcomputersleep Never > press Enter"/></a>
<p>sudo systemsetup -setcomputersleep Never > press Enter.</p>
</div>
<h3><aclass="anchor"name="step-3-install-ssh-keys-on-the-virtual-machine"href="#step-3-install-ssh-keys-on-the-virtual-machine"><iclass="anchor-icon"></i></a>Step 3. Install SSH keys on the virtual machine</h3>
<p>In the virtual machine, open System Settings > Sharing and enable <strong>Remote Login</strong>.</p>
<divclass="blog_wide_image">
<ahref="/file/464001585/1/PEomlV3X5tY.2043293/4945fabb3f0dbc3498"target="_blank"><imgsrc="/file/464001585/1/PEomlV3X5tY.2043293/4945fabb3f0dbc3498"title="Go to macOS Settings > Sharing > enable Remote Login"/></a>
</div>
<p>In the virtual machine, open Terminal and run:<br><code>mkdir -p .ssh; nano .ssh/authorized_keys</code></p>
<p>In your main OS, open Terminal and run:<br><code>if [ ! -e ~/.ssh/id_rsa.pub ]; then ssh-keygen -t rsa -b 4096; fi && cat ~/.ssh/id_rsa.pub | pbcopy</code></p>
<p>If you see the line “Enter file in which to save the key (/Users/…/.ssh/id_rsa):”, press Enter<br>In the virtual machine, press <strong>CMD+V</strong><br>Then <strong>Ctrl+O</strong>, <strong>Ctrl+X</strong></p>
<h3><aclass="anchor"name="step-4-install-xcode-version-12-5-1"href="#step-4-install-xcode-version-12-5-1"><iclass="anchor-icon"></i></a>Step 4. Install Xcode version 12.5.1</h3>
<p>In the virtual machine, open Safari and go to https://developer.apple.com<br>Sign in to your Account:</p>
<divclass="blog_image_wrap">
<ahref="/file/464001443/2/LhmF4qgPgn4.501969/6edbc244d8b9f8298e"target="_blank"><imgsrc="/file/464001443/2/LhmF4qgPgn4.501969/6edbc244d8b9f8298e"title="developer.apple.com > Account > sign in with your Apple ID"/></a>
<p>developer.apple.com > Account > sign in with your Apple ID</p>
</div>
<p>Go to <strong>Downloads > More</strong><br>Enter <strong>Xcode</strong> in the search field and find the version 12.5.1</p>
<divclass="blog_image_wrap">
<ahref="/file/464001260/1/njYJxQDnzzQ.664134/d4e8de0aed2d74d6e0"target="_blank"><imgsrc="/file/464001260/1/njYJxQDnzzQ.664134/d4e8de0aed2d74d6e0"title="Downloads > More > 12.5.1"/></a>
<p>Downloads > More > Xcode 12.5.1</p>
</div>
<p>Once the installation is complete, open the file Xcode 12.5.1.xip. The system will unarchive the app into the same folder. Move it to the <strong>Applications</strong> folder using Finder.</p>
<divclass="blog_image_wrap">
<ahref="/file/464001707/1/GIIAXXifhbI.2058152/af989007034194b28b"target="_blank"><imgsrc="/file/464001707/1/GIIAXXifhbI.2058152/af989007034194b28b"title="Unarchive Xcode > drag the app to Applications folder"/></a>
<p>Unarchive Xcode > drag the app to Applications folder</p>
</div>
<divclass="blog_image_wrap">
<ahref="/file/464001214/1/CZJfqS7Fhr8.2206987/d29e070d1cef8de8fb"target="_blank"><imgsrc="/file/464001214/1/CZJfqS7Fhr8.2206987/d29e070d1cef8de8fb"title="Move Xcode to Applications using Finder > Run > Agree to install additional components"/></a>
</div>
<p>On the virtual machine, run this command from the terminal:<br><code>sudo xcode-select -s /Applications/Xcode.app/Contents/Developer</code></p>
<ahref="/file/464001752/2/kos29MZFaJ0.3515145/88dff67ef53dbf4dcc"target="_blank"><imgsrc="/file/464001752/2/kos29MZFaJ0.3515145/88dff67ef53dbf4dcc"title="Shut down the virtual machine"/></a>
<p>Download the certificates at https://github.com/TelegramMessenger/Telegram-iOS/tree/master/build-system/fake-codesigning/certs/distribution and install them into the virtual machine.</p>
<p>Launch Keychain Access and double-click the installed certificate. Under “Trust”, change “When using this certificate” to “Always Trust”.</p>
<h3><aclass="anchor"name="step-5-obtaining-the-source-code"href="#step-5-obtaining-the-source-code"><iclass="anchor-icon"></i></a>Step 5. Obtaining the source code</h3>
<p>E.g., <code>git checkout release-7.3</code>. Please note that you need to check out the whole git history as the build version depends on the number of commits in the repository.</p>
<p>Check that you have downloaded the correct version:<br><code>chmod +x bazel</code><br><code>./bazel --version</code></p>
<h3><aclass="anchor"name="step-7-building-the-app"href="#step-7-building-the-app"><iclass="anchor-icon"></i></a>Step 7. Building the app</h3>
<p>Open Terminal, run the commands:<br><code>cd $HOME/telegram-ios
BAZEL="$HOME/bazel/bazel" sh buildbox/build-telegram.sh verify</code></p>
<divclass="blog_wide_image">
<ahref="/file/464001292/1/9vG9rIqfOK0.38309/7f7df70686fc4afc36"target="_blank"><imgsrc="/file/464001292/1/9vG9rIqfOK0.38309/7f7df70686fc4afc36"title="Building the app"/></a>
</div>
<p>If the environment has been set up correctly, this will start the building process. Note that this step can easily take <strong>30-40 minutes</strong>. The average build time on a MacBook Pro (i9 6 core) is 35 minutes.</p>
<p>Once the process is complete the resulting IPA file can be found in <code>build/artifacts/Telegram.ipa</code><br>All the following steps will be made via Terminal on your main system.</p>
<h3><aclass="anchor"name="step-8-downloading-a-decrypted-version-of-the-app-from-the-app-s"href="#step-8-downloading-a-decrypted-version-of-the-app-from-the-app-s"><iclass="anchor-icon"></i></a>Step 8. Downloading a decrypted version of the app from the App Store</h3>
<p>This step requires a jailbroken device equipped with tools for decrypting apps. We‘d love to make this process more simple but that’s what you get for using Apple tech.</p>
<h3><aclass="anchor"name="step-9-comparing-the-appstore-build-and-the-version-built-in-the"href="#step-9-comparing-the-appstore-build-and-the-version-built-in-the"><iclass="anchor-icon"></i></a>Step 9. Comparing the AppStore build and the version built in the virtual machine</h3>
<p>Install the necessary tools:<br><code>if ! type brew > /dev/null;
then /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"; fi && brew install python3</code></p>
IPAs contain Watch directory with a Watch app which can't be checked currently.
IPAs contain .car (Asset Catalog) files that are compiled by the App Store and can't currently be checked:
Frameworks/TelegramUI.framework/Assets.car
Assets.car
IPAs contain .nib (compiled Interface Builder) files that are compiled by the App Store and can't currently be checked:
Base.lproj/LaunchScreen.nib</code></pre>
<divclass="blog_wide_image">
<ahref="/file/464001561/2/8mgy93NZXIg.138258/a0a0dca779416fba8a"target="_blank"><imgsrc="/file/464001561/2/8mgy93NZXIg.138258/a0a0dca779416fba8a"title="The result > equal IPAs"/></a>
</div>
<p>In case of any mismatches, you'll get a detailed report.</p>
<p>Due to compiler bugs introduced by Apple in <strong>Xcode 14</strong> (<ahref="#troubleshooting-ios">read more</a>), you will need to use the modified instructions below to verify the latest builds:</p>
<p><strong>Remove steps 6, 7</strong></p>
<p><strong>Steps 1-4.1</strong> are replaced with:</p>
<p>Follow the installation instructions. Set username to <code>containerhost</code> and password to <code>containerhost</code>.<br>Enable Remote Login and allow full disk access for remote users.<br>Connect to the guest VM using SSH with username <code>containerhost</code> and password <code>containerhost</code>.<br>Create directory <code>~/.ssh</code> and set up the <code>authorized_keys</code> using the public key string printed by the <code>darwin-containers create</code> command earlier.<br>Upload the appropriate version of Xcode via <code>scp</code> and install to /Applications. Run it at least once to complete installation.<br>Shutdown the guest OS.</p>
<li><p>You will get a warning if the archive created in <ahref="#step-7-building-the-app">Step 7</a> contains encrypted files. If all these files are in the <code>PlugIns</code> subfolder, they represent various system extensions (e.g. external sharing, Siri, 3D touch). Decrypting such files using existing ways of receiving app archives via Jailbreak is non-trivial (but we're working on resolving this issue). If you do manage to decrypt them, e.g. on iOS 8, they will be matched.</p>
</li>
<li><p>You will be notified if the archive includes an <strong>Apple Watch app</strong>. The watch app will soon no longer be included in the archive.</p>
</li>
<li><p>Files with the <code>.car</code> extension are app resource archives (images, sounds) which were compiled and processed specifically for the target device. The App Store processes them in non-trivial ways, we're planning on getting rid of them in future versions.</p>
</li>
<li><p>The <code>LaunchScreen.nib</code> file is an empty file containing a description of the interface which is displayed by the system before the app is launched. It is processed by the App Store in a non-trivial way but doesn't contain any code and therefore may be ignored.</p>
<p>If you encounter any issues with obtaining the code, building and comparing the apps, please contact us at <ahref="https://t.me/botsupport">@BotSupport</a> and include the hashtag <code>#reproducibleBuilds</code> with your message describing the problem.</p>
<li><p>Make sure that you checkout <ahref="#step-2-confirm-which-version-you-have-installed-on-your-android">the correct version</a> of the code.</p>
</li>
<li><p>Make sure that you build the app using <ahref="#step-4-build-the-app">the right SDK</a>.</p>
</li>
<li><p>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.</p>
<p><strong>UPD:</strong> Despite the fact that the issue below persists, we were able to restore deterministic builds using manually crafted linker flags. See these updated <ahref="#ios-xcode-14">steps for XCode 14</a>.</p>
<p>Due to recent changes introduced in <strong>XCode 14</strong> by <strong>Apple</strong>, it is currently not possible to create <ahref="#reproducible-builds-for-ios">reproducible builds for iOS</a> using tools officially supported by Apple. <strong>We will update this page as soon as Apple resolves the issue.</strong></p>
<p>To confirm the issue for yourself, follow these steps:</p>
