pub.dev

ad_flow

5.3.0faizahmaddae/ad_flow ↗New releases in your daily digest, changelog included.

AdMob integration for Flutter with policy-aware defaults: banner, interstitial, rewarded, rewarded interstitial, native and app open ads with GDPR/UMP consent.

Last release 2 months ago
07 Aug 2026
Release timing varies
gaps range from 1 weeks to 5 months
Nearly every release is documented
notes for 34 of 36 stable releases
Nothing withdrawn
no release was ever pulled
9 months old
36 releases · first in 2025

Release timeline

36 releases since 2025

20252026

One column per month.

Releases

5.3.07 Aug 2026Breaking
No breaking changes, no migration — every existing call site compiles unchanged. Two behaviours change on purpose (see BEHAVIOUR CHANGES).
A banner sizing release. Fixes issue #15: an anchored adaptive banner reserving far more vertical space than the ad it showed, with the app's own background visible around a narrow, short creative.

No breaking changes, no migration — every existing call site compiles unchanged. Two behaviours change on purpose (see BEHAVIOUR CHANGES).

FIXED

An anchored adaptive banner is now sized from what the SDK actually rendered, not from what Dart asked for. google_mobile_ads 9.0.0 cannot round-trip the "large" bit of an anchored adaptive size: the height query honours it, but the codec that sends the size back down to the platform writes only (orientation, width) and both native decoders rebuild it with isLarge = false. So Dart held the large height while the ad view the creative rendered in was built at the classic size — on a 426x952dp phone, a 67dp ad inside a 133dp box. The ~66dp remainder is unpainted by both the plugin and the SDK, so the app's own surface showed through it, on every anchored banner, whatever creative served. The seam now resolves the handle's dimensions via getPlatformAdSize() for both adaptive kinds. Failure handling is deliberately asymmetric: inline adaptive has no requested height to fall back on and keeps its existing semantics, while anchored adaptive falls back to the requested size and never fails or disposes a loadable ad over a lost size query. This also roughly halves the pre-load layout shift.

Test mode picked the wrong sample ad unit for adaptive banners on Android. Google publishes a different demo unit per banner format, and TestAdUnitIds.banner.android was the fixed-size one — so an adaptive request was answered with fixed IAB creatives (320x50, 320x100, 468x60) that cannot fill an adaptive slot. The iOS entry was already the adaptive unit, so the pair was inconsistent and the defect was Android-only. Sample units are now per-format and selected by BannerKind, per placement.

A banner slot with no usable width no longer requests an ad. The load was gated on the layout width being finite, which admits zero. A zero-width placement (a collapsed panel, a mid-animation container) still resolves to a valid adaptive ad size natively, so nothing refused it: a real, billable ad loaded and rendered in a zero-width box — an impression nobody can see. Now gated on a positive width; a slot that later gains one loads then, and a collapse/expand cycle does not re-request.

ADDED

AdFlowBanner.backgroundColor — an opaque colour painted behind the slot (and behind the pre-load placeholder). An adaptive slot is anchored to its width, so a smaller creative is centred by the SDK with the surround left unpainted; Google's guidance is an opaque ad-view background. Paints strictly under the ad, never over it, and disappears entirely while ads are disabled.

Note: TestAdUnitIds.banner is now an alias of adaptiveBanner, so its Android value changed (…/6300978111 → …/9214589741). Nothing stops compiling. But if you deliberately passed TestAdUnitIds.banner to a BannerKind.fixed slot — the only sample constant available before 5.3.0 — switch that placement to TestAdUnitIds.fixedBanner. Slots that let testMode resolve the id are selected by kind automatically.

TestAdUnitIds.adaptiveBanner, TestAdUnitIds.fixedBanner, TestAdUnitIds.forBannerKind(kind) — Google's documented per-format sample banner units. TestAdUnitIds.banner is kept as an alias of adaptiveBanner (the default kind's unit), so existing references still compile.

BannerConfig.defaultKind and an optional kind: on AdFlowConfig.bannerAdUnitId.

BEHAVIOUR CHANGES

An anchored adaptive banner's box now matches the rendered ad — typically about half its previous height on a phone. Nothing about the ad request, fill or revenue changes; the box was simply too tall before.

testMode on Android now serves correctly-sized adaptive test creatives.

KNOWN UPSTREAM LIMITATION

Because the plugin drops the "large" flag, Google's large anchored adaptive format cannot currently be requested from Flutter at all — every anchored request degrades to the classic size. ad_flow is now honest about that (the box matches reality), but it cannot recover the format. There is deliberately no standard-vs-large option, because both Dart factories produce an identical wire message and such a knob would be inert. See ADR-073.

5.2.221 Jul 2026

A focused reliability patch completing the 5.2.1 cached-consent fast path. Upgrade: ad_flow: ^5.2.2 .

A focused reliability patch completing the 5.2.1 cached-consent fast path. Upgrade: ad_flow: ^5.2.2.

No public API or default configuration changes; internal cached-consent reconciliation and reactive state accuracy were corrected.

What changed

5.2.1 introduced safe cached-consent startup serving: an eligible returning user with valid cached UMP consent serves ads while this launch's consent-info update is still in flight.
5.2.2 completes downgrade reconciliation when this launch's final consent result becomes false (consent lapsed and a now-required form was declined). The downgrade invalidates inventory through the existing consent generation before rechecking — so a stale ad whose SDK load was still in flight, and a full-screen show already waiting at an async pre-show check, are now rejected rather than served: the stale handle is disposed, never published as AdLoaded, no impression/show occurs, and the slot settles into an honest blocked state (no duplicate request or retry storm, balanced coordinator).
AdFlow.canRequestAds now reflects the accepted cached true result immediately while the fast path is actively serving, then reconciles to the final result. whenReady semantics are unchanged.

Preserved

Cached-false blocking, ATT exclusion, forwardConsent fail-closed, and request-configuration ordering are all unchanged; a final true settlement does not invalidate good inventory or duplicate loads.

Compatibility

No public API, dependency, configuration, or migration change. SemVer patch.

Open source →

Additional notes

A focused reliability patch that completes the 5.2.1 cached-consent fast path. No public API changes, no default changes, no migration — the change is internal, and every existing call site compiles unchanged.

FIXED

Cached-consent downgrade now invalidates inventory in flight. When the fast path served a returning user on cached consent and this launch's flow then concluded ads may not be requested (consent lapsed and a now-required form was declined), 5.2.1 dropped an already-loaded ad but could still install an ad whose SDK load was in flight at the moment of the downgrade (and could let a full-screen show already waiting at an async pre-show check dispatch), because recheckGate() does nothing while a controller is AdLoading/AdShowing and — for a non-forwarding app — nothing bumped the consent generation. The downgrade now invalidates the consent generation before re-checking, so the completing load's own generation check and the final show-dispatch guard both reject the stale handle: it is disposed, never published as AdLoaded, no impression/show occurs, and the slot settles into an honest blocked state — with no duplicate request or retry storm, and balanced coordinator state. Cached-false blocking, ATT exclusion, forwardConsent fail-closed, and request-config-before-load are all unchanged.
AdFlow.canRequestAds reflects the accepted fast path. The documented live reactive consent value now publishes true the moment the cached-consent fast path is accepted (it previously stayed false until the slow flow finished, despite ads already serving), and the full flow later reconciles it to its real final value (false on a downgrade). whenReady semantics are unchanged.

Open source →

5.2.121 Jul 2026

A focused reliability patch . Upgrade: ad_flow: ^5.2.1 .

A focused reliability patch. Upgrade: ad_flow: ^5.2.1.

No public API or default configuration changes; internal correctness, weak-network recovery, and final dispatch safety were improved.

Cached-consent startup recovery

Returning users with valid cached UMP consent from a previous session no longer wait for this launch's (possibly slow) consent-info update before ads can serve. Per Google's UMP guidance, once this launch's update has been dispatched, a valid cached canRequestAds() lets first-frame banners/natives, full-screen preloads and cold App Open readiness serve immediately instead of stalling on slow or intermittent connections. The full flow still runs and publishes its final result; a downgrade drops the early inventory.

Protections remain intact: requestConsentInfoUpdate() runs every launch and no request precedes its dispatch; a cached-false (first-install) user stays blocked until settled; ATT ordering / a required ATT decision is honored (fast path disabled when a client-driven ATT primer is configured); forwardConsent stays fail-closed and forward-before-init (fast path disabled for forwarding adopters); request-configuration-before-load is unchanged; no duplicate consent flows or load storms.

Final full-screen dispatch guard

Full-screen ads are re-validated immediately before the SDK handle.show() dispatch: ads still enabled, the loaded ad's consent generation still current, not expired, not disposed. A disableAds() / consent mutation / expiry that lands during an async pre-show wait — previously skipped while the controller was AdShowing — no longer dispatches a disabled, stale, or expired ad. Revoked inventory is dropped (not left warm); stale/expired inventory is discarded and reloaded. Coordinator balance, exactly-once show(), reward semantics and the rewarded-interstitial intro are unchanged.

Documentation

Corrected App Open trigger-mode docs (README + AppOpenHandle: launchOnly / resumeOnly / launchAndResume, not "warm-start only") and the runtime-SSV helper doc (load-time attach fails the load closed for a configured SSV, not silent best-effort).

Compatibility

No public API, dependency, migration, or default-configuration change. SemVer patch.

Open source →

Additional notes

A focused reliability patch. No public API changes, no default changes, no migration — both fixes are entirely internal, and every existing call site compiles unchanged.

FIXED

Cached-consent startup fast path. A returning user whose previous session already made canRequestAds() true no longer loses ad serving while this launch's consent-info update is slow. Per Google's UMP guidance, once this launch's requestConsentInfoUpdate() has been dispatched, a valid cached consent lets first-frame banners/natives and full-screen preloads serve immediately, instead of waiting out the update (up to the 30s timeout) on slow or intermittent connections. The full flow still runs and publishes its final result; if it downgrades (consent lapsed and a now-required form was declined) the inventory that loaded is dropped. All ordering guarantees are preserved: requestConsentInfoUpdate() still runs every launch and no ad requests before it is dispatched; a first-install user (cached false) stays blocked until settled; ATT ordering and required ATT decisions are honored (the fast path is disabled when a client-driven ATT primer is configured); forwardConsent stays fail-closed and forward-before-init (the fast path is disabled for forwarding adopters, whose loads are gated on the barrier regardless); request-configuration-before-load is unchanged; and there are no duplicate consent flows or load storms.
Final full-screen dispatch guard. showEngine() now re-verifies the cheap synchronous facts — ads still enabled, the loaded ad's consent generation still current, not expired, not disposed — immediately before the irreversible handle.show(). A disableAds() or consent mutation that landed during a prior await (the show-permission or frequency-cap check), or an expiry that crossed during a slow cap-store hydration, is deliberately skipped by recheckGate() while the controller is AdShowing — so the previously captured handle could be dispatched despite being revoked or stale. Now a revoked ad is dropped (not left warm under adsDisabled), and a stale/expired one is discarded and reloaded, rather than shown. Interstitial, rewarded, rewarded interstitial and app open are all covered; coordinator balance, exactly-once show(), reward semantics and the rewarded-interstitial intro are unchanged.

DOCS

Corrected three stale claims: the README and AppOpenHandle dartdoc said app open was "warm-start only" (5.1+ has launchOnly / resumeOnly / launchAndResume trigger modes); and the runtime-SSV helper doc implied load-time SSV attach is silently best-effort, when in fact an unattachable configured SSV fails the load closed.

5.2.021 Jul 2026

A focused reliability release. Backward-compatible — no migration .

A focused reliability release. Backward-compatible — no migration.

Never load while Mobile Ads init is in flight

No ad request is ever sent while the real MobileAds.initialize() future is still running, on every path:

Ordinary first-frame fail-open / vacuous config — the request-config gate no longer honours fail-open while init is still running; it blocks with AdBlockReason.requestConfigNotApplied and fail-open applies only after init has genuinely completed (a config attempted and failed for real).
The forwardConsent-starts-init-later path — for a mediation forwardConsent adopter the SDK's init only starts after forwarding succeeds, i.e. after the first config check already ran. The gate now re-settles request configuration after the forwarding barrier, so a placement can no longer slip through on the forwarding-path init-wait timeout while init is still in flight. Forward-before-init is preserved.
Prompt recovery — when init completes late, request configuration is applied at once and blocked slots recover automatically (no app code, no long cooldown, no duplicate config calls or load storms). A never-completing init leaves slots in an honest blocked state, never AdLoading, never a request. Startup stays fully non-blocking.

In-flight `disableAds()` (Remove-Ads) protection

A disableAds() that lands after a load passed the gate but before the SDK returned its handle no longer publishes the late handle as loaded or keeps it warm. Banner, Native, Interstitial, Rewarded, Rewarded Interstitial, and App Open now re-check the current permission synchronously immediately before installing the handle, drop it if ads are disabled (AdBlocked(adsDisabled)), and re-warm on enableAds(). A transient indeterminate read never drops good inventory.

SSV backend-security guidance

Rewarded / rewarded-interstitial docs now explain, operationally: onReward is a client-side signal, not proof; attaching userId/customData does not prove backend verification; the backend must verify Google's callback signature and key_id, validate user / ad-unit / reward / custom data, and process transaction_id idempotently; the two fulfillment strategies; a no-double-grant warning; and a link to Google's official Flutter SSV guide.

Public API

+AdGate.isEnabled — one additive getter (mirrors AdGate.consentGeneration). This is the entire delta; no removals, no signature/enum/default changes; hence a correct minor. No migration.

Known limitation

The upstream google_mobile_ads 9.0.0 App Open failed-load leak remains (the plugin omits dispose() on that branch and its callback carries no ad reference, so the seam cannot fix it) — low-severity, process-bounded.

Verification

543 tests pass; analyze & format clean; pana 160/160; publish dry-run 0 warnings; Android and iOS simulator example builds pass. No physical-device run was performed — not required for this pure-Dart lifecycle change.

Open source →

Additional notes

A focused reliability release: two lifecycle fixes that close windows where an ad request could go out before the SDK was ready, plus operationally-correct SSV documentation. Backward-compatible — no migration, and every existing call site compiles unchanged. This is a minor (not a patch) only because it adds one small public symbol: an additive, internal-facing getter AdGate.isEnabled (a synchronous mirror of the injected Remove-Ads/alive predicate, parallel to the existing AdGate.consentGeneration). No types, methods, enums or defaults were removed or changed.

FIXED

No ad request is ever sent while Mobile Ads initialization is still in flight — not even for a fail-open / vacuous request configuration, and not on the mediation forwardConsent path. The request-config gate previously honoured the fail-open RequestConfigFailurePolicy (the auto default for a non-policy-sensitive config) even while the real MobileAds.initialize() was still running, so a first-frame banner or native slot on a weak network / mediation cold-start could dispatch an ad request before the SDK had initialized. Fail-open now takes effect only after init has genuinely completed (a config that was attempted and failed for real); while init is in flight the slot blocks with AdBlockReason.requestConfigNotApplied. For a forwardConsent adopter — where the SDK's init only starts after forwarding succeeds, i.e. after the first config check already ran — the gate now re-settles request configuration after the forwarding barrier, so a load can no longer slip through on the forwarding-path init-wait timeout while init is still in flight. Startup stays fully non-blocking (AdFlow.initialize() returns immediately, the first frame never waits), gate waits stay bounded, and the ADR-028 init→updateRequestConfiguration ordering (and forward-before-init) are preserved. When init completes late, request configuration is applied promptly and blocked slots recover automatically — no app code, no long cooldown, no duplicate config calls or load storms. If init never completes, the UI stays usable and slots settle into an honest blocked state rather than sending requests or staying AdLoading forever.
The disableAds() in-flight-load race is closed for every format (banner, native, interstitial, rewarded, rewarded interstitial, app open). A load that had already passed the gate but not yet received its SDK handle when disableAds() (Remove-Ads) fired could still publish the late handle as AdLoaded / keep it warm, because recheckGate() cannot drop an AdLoading controller. Each controller now re-reads the cheap, current permission synchronously — in the same turn it would publish AdLoaded — and, if ads were disabled while the request was in flight, disposes the returned handle, never installs it, and reports AdBlocked(AdBlockReason.adsDisabled). enableAds() re-warms automatically. The existing consent-generation invalidation is untouched, and — because the re-check is a pure synchronous bool — a transient internalError can never wrongly drop a good loaded ad.

DOCUMENTATION

Server-Side Verification (SSV) guidance is now operationally correct. The README rewarded section and the ServerSideVerification / OnUserEarnedReward dartdoc now spell out that onReward is a client-side completion signal (not cryptographic proof), that attaching userId/customData does not prove your backend verified anything, and what a valuable-reward backend must do: verify Google's callback signature and key_id, validate the user / ad unit / reward / custom data, and process transaction_id idempotently. It documents the two valid fulfillment strategies (grant-then-reconcile vs. wait-for-verified callback), warns against double-granting from both client and server, and links Google's official Flutter SSV guide.

KNOWN LIMITATIONS

The upstream google_mobile_ads 9.0.0 App Open failed-load cleanup asymmetry (a failed AppOpenAd load is not auto-disposed by the plugin, and its failure callback carries no ad reference the seam could dispose) still exists, verified against the installed source. It is a low-severity, process-bounded plugin-side leak that ad_flow cannot safely fix from outside the seam; the honest note is retained (ADR-048 / RESEARCH.md §3). No fragile internal-import/reflection workaround was added.

5.1.121 Jul 2026

A focused, backward-compatible ad-surface layout bug fix prompted by real emulator screenshots.

Remove-Ads now immediately collapses Banner and Native surfaces to zero. Widget-first mode collapses synchronously on disableAds(); advanced controller mode on AdBlocked(adsDisabled).
The example also removes parent SafeArea / Card surfaces when ads are disabled (not just the ad inside them).
Anchored adaptive uses a 50dp pre-load floor and then the exact loaded dimensions.
Inline adaptive defaults to zero before load.
Fixed and loaded sizing remain exact.
placeholderHeight remains supported, but adsDisabled always overrides it (zero footprint).
Re-enabling ads reloads normally, with no duplicate requests.
No public API change and no migration required.

Verification: dart format/analyze clean, 537 tests green, coverage 87.3%, pana 160/160, publish dry-run 0 warnings. Android runtime was verified on an emulator with Google test ads (enabled / disabled / re-enabled); the iOS simulator build passed (iOS was not interactively runtime-tested).

Open source →

Additional notes

A focused ad-surface layout bug-fix, prompted by real emulator screenshots. Backward-compatible — no API changes, no migration; existing call sites keep working unchanged.

FIXED

Remove-Ads now reclaims layout space. After disableAds(), a mounted AdFlowBanner / AdFlowNativeAd previously kept reserving its placeholder height. Both now collapse to a zero footprint immediately. In widget-first (adFlow:) mode the collapse is synchronous — the widgets listen to adFlow.adsEnabled, so it happens on the frame disableAds() is called, without waiting for the asynchronous controller re-check; advanced controller mode collapses on AdBlocked(AdBlockReason.adsDisabled). adsDisabled overrides any explicit placeholderHeight. Re-enabling loads and renders normally again, with no duplicate loads, controller reminting or request storms.
Correct adaptive pre-load placeholder. AdFlowBanner no longer reserves a speculative adaptive estimate (the old "15% of device height, clamped to 50–90dp"). A loaded banner always uses its exact live handle.dimensions. Before load: fixed reserves its exact configured height; large anchored adaptive reserves the documented 50dp floor (Google documents large anchored adaptive banners as 50–150dp) and then grows to the exact resolved size once loaded; inline adaptive reserves 0 (its real height is unknown until onAdLoaded). An explicit placeholderHeight is still honoured for ordinary non-loaded states, and placeholderHeight: 0 opts into fully collapsed pre-load behaviour — but it is never honoured while ads are disabled.

EXAMPLE

Remove-Ads now visibly removes the complete ad surfaces: the bottomNavigationBar returns SizedBox.shrink() before constructing SafeArea (so no empty inset bar remains), and the native Card (title, padding and border) is hidden entirely — demonstrating that parent decorations must also be conditionally hidden, not just the ad. Corrected the stale App Open tile subtitle (the example is configured with launchAndResume, so it no longer claims "never on a cold launch").

DOCS

README: Remove-Ads collapses the ad widgets automatically; loaded banners use exact SDK dimensions; anchored adaptive uses a 50dp pre-load floor then the exact loaded size; inline adaptive defaults to zero before load; placeholderHeight: 0 for no pre-load reservation; parent decorations must be hidden too. Removed the stale 15% / 50–90dp claim. No migration required — this is a backward-compatible layout bug fix (ADR-070).

Open source →

5.1.020 Jul 2026

A focused reliability + App Open UX minor. Additive and backward-compatible — every 5.0 call site compiles unchanged, and the default App Open behavio

A focused reliability + App Open UX minor. Additive and backward-compatible — every 5.0 call site compiles unchanged, and the default App Open behavior is preserved.

App Open trigger modes

AppOpenConfig.triggerMode selects AppOpenTriggerMode:

resumeOnly — the default, exactly the v5.0 behavior (show on a genuine warm return only).
launchOnly — show only at cold launch, via showAtLaunchIfReady().
launchAndResume — both.

`showAtLaunchIfReady()`

Call it from your real loading screen, right before entering main content. It returns immediately and never waits for an ad, the SDK, consent, or the network — it shows only when an eligible ad is already ready, otherwise returns false at once and your app proceeds. It is one-shot per process launch, so a false result never turns into a surprise App Open later. Cold-launch App Open is best-effort, not guaranteed — it appears only if an ad happened to be ready.

Also in this release

launch-only inventory retirement — after its single launch, launchOnly stops maintaining an ad it can never show again.
Native-ad expiry — NativeConfig.maxAdAge (safe default 55 min; null disables); stale native inventory is dropped and reloaded through the normal gate.
Runtime SSV readiness fix — a rewarded / rewarded-interstitial ad is never ready or showable until the latest SSV payload has settled (finalized before AdLoaded; concurrent updates generation-serialized).
Callback / lifecycle containment — AppStateEventNotifier.startListening() rejection contained; enableAds()/disableAds() and the App Open manager are inert after dispose().
Backward compatibility — FullScreenAdControllerBase.onLoaded() unchanged; resumeOnly default unchanged.
Docs & example — README/MIGRATION/CHANGELOG reconciled; the example gains a real launch/loading screen demonstrating the launch path without an artificial delay.

See the CHANGELOG and MIGRATION. Live on pub.dev: https://pub.dev/packages/ad_flow/versions/5.1.0

Open source →

Additional notes

A focused reliability + App Open UX pass. Additive and backward-compatible — no breaking changes; existing call sites keep working, and the App Open default is unchanged.

NEW

App Open trigger modes. AppOpenConfig.triggerMode selects AppOpenTriggerMode.{launchOnly, resumeOnly, launchAndResume}. Default is resumeOnly — the exact v5 behaviour.
Explicit cold-launch opportunity. AppOpenAdManager.showAtLaunchIfReady() (reachable as ads.appOpen.showAtLaunchIfReady()), for launchOnly / launchAndResume. Call it from your real loading screen right before entering main content. It shows an already-ready eligible ad and never waits for network, UMP, SDK init, or a load — returns false immediately otherwise. It is one-shot per process launch (surviving AdFlow reinitialization), so a false result can never become a surprise App Open once the user is in main content. Cold launch is not faked from a lifecycle event. All existing consent / coordinator / cap / expiry / click-return / blocking-view / Remove-Ads rules stay authoritative.
NativeConfig.maxAdAge (nullable; default 55 min, matching the full-screen formats; null disables). Native ads now expire and safely reload, so a long-lived screen never renders stale inventory (Google documents native ads as expiring after ~1 hour).
AdFlowConfig.test(appOpenTriggerMode: …) so the example / tests can opt into the launch path.

FIXED

Runtime SSV readiness race. A rewarded / rewarded-interstitial ad could become externally ready and showable carrying a stale (or missing) server-side-verification payload: the ad published AdLoaded before an in-flight override finished re-attaching, so a state listener or an immediate show() used the previous payload; concurrent updates could also complete out of order. Now the loaded handle is finalized (the override settled) BEFORE AdLoaded is published, a re-attach failure fails the load closed, and every update is generation-serialized so the latest value wins regardless of native completion order.
Uncontained AppStateEventNotifier.startListening() rejection in the seam is now contained (was an unhandled zone error on a misconfigured host).
enableAds() / disableAds() after AdFlow.dispose() are now inert no-ops (they threw a "used after disposed" error before) — consistent with every other post-dispose call.

A post-release audit of 4.0.0 (independent adversarial verification, 25 confirmed findings) plus two release-gate corrections to the mediation consent lifecycle. The major is driven by mediation-privacy correctness: consent forwarding now runs before MobileAds.initialize() and fails CLOSED, a new AdBlockReason case, and the removal of the conceptually invalid deferMediationInit.

BREAKING

AdFlowConfig.deferMediationInit REMOVED (was in 4.0.0). It called the plugin's disableMediationInitialization, which — verified against Google's Android/iOS docs and the plugin source — is a session-wide disable of Google mediation (an A/B-testing tool: "noop once initialize() or the first ad request is made"), not a defer/resume. It could not achieve "set the partner flag, then let adapters come up," and disabling Google mediation is revenue-harming. Use forwardConsent instead — it now runs before init (below).
AdSdk.disableMediationInitialization() REMOVED from the seam interface (was in 4.0.0). It backed deferMediationInit and has no correct use (see above). Affects only code that implements or subclasses AdSdk directly (a custom seam, or a test double not built on the shipped FakeAdSdk) — remove the override. Apps using the package normally never touch AdSdk.
forwardConsent runs BEFORE MobileAds.initialize(). Mediation adapters initialize during MobileAds.initialize(), and AppLovin/Meta read their privacy flag at that point (Google: set it "before you initialize the Google Mobile Ads SDK"). So ad_flow gathers consent, runs forwardConsent, and only then initializes the GMA SDK. Fail-CLOSED by default: a failed/timed-out forward means the SDK is not initialized and loads are BLOCKED (AdBlockReason.consentNotForwarded), retried in the background; init + serving recover when forwarding succeeds. unsafeFailOpen initializes/serves anyway. UI is never blocked — initialize() returns immediately; only whenReady/loads wait. Non-adopters keep parallel init.
AdBlockReason gained consentNotForwarded — exhaustive switches over AdBlockReason need the new case (or a wildcard). Non-adopters of forwardConsent never see it.

Added

forwardConsent on AdFlow.initialize — the fail-closed, before-initialize consent-forwarding barrier for mediation networks that do not read the IAB TCF string themselves (Unity MetaData, AppLovin US-state, Meta LDU). Its callback is serialized — never invoked concurrently, even across the internal 15s wait bound (Future.timeout does not cancel its source), and a newer consent generation's forward never applies its partner-SDK side effect before an older one's completes. Generation-guarded.
AdFlowConfig.mediationConsentPolicy + MediationConsentFailurePolicy (failClosed default, unsafeFailOpen = explicit unsafe opt-out).

Fixed (correctness / reward integrity / reliability)

Frequency-cap late-hydration overwrite. _hydrate bounds itself with a 5s timeout but does not cancel the underlying store reads; a store that hung past the timeout then resumed would overwrite the (by then authoritative) in-memory caps with stale persisted state — rolling back a fresh impression and allowing two full-screen ads back to back. A late read now MERGES (union history, keep the more-recent last-stamp) and never rolls memory back.
Runtime SSV in-flight race + fail-drop. setServerSideVerification called while a load was in flight reported success but the installed ad carried the previous payload; it now re-applies the override to the ad the moment it installs. An attach failure on a warm ad now DROPS that ad (and warms a fresh one with the new override) instead of leaving it showable with stale verification.
Rewarded-interstitial: re-validate after the intro. The mandatory intro is unbounded; a Remove-Ads purchase or the ad aging past maxAdAge during it was ignored and the ad showed anyway. show() now re-checks live permission and expiry after the intro, rolling back rather than showing.
Async callback + refreshed-banner isolation. guardedCallback now contains an ASYNC callback's later rejection (an onConsentChanged/ onPaidEvent async closure's Future no longer escapes as an unhandled zone error). The refreshed-banner paid-event subscription, which bypassed the guard, now routes through it. New safeUnawaited contains a rejecting handle dispose()/subscription cancel() during teardown.
validate() mirrors every constructor assert (release builds strip asserts): FrequencyCap.maxPerSession/maxPerHour >= 0, RetryConfig.maxAttempts >= 0 / jitterFactor in [0,1], InterstitialConfig.minActionsBetween >= 0, NativeConfig exactly-one.
Forwarder serialization across the timeout boundary. Future.timeout does not cancel its source, so a forwarder that outran the 15s wait could be invoked again by a retry while the first invocation was still running — and an older consent operation could apply its partner-SDK side effect after a newer one. The un-timeout'd source is now tracked: at most one forwardConsent runs at a time, strictly ordered.
Stale-consent ad invalidation. After a consent/privacy mutation a warm full-screen ad or visible banner/native (requested under the old consent) is dropped and reloaded under the fresh gate; a full-screen ad on screen is not interrupted. Handled by the existing AdController.recheckGate() (which already runs after every consent mutation) via an internal consent-generation stamp — no new public method, no new integration step.
MediationNetworkExtras asserts against an empty class name (a silent reflection no-op at request time).

Docs

README install constraint corrected ^3.0.0 → ^5.0.0; the AdBlockReason cases (requestConfigNotApplied, internalError, consentNotForwarded) added to the enumeration; a "What's new" section covers the newer surfaces.
doc/MEDIATION_SETUP.md documents forwardConsent as the recommended fail-closed path, mediationConsentPolicy, and a concrete MediationNetworkExtras example.

5.0.020 Jul 2026

A post-release adversarial audit of 4.0.0 plus a mediation-consent lifecycle redesign. The major is driven by mediation-privacy correctness : consent

A post-release adversarial audit of 4.0.0 plus a mediation-consent lifecycle redesign. The major is driven by mediation-privacy correctness: consent forwarding now runs before MobileAds.initialize() and fails closed by default, and the conceptually-invalid deferMediationInit is removed.

📦 pub.dev: https://pub.dev/packages/ad_flow/versions/5.0.0

Breaking changes

Removed AdFlowConfig.deferMediationInit and AdSdk.disableMediationInitialization(). Both drove the plugin's session-wide disable of Google mediation (an A/B-testing tool), not a defer/resume — conceptually invalid and revenue-harming. AdSdk removal affects only direct seam implementers; FakeAdSdk/GmaAdSdk are updated.
forwardConsent runs BEFORE MobileAds.initialize() and fails CLOSED by default. A failed/timed-out forward means the GMA SDK is not initialized and mediation-capable loads block with AdBlockReason.consentNotForwarded (retried in the background); init + serving recover when forwarding succeeds. UI is never blocked — initialize() returns immediately. Opt out only via MediationConsentFailurePolicy.unsafeFailOpen.
AdBlockReason gained consentNotForwarded — exhaustive switches need the new case (or a wildcard).

Added

AdFlow.initialize(forwardConsent:) — the fail-closed, before-init consent-forwarding barrier for networks that don't read the IAB TCF string themselves. Serialized (never invoked concurrently, even across the 15s wait bound — Future.timeout does not cancel its source) and generation-guarded.
AdFlowConfig.mediationConsentPolicy + MediationConsentFailurePolicy (failClosed default, unsafeFailOpen = explicit unsafe opt-out).

Fixed (correctness / reward integrity / reliability)

Frequency-cap late-hydration overwrite (late store read now merges, never rolls memory back / double-counts).
Runtime SSV in-flight race + fail-drop (re-apply on install; drop a warm ad on attach failure).
Rewarded-interstitial: re-validate live permission + expiry after the unbounded intro.
Async-callback + refreshed-banner-paid isolation; safe teardown (safeUnawaited).
validate() mirrors every constructor assert (release builds strip asserts).
Forwarder serialization across the timeout boundary (at most one invocation, strictly ordered).
Stale-consent ad invalidation folded into recheckGate() via an internal consent-generation stamp (no new public method).
MediationNetworkExtras asserts against an empty class name.

Verification

Static/tests: flutter analyze clean · 494 tests · coverage 85.2% · pana 160/160 · publish dry-run 0 warnings.

Runtime (Google-demand only, AdFlowConfig.test(), no Unity/overrides): Android emulator — all six formats shown; iOS simulator — banner, native, interstitial, rewarded, rewarded-interstitial shown, app-open loaded/ready. Physical-device testing intentionally deferred.

Unity mediation — known limitation (not a v5 blocker)

Unity mediation via gma_mediation_unity is temporarily unavailable with 5.0.0: the latest published adapter (1.8.1) requires google_mobile_ads: ^8.0.0 while 5.0.0 requires ^9.0.0. Google's main has an in-progress 1.9.0 for ^9.0.0 but it is unpublished; this release intentionally uses no git dependency, override, or vendored patch. Documented as an optional-integration limitation in doc/MEDIATION_SETUP.md. Unity mediation itself was not runtime-validated.

Upgrading

Most apps compile unchanged — see MIGRATION.md. Delete deferMediationInit if set; add the consentNotForwarded case to exhaustive AdBlockReason switches; if you use forwardConsent, note it now runs before init and fails closed.

Full notes: CHANGELOG.md.

Open source →

4.0.018 Jul 2026

No silent failure: exception containment + callback isolation, per-load watchdog, SSV fail-closed, rewarded-interstitial atomic show reservation, memo

No silent failure: exception containment + callback isolation, per-load
watchdog, SSV fail-closed, rewarded-interstitial atomic show reservation,
memory-authoritative frequency caps, request-config failure policy
(auto/failOpen/failClosed), honest mediation surfaces and docs.
448 tests, pana 160/160. See CHANGELOG.md and MIGRATION.md.

Open source →

Additional notes

A production-hardening major from an independent adversarial audit of 3.0.0. Theme: no silent failure — collaborator faults, lost SDK callbacks, failed policy-critical configuration and unattachable reward verification now either recover visibly or refuse visibly, never wedge or degrade silently. See MIGRATION.md for the short 3.x → 4.0 checklist.

BREAKING

AdBlockReason gained cases (requestConfigNotApplied, internalError) and AdFlowErrorKind gained ssv — exhaustive switches over these enums need the new cases.
SSV fail-closed. A rewarded / rewarded-interstitial load whose configured server-side verification cannot be attached is now a FAILED load (AdFlowError(ssv), normal retry) instead of a ready ad that silently lost its verification payload. Honesty note: the plugin acks the SSV call unconditionally native-side, so only channel-level faults are detectable — final confirmation is always your SSV endpoint.
Rewarded interstitial: atomic show reservation. Every policy check (consent, per-slot AND global caps, pacing, expiry, coordinator) now runs BEFORE the mandatory intro, and the full-screen claim is held through it: accepting the intro can no longer end in "no ad, no reward", nothing can stack over the intro (app-open included), and a throwing intro presenter rolls back instead of rejecting show(). Behavior change (revises ADR-039): the rewarded interstitial is no longer exempt from the global frequency cap — its intro is an app-chosen interruption; a capped sequence simply never starts. Classic rewarded stays exempt.
Request configuration is a retried process with a failure policy. RequestConfigFailurePolicy {auto, failOpen, failClosed} on AdFlowConfig (default auto): when updateRequestConfiguration fails or times out and the config carries policy-critical fields (COPPA / under-age tags, content rating, test device IDs), loads BLOCK visibly (AdBlocked(requestConfigNotApplied)) and recover when the retried apply succeeds — instead of silently sending untagged requests. A config with no such fields keeps failing open. The apply also never races a live SDK init (ADR-028 hardening; it previously dispatched right after a timed-out init — the exact deadlock window).
AdGate constructor: configReady (future) replaced by settleRequestConfig (bounded callback).
Implementer note: AdSdk gained disableMediationInitialization(); FakeAdSdk gained knobs (ssvAttachError, dispatch counters, fullScreenRequests). Package-provided fakes are updated; external AdSdk implementations must add the new member.

Added

Per-load watchdog — RetryConfig.loadTimeout (default 60s, null disables): the plugin has no load timeout of its own, so a lost SDK callback used to pin a slot at AdLoading for the whole session. A timed-out attempt fails into the normal retry path; a LATE completion is disposed, never installed, and can never stomp a newer attempt.
Per-slot AdRequestOptions on every format config (keywords, contentUrl, nonPersonalizedAds, AdMob-adapter extras) plus MediationNetworkExtras mapped onto the plugin's mediation-extras mechanism.
AdFlow.onConsentChanged — fires (isolated) after every consent flow or mutation: the forwarding point for per-network mediation consent APIs (Google does not propagate consent to non-TCF networks automatically).
AdFlowConfig.deferMediationInit — defers mediation adapter init out of SDK init so pre-init privacy flags can be set after consent settles.

Fixed (correctness / revenue / reward integrity)

No collaborator or app-callback throw can wedge a controller. The permission gate never throws (contained → AdBlockReason.internalError, re-checked on backoff); the whole load body sits in one try; app callbacks (onPaidEvent, onAdBlocked, reward grants, onConsentChanged) are isolated via FlutterError.reportError. A throwing canRequestAds() used to pin slots at AdLoading forever with an unhandled async error.
Indeterminate permission never drops a live ad — a transient channel hiccup during a gate re-check keeps the mounted banner/native earning; only definite answers (Remove-Ads, consent withdrawn) take ads down.
Frequency caps are memory-authoritative. An impression recorded at dismiss binds the very next check from ANY controller (min-gap/hourly state used to be read back from storage mid-write — two full-screen ads could run back to back). Persistence is a serialized write-behind snapshot chain (no lost updates); a hanging/corrupt store degrades to session-only capping instead of blocking every show.
UmpConsentGateway.ensureCanRequestAds honours its "never throws" contract on the final canRequestAds() read; Gma handles close their event streams even when the channel dispose rejects.

Open source →

3.0.017 Jul 2026

Production hardening (2026-07 multi-agent audit, 25 confirmed findings fixed) + backward-compat-lifted API cleanup. Breaking: AdBlocked(reason) AdLoad

Production hardening (2026-07 multi-agent audit, 25 confirmed findings
fixed) + backward-compat-lifted API cleanup. Breaking: AdBlocked(reason)
AdLoadState case, widget-first AdFlowBanner/AdFlowNativeAd, show() reward
callback only on rewarded formats, AdGate.canShow removed, showOnColdStart
removed. Added: runtime SSV, mediation observability (AdResponseSummary,
paid-event slot/adSourceName), maxAdAge expiry, live canRequestAds,
config validation, drop-on-Remove-Ads/consent-withdrawal.

Validated on Android emulator + iOS simulator with Google test IDs.
See CHANGELOG.md and MIGRATION.md.

Open source →

Additional notes

Two releases in one (2.2.0 was never published): the production-hardening work from a deep 2026-07 multi-agent audit (25 confirmed findings, all fixed), plus the API cleanup that backward compatibility had forbidden. See MIGRATION.md for the short 2.x → 3.0 checklist.

BREAKING

AdBlocked(reason) is a new AdLoadState case. A load refused by policy (consent pending, Remove-Ads, withdrawal, disposed graph) now reports itself as a state instead of an AdIdle indistinguishable from "nothing requested yet" — the model ADR-045 documented as correct but could not ship in 2.x. Exhaustive switches gain one case; the controller still re-checks its gate and proceeds to AdLoading on its own.
Widget-first ad widgets. AdFlowBanner(adFlow: ads) / AdFlowNativeAd(adFlow: ads) create AND own their controller, making the ADR-029 footgun (minting a controller inside build() → permanently blank ad) unrepresentable. controller: is now optional (advanced use).
FullScreenAdController.show() takes no reward callback — it was silently ignored by interstitial and app-open. The rewarded formats keep show({onReward}).
AdGate is a pure permission gate: the racy composed canShow() query (review finding #6) and its caps/coordinator collaborators are removed. Show pacing lives in the controllers, where the atomic tryEnter() is.
AppOpenConfig.showOnColdStart removed (deprecated + ignored since 2.1.0; it never could do anything). Banner/native slot constants renamed slot → slotName to match the full-screen formats.

Added (3.0)

AdFlow.canRequestAds — a ValueListenable<bool> with the LIVE consent answer: follows a late consent grant (ADR-035 retry) and a privacy-options withdrawal, unlike the one-shot whenReady snapshot.

Fixed (correctness / revenue)

Banner refresh/resize races: a rotation during an in-flight opt-in refresh could leak a live BannerAd (a native view), destroy a fresher right-width ad, corrupt the recorded width, or cancel the slot's only recovery timer (wedging it blank). resize() now defers to an in-flight refresh; the refresh completion re-validates state and reconciles a mid-flight width change; the failure path backs off only while a current ad exists.
Refresh swaps now actually reach the screen: the plugin's AdWidget cannot re-point its platform view at a new ad, so an unkeyed rebuild after a swap kept hosting the DISPOSED ad — a permanently dead slot that still requested (and paid for) fresh ads. AdFlowBanner/AdFlowNativeAd now key the hosted subtree by handle identity, forcing a correct remount.
Inline-adaptive auto-refresh: a failed post-refresh size query tore down the LIVE mounted banner and silently ended its revenue reporting; it now only fails the initial load. A refresh that resolves a different height updates the widget via the new BannerHandle.dimensions listenable (inline adaptive creatives vary per refresh).
Preloaded full-screen ads expire (Google documents ~1 hour): new maxAdAge on interstitial/rewarded/rewarded-interstitial configs (default 55 min; null disables) — stale warm ads are proactively replaced and never shown. App-open's 4h expiry now runs through the same shared mechanism and also replaces proactively.
Ads come DOWN when no longer permitted: disableAds() (Remove-Ads), dispose(), a re-initialize, and a consent withdrawal through ads.consent now DROP live banner/native ads and warm full-screen inventory (previously only future loads were blocked — a mounted banner kept serving and auto-refreshing). enableAds() re-warms at once. New AdController.recheckGate().
show() no longer holds the shared coordinator across a consent settle: a network-bound consent retry could freeze every full-screen format behind one show() call for up to 30s. The show path now uses cheap live checks only (AdGate.showBlockReason).
View-ad click latch can no longer be stranded: an iOS in-app overlay click (open→close with no foreground event) used to eat the NEXT genuine warm return's app-open ad. onAdClosed now starts a 3s grace clock; Android's external-browser return ordering stays suppressed.
Raw platform-channel throws from the load dispatch are normalized to AdFlowError and no longer leak the constructed ad + stream controllers.
SharedPrefsKeyValueStore reads type-corrupt data as absent instead of throwing (a throwing cap read blocked every full-screen show, with no self-heal).
Consent/ATT primers wait (bounded) for the first frame, so a fast launch no longer silently drops the primer before the navigator mounts.
PrivacyOptionsButton failures default to FlutterError.reportError instead of a silent swallow.

Added

Runtime SSV: setServerSideVerification(ssv) on both rewarded controllers — set userId after login and per-show customData; applies to the warm ad and future loads; throws if attaching fails.
Mediation observability: AdResponseSummary (handle.response / controller.response) — winning ad source, adapter class, response ID. AdPaidEvent gains slot and adSourceName for analytics-ready impression logging.
AdFlowConfig.validate() (run automatically): empty ad-unit strings and nonsensical durations fail fast at init.
Null-safe slot getters: interstitialOrNull, rewardedOrNull, rewardedInterstitialOrNull, appOpenOrNull, appOpenControllerOrNull.
Testing surface: FakeBannerHandle.simulateResize/responseSummary, FakeFullScreenAdHandle.simulateShowFailed/ssvUpdates/ssvUpdateError, FakeAdSdk.onPrivacyOptionsFormShown.

Changed

AdFlow.consent now returns a thin graph-aware wrapper: consent-mutating calls trigger a permission re-check across every controller (this is what makes withdrawal drop live ads). Read-only members delegate unchanged.
Docs: doc/MEDIATION_SETUP.md and doc/NATIVE_ADS_SETUP.md rewritten for v2 (they still described the removed v1 API); README documents the emergency kill-switch pattern, the Families app-open prohibition, and both-platform ad unit configuration.

For implementers of the seam interfaces (rare)

BannerHandle gained dimensions; all handles gained response; the rewarded handles gained updateServerSideVerification; AdController gained recheckGate(). The in-package fakes implement all of these — custom implementations must add them.

Open source →

2.1.014 Jul 2026Deprecated

`AppOpenConfig.showOnColdStart` is deprecated and ignored (ADR-043). It could never do what its name promised, and its only real effect is now the def…

Behaviour and default changes from the eight judgment calls raised by the 2.0.2 audit, all approved by the maintainer. No breaking API changes — every existing call site still compiles. But several DEFAULTS and BEHAVIOURS changed deliberately; read this section before upgrading. See MIGRATION.md for the upgrade checklist and ADR-039 … ADR-045 for the reasoning.

Revenue

The global frequency cap no longer blocks user-initiated rewarded ads (ADR-039). A user who tapped "watch an ad for 100 coins" 10s after an interstitial fired got no ad, no reward and no explanation — the shipped default global gap (15s) silently refused the highest-eCPM format in the package. The global cap now paces involuntary ads only (interstitial, app-open). Rewarded impressions are still recorded globally, so an interstitial cannot fire straight after one. New: RewardedConfig.cap / RewardedInterstitialConfig.cap (unlimited by default) if you do want a per-format limit.
App-open ads now show on the FIRST genuine warm return of a session (ADR-043). The manager was consuming that return as a "cold start" the platform never actually emits — costing one impression in every single session, on both platforms. A true cold start still cannot show an ad: nothing is loaded yet.
A banner refresh no longer blanks the slot (ADR-041). It used to destroy the live ad and reload from empty, so the slot went blank for the whole load — multi-second on a weak network, every cycle — and a refresh that merely failed (no-fill, routine) left it empty, having destroyed a perfectly good ad to get there. The replacement now loads in the background and swaps in only on success.

Defaults changed

BannerConfig.minRefresh now defaults to null = no client-side refresh at all (ADR-041). AdMob already auto-refreshes banner ad units server-side, from the console, on by default; the client timer was a second, unsynchronised refresh loop on the same placement — up to 2x the ad requests for no extra revenue. Set the refresh rate in the AdMob console. Pass minRefresh: explicitly to opt back in.
The frequency gap is now measured from the previous ad's DISMISS, not its SHOW (ADR-040). Stamped at show time, the gap ran down while the user was still watching: a 30s rewarded ad under a 15s global gap used the gap up on screen, so an interstitial could fire the instant the user closed it — two full-screen ads back to back.
AppOpenConfig.showOnColdStart is deprecated and ignored (ADR-043). It could never do what its name promised, and its only real effect is now the default. Remove it.

Policy

An app-open ad no longer stacks on a banner/native ad (ADR-042). Returning from a banner or native ad the user clicked no longer shows one — they were being handed a second ad the moment they closed the first. And the new AdFlow.setBlockingViewAdVisible(bool) lets the app declare that a blocking banner occupies the screen, so no app-open ad covers it. ad_flow cannot judge that itself — whether a banner is "blocking" is a question about your layout — so placement remains partly the integrator's job.

Robustness

AdFlow.initialize() is now idempotent (ADR-044). A second call used to build a whole new graph and leave the previous one fully alive — still listening to the foreground stream, still preloading, still able to show ads, and coordinating through its own separate coordinator, so it could not even see the new graph's ads. Two app-open reactors, each blind to the other. It now disposes the previous graph.

New

AdBlockReason + AdFlow.onAdBlocked + controller.lastBlockReason (ADR-045) — the answer to "why aren't my ads showing?". A refused load reported plain AdIdle, which is also what "nothing requested yet" looks like, so consent-not-gathered, Remove-Ads and a frequency cap all looked identical, and the package logged nothing. Deliberately not a new AdLoadState case: AdLoadState is sealed, and adding one would break every exhaustive switch in every app.
AdFlow.setBlockingViewAdVisible(bool); BannerAdController.revision, .resize(), .loadedWidth; StoredFrequencyCapPolicy.globalCapExemptSlots; AdGate.loadBlockReason(); FullScreenAdCoordinator.noteViewAdOpened() / .consumeViewAdOpened() / .blockingViewAdVisible.

Open source →

2.0.014 Jul 2026

Ground-up rewrite targeting google_mobile_ads ^9.0.0. Breaking — see MIGRATION for the field-by-field and symbol-by-symbol mapping.

Ground-up rewrite targeting google_mobile_ads ^9.0.0. Breaking — see MIGRATION for the field-by-field and symbol-by-symbol mapping.

NEW: Rewarded interstitial format with the policy-mandated intro/skip screen enforced by construction (RewardedIntroScreen + injected presenter).
NEW: Frequency capping — per-format time/count caps AND a global cross-format cap, persisted across restarts.
NEW: Interstitial user-action pacing (recordUserAction + minActionsBetween), opt-in by first use.
NEW: Server-side verification options for rewarded formats.
NEW: onPaidEvent impression-level revenue callback for every format.
NEW: package:ad_flow/ad_flow_testing.dart ships FakeAdSdk so apps can unit-test their ad integration.
NEW: Experimental Next-Gen GMA SDK opt-in on Android via --dart-define=USE_NEXT_GEN_SDK=true (no Dart changes).
NEW: Non-blocking AdFlow.initialize() — builds the graph synchronously and returns immediately; consent/ATT/SDK-init run in the background. Render your first frame at once (no FutureBuilder<AdFlow> spinner). Optional Future<bool> ads.whenReady awaits the consent gate. Nothing loads before the gate opens (ADR-032).
NEW: Opt-in consent & ATT priming screens — the v2 equivalent of v1's initializeWithExplainer, now decoupled from BuildContext via presenters (attExplainer/consentExplainer on initialize, ready-made AttExplainerScreen/ConsentExplainerScreen). Supplying attExplainer enables client-driven ATT (iOS). Additive — pass nothing for today's UMP-driven behaviour (ADR-030).
IMPROVED: Architecture — dependency injection everywhere, no static global config; one AdSdk seam is the only door to the plugin; state is ValueListenable<AdLoadState>.
IMPROVED: Consent — UMP wrapped once into ConsentGateway Futures; ATT handled by UMP (dependency on app_tracking_transparency removed); consent failures degrade gracefully with a typed lastError.
IMPROVED: Retries — exponential backoff with jitter, cooldown, then automatic re-arm (v1 never re-armed banner/native loads).
FIXED: App-open ads no longer fire after Control Center / permission dialogs / app switcher (v1 treated iOS inactive as backgrounding); foreground detection now uses AppStateEventNotifier; 4-hour expiry enforced with discard-and-reload.
FIXED: isUsingTestAds false positives — test mode is an explicit config flag, never derived from resolved IDs.
BREAKING: Requires Flutter ≥ 3.38.1, Dart ≥ 3.10, iOS 13+, Android minSdk 24 / compileSdk 36 (from google_mobile_ads 9.x).
BREAKING: All v1 managers, mixins, Easy* widgets and the broad google_mobile_ads re-export are gone — see MIGRATION §7.

Open source →

ad_flow

Release timeline

Releases

FIXED

ADDED

BEHAVIOUR CHANGES

KNOWN UPSTREAM LIMITATION

What changed

Preserved

Compatibility

FIXED

Cached-consent startup recovery

Final full-screen dispatch guard

Documentation

Compatibility

FIXED

DOCS

Never load while Mobile Ads init is in flight

In-flight disableAds() (Remove-Ads) protection

SSV backend-security guidance

Public API

Known limitation

Verification

FIXED

DOCUMENTATION

KNOWN LIMITATIONS

FIXED

EXAMPLE

DOCS

App Open trigger modes

showAtLaunchIfReady()

Also in this release

NEW

FIXED

BREAKING

Added

Fixed (correctness / reward integrity / reliability)

Docs

Breaking changes

Added

Fixed (correctness / reward integrity / reliability)

Verification

Unity mediation — known limitation (not a v5 blocker)

Upgrading

BREAKING

Added

Fixed (correctness / revenue / reward integrity)

BREAKING

Added (3.0)

Fixed (correctness / revenue)

Added

Changed

For implementers of the seam interfaces (rare)

Revenue

Defaults changed

Policy

Robustness

New

In-flight `disableAds()` (Remove-Ads) protection

`showAtLaunchIfReady()`