[AALookUp] 最快的系统级查词App和mdx词典|三指手势查词|全平台支持

bobzhang · 2026 年8 月 21 日 22:01

特别好的工具。我之前在windows上用的是STranslate，也希望能支持mdd格式的字典，本地查询总要比起问AI更快一些，这个工具完美解决了痛点。感谢楼主！

YYDWHY · 2026 年8 月 22 日 03:01

感谢分享！
请问从哪里选择不同的词典查看词条呢？

laizn · 2026 年8 月 22 日 03:03

往下滚动进度条直到出现第二个词典的解释。此处UI需要优化，下版本补一下。

laizn · 2026 年8 月 22 日 03:03

没有AI不快

laizn · 2026 年8 月 22 日 03:04

已复现，修复中。

laizn · 2026 年8 月 22 日 03:04

手上没有iPhone，我先按这个改一下看能不能解决。

webguest · 2026 年8 月 22 日 03:05

我这个是谷歌最傻那个AI写的，估计不行。然后我问一下ChatGPT吧。

Yes — your diagnosis is basically correct, but there is an important distinction: this is not really an iOS privacy permission problem. It is a Tauri ACL (Access Control List) configuration problem inside the app.

The error in your screenshot is extremely specific:

Command plugin:dialog|open not allowed by ACL

That means the JavaScript side of the Tauri app is trying to call the Tauri Dialog plugin’s open command, but the app’s security configuration has not granted that command permission.

1. The immediate problem: `dialog:allow-open`

Tauri v2 uses a capability/permission system. The Dialog plugin has a permission called:

dialog:allow-open

and Tauri’s documentation explicitly says this permission enables the open command. The Dialog plugin’s default permission set also includes allow-open. (Tauri)

So if this is your Tauri application/source code, the developer needs to add something like this to the appropriate capability file:

{
  "$schema": "../gen/schemas/mobile-schema.json",
  "identifier": "mobile",
  "description": "Mobile capabilities",
  "windows": ["main"],
  "platforms": ["iOS", "android"],
  "permissions": [
    "core:default",
    "dialog:allow-open"
  ]
}

Or, more simply, the capability could use:

"permissions": [
  "core:default",
  "dialog:default"
]

because dialog:default includes dialog:allow-open. (Tauri)

The exact location is normally something like:

src-tauri/
    capabilities/
        default.json
        mobile.json

The important thing is that the capability that applies to the iOS build must contain the Dialog permission. Tauri allows capabilities to be platform-specific, including "iOS" and "android". (Tauri)

2. But there is a second, potentially bigger problem

This is the part I think is particularly important for your AALookup application.

You said:

“It won’t pop up the window to choose a folder.”

If the application is actually trying to let you choose a folder, then fixing the ACL may not be sufficient.

The current Tauri Dialog plugin documentation explicitly says:

iOS does not support folder picker.

The same limitation exists on Android. (Tauri)

Tauri’s open() API has two relevant options:

open({
    directory: true
})

means choose a directory/folder.

Whereas:

open({
    directory: false,
    multiple: true
})

means choose one or multiple files. (Tauri)

So there are actually two separate issues to investigate:

Problem	What it means	Fix
`plugin:dialog\|open not allowed by ACL`	Tauri won’t even allow the app to invoke the file picker	Add `dialog:allow-open`
`directory: true` on iOS	Tauri Dialog doesn’t implement folder picking on iOS	Change the design to select files, or implement native iOS folder picking

3. For AALookup, selecting files is probably the right solution

Looking at your screenshot, the application says:

“Add an MDic file you already have.”

and:

“Download the four-file WordNet example…”

That makes me suspect the intended operation is actually selecting dictionary files, rather than selecting an arbitrary folder.

If so, the developer should probably implement something along the lines of:

const selected = await open({
    multiple: true,
    directory: false,
    pickerMode: "document",
    filters: [
        {
            name: "Dictionary files",
            extensions: ["mdx", "mdd"]
        }
    ]
});

The exact extensions would depend on what AALookup expects.

Tauri’s current API supports pickerMode: "document" specifically for mobile platforms such as iOS, and its iOS implementation returns file:// URIs for selected files. (GitHub)

That is a much better fit for iPhone/iPad than trying to expose a traditional desktop-style folder picker.

4. So if you’re just using the app, you cannot fix this in iOS Settings

This is the key point.

You don’t need to go to Settings → Privacy → Files or give AALookup some missing iOS permission.

The failure occurs before iOS gets a chance to display the picker.

Think of the sequence as:

You tap "Import dictionary files..."
             ↓
AALookup JavaScript calls
@tauri-apps/plugin-dialog → open()
             ↓
       Tauri ACL checks
             ↓
       ❌ permission denied
             ↓
      iOS file picker never opens

Your screenshot is essentially showing us the failure at the ACL check stage.

Tauri’s security model intentionally blocks plugin commands unless they have been granted through the application’s capabilities. (Tauri)

So if you’re just an end user, this is an AALookup bug that the developer needs to fix.

If you’re building AALookup yourself, then I would fix it in this order:

Fix #1 — ACL

Add:

"dialog:allow-open"

to the iOS capability.

Fix #2 — iOS picker mode

If the code currently has:

open({
    directory: true
})

change the design so iOS uses:

open({
    directory: false,
    multiple: true,
    pickerMode: "document"
})

if the goal is to import multiple dictionary files.

Fix #3 — If you genuinely need a folder

Then the standard Tauri Dialog plugin isn’t enough on iOS, because its folder picker isn’t supported there. The developer would need to implement an iOS-specific native document/folder picker or redesign the import workflow. (Tauri)

So your instinct was right about “permission,” but the precise diagnosis is: Tauri ACL permission, not iOS user permission. And there may additionally be an iOS folder-picker compatibility problem.

If you have the AALookup GitHub repository/source code, give me the link and I can look at the actual Tauri configuration and tell you exactly which file and which lines need to be changed.

YYDWHY · 2026 年8 月 22 日 03:07

期待新版本能自由选择想查看的词典。另外，已经在App Store上架了吗？

laizn · 2026 年8 月 22 日 03:09

核心功能需要Accessibility权限（用于直接读取文字）和Screen Record权限（用于OCR读游戏之类的），上架不了App Store。预计把功能阉割了以后能上。

laizn · 2026 年8 月 22 日 03:16

啊这也是我迷惑的一点：iOS本身没有文件系统，只能选择iCloud和照片，或在微信/网盘里面点击发送到外部应用。然后AALookup对此的设计是移动端通过拷贝的方式，放到本地文件里面。

不过现在我在Android上面实测了一下遇到几个问题：

移动端解析大词典的词典entry速度太慢了，我有一个大约3G的词典，解析一次要5秒以上，每次打开App都得重新解析。需要优化，优化又要额外占缓存。
移动端获取Accessibility的方法和桌面端差异太大，而且几乎不可能上App Store/Play商店。所以只有词典功能。
移动端的权限设计太复杂了，新手引导可能得多做几个版本。

laizn · 2026 年8 月 22 日 03:18

现在就是能自由选择的，我没想到直接平铺会造成那么大的误解，我会优化一下交互。

webguest · 2026 年8 月 22 日 03:21

就算只有词典功能，已经是非常好了。我觉得现在iOS上的词典都没有好用的。你这个，就算不提点译这个功能，界面让人觉得很惊艳。而且我装的时候，我看到了这个词典其实有那个分享查词功能，就是从别的软件也可以通过分享传到这个词典查词。我觉得这个功能就可以了，我就可以用这个词典在别的程序里面查词了。我先试一下自带词典，怎么样？我还没有试。