Keys of the web OptiViewAdsConfig that can never cross the React Native
bridge: they reference DOM objects or JS functions that only make sense
in-process on web.
player — replaced by the host RN player's nativeHandle; the native
bridge constructs the matching native PlayerAdapter.
container / playerContainer — replaced by the native overlay host
view that the bridge attaches above the player view.
createAdAdapter — ad rendering is native (OverlayAdRenderer).
Keys of the web
OptiViewAdsConfigthat can never cross the React Native bridge: they reference DOM objects or JS functions that only make sense in-process on web.player— replaced by the host RN player'snativeHandle; the native bridge constructs the matching nativePlayerAdapter.container/playerContainer— replaced by the native overlay host view that the bridge attaches above the player view.createAdAdapter— ad rendering is native (OverlayAdRenderer).interceptManifestRequest/interceptManifestResponse— registered through OptiViewAdsConnector.setManifestRequestInterceptor / OptiViewAdsConnector.setManifestResponseInterceptor instead, so the bridge round-trip policy (timeout, fail-open) is explicit.