Path resolving issue

[TheTharin]

Report

Hello! I'm fairly new to Flutter and Rust ecosystem. I'm writing my app and I have problems with accessing files through Path::new() in Rust. Tests for my code run okay, but the actual code panics with No such file or directory from a library I pass my Path to. I started digging with env::current_dir().unwrap() and that's what I found:

1. when I run specs with cargo test, everything is fine and current_dir is "/Users/me/work/my_app/native/hub"
2. when I run the app from within VSCode, current_dir returns "/Users/me/Library/Containers/com.example.myApp/Data" and I can't seem to find a way to navigate into native/hub from there.

Would you be so kind to give me an advice on that?

System Information

OS X Ventura 13.4
rustc 1.77.2 (25ef9e3d8 2024-04-09)
Flutter (Channel stable, 3.19.6, on macOS 13.4 22F66 darwin-arm64, locale en-GB)

[temeddix]

Hello TheTharin :)

This is a very common issue related to macOS file access permission. By default, Flutter apps on macOS don't have access to files on your disk. To resolve this issue, you can modify some app config files.

macos\Runner\DebugProfile.entitlements:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.security.app-sandbox</key>
	<false/>
	<key>com.apple.security.cs.allow-jit</key>
	<true/>
	<key>com.apple.security.network.server</key>
	<true/>
</dict>
</plist>
'

macos\Runner\Release.entitlements:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.security.app-sandbox</key>
	<false/>
</dict>
</plist>

More information is written here:

• https://stackoverflow.com/questions/67128763/flutter-macos-access-to-files

If the problem persists, please let me know!

[TheTharin]

Thanks, that solved it!
Probably a good idea to pin it in FAQ section, as it looks like every MacOS user would be having this issue by default.
Have a great day :)