Element 'Style' has no registered factory method

I’ve just set up a localization system and I’m getting the error even in Edit mode:
Element 'Style' has no registered factory method.
AFAIU the error comes from Localization Settings asset (at the top of it, before Locale Selectors, there is string “Unknown type: ‘Style’”)
When I’m launching the game I’m getting a bunch of errors, but the main thing is that locale from Specific Locale Selector is not chosen. Instead I’m getting None locale (that’s why I’m getting all those errors, I suppose). I didn’t find any solution online on how to fix it.

You can ignore the style error, it’s just coming from a uxml file that is incompatible with 2019.4, we have fixed it in the next release.
Are the errors in the player or editor?
Try disabling the WaitForCompletion option on any localized strings you have. It has a bug that causes this. Its also fixed in the next release.

1 Like

It’s in the editor. Disabling WaitForCompletion doesn’t help (it produces another error, lol).
I think I’ll just ignore those errors or download the latest Unity version.
Thanks for the answer.

Whats the new errors you get?

Cannot find mono image in MonoManager for assmebly 'Unity.Localization'

It pops up randomly.

Ah yes we have had some reports of this. Seems to come from an assembly reload. We are still investigating this one.

1 Like

When will the next release be published?

Probably the first week of September. We are still waiting for some things to land.

Hello my friends, have you fixed this bug? I have the same problem “Unknown Type Style”

It should be fixed in 1.0.0. We are just waiting for it to be released, should be later today.

I still have this issue in 1.0.1 (after upgrading from 1.0.0-pre10). Unity 2019.4.21f1. The Project Settings > Localization window looks rather weird and the message about the style is on top of it. See here:

1 Like

Can you try updating to the latest 2019.4?
There should not be any style references in uxml now so I’m not sure why you are still getting it.

I just managed to reproduce this. Seems the style tag has crept back into the uxml. Ill try and get it fixed.

1 Like

Confirmed fixed in 1.0.2. Thank you!

1 Like