Fabian-Lars
Fabian-Lars
Can someone upload a minimal reproduction (this means, reproduce the error in a new app created with create-tauri-app and upload that to github). Also, do you have a system proxy...
Ahhh, okay i understand. For CORS issues we generally recommend using tauri's [fetch](https://beta.tauri.app/references/v2/js/http/#fetch) instead of the browser's one which ignores CORS because it executes the requests on the Rust side....
Can you try again with the --verbose flag and see if it gives you a more helpful error message? iirc the cli/bundler don't handle extra binaries for universal targets yet...
Yes, it's the same issue. I'm honestly not quite sure how we should fix this, i think just documenting that a universal tauri app needs universal sidecars (via lipo) because...
i think it does, yes. But iirc at runtime it tries to run the sidecar for the actual arch that's running instead of looking for the universal one. (could also...
Can you try setting `$env:STATIC_VCRUNTIME="false"` before running tauri?
Hmm, what about `$env:RUSTFLAGS="-C target-feature=+crt-static"`?
Hmm, then i don't know either and i don't have a project that uses c++ code myself so i can't test it. I'd recommend to maybe reach out to the...
The issue should be the store plugin. Try running `cargo update` before `migrate`. If that doesn't work, try changing it's branch to v2 and run cargo update again. If that...
Oh, the app didn't load the full error message, apologies. I think the second error can also be fixed by upgrading the store first (or commenting it out while migrating)....