Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

binary not work by fyne package on windows #1521

Closed
Nigh opened this issue Nov 11, 2020 · 5 comments
Closed

binary not work by fyne package on windows #1521

Nigh opened this issue Nov 11, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@Nigh
Copy link

Nigh commented Nov 11, 2020

Describe the bug:

Program 'test.exe' failed to run: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for 
more detailAt line:1 char:1
+ .\OProgX.exe
+ ~~~~~~~~~~~~.
At line:1 char:1
+ .\OProgX.exe
+ ~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

!! After using ResHacker to remove the Manifest resourse, it could run normally.

To Reproduce:

Steps to reproduce the behaviour:

  1. fyne package -os windows
  2. ./test.exe throw error
  3. use ResHacker to remove Manifest resourse.
  4. ./test.exe works fine

Device (please complete the following information):

  • OS: Win10
  • Version: 2004
  • Go version: 1.15.2 windows/amd64
  • Fyne version: 1.4
@andydotxyz
Copy link
Member

Is it possible to get more information as suggested in Please see the application event log or use the command-line sxstrace.exe tool for more detail?
It is likely an issue inside the manifest, hopefully the output has more.
We can't remove the manifest completely so unfortunately it's not a solution.

@andydotxyz andydotxyz added the bug Something isn't working label Nov 11, 2020
@tsoun
Copy link

tsoun commented Nov 11, 2020

I got the exact same issue. Upon deleting the Manifest, the *****.exe runs.

andydotxyz added a commit that referenced this issue Nov 11, 2020
The default package numbering did not match our default format
Fixes #1521
@andydotxyz
Copy link
Member

Apologies, this has been resolved on release/v1.4.x branch, and will be in the 1.4.1 release soon.

@cplasfwst
Copy link

Haha, I also encountered this problem, and then I solved it like this:
fyne package -os windows -appVersion 1.1.1

@andydotxyz
Copy link
Member

Thanks for providing this information, that is a great workaround.
The problem was that version numbering is optional on package, but the fallback number was not Windows compatible.
Adding -appVersion is perfect until 1.4.1 is out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants