Create xar archive - Unknown Error

Question

Create xar archive - Unknown Error

sagecook opened this issue 2 years ago · 10 comments

I get an "Unknown Error" message when the packager (1.2.9) is creating the xar archive. This used to work a couple years back. I updated to the latest packager version (1.2.10) and it still gives the error. Also, I get this error both in the GUI and when running the packagesbuild command.
The OS is Catalina (10.15.7) and the payload is around 2.2 GB I would guess. BTW, I have plenty of disk space.
Any thoughts?

Answer 1 · 2023-02-21T20:53:45.000Z

What's the size of the biggest file in the payload?
Is Full Disk Access granted?

Answer 2 · 2023-02-21T21:01:31.000Z

There is a file in one of the Payload directories that is about 2.2 GB, probably the same size as it has been for several years. My user has full access to the file system where the package is being assembled. Obviously the temporary files are in /tmp/xxxxx where everyone has read/write access. Does that help? The frustrating thing is this used to work a couple years back. I am simply dusting this build off to release some fixes in our app. Thanks, Steve

On 2/21/23 3:53 PM, packagesdev wrote: What's the size of the biggest file in the payload? Is Full Disk Access granted? — Reply to this email directly, view it on GitHub <#133 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZ5XOSEIOGKXYCUV6YDQIDWYUTOHANCNFSM6AAAAAAVDP33WA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Stephen Cook 561.212.4846d ***@***.***

Answer 3 · 2023-02-22T13:28:12.000Z

There is a file in one of the Payload directories that is about 2.2 GB

This is OK.

My user has full access to the file system where the package is being assembled.
Obviously the temporary files are in /tmp/xxxxx where everyone has read/write access.

The limitation with Full Disk Access is not whether the user has full access or whether the files/directories have proper POSIX permissions. It's whether macOS grants access to these locations to some applications.

I would suggest to check first the System Preferences > Security & Privacy > Privacy and check the list of apps in Full Disk Access.

If the list does not include one of more items listed in this document (http://s.sudre.free.fr/Software/Packages/Q&A_7.html), this could be a possible origin of the issue.

Answer 4 · 2023-02-22T13:29:34.000Z

Good idea, I will check out that "full disk access" issue. Thanks, Streve

On 2/22/23 8:28 AM, packagesdev wrote: There is a file in one of the Payload directories that is about 2.2 GB This is OK. My user has full access to the file system where the package is being assembled. Obviously the temporary files are in /tmp/xxxxx where everyone has read/write access. The limitation with Full Disk Access is not whether the user has full access or whether the files/directories have proper POSIX permissions. It's whether macOS grants access to these locations to some applications. I would suggest to check first the System Preferences > Security & Privacy > Privacy and check the list of apps in Full Disk Access. If the list does not include one of more items listed in this document (http://s.sudre.free.fr/Software/Packages/Q&A_7.html <http://s.sudre.free.fr/Software/Packages/Q&A_7.html>), this could be a possible origin of the issue. — Reply to this email directly, view it on GitHub <#133 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZ5XOTA7ZVYK7JCPPDIJADWYYH7RANCNFSM6AAAAAAVDP33WA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Stephen Cook 561.212.4846d ***@***.***

Answer 5 · 2023-02-24T20:26:16.000Z

To follow up, I still have the problem. All the packaging apps, like packagesbuild, packagesutil, and Packages.app have Full Disk access.

Answer 6 · 2023-06-13T14:24:40.000Z

@sagecook did you ever find a solution to this? In my case, the package builds perfectly when I don't include my codesigning Developer ID Installer certificate. When I add the certificate, I get the same error. Full disk access granted on my end as well (using packages 1.2.11 and macOS 13.1 if it helps)

Answer 7 · 2023-06-13T19:49:46.000Z

I was able to get around this issue by building without the certificate, then manually signing the package with productsign

Answer 8 · 2023-10-27T01:15:26.000Z

Also getting this create xar archive unknown error. Only happens when I try to sign with my Developer ID Installer cert. Error occurs both when trying to sign with a G2 Sub-CA certificate and a Sub-CA.

Answer 9 · 2024-08-26T06:53:20.000Z

Got this too. Just delete 'build' folder in the same folder with pkgproj file. Deleteing this build folder need sudo auth, guess that's the problem.

Answer 10 · 2024-10-24T22:13:08.000Z

Same issue here, and unfortunately deleting the build folder did not do the trick for me. However removing the signed cert did allow the pkg to build with no errors.
Packages Version: 1.2.11
MacOS Version: 15.0.1