Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.5f1
Issue ID
807476
Regression
No
New DLL is not updated and old version is used instead of the new one until the project is reopened on OSX
Might be related to plugins given the DLL issue
Steps to reproduce:
1. Open the attached project (UnityOSXBundleIssue.tar.gz)
2. Open and play 'TestScene'
3. Look at the console, notice it prints: "CallBundleFunction called", stop the scene
4. Open up the XCode project (located in UnityOSXBundleIssue/UnityBundle) and change the log string to something else,
recompile the project
5. Remove the bundle from the Unity project from inside Unity (Assets/Plugins)
6. Copy the new compiled Bundle (from step 4) into the Plugins directory
7. Play 'TestScene' again, look at the console:
Expected behaviour: New string should be logged
Actual behaviour: The old string "CallBundleFunction called" is logged
Note:
Reopening the project or reimporting all assets updates the bundle and the new string is correctly printed out.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment