And what are the steps to re-create the above behavior?
EDIT:
The issue appears to be related to the fact a Canvas needs to be added and the text object a child of that new Canvas. For some reason, the object creation handling used in a normal scene isn’t handled correctly in Prefab isolation mode. Will look further into it later this afternoon.
Thanks. I just ran into this myself - it also sets the scale of the object to 2.
Will the new text object I just created (that gave an error) be usable or should I exit prefab mode, create the object and then apply to the prefab? Basically can I ignore the error and continue?
This issue has been fixed but I am still putting the final touch in the next release which I really want to release next week.
In terms of the Prefab issue, this only occurs in Isolation mode. If you make the changes in the scene, it should be fine. Furthermore, the issue is related to the text object not being created as a child of the Canvas which is something that can be fixed manually in prefab isolation mode if needed.
This fix will be in the next release which is expected to be version 1.5.2 for Unity 2018.4, version 2.1.2 for Unity 2019.4 and version 3.0.2 for Unity 2020.x.
I just found this bug, and this thread for the solution. I’m in Unity 2020.2.2f1 and upgraded TMPro to 3.0.5, and now get this error in three places:
Library/PackageCache/com.unity.textmeshpro@3.0.5/Scripts/Runtime/TMP_InputField.cs(429,42): error CS0117: ‘RuntimePlatform’ does not contain a definition for ‘PS5’
[edit] Also, the upgrade didn’t solve the original issue.
In terms of the initial issue reported in this thread, this should have been fixed so let’s see if I can first remember the steps to reproduce it and then figure out what is up.
UPDATE
I was able to track down the original report where everything appears to be working as expected using 3.0.4 or 3.0.5.
I also installed 2020.2.2f1 with 3.0.5 and everything is working as expected with the exception of the PS5 issue.
Can you provide the steps to reproduce the issue you are running into?
Ok, now it works. I guess something didn’t get fully updated the first time I upgraded to 3.0.5, so it was still happening. After downgrading to 3.0.4, then reimporting the entire project, then re-upgrading to 3.0.5, the original issue is fixed. Thanks for the quick replies.