-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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] can't get the updater status #7128
Comments
Thanks for the report! Could you share a reproduction example we can take a look at? 🙏 |
the reproduction example completely follows https://tauri.app/zh-cn/v1/guides/distribution/updater. because need a public ip, so it's not easy to give a real example. Maybe we can analyze the logic of
|
Most of that should be reported by onUpdaterEvent, but only if you trigger it via Since it doesn't report anything for you, you can also try the rust counterpart as a sanity check: let app = tauri::Builder::default().build(tauri::generate_context!()).expect("error building tauri app");
app.run(|_app_handle, event| {
if let RunEvent::Updater(updater_event) = event {
dbg!(updater_event);
}
}); |
but, if i invoke |
For visibility, the testing we did on Discord so far showed that, if we use the server approach works, but the static json approach never resolves the |
Okay so i forgot that the events are limited if you enable the default dialog, because tauri still logs most of the events. I'm a bit unsure what the best approach is tbh:
Currently lean towards 1&2 but idk... |
@FabianLars just patch the current implementation for it to barely work. v2 will have a better implementation and straight-forward JS API. |
Describe the bug
how to get the status of emit('tauri://update')? onUpdaterEvent seems not work.
I found that the dialog will show when there is a new version available, but nothing happens when not.
Promise.reject
expectedPromise.reject
expectedReproduction
No response
Expected behavior
No response
Platform and versions
Stack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: