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.

Sign up for GitHub

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

Jump to bottom

Linked Tauri version does not compile under OSX #92

Closed
thurn opened this issue May 15, 2024 · 5 comments
Closed

Linked Tauri version does not compile under OSX #92

thurn opened this issue May 15, 2024 · 5 comments

Comments

@thurn
Copy link

thurn commented May 15, 2024

Attempting to follow the example in the documentation, it forces the project to use Tauri 2 Beta 17. This version does not seem to compile under OSX/rustc 1.7.8:

    --> /Users/me/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.0.0-beta.17/src/webview/mod.rs:1078:5
     |
1077 |   pub fn url(&self) -> Url {
     |                        --- expected `url::Url` because of return type
1078 |     self.webview.dispatcher.url().unwrap()
     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Url`, found `String`

The newest beta of Tauri 2 (19) does compile correctly.
@reyamir
Copy link
Contributor

reyamir commented May 16, 2024

Look like tauri-specta is not compatible with latest tauri beta yet

@oscartbeaumont
Copy link
Member

This doesn't appear to be a bug in Tauri Specta but in fact a bug in Tauri so going to close this.

You should open an issue in the tauri-apps/tauri repository

@oscartbeaumont
Copy link
Member

oscartbeaumont commented May 16, 2024 •
edited
Loading

For context, this same issue is present in v19.

I don't know if you have any other features enabled but i've never observed it under v17 on macOS so maybe sharing a reproduction could help the Tauri team? Although upgrading to v19 does make the error occur on my end.

Also in the current Tauri Specta releases we hard lock the version to 2.0.0-beta.17 so despite you likely specifiying 19 in your own project v17 wins. I'm not sure if I should relax the restriction or not as Tauri are still making breaking changes so I suspect this is for the best as much as it's annoying.

@thurn
Copy link
Author

thurn commented May 18, 2024

@oscartbeaumont are you saying you do see this compile issue with tauri b19 and don't see it under b17? That's the opposite of me. It's pretty consistently reproducible for me with tauri-specta and beta17.

@oscartbeaumont
Copy link
Member

oscartbeaumont commented May 20, 2024 •
edited
Loading

I think I may have mistyped 18 not 19 when testing, sorry!

Just checked again and b19 is good to go so did a release.

@oscartbeaumont oscartbeaumont linked a pull request May 20, 2024 that will close this issue
fix: Update the tauri version to resolve tauri error #94
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Update the tauri version to resolve tauri error
3 participants
@thurn @oscartbeaumont @reyamir