So I’m working on a reusable Unity library that exports as a .unitypackage and can be brought into a new or existing Unity project. One of the files in this library is a MacOS dylib module (with a .bundle extension although it isn’t a bundle that can be opened). It’s a third-party library so I can’t change the way it’s built.
Interestingly, I am able to bring it into the library project just fine. However, when I go to export it along with the other files in the project (i.e. Assets->Export Package…), I can’t select the dylib. I’m guessing it has to do with this file being a container format but I’m not sure why Unity can’t export this file into a .unitypackage.
I recently started using Unity 2021 on Mac Silicon and running into this problem. My .bundle will not export, it is checked in the export window but, when I go to import the package it isn’t included.
I have a CI process that has been reliably building a .unitypackage from a project for several years. The project includes a Plugins folder which includes native plugins for Windows, iOS, Android, and mac OS. Just recently, in spite of the mac .bundle being in the Assets plugins folder, it is no longer being packaged by the call to AssetDatabase.ExportPackage.
This change coincides with our update from Unity 2021.3.2f1 to 2021.3.25f1. I have also tested with 2021.3.27f1 and I am getting the same result.
The bundle is correctly code-signed and has a valid bundle ID.
If I manually create the package from inside the Unity Editor, just like the previous poster, I can select the plugin.bundle file in the listing, but when I examine the unitypackage created, I can see that only an entry for the top level directory of the bundle has been created (as expected, without an asset, since its just a folder). The bundle contents (which are inside the top level folder of the bundle) are not present in the unitypackage.
I’m also affected by this bug. From the 2021.3.23 changelog:
In my case, this “fix” breaks Wwise audio middleware upgrades in the project.
Wwise has some .bundle plugin folders for Mac platform - including the main audio engine.
I’m unable to upgrade Wwise Unity Integration on Unity versions from 2021.3.23 onward.
@bleater
Thanks a lot! I added links to this forum thread and the bug fix which caused regression, so hopefully that all will help to draw the full picture for the team who work on the fix.
Is there any news to this? This is a major bug that appears to be underestimated by the unity developers. Exporting the unitypackage file is the last step in the release process of asset store developers. Unity will filter out the ios and mac native plugins without a warning causing us to upload broken builds to the asset store.
Edit: I just tested it. The unity asset store tools themselves do export correctly so only manual exports are hit by the bug
