Creating a package with native OSX plugin

We have observed that the settings we set in the inspector for our .bundles are not exported properly to a .unitypackage.

I did a minimal test and effectively, the settings are lost. I have decompressed the .unitypackage and analyzed its content to see what happens and I see that the .meta for the .bundle is not inside the .unitypackage (probably because it is a directory).

Anyone can help with this? If this a confirmed bug of Unity?

 

Confirmed. The .meta for directories are not included in the .unitypackage. So, as .bundle is a directory the plugin information is lost.

We tried manually adding the .meta files inside the .unitypackage, but they are ignored when importing.

 

We are thinking that maybe it would be possible to update this settings (plugin platform selection) via scripting (using Reflection perhaps?), this way it will work even if users don't upgrade Unity Editor (if this issue is sorted out in a future release).

Anyone from Unity could shed some light on this please? Otherwise our package won't work just by importing, it would require user to manually update these settings in the .bundle plugins.

Thanks.

 

http://issuetracker.unity3d.com/iss...-do-not-persist-when-exporting-a-unitypackage

 

So, it seems the solution is manually doing this using the PluginImporter API

http://docs.unity3d.com/ScriptReference/PluginImporter.html