Unity Cloud Build deletes symbolic links in the final zipped app, resulting in damaged builds

Hello there,

I build my game as a MacOS app via Unity Cloud Build. In order to run some specifics features of my games, I need to include a "Framework Bundle" (a package following Apple standards).

As described in Apple documentation, Framework Bundles are folders that have a specific structure and which contain symbolic links :

Code (Folder Structure):

1. MyFramework.framework/
2.     MyFramework  -> Versions/Current/MyFramework
3.     Resources    -> Versions/Current/Resources
4.     Versions/
5.         A/
6.             MyFramework
7.             Resources/
8.                 English.lproj/
9.                     InfoPlist.strings
10.                 Info.plist
11.         Current  -> A

For example, "Resources" points to "Versions/Current/Resources".

When the Unity Cloud Build's build agent processes the build, symbolic links are still present in the build directory (I checked that using logs on UCB). The problem is that, once the build completes, the sym links are completely destroyed in the .zip file downloadable from Unity Cloud Build. The way UCB zips the applications seem not to accept sym links, which result in providing damaged builds that cannot be opened on Mac.

Looks like a bug on UCB. Did someone have the same issue?

 

Yes, I've got the same issue here.. Build runs successfully and also completes notarization without issues, but the downloaded build doesn't work ("damaged, move to trash" message)

 

Thanks for your suggestion @rajivrao, I have already opened a ticket a month ago to raise this issue.
Even if it looks like the issue is acknowledged, it's still not fixed nor in the process of being fixed. Here is the last answer I received from the support:

Unfortunately, I've not seen any further investigation from the dev team on this issue yet, but the task is still open with the team. I'll continue to keep an eye on it, but feel free to poke me again any time as well.​

I have sent a lot of details about the issue and also allowed the team to build my project to reproduce the issue.

Maybe you could have a look on it and/or poke the dev team to figure out whether they will be able to tackle this ticket?
The ticket number is: 1052086 (https://support.unity.com/hc/en-us/requests/1052086)

Thanks for your help

@Nith666 if you want I can add you in cc of the support request in order for you to be informed of its resolution. Give me your e-mail in DM if it's the case.