Replies: 2 comments
-
If you're asking for signCommand then this was backported to v1 too.
That should be totally fine yes. Until very recently that was even an option in create-tauri-app and we only removed it to simplify the docs. How are you creating the webviews? In tauri.conf.json or in code? |
Beta Was this translation helpful? Give feedback.
-
Ah no, really? I've kept an eye on releases but I totally missed that. Cheers! I'll stick with v1 for now then and worry about upgrading later. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hello Tauri people,
I have a fairly complicated Tauri app I'm trying to migrate to v2 now it's in RC, because I need the Azure cloud signing stuff.
I ran the
migrate
command and it helped a little, but I've spent a lot of time fixing compiler issues to account for the many changes. Now that my app actually compiles, it launches with this:I've seen some other issues mentioning this error that have been closed, but I'm unsure of a fix personally. It's hard to make a minimal reproducible example because I think it's a product of the migration from v1, and if I make a new test v2 project using
tauri-create-app
, it builds and runs fine.One difference is that my app is not a lib, but still a bin project as generated by v1, and I haven't made any of the other changes to support targeting a mobile platform. I'm not planning on ever targeting mobile so I'm assuming that's fine though.
Is there anything obvious I'm missing or should be looking for? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions