-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
xdg-open does not work in release artifacts produced by tauri-action #10617
xdg-open does not work in release artifacts produced by tauri-action #10617
Comments
Oh, sorry for the ping, this was originally going to be a comment on another issue and I forgot to remove the ping. |
Seems like there is some useful information in this comment. |
Any update? Or some kind of manual fix? |
I've also encountered a few issues with an app built using
But when I build app on my computer ( |
Yeah, seems like the same symptoms. @FabianLars any update? |
Hey @FabianLars
3 different, but related, functions of my application do not work when using the AppImage of my application produced by tauri-action in GitHub Actions, but work in AppImages produced locally for myself and 3 other users (as well as other methods of running the application, such as
cargo tauri dev
or other packaging formats). On my system, at least, the .RPM produced by tauri-action seems to work, and it is only the .AppImage that does not work. This issue is possibly related to #6172.My application OpenDeck loads plugins, which then communicate by sending JSON events back and forth over a websocket. One such event is
openUrl
, which a plugin can send to open a URL in the user's browser, which OpenDeck handles using Tauri's shell::open (see here).OpenDeck also has a button to open its config directory in its settings tab, which, on Linux, uses xdg-open using std's
Command
inside a Tauri command.Additionally, OpenDeck's "starter pack" plugin has a "Run Command" action, in which users can input a command to run on key down and key up. The starter pack plugin is also written in Rust, and uses std's
Command
to implement this action.For example, when pressing "open config directory" when using the AppImage from GitHub Actions, run with
./opendeck_2.0.0_amd64.AppImage
, this is printed to the terminal that the AppImage was run from:and then it seems to finally find and open w3m on my system in the terminal in the correct directory, whereas it should open in Nautilus for me, as it does when running OpenDeck from different methods.
Or, when using the Run Command action with
xdg-open https://example.com/
, this is the stdout of the executed command:OpenDeck is using the latest Tauri v1.7 and
uses: tauri-apps/tauri-action@v0
. I would appreciate some steps to follow to resolve this issue.The text was updated successfully, but these errors were encountered: