can only be applied to host components, and doesn't render itself any host component directly. The first host component in any subtree of will always be the root (html) renderer, which will have the . This host component receives the prop.

To support this feature, we could render a top-level , and allow any prop that can be passed to a to be passed to , but that would be a breaking change as it will affect the React tree hierarchy (most notably, it could break style properties applied to the renderer which depend directly on the parent, such as .

We could also opt to support specifically to override html renderer own , but that would obscure responsibilities of this renderer, and you wouldn't be able to query the React node easily to do assertions. Depending on your test case, that could be an issue.

In the meantime, you could choose to wrap with a , and assign a to this view for testing purposes.

Final point: as I am not familiar with detox, I suggest you lay out arguments in favor of , by explaining how it is used by this tool, to make sure any solution, were it implemented, would satisfy the use case.