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
[bug] Error in generating wix installer on Windows #4791
Comments
Can you run it with the verbose flag enabled, like |
Well, the verbose logs definitely tell a story:
Might it be because the githubrunner user is not an admin? |
@miniBill I've seen this issue on a GitLab runner, and the issue was that I had some large secrets being dumped to the runner, so I had to delete some unused environment variables. I found this SO answer that helped me: https://stackoverflow.com/questions/1064580/wix-3-0-throws-error-217-while-being-executed-by-continuous-integration/9722623#9722623 |
The issue is that the GH secrets are needed for the previous steps of the tauri build. Could tauri itself clean them before calling wix? |
@miniBill You can just clear the larger env vars before running tauri build, like: $Env:APPLE_CERTIFICATE = ''
$Env:SOME_HUGE_VAR = ''
tauri build --verbose (that syntax is for powershell, if the runner uses a different shell you can just use |
We could clear the env when running wix, though i'm not sure if that would break any feature in case wix relies on env vars. Worth trying. |
Pushed a fix if you want to test it. - uses: tauri-apps/tauri-action@v0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tauriScript: cargo tauri EDIT: gotta fix an issue first :( |
I get the same error, unfortunately. The relevant part of the GitHub action: - name: Install app dependencies and build web
run: |
python -m pip install --upgrade pip
pip install -r requirements.txt
yarn
make Makefile.images
make -j dist
cargo install --git https://github.com/tauri-apps/tauri --branch fix/wix-clear-env tauri-cli --force
- name: "Build and release the app (PR)"
if: github.event_name == 'pull_request'
uses: tauri-apps/tauri-action@v0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
TAURI_PRIVATE_KEY: ${{ secrets.TAURI_PRIVATE_KEY }}
TAURI_KEY_PASSWORD: ${{ secrets.TAURI_KEY_PASSWORD }}
with:
args: --verbose
tagName: pr-${{ github.head_ref }}
releaseName: "[XXX] - PR ${{ github.head_ref }}"
releaseBody: "See the assets to download this version and install."
releaseDraft: true
prerelease: true
configPath: src-tauri/tauri.conf.release.json
tauriScript: cargo tauri |
@miniBill that's sad :( only other thing i could do is allow skipping that ICE validation from WiX. |
@miniBill can you try again, but this time with the |
@lucasfernog only With
How can I make sure that the action is using the correct tauri CLI from the branch? |
@miniBill can you share the build logs? |
@lucasfernog https://dpaste.com/C63LWSCXC |
@miniBill the |
i am facing the same issue, i am not trying to build in CI/CD but on local machine, i am getting the error similar to this. relevent section of verbose is below,
light.exe : error LGHT0217 : Error executing ICE action 'ICE01'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.". i am new to tauri, and not able to figure out what the issue is. any help is appreciated. |
@vedaprakashms can you try my fix?
|
Describe the bug
I've used the
tauri-apps/tauri-action@v0
to automatically build the installer, but I get this error:Reproduction
Use
tauri-apps/tauri-action@v0
on a self-hosted runnerExpected behavior
The release gets correctly created
Platform and versions
@tauri-apps/cli 1.0.3
@tauri-apps/api 1.0.2
tauri 1.0.5
tauri-build 1.0.4
Stack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: