joel.poyet
65d19d3274
Both documents told the reader to pin Xcode 26.4 and to install it via a Brewfile. A probe of novaloop-mac-studio-001 refutes the premise: it carries exactly one Xcode, 26.6, globally selected, with no versioned siblings and no 26.4 anywhere. The design justified the pin with "the runner has it and the legacy pipeline proves it works" — both halves are false, and a pin naming an absent version does not fail fast: xcodes starts a multi-GB authenticated download that no CI secret can satisfy, so before_all hangs. Record the no-pin decision and its cost — whatever Xcode the runner has is what ships, unrecorded — rather than only deleting the wrong instruction, so nobody reintroduces the pin from the same reasoning. Drop the Brewfile with it: its only purpose was installing xcodes for that pin, and brew has no business running on a shared release machine where it could upgrade xcodegen mid-release. Add the runner's real constraints (no passwordless sudo, single Xcode, five missing tools installed by hand) to the design, since they are why upstream's setup_github_actions_environment cannot run here. Two new risks. The legacy element-ios pipeline pins the same absent 26.4, so it is very likely broken right now — not this fork's problem to fix, but the human needs to know before the next legacy release. And with no pin, an Xcode upgrade on the runner silently changes the compiler for every subsequent release. The plan's embedded Fastfile and skill now match the branches that implement them byte-for-byte, so the plan cannot drift from the artefacts it describes.
Element X iOS
Element X iOS is the next-generation Matrix client provided by Element.
Compared to the previous-generation Element Classic, it is a total rewrite using the Matrix Rust SDK underneath and targeting devices running iOS 18+.
Rust SDK
Element X leverages the Matrix Rust SDK through an FFI layer exposed as a swift package that the final client can directly import and use. We're doing this as a way to share code between platforms, with Element X Android using the same SDK.
Status
This project is actively developed and supported. New users are recommended to use Element X instead of the previous-generation app.
Contributing
Please see our contribution guide.
Come chat with the community in the dedicated Matrix room.
Build instructions
Please refer to the setting up a development environment section from the contribution guide.
Support
When you are experiencing an issue on Element X iOS, please first search in GitHub issues and then in #element-x-ios:matrix.org. If after your research you still have a question, ask at #element-x-ios:matrix.org. Otherwise feel free to create a GitHub issue if you encounter a bug or a crash, by explaining clearly in detail what happened. You can also perform bug reporting (Rageshake) from the Element application by going to the application settings. This is especially recommended when you encounter a crash.
Forking
Please read our forking guide.
Copyright & License
Copyright (c) 2025 - 2026 Element Creations Ltd. Copyright (c) 2022 - 2025 New Vector Ltd.
This software is dual licensed by Element Creations Ltd (Element). It can be used either:
(1) for free under the terms of the GNU Affero General Public License (as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version); OR
(2) under the terms of a paid-for Element Commercial License agreement between you and Element (the terms of which may vary depending on what you and Element have agreed to).
Unless required by applicable law or agreed to in writing, software distributed under the Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.