Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.55f1
6000.0.33f1
6000.1.0a9
Issue ID
UUM-92306
Regression
Yes
Error "NullReferenceException: Object reference not set to an instance of an object" is present when loading 3D text mesh in Player from an asset bundle that is built with an older Editor version
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the red cube with text on it
5. Exit the Play Mode
6. Build and Run
7. Observe the Player
Expected result: Text is present on the red cube
Actual result: Text does not exist
Reproducible with: TMP 3.2.0-pre.1 (2022.3.55f1), 4.0.0-pre.2 (2022.3.55f1), 6000.0.33f1, 6000.1.0a9
Not reproducible with: TMP 3.0.9 (2022.3.55f1)
Reproducible on:
Windows Standalone Player
Not reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- Red spots appear when Blending Lighting Scenarios using Adaptive Probe Volumes
- [Windows] About Unity Window needs to be opened twice to adapt to resolution
- NullReferenceException and temporary graph corruption after entering playmode if output node connection was changed
- Sprite Renderer with Animation does not reflect Sprite changes in the Scene when switching Mask Interaction
- User is redirected to a non-existing online documentation link when clicking on "?" help button inside Inspector window while Animator Override Controller is selected
Resolution Note:
According to the documentation, asset bundles are not guaranteed to be forward compatible. It is recommended to upgrade to the new version.
From https://unity.com/blog/engine-platform/unity-asset-bundles-tips-pitfalls:
**Asset Bundles are generally forward compatible, so bundles built with older versions of Unity will in most cases work on games built on newer versions of Unity (assuming you do not strip the TypeTree info, as covered later).
As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.