Permissions/ACL Errors in Built Tauri App

[QuirkyQueryQuester]

I've developed a Tauri application using several plugins. While the app functions correctly when run with npm run tauri dev, I encounter permission/ACL errors after building it with npm run tauri build.

Current Behavior

1. npm run tauri dev: The application runs without any errors, and all plugins work as expected.

2. npm run tauri build: The built application produces the following errors:

These errors prevent the plugins from functioning, which significantly impacts the application's core functionality.

Expected Behavior

The built application should run without permission/ACL errors, and all plugins should function correctly, mirroring the behavior observed in the development environment.

Can anyone help me with this/had similar problems?

Environment

• OS: macOS 15.0 - Sequoia
• Tauri version: 2.0.0-rc
• Node.js version: v21.7.1
• npm version: 10.5.0

Here's my cargo.toml + the default.json for the plugin permissions:

[package]
name = "app"
version = "0.1.0"
description = "A Tauri App"
authors = ["you"]
license = ""
repository = ""
edition = "2021"
rust-version = "1.70"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[lib]
name = "main_lib"
crate-type = ["lib", "cdylib", "staticlib"]


[build-dependencies]
tauri-build = { version = "2.0.0-rc", features = [] }

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tauri = { version = "2.0.0-rc", features = ["devtools"] }
tauri-plugin-fs = "2.0.0-rc"
#tauri-plugin-http = { version = "2.0.0-rc", features = [] }
tauri-plugin-os = "2.0.0-rc"
tauri-plugin-shell = { version = "2.0.0-rc", features = [] }
dirs = "5.0.1"
pnet = "0.35.0"
sha2 = "0.10.8"
rusqlite = {version = "0.32.1", features = ["bundled-sqlcipher", "serde_json"] }

[profile.release.package.wry]
debug = true
debug-assertions = true

{
  "$schema": "../gen/schemas/macOS-schema.json",
  "identifier": "default",
  "description": "enables the default permissions",
  "windows": [
    "main"
  ],
  "permissions": [
    "core:app:default",
    "core:path:allow-resolve",
    "core:path:allow-resolve-directory",
    "core:window:default",
    "core:webview:default",
    "core:resources:default",
    "core:image:default",
    "core:menu:default",
    "core:tray:default",
    "core:path:allow-resolve-directory",
    "os:allow-hostname",
    {
      "identifier": "fs:allow-copy-file",
      "allow": [
        "**"
      ]
    },
    {
      "identifier": "fs:allow-exists",
      "allow": [
        {
          "path": "**"
        }
      ]
    },
    {
      "identifier": "fs:allow-remove",
      "allow": [
        "**"
      ]
    }
  ],
  "platforms": [
    "macOS",
    "windows"
  ]
}

[FabianLars]

If it's not too much to ask, do you think you can try to reproduce it in a fresh create-tauri-app project and upload that for us to investigate?

[FabianLars]

That all looks good... I'm pretty much out of ideas. There's a mention of a https website in your screenshots, do you also load that in development or only in build mode?

[QuirkyQueryQuester]

In Developement Mode also the https calls work.
The errors occure only in production mode.

It's extremely weird because as you can see in the devtools picture there are commands which randomely never finish.
When this happens my application is kinda "freezed" and I don't even get the ACL errors.

If you want I can provide you (later that day) my rust code - Maybe I did something which breaks my application.

I don't think that the frontend build is the problem.

[imfunniee]

While working with tauri_plugin_localhost, I encountered an issue similar to OP's issue. Worked fine (allow-maximize, allow-minimize etc.) in dev mode but not in production. Resolved this by adding the localhost to the remote urls... idk if this is of much help

also removed devtools from.. idk which one fixed it

tauri = { version = "2.0.0-rc.7", features = ['tray-icon', "devtools"] }

"remote": {
  "urls": ["http://localhost:3001/*"]
}

[QuirkyQueryQuester]

Thank's for your reply! Unfortunately the advice with the remote urls also don't work.

I found something interesting: When I create a build of my frontend project there are several .js files which are generated.

When you take a look at the error in my console you see that the file in my console has a different identifier than the files. in my build folder.

As you can see the file in the build folder has the name "main.806fd088....." while the file in the console error is "main.1b59cf....."

How is this possible? On every tauri build there will be a new frontend build generated

Also nice to know: The error Error: Command get_hostname not found didn't even exist anymore in my code - I removed it a few builds ago.

Is there a directory which is not in my project where the tauri build files are stored and reused?

Removing the directories dist, target, cargo.lock also don't work.

[FabianLars]

Is there a directory which is not in my project where the tauri build files are stored and reused?

No, only your dist dir and target (though target only stores the exe, not the plain dist files)