PluginInitialization("shell", "unknown field `allow`, expected `open`") | Tauri Apps | Page 1

twilit bear Mar 17, 2024, 3:43 PM

#

Hi! I'm on the latest beta and after following the doc to create a new command, I get this error. Any idea to fix this? Thanks :D

#

I tried following this https://github.com/tauri-apps/plugins-workspace/blob/53c0e898608b2fe96d20e417905674ca41d8a089/examples/api/src-tauri/capabilities/base.json#L33-L42 but still get the same result, error.
This is my attempt, maybe my JSON is wrong..?

  "plugins": {
    "shell": {
      "identifier": "shell:allow-execute",
      "allow": [
        {
          "name": "legendary-auth",
          "cmd": "legendary",
          "args": [
            "auth"
          ]
        }
      ]
    }
  }```

```ts
import { Command } from "@tauri-apps/plugin-shell";

Command.create('legendary-auth', 'auth').execute()```

GitHub

plugins-workspace/examples/api/src-tauri/capabilities/base.json at ...

All of the official Tauri plugins in one place! Contribute to tauri-apps/plugins-workspace development by creating an account on GitHub.

sturdy spade Mar 17, 2024, 11:28 PM

#

That syntax looks like you're editing src-tauri/tauri.conf.json rather than src-tauri/capabilities/default.json (might be called migrated.json).

twilit bear Mar 18, 2024, 12:39 AM

#

sturdy spade That syntax looks like you're editing `src-tauri/tauri.conf.json` rather than `s...

Oh yeah, I'm editing src-tauri/tauri.conf.json. Has the file changed since? Where can I find some docs for the new file you're talking about?

sturdy spade Mar 18, 2024, 12:43 AM

#

https://beta.tauri.app/references/v2/acl/

#

It's also the file you linked 😅

#

You can call the capabilities files whatever you like, the default files are just called default and migrated depending on what generated them, create-tauri-app and tauri migrate respectively.

twilit bear Mar 18, 2024, 12:45 AM

#

Oh, I didn't saw, I thought it was the same file as v1 :')

#

It works like a charm, thank you so much!

#

And where would I see all the options, for example for the fs?

sturdy spade Mar 18, 2024, 1:15 AM

#

You can point the $schema field at src-tauri/gen/schemas/acl-manifest.json or read the file manually. It's intended for editors to provide auto-complete so it's a little bit hard to read without formatting it.

#

My mistake. It was plural: acl-manifests.json.

twilit bear Mar 18, 2024, 1:24 AM

#

Saw that yup. By the way in the link I provided, it pointed to desktop-schema.json. Is it normal or a bug?

sturdy spade Mar 18, 2024, 1:24 AM

#

That's normal.

twilit bear Mar 18, 2024, 1:25 AM

#

sturdy spade You can point the `$schema` field at `src-tauri/gen/schemas/acl-manifest.json` o...

Doesn't seem to privode autocomplete on my end, weird. I'm trying to see all the identifiers for fs but can't even find one if I ctrl+f in acl-manifests.json

sturdy spade Mar 18, 2024, 1:26 AM

#

Hm... seems it's in a different format than I remember. Maybe it was the desktop-schema.json file instead.

twilit bear Mar 18, 2024, 1:28 AM

#

Hmmm

#

Expected type "string"

#

^ with desktop-schema.json. Doesn't seem to work alot

sturdy spade Mar 18, 2024, 1:32 AM

#

Hm... "permissions" should be on the root.

#

You only need to specify it once.

twilit bear Mar 18, 2024, 1:33 AM

#

Oh, see it already there, I'm blind

twilit bear Mar 18, 2024, 2:05 AM

#

{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "default",
  "description": "Capability for the main window",
  "windows": ["main"],
  "permissions": [
    "event:default",
    "window:default",
    "app:default",
    "image:default",
    "resources:default",
    "menu:default",
    "tray:default",
    {
      "identifier": "shell:allow-execute",
      "allow": [
        {
          "name": "legendary-auth",
          "cmd": "legendary",
          "args": [
            "auth"
          ]
        }
      ]
    },
    "path:allow-join"
  ]
}``` it only wants to autocomplete the shell identifier, why? It's frustrating me so much haha

sturdy spade Mar 18, 2024, 2:06 AM

#

What editor are you using?

twilit bear Mar 18, 2024, 2:06 AM

#

VSCode

sturdy spade Mar 18, 2024, 2:06 AM

#

It generates the schema files every build so you should have more than shell in there.

twilit bear Mar 18, 2024, 2:06 AM

#

Wherever I try to add another thing, for the allow path, it tries and wants to autocomplete for the shell

sturdy spade Mar 18, 2024, 2:07 AM

#

Oh, that's a side-effect of the way the schema is handled.

twilit bear Mar 18, 2024, 2:07 AM

#

And in the examples I can see fs used, and I can only see path

sturdy spade Mar 18, 2024, 2:08 AM

#

What permission were you trying to add?

twilit bear Mar 18, 2024, 2:09 AM

#

A permission to allow me to edit the .zshrc file in the home directory for example

sturdy spade Mar 18, 2024, 2:09 AM

#

You also have to reload VSCode to get it to pick up the schema again.

#

I find that really annoying too 😅

twilit bear Mar 18, 2024, 2:10 AM

#

Let me try by reloading it

sturdy spade Mar 18, 2024, 2:10 AM

#

There's even a JSON: Clear Schema Cache command but it doesn't seem to make a difference.

twilit bear Mar 18, 2024, 2:10 AM

#

Nothing changed. Also, in my shell identifier it throws me a warning because there is no command and sidecar property

sturdy spade Mar 18, 2024, 2:11 AM

#

Have you run tauri dev or tauri build since you added the plugins?

twilit bear Mar 18, 2024, 2:12 AM

#

Well, just did but nothing changed

sturdy spade Mar 18, 2024, 2:18 AM

#

Seems regenerating the schemas has broken for some reason. It doesn't overwrite the existing files.

#

Should be fine to delete gen/schemas so it get generated next build.

#

I'll look into the cause when I have a moment in the evening.

twilit bear Mar 18, 2024, 2:21 AM

#

sturdy spade Should be fine to delete `gen/schemas` so it get generated next build.

Deleted the schemas, got them again but same problem unfortunately

#

I found my first bug 🥳

sturdy spade Mar 18, 2024, 2:22 AM

#

Can you upload a minimum reproduction to GitHub?

#

If you've only got the output of create-tauri-app so far, that works too.

twilit bear Mar 18, 2024, 2:24 AM

#

I just got the basic file from bun create tauri-app@latest -- --beta, nothing changed. How would I get a minimum reproduction..? ^^'

sturdy spade Mar 18, 2024, 2:25 AM

#

Did you also run tauri add fs?

twilit bear Mar 18, 2024, 2:25 AM

#

.....................

#

Wait a few seconds ^^'

sturdy spade Mar 18, 2024, 2:26 AM

#

That's just a shortcut to automatically add the plugin. You could also have manually added it to Cargo.toml, package.json, and lib.rs.

#

More detailed instructions can be found in the README or on the website: https://beta.tauri.app/features/file-system/.

twilit bear Mar 18, 2024, 2:29 AM

#

I'm just a fool who tried to do his stuff in the wrong order

#

Guess who has autocomplete for fs now

sturdy spade Mar 18, 2024, 2:29 AM

#

That's good. I thought something had gone wrong in the ACL which is code I haven't looked at yet.

twilit bear Mar 18, 2024, 2:30 AM

#

It's usual on my end when I have a problem haha, don't worry

#

So whenever I want to add any identifier, I need to add it to Tauri first right?

sturdy spade Mar 18, 2024, 2:31 AM

#

Only if it's a plugin.

#

Most stuff is a plugin though.

#

The list of stuff that's not a plugin can be found at https://beta.tauri.app/references/v2/js/core/.

twilit bear Mar 18, 2024, 4:05 AM

#

Got it. One last thing, my command works but why doesn't it accept my shell:allow-execute? It throws me a warning there, it wants any fs identifier

{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "default",
  "description": "Capability for the main window",
  "windows": ["main"],
  "permissions": [
    "event:default",
    "window:default",
    "app:default",
    "image:default",
    "resources:default",
    "menu:default",
    "tray:default",
    "fs:default",
    {
      "identifier": "shell:allow-execute",
      "allow": [
        {
          "name": "legendary-auth",
          "cmd": "legendary",
          "args": [
            "auth"
          ]
        }
      ]
    }
  ]
}```

sturdy spade Mar 18, 2024, 5:21 AM

#

Not sure what causes that behaviour. It doesn't seem to cause any compile errors so it's probably just a problem with the schema file.

twilit bear Mar 18, 2024, 5:28 AM

#

Maybe I should try to delete it again? Or wait for a future update

sturdy spade Mar 18, 2024, 5:29 AM

#

Future update, I tried deleting it and it didn't make a difference.

twilit bear Mar 18, 2024, 5:30 AM

#

And quick question, is the upgrade command the same as the install command for beta?

sturdy spade Mar 18, 2024, 5:32 AM

#

Upgrade command?

#

You mean with pnpm and Yarn?

#

I think they behave the same when you specify a package and version.

twilit bear Mar 18, 2024, 5:33 AM

#

sturdy spade You mean with pnpm and Yarn?

Bun 👀

sturdy spade Mar 18, 2024, 5:34 AM

#

I don't see a bun upgrade in their docs.

twilit bear Mar 18, 2024, 5:35 AM

#

So still bun create tauri-app@latest -- --beta?

sturdy spade Mar 18, 2024, 5:35 AM

#

I don't know if the extra -- is needed for Bun but yes, that should do it.

#PluginInitialization("shell", "unknown field `allow`, expected `open`")