Search Issue Tracker
Fixed in 4.0.0-pre.1
Votes
5
Found in [Package]
2.0.1-preview2
Issue ID
1172350
Regression
No
Building OSX standalone with FBX Exporter package installed includes extra bundle in the .app package
How to reproduce:
1. Build the attached project for OSX Standalone
2. Check Build.app/Contents/Plugins content
Actual result: UnityFbxSdkNative.bundle gets added to the build.
Expected result: UnityFBxSdkNative is only used in Editor.
Reproducible with: 2018.4.4f1, 2019.3.0a11, 2019.2.0f1, 2019.1.12f1, 2018.4.5f1, 2018.3.0b1.
Reproducible with FBX Exporter versions: 2.0.2-preview1, 2.0.1-preview2.
Notes:
Can't test in 2018.3 alpha as FBX Exported package is broken.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Awaitable.NextFrameAsync() fails to resume when invoked multiple times from the playModeStateChanged event
- Text input duplicates in the TextField when textField.isDelayed is set to true and typing with a Japanese keyboard layout
- “AssetDatabase.GetMainAssetTypeAtPath" returns the incorrect type when using a global namespace class with the same name as a Unity type
- Editor silently crashes when switching platforms when Meta XR Core SDK is imported
- Crash on Object::SetCachedScriptingObject when entering the Play Mode immediately after stopping asynchronous operations in the previous Play Mode session
Resolution Note (fix version 4.0.0-pre.1):
Fixed in FBX Exporter 4.0.0-pre.1 (Verified in 2019.4.15f1)