Autowiring not working for native applications with prototype components

If you have a Spring Component with a Scope of "prototype" and the Component has a constructor with some parameters, when that Component is created using BeanFactory in a native application, any Autowired member variables are not populated and no errors are generated. However, the same application run normally works as expected.

To replicate,

1. Spring Initialzr to create an project containing "GraalVM Native Support" and "Spring Web"
2. Change version of "org.graalvm.buildtools.native" plugin to "1.0.0"
3. Create DemoComponent class:

@Component
@Scope("prototype")
public class DemoComponent {
    @Autowired
    public BeanFactory beanFactory;

    public DemoComponent(Object obj) {

    }
}

4. Create DemoController class:

@RestController
public class DemoController {

    @Autowired
    protected BeanFactory beanFactory;

    @RequestMapping
    public void demo() {
        DemoComponent demoComponent = beanFactory.getBean(DemoComponent.class, new Object());
        System.out.println("HERE1: " + demoComponent.beanFactory);
    }
}

5. Build using gradlew bootJar
6. Generate reachability-metadata.json using java -agentlib:native-image-agent=config-output-dir=src\main\resources\META-INF\native-image -jar build\libs\demo-0.0.1-SNAPSHOT.jar
7. Use browser to go to "http://localhost:8080" and confirm that beanFactory of DemoComponent is populated
8. Build and run native application using gradlew nativeRun
9. Use browser to go to "http://localhost:8080" and confirm beanFactory of DemoComponent is not populated

Note that if I remove the parameter from the DemoComponent constructor and from the beanFactory.getBean(... line in the DemoController, the beanFactory in the DemoComponent is populated as expected in both native and bootJar.

Start with the DemoComponent and DemoController reproduction, then compare the behavior of bootJar with nativeRun using the generated reachability-metadata.json. The fix is complete when the prototype component's autowired BeanFactory is populated in the native application as it is in the regular run.