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

error obtaining VCS status: exit status 128 Use -buildvcs=false to disable VCS stamping. Unable to complete effective action #3340

Open
bambuo opened this issue Mar 25, 2024 · 3 comments
Labels
Bug Something isn't working

Comments

@bambuo
Copy link

bambuo commented Mar 25, 2024

Description

I was unable to complete the target build according to the prompted parameters.

Here is my output

> wails dev   
Wails CLI v2.8.0

Executing: go mod tidy
  • Generating bindings: 
  ERROR   
          error obtaining VCS status: exit status 128
                Use -buildvcs=false to disable VCS stamping.

          exit status 1
 ♥   If Wails is useful to you or your company, please consider sponsoring the project:
https://github.com/sponsors/leaanthony

To Reproduce

  1. go install github.com/wailsapp/wails/v2/cmd/wails@latest
  2. wails dev

Expected behaviour

Completes the desired goal of the command normally, or prompts for the validity of the parameters

Screenshots

No response

Attempted Fixes

No response

System Details

> wails doctor   


          Wails Doctor



# Wails
Version | v2.8.0

# System
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
| OS           | Windows 10 Pro                                                                                   |
| Version      | 2009 (Build: 19045)                                                                              |
| ID           | 22H2                                                                                             |
| Go Version   | go1.22.1                                                                                         |
| Platform     | windows                                                                                          |
| Architecture | amd64                                                                                            |
| CPU          | 12th Gen Intel(R) Core(TM) i5-12400                                                              |
| GPU 1        | OrayIddDriver Device (Shanghai Best Oray Information Technology Co., Ltd.) - Driver: 17.1.58.818 |
| GPU 2        | Intel(R) UHD Graphics 730 (Intel Corporation) - Driver: 31.0.101.4255                            |
| Memory       | 16GB                                                                                             |
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

# Dependencies
┌───────────────────────────────────────────────────────┐
| Dependency | Package Name | Status    | Version       |
| WebView2   | N/A          | Installed | 122.0.2365.92 |
| Nodejs     | N/A          | Installed | 20.11.0       |
| npm        | N/A          | Installed | 10.2.4        |
| *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!

 ♥   If Wails is useful to you or your company, please consider sponsoring the project:
https://github.com/sponsors/leaanthony

Additional context

No response

@bambuo bambuo added the Bug Something isn't working label Mar 25, 2024
@bambuo
Copy link
Author

bambuo commented Mar 25, 2024

Found a detail that compiles properly if the project is placed in non-mobile storage

@leaanthony
Copy link
Member

Thanks for opening this. This sounds more like a Go issue?

@Flussen
Copy link

Flussen commented Mar 27, 2024

The same thing happened to me, but I simply checked in visual studio code, with the github pull request extension, and it had not connected properly to the repository, I reconnected and it worked again

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

3 participants