Wails app on build macos

[zuno90]

I had successfully build on my macos m1 and embeded ffmpeg static into binary build, but bundle file was not work. By running executable file inside Contents/MacOS, that is worked as I expected. So what s happen with bundle file, what i need to active and anything. Thanks for any helps!

[atterpac]

Mac has a lot of restrictions security wise, you need to make sure everything inside the contents is properly signed and notarized as well as the final application

https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/

*Fixed link

[ayush-shta]

Do we need to go through the app signing steps mentioned here, even if we do not want to distribute through app store? or is there a simpler way for this?

[atterpac]

Do we need to go through the app signing steps mentioned here, even if we do not want to distribute through app store? or is there a simpler way for this?

You can try packaging it with ditto into a zip for sharing but apple is getting more and more strict every release on what it allows through security

[ayush-shta]

Do we need to go through the app signing steps mentioned here, even if we do not want to distribute through app store? or is there a simpler way for this?

You can try packaging it with ditto into a zip for sharing but apple is getting more and more strict every release on what it allows through security

I'm not sure I follow you.

I'm having the same issue as @zuno90 where the .app file for mac does not open but running executable file inside Contents/MacOS works properly. However according to this doc from apple, you should be able to distribute to the user without notarization.

What I am not sure about is if there is a minimum step I need to perform for my mac app (.app file) to open in my machine after I build it.

Please let me know if I'm missing anything.

[leaanthony]

Is this failing to open on your own machine? What does wails doctor output?

[ayush-shta]

Is this failing to open on your own machine? What does wails doctor output?

@leaanthony , Yes. For context, I've build the app on my machine using the command wails build.

Here is the output from wails doctor

# Wails
Version | v2.7.1

# System
┌─────────────────────────┐
| OS           | MacOS    |
| Version      | 13.2     |
| ID           | 22D49    |
| Go Version   | go1.21.6 |
| Platform     | darwin   |
| Architecture | amd64    |
| CPU          | Unknown  |
| GPU          | Unknown  |
| Memory       | Unknown  |
└─────────────────────────┘

# Dependencies
┌─────────────────────────────────────────────────────────────────────────┐
| Dependency                | Package Name | Status    | Version          |
| Xcode command line tools  | N/A          | Installed | 2396             |
| Nodejs                    | N/A          | Installed | 20.11.0          |
| npm                       | N/A          | Installed | 10.2.4           |
| *Xcode                    | N/A          | Installed | 14.3.1 (14E300c) |
| *upx                      | N/A          | Available |                  |
| *nsis                     | N/A          | Available |                  |
└──────────────────────── * - Optional Dependency ────────────────────────┘

# Diagnosis
Optional package(s) installation details:
  - upx : Available at https://upx.github.io/
  - nsis : More info at https://wails.io/docs/guides/windows-installer/

 SUCCESS  Your system is ready for Wails development!

Also one another note, I tried to do a build in a new project, and it works as expected there. However I am having this issue in one of the old project and I'm not sure how to debug this.

[leaanthony]

Looks like this isn't directly a Wails bug. If you have more details and can show hoot reproduce, feel free to open this again 👍