#[v2] capabilities ignored in built app, but work when running dev

2 messages · Page 1 of 1 (latest)

zenith lance
#

I have a weird issue, when in the src-tauri/capabilities, I have my JSON, with all necessary permissions, and the window listed in windows.

When running / debugging the app with npm run tauri dev, all works fine. Commands all work, there are no permissions issues (and I know the permissions are read, because if I remove anything from there, the appropriate command will throw an error).

However, if I build the app with npm run tauri build, things are broken. Using the --debug options, I can see in the debug console, that seemingly the capabilities are ignored? I see a bunch of errors like:

Unhandled Promise Rejection: path.resolve_directory not allowed on window main, webview main, allowed windows: , allowed webviews: , referenced by

I tried explicitly referencing the capability identifier in tauri.conf.json, or even having it all inline the conf; tried to explicitly tell the build process to use this conf, to no avail. Using --verbose when building also gives no mention of anything related to permissions or capabilities.

Does anyone have any idea what could be wrong?

modest elk