Hello,
our team just stumpled upon a bug with LocalizedStrings in our node-based scripting system when copying nodes (using the default Unity serialization / copy behaviour). First I thought it’s a problem with a custom localization-key dropdown to chose and setup a localized string from a specific localization-table working with the long-id of the table-entries. Turns out that one carries over the data correctly and even resolve it from the targeted table correctly, showing the correct string-preview in the editor.
Problem is, the LocalizedString marked with SerializedField, but hidden in the inspector, does not. Quite easily reproducable manually too, by right-clicking a LocalizedString in the Inspector choosing copy and either paste it on the same field or a another LocalizedString, this results in a LocalizedString without any data (any fields in the localizedString jump to default values).
Edit: A bit funny is, that if you do it manually on a test-script, it resets everything, but in our node-system, in the copied instance only the table-reference is reset and the table entry reference is copied half-correctly, keeping the keyId, but not the Type:
Original (debug-view):
Copied (debug-view):
