Accessing resources in an iOS bundle (beta)

[stijnfrishert]

Hello everyone,

I'm building a mobile app for iOS, and I'd like to package some resource files along with the bundle. I want to read the (audio) files in within Rust, but send their relative paths over from the frontend.

All these files live in ../../../assets (or subfolders therein), relative to tauri.config.json.

I've set up ["bundle"]["resources"] = ["../../../assets"] in tauri.config.json, but this doesn't seem to be enough. The v1 guide mentions an allowList, but I can't seem to find anything about that in the sparse v2 docs.

I'm also not sure whether specifying it like this will copy the assets folder, or it's children, and whether it'll keep the internal folder structure.

In other words: how do I put external files in my bundle, so that I can send the path through a command and load them from my rust code with the v2 beta?

---

Just found out I can view the web console when right clicking the window, and when trying to access the file with resolveResource() it does give me a 400 bad request error.

Unhandled Promise Rejection: path.resolve_directory not allowed. Permissions associated with this command: path:allow-resolve-directory, path:default

---

Found a v2 guide about permissions, but I'm still a bit baffled how I'm supposed to tie this all together 😅

[FabianLars]

Found a v2 guide about permissions, but I'm still a bit baffled how I'm supposed to tie this all together 😅

There should be a json file in src-tauri/capabilities/ already. Open that and you should see a permissions array. Simply add the missing permissions to that and the error should go away (not sure if it will work then, can't remember whether resources are implemented on mobile).

[stijnfrishert]

@FabianLars I managed to silence the warnings by adding this capabilities/main.json

{
  "identifier": "main-capability",
  "description": "Capability for the main window",
  "windows": ["main"],
  "permissions": [
    "path:default",
    {
      "identifier": "path:allow-resolve-directory",
      "allow": [{ "path": "$RESOURCE" }]
    }
  ]
}

However, when I log the path that comes out of resolveResource('sounds/correct.wav'), I get /Users/<name>/Development/mimi2/target/x86_64-apple-darwin/debug/sounds/correct.wav. When I check the debug build folder, none of the assets seem to have been copied over/linked. Is that something I should do manually?

I'm building an iOS app here, but testing on macOS.

Any pointers in the right direction are appreciated :)

[lyager]

@stijnfrishert Did you manage to get further on this? I'm trying to add binary files to my IOS app, but when calling resourceDir() from typescript, I'm just getting unknown path. I have a capabilities file in src-tauri/capabilities/ but it was generated some time ago when I started out.

[lyager]

AFAIKS these are not implemented for IOS yet?

[stijnfrishert]

@lyager Not yet. I ran into other issues building Tauri locally. Those have been resolved, next I need to finish off #9992, and after that I hope to take a look at assets. I need both the aforementioned PR and assets for my mobile app, so 🤞

[lyager]

@stijnfrishert Thanks for the reply - I created this #10070 and I have a workaround in my local Tauri repo.

[stijnfrishert]

Ok, took me a while to figure out what was wrong here (needed frameworks for iOS first).

Long stor short, the issue here seems to be that the binary resource system simply hasn't been implemented for iOS yet.

There's more people running into that though, so I suppose feature parity on this front with regular macOS builds is something people expect to work.

Is this something that's on the roadmap for the initial v2 release?

[FabianLars]

Is this something that's on the roadmap for the initial v2 release?

No, 2.0.0 is pretty much in feature freeze right now. I expect this to be high-ish in prio for one of the first 2.x minor releases though.