Search Issue Tracker


Fixed in 2020.3.48f1, 2021.3.23f1, 2022.2.12f1, 2023.1.0a25



Found in




Issue ID




[macOS] .meta files are created inside a loadable plugin folders when it's imported into the project



Reproducible on MacOS, but potentially the same issue affects Windows and Linux

How to reproduce:
1. View the attached file's "plugin.bundle" contents
2. Create a project with the default 3D template
3. Make the .meta files visible (Edit->Project Settings->Editor->Version Control->Mode)
4. Import "plugin.bundle" to the project
5. View the imported file's contents

Expected result: Meta files are not created inside the .bundle files
Actual result: Meta files are created inside the .bundle files

Reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.3.12f1, 2020.1.0b8, 2020.2.0a9, 2023.1.0a3 (checked)


*Additional requirements:*
|Disallow Drag and Drop into Bundle folders|h1. ✔️|
|Disallow Drag and Drop when multiple assets are selected|h1. ✔️|
|Prevent .meta file creation|h1. ✔️|
|Do not show plugin folders as folder in project browser two column view|h1. ✔️|
|Do not show plugin folders as folders in project browser one column view|h1. ✔️|
|Handle DirectoryMonitor message when deleting an already existing .meta file in a plugin folder correctly|h1. ✔️ |
|Write tests that ensure the AssetDatabase.ValidateMoveAsset and AssetDatabase.MoveAsset APIs don't allow moving assets into loadable plugin directories|h1. ✔️|
|Update AssetDatabase.MoveAsset & AssetDatabase.ValidateMoveAsset documentation to mention new restriction|h1. ❌|
|Write test to ensure folders named "bundle", "framework", etc. are still imported |h1. ✔️|
|Write test to ensure folders named "bundle", "framework", etc. can have assets moved into them|h1. ✔️|
|Write test to make sure you can move a loadable plugin folder to another folder with no imports on its children happening|h1. ✔️|
|Reimporting loadable plugin directories should not import their contents|h1. ✔️|
|Reimporting parent folders of  loadable plugin directories should not import the loadable plugin directories' contents|h1. ✔️|


  1. Resolution Note (fix version 2022.2.12f1):

    Fixed in 2022.2.12f1

  2. Resolution Note (fix version 2021.3.23f1):

    Fixed in 2021.3.23f1

  3. Resolution Note (fix version 2020.3.48f1):

    Fixed in 2020.3.48f1

Comments (2)

  1. andreiagmu

    Jul 10, 2023 11:43

    I'm also affected by the regression introduced by this "fix".
    Namely, 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.

  2. bleater

    Jun 15, 2023 10:13

    This has introduced a regression that exporting a package that should include the loadable plugin will not include the plugin contents. See discussion here:

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.