wails: v2.8 not running on Mac M2

Description

a clean install of Wails v2.8 and a new project init will not run on my Mac, I get an error " ERROR option -r not recognized" when running wails dev or wails build

If I downgrade Wails I can run it fine.

To Reproduce

  1. upgrade wails to v2.8
  2. wails init -n my-app
  3. cd my-app
  4. wails dev

Expected behaviour

Should run without error

Screenshots

Screenshot 2024-03-19 at 13 31 07

Attempted Fixes

No response

System Details

# Wails
Version | v2.8.0

# System
┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
| OS           | MacOS                                                                                                                       |
| Version      | 14.2.1                                                                                                                      |
| ID           | 23C71                                                                                                                       |
| Go Version   | go1.21.6                                                                                                                    |
| Platform     | darwin                                                                                                                      |
| Architecture | arm64                                                                                                                       |
| CPU          | Apple M2 Pro                                                                                                                |
| GPU          | Chipset Model: Apple M2 Pro Type: GPU Bus: Built-In Total Number of Cores: 19 Vendor: Apple (0x106b) Metal Support: Metal 3 |
| Memory       | 16GB                                                                                                                        |
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

# Dependencies
┌───────────────────────────────────────────────────────────────────────┐
| Dependency                | Package Name | Status    | Version        |
| Xcode command line tools  | N/A          | Installed | 2405           |
| Nodejs                    | N/A          | Installed | 21.0.0         |
| npm                       | N/A          | Installed | 10.2.0         |
| *Xcode                    | N/A          | Installed | 15.2 (15C500b) |
| *upx                      | N/A          | Available |                |
| *nsis                     | N/A          | Installed | v3.09          |
└─────────────────────── * - Optional Dependency ───────────────────────┘

# Diagnosis
Optional package(s) installation details:
  - upx : Available at https://upx.github.io/

Additional context

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (7 by maintainers)

Most upvoted comments

@stukennedy I saw the exact same error text as you, which makes me think maybe we have the same problem. I use asdf to manage versions of the different tools on my machine, and one of my python installs had added an xattr executable to my path.

Merged. Thanks for the quick feedback 🙏

I can confirm that the absolute path fix from #3328 works on my machine even when I have a different xattr installed in my PATH 👍

Thanks for the update - Will try again after work

Thanks for testing. Having the correct xattr should always have worked. I’m just thinking that perhaps we could drop the r flag but I’m not sure it would strip all the extended attributes

The default xattr command is (in theory) always going to be in a standard location on darwin systems, right? What if you used the absolute path where the system xattr is expected to be installed (/usr/bin/xattr)?

Alternatively, maybe you could accept some kind of escape hatch for the user to provide a path for xattr in situations where the xattr from the PATH isn’t the right one. I’m not sure how it would be best to expose such an option… maybe a command line flag?