v2.9.2 can't build runnable .app on macOS when 'name' and 'outputfilename' are different

[tramamte]

Description

from v2.9.2, on macOS, wails uses 'outputfilename' value to make a binary file. But still the CFBundleExecutable is set to {{.Name}} in the Info.plist. So, when 'name' and 'outputfilename' are different, the .app cannot be executed.

The CFBundleExecutable should be set to 'outputfilename'. The 'buildassets', however, only exports 'Name' and 'Info'. https://github.com/wailsapp/wails/blob/master/v2/pkg/buildassets/buildassets.go#L109

[leaanthony]

Nice catch. Are you able to raise a PR for this?

[nickisworking]

@leaanthony Hello, I'm a team member of @tramamte and I would like to raise a PR for this issue.

It seems very clear, but I'll leave a few additional comments according to the contribution guide.

1. First of all, I have confirmed that the bug is reproducible in my environment as well.
   • If thname and outputfilename in wails.json are different, the app cannot be executed.

2. The result of wails doctor is as follows

[raguay]

I'm also having this issue. I can't use Modal File Manager anymore since I recompiled it using 2.9.2 and it will not run. It says the program is incomplete. Wails doctor shows the same as the person before me.

[raguay]

I was able to fix it as above. Make the program name and output name the same. Interesting.

[tramamte]

@raguay As I mentioned above, there is no issue, if the 'name' and 'outputfilename' are same. And because wails v2.9.1 ignored 'outputfilename', it also had no issue.

[nickisworking]

@raguay @tramamte

Yes. Plus, I have also figured out that It works well even if the case is different. e.g) test/Test 🤔🤔

[leaanthony]

I think this is something we should fix. Should be no need to manually keep these the same