react-native-google-mobile-ads
    Preparing search index...

    Type Alias AdPoolResolvedConfig

    AdPoolResolvedConfig: AdPoolConfig & {
        degraded: boolean;
        degradeReasons: AdPoolDegradeReason[];
        effectiveBufferSize: number;
        effectiveStalenessWindowMillis: number;
        effectiveStalenessWindowSource: AdStalenessWindowSource;
        requestedBufferSize?: number;
    }

    Effective pool configuration after capability and app-wide accounting.

    Impossible requests hard-error at AdPools.create; safe fallback is loud: degraded is true, reasons are listed here, and development builds warn. For example, a display pool requesting depth 3 resolves at depth 1 with 'pool/degraded-buffer-size' and 'pool/emulated-no-sdk-preloader'.

    Presets default bufferSize to 1. A hand-written fullscreen config with no size uses the platform preload default; display pools are depth 1. pollTimeoutMillis has no implicit timeout, so the timeout result is only reachable when a positive timeout is configured.

    AdPoolConfig.adServer accepts AdMob or Ad Manager. Multi-format banner requests intentionally accept only Ad Manager because that is the AdLoader-style banner path.

    Type Declaration

    • degraded: boolean
    • degradeReasons: AdPoolDegradeReason[]
    • effectiveBufferSize: number
    • effectiveStalenessWindowMillis: number

      Applied staleness window after config defaulting. Readable so callers do not have to re-derive the guidance table.

    • effectiveStalenessWindowSource: AdStalenessWindowSource
    • OptionalrequestedBufferSize?: number
    const pool = await AdPools.create(
      AdPoolPresets.display(gamUnitId, {
        bannerSizes: [BannerAdSize.MEDIUM_RECTANGLE],
        bufferSize: 3,
      }),
    );
    console.log(pool.resolved.requestedBufferSize); // 3
    console.log(pool.resolved.effectiveBufferSize); // 1
    console.log(pool.resolved.degraded, pool.resolved.degradeReasons);

    Settings
    Member Visibility