Circular dependency causes a component to become null when compiling a subclass

In a project with circular dependencies, components belonging to a native base-class are nulled when a blueprint sub-class is compiled.

1. Download attached project
2. Open project
3. Open the TestActorChild1 blueprint
4. Click on TestComponent1 (inherited)
5. Notice that the details panel looks like the attached image
6. Compile the blueprint
7. Click on TestComponent1 (inherited)
8. Notice the details panel is basically empty now

Expected: Details panel should retain previous information
Result: The component becomes null

Why does the REMOVE method of map container remove elements have memory leaks?

How does TextureRenderTarget2D get TArray<uint8> type data?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

How do I set a material as a post-processing material?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

How to delete some elements correctly when deleting an array loop?

What controls of umg have mouse wheel events in UE4.27?

What is the difference between Camera and CineCamera?

How does TArray loop correctly remove elements in blueprints?

In UE5.4, custom variables in the level blueprint cannot be set to default values, and the eyedropper tool is also unavailable, whereas in UE4.27, these features work normally.