Replies: 3 comments 3 replies
-
Ok, I dig in documentation and code, and found out some things I was missing. So, now I'm at that point:
This way, app starts but still I have no permission to use my plugin.
This shows me a build error, with that output:
In this long output I can see that my plugin permissions exist, under name "cy3:allow-translate" and "cy3:deny-translate". Then, I try adding my capabilities to file "builtin.json", like that:
This way, I get a build error:
I tried to dig in tauri_build code, and from what I'm understanding the only file that could cause this problem is actually the "builtin.json", but I'm not figuring out why that file is failing in parsing... there is no syntax error, and capability "cy3:allow-translate" is existing. The only other json file that is involved (maybe?) in this process is in crate "cy3" /permissions/schemas/schema.json, but that's autogenerated and looks like a "PermissionFile" and not a "CapabilityFile"... Any clue? |
Beta Was this translation helpful? Give feedback.
-
Ok, I dig even more, and found out that parsing error happens because of Identifier failing to be parsed I'll open an issue about that, because I see that in identifier.rs many failure cases are possible, but error message popping out is not helpful, BTW, is there any reason why a number cannot be in an identifier? why not traditional "alpha" + many "alpha_or_digit" pattern for identifier? Thanks!! |
Beta Was this translation helpful? Give feedback.
-
Ok, thanks :) At end I solved by changing the plugin name, but I don't understand why it works :) This puzzles me :) anyway :) now works!! |
Beta Was this translation helpful? Give feedback.
-
Hi everybody!
I've updated tauri from 2.0.0-alpha.21 to 2.0.0-beta.2, and I figured out that ACL is now denying my app to work :)
I've added capabilities file (in src-tauri/capabilities) to allow all built-in plugins, that solved part of issues (many errors about mouse movement) but I cannot figure out how to allow my own plugin to work.. it worked before, now all it's commands are denied in my TypeScript part with errors like "<my_plugin_name>.<my_plugin_command> not allowed. Plugin did not define its manifest"
Let's say my plugin is called "doggy" and has a "bark" command, how should I allow my main window (or even better any window) to interact with that command?
Thanks!!
Beta Was this translation helpful? Give feedback.
All reactions