pkgbuild on Tahoe fails to build packages if any directory name contains non-ascii characters

Question

Created 1w

Replies 3

Boosts 0

Participants 2

pkgbuild on Tahoe (26.3.1) fails to build packages if any directory name contains non-ascii characters.

pkgbuild is able to build successfully with the same source data on previous versions on macOS, so this is a regression and prevents us from build able to build our products on macOS 26.

Example that demonstrates the issue:

mkdir -p MyAppData/Taishōgoto
echo "Testing" >> MyAppData/Taishōgoto/Content.txt
pkgbuild --identifier com.example.MyAppData --install-location '/Library/Application Support/MyAppData' --root MyAppData myappdata.pkg

Error messages:

parent directory ./Taishōgoto does not exist
pkgbuild: error: Cannot write package to "myappdata.pkg". (The file “package.bom” couldn’t be saved in the folder “NSIRD_pkgbuild_52fPuN”.)

I have submitted this via Feedback Assistant (FB22312299).

I have not found a workaround. Tried copying pkgbuild from Sequoia but the problem persisted, probably because the buggy code is in PackageKit rather than the tool itself.

Answered by DTS Engineer in 881286022

I have submitted this via Feedback Assistant (FB22312299).

Thanks.

I’m not sure what’s going on here, but it’s clearly a regression and thus warrants a bug report.

Having said that, there’s a long-standing gotcha you need took out for. Using non-ASCII names for pure data should be fine, but you have to be careful when using non-ASCII names for files within a code-signed bundle. There’s a long-standing problem with that, as explained in this post.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

1w

Recommended

I have submitted this via Feedback Assistant (FB22312299).

Thanks.

I’m not sure what’s going on here, but it’s clearly a regression and thus warrants a bug report.

Having said that, there’s a long-standing gotcha you need took out for. Using non-ASCII names for pure data should be fine, but you have to be careful when using non-ASCII names for files within a code-signed bundle. There’s a long-standing problem with that, as explained in this post.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

nixx OP

1w

Thanks Quinn!

This is a pure data package, but your linked post was helpful and helped me identify a workaround - staging the package contents in an HFS volume (disk image) allows pkgbuild to succeed.

0

Answer 3

DTS Engineer OP

Apple

1w

staging the package contents in an HFS volume … allows pkgbuild to succeed

I’m glad that worked but… sheesh… it’s a bit of a worry. Hopefully we’ll get a fix to FB22312299 sooner rather than later.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0