Transform not registered after updating to 0.17

[open stone]

Heya, I just completed the update of my game from 0.16 to 0.17, and I've got most of it working again. The game compiles now, however my server seems to struggle loading the map due to Transform apparently not being registered.

I see in the migration guide that automatic type registration was added, but this is not something I use in my code.
The TransformPlugin is added, so doubt that's the issue here.

Unsure what code to send here as it worked perfectly fine on 0.16 but during the migration to 0.17 it's broken.

Transform not registered after updating to 0.17

[mighty mulch]

if you're not using the default set of features you'll need to enable the automatic registration feature yourself, as per the migration guide

[open stone]

the reflect_auto_register feature? I tried that, however seems to have no effect

yeah re-checked it now again just in case and it is still very much panicing

[mighty mulch]

you can try doing App.register_type::<Transform>() just like the old way, just to see if it makes a difference before chasing rabbits

having not seen the error, but knowing you did an upgrade, makes me think you might even have multiple Bevy versions installed or similar

[open stone]

Bevy versions installed or similar
Checked via cargo tree and only 0.17.3 is installed

https://workbin.dev/?id=1766949172943649 full cargo tree incase it's interesting in any way

[open stone]

that does work

[mighty mulch]

ok so its just a matter of enabling the auto registration then

[open stone]

is there anything else I need to do other than adding the feature?

[mighty mulch]

well in default applications the feature is on by default, so idk what kind of project set up you have. but yeah you should only need to enable the feature.

its worth noting that in the main bevy crate this is a flag that enables it for multiple sub-crates: https://github.com/bevyengine/bevy/blob/b176e1888c04b6c37035b85c115ad3a1266c22dd/crates/bevy_internal/Cargo.toml#L349-L353

[open stone]

I am using MinimalPlugins, however I couldn't find anything relating to the feature in StandardPlugins

[mighty mulch]

these are cargo feature flags

[open stone]

yeah that's the feature flag that I enabled?

[mighty mulch]

I feel like this is worth a bug report tbh

if you're using minimal plugins and turning it on doesn't work, there should be some instructions somewhere

[open stone]

Right I did some looking and I figured out why (it was not a bevy bug)

Since I used a SubApp directly instead of App, I needed to switch from

        sub_app.init_resource::<AppTypeRegistry>();

to

        sub_app.insert_resource(AppTypeRegistry::new_with_derived_types());