I think you mean 'built-in' into react native? Facebook routinely lets the community settle on the correct api aside from a limited core.
E.g. react router on web has gone through many versions and there are several community libraries for doing web navigation and how you want to track that application state.
And as a result there's a ton of churn, waiting for third parties to update their libraries (sometimes forever) and beginners having to make choices on how to do the most basic things without the experience or knowledge to help them make good decisions.
It's just beyond the needs of fb and what they cared to provide for. No one is paying for the extra dev work, so until some other entity pays or volunteers that will be the situation. Incidentally, Expo did extend RN to cover many of the missing APIs. It's just the reality we live in.
E.g. react router on web has gone through many versions and there are several community libraries for doing web navigation and how you want to track that application state.