wireguard-apple VS asdf

I am trying to integrate WireGuard for iOS and macOS in Xcode, the build process is success, but the integration shows error which is attached below,although I had followed the procedures said in Github(https://github.com/WireGuard/wireguard-apple/blob/master/README.md)... I am facing issue while integrating WireGuardKit in Xcode project. Help me to solve this, if anyone had done with it, share your ideas/thoughts as soon as possible... Anyhelp will be appreciated!

The [github repo](https://github.com/WireGuard/wireguard-apple) is a readonly mirror. The [official git repo](https://git.zx2c4.com/wireguard-apple) has no discussion/wiki area that I can see.

I thought so too, but I saw posts like this that made me wonder. I haven't had a chance to look at the source code yet.

I have an MDM and for iOS devices I am able to send configurations (profiles) with Wireguard client data and it is configured automatically. I have followed this: https://github.com/WireGuard/wireguard-apple/blob/master/MOBILECONFIG.md

Okay, I just dove into wireguard‘s source code and it looks like I made wrong assumptions. When I used mullvad or wireguard, it always showed „127.0.0.1“ as the server, however, according to wireguard‘s source, this is just set as a placeholder. I assume that mullvad used this code to implement their app too.

https://github.com/WireGuard/wireguard-apple/blob/13b720442d...

https://ibb.co/x5kwxZW

The most hopeful discussion was this Github project... but., I can't get iOS to accept the .mobileconfig as a legitimate profile. Hoping some of the smart folks here had a solution.

The Apple Wireguard project on Github currently supports both iOS and MacOS natively.

So, I found this guide to create a mobileconfig for WireGuard (https://github.com/WireGuard/wireguard-apple/blob/master/MOBILECONFIG.md) , and I’ve heard a mobileconfig with a managed device can force the phone to make ALL traffic go through vpn (I run a pihole accessible via WireGuard and want to use with that) and my question is how do I setup a managed device for myself for the purpose of total network traffic control?

I'm trying to build the official Wireguard Xcode for iOS, but I get this build error with WireGuardGoBridgeiOS

The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.

I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.

[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...

[1]: https://github.com/asdf-vm/asdf/pull/1441

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions

https://asdf-vm.com/

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:

I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.