Closed codesoda closed 9 months ago
Just some updates
It looks like two issues need to be solved:
No such file:
lines, which are invalid symlinks in the framework itself. Maybe we can use xattr -crs
instead.@pewsheen I previously had no trouble with building, code-signing and notarizing builds with 1.4. I was thinking of making a fake xattr and dropping it into the build path so I can upgrade to Tauri 1.5 before Apple cuts off my use of atool for notarizing.
Might be worth trying xattr -crs
as you suggested, or use a find and pipe the results to xattr, e.g. find /path/to/base_directory -type f -exec xattr -c {} \;
Are you bundling Accelerate.framework with the app bundle? (/Users/me/projects/accelerate_test/src-tauri/target/release/bundle/macos/accelerate_test.app/Contents/Frameworks/Accelerate.framework
). I might be missing something, but why do you have to do that? Isn't that framework included with macOS?
Tip to anyone coming across this: Make sure that your version of xattr
supports the -r
option. My Python Poetry installation was overriding the system xattr
binary on my $PATH. Run which xattr
-- it should return /usr/bin/xattr
. If it returns something else, remove whatever it is from your $PATH and try again.
Describe the bug
Hi all, I have a Tauri macOS app that uses Apple's Accelerate.framework and CoreML.framework. I've recently upgraded from 1.4 to 1.5, and now the bundler is failing when running
xattr -cr myapp.app
to clear any attributes on the frameworks. This likely has some relation to the work done for #7690.Reproduction
xattr -rc myapp.app
command.Example repo can be found at https://github.com/codesoda/accelerate_bug.
Expected behavior
I would expect that the
xattr
command succeeds and the app bundle is then code-signed and passed to Apple to be notarized.Platform and versions
Stack trace
Additional context
No response