NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev, #5958 most downloaded on pub.dev
Dual-provider ad SDK for Flutter (AdMob + AppLovin MAX). Offline-verified VIP codes, GDPR/COPPA/CCPA consent, safety caps, AdEvent stream, debug overlay.
Latest stable
3.7.1
Last release 12 days ago
08 Nov 2026
Ships fairly regularly
a new release about every 1 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 months old
86 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
SafeLogger's default log level is now kDebugMode-based (verbose in debug, warning-and-above in release) instead of always-verbose — a host that never
SafeLogger's default log level is now kDebugMode-based (verbose in
debug, warning-and-above in release) instead of always-verbose — a host
that never calls AdManager.setLogLevel() no longer leaks raw GAID and
other diagnostic detail into release logs by default.autoRequestUmpConsent
false + requestUmpConsent() never called before initialize()) now hard-
blocks ad requests in release builds (kReleaseMode), not just a dev-time
assert() (which strips in release and was previously log-only in
production). The block clears automatically the moment setConsent() is
called — directly by a host's own consent UI or internally by
requestUmpConsent() — and triggers a refill of any ad slots held back
while it was active.NativeAdWidget's MaxNativeAdView listener callbacks now check
adapter.isInitialised before writing to its ValueNotifiers or firing a
click event, closing the same disposed-adapter race already guarded on the
AppLovin banner/mrec views.VipManager.firstInstallGrantDueListenable — fires once when the first-install VIP grace window is granted (previously silent/log-only), paired with la
VipManager.firstInstallGrantDueListenable — fires once when the
first-install VIP grace window is granted (previously silent/log-only),
paired with lastFirstInstallGrantDuration and
acknowledgeFirstInstallGrant(). Mirrors the existing
graceNudgeDueListenable pattern. AdManager.initialize() now calls
notifyFirstInstallGrant() right after granting the window.Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
RevenuePanel gained an optional debugModeOverride constructor param (test-only seam, @visibleForTesting) so the widget's kDebugMode gate can be exerci
RevenuePanel gained an optional debugModeOverride constructor param
(test-only seam, @visibleForTesting) so the widget's kDebugMode gate
can be exercised from flutter test.SimpleEventBus now replays the last-fired event to a listener that
subscribes after the event already fired, closing a gap where late
subscribers silently missed init-completion signals. clearAll() (called
from AdManager.destroy()) resets the replay buffer.RevenuePanel now fully gates on kDebugMode (or the override above): no
event subscription and SizedBox.shrink() render in release builds,
instead of only skipping the visual chrome.ad_manager.dart escalates the existing silent log warning for a
misconfigured consent flow (AppLovin CMP disabled, autoRequestUmpConsent
false, requestUmpConsent() never called before initialize()) to a
dev-time assert() — asserts strip in release, so production behavior is
unchanged, but dev/test builds now fail loudly instead of silently
shipping with no consent flow.requestUmpConsent() now logs a warning if called before requestAtt()
on iOS (ATT must run first per platform policy) — log-only, non-blocking.enableFillRateMonitor/enableArbitrator
are production-safe opt-in tools with no kDebugMode distinction; UMP→
AppLovin consent sync is boolean-only by design since AppLovin MAX SDK
12.0.0+ auto-reads the IAB TC-String directly; pointers to the existing
CCPA CupertinoSwitch pattern and consent_dialog.dart's binary-only
rationale for hosts that need more UI; noted the Android VIP-key
reinstall-replay limitation.example/ios/Runner/Info.plist synced from 50 → 152 SKAdNetworkItems
entries to match the host app.…connection_notifier's 3.x/4.x majors — those breaking changes only affected its widget/UI layer, which this SDK doesn't use.
confetti ^0.7.0 → ^0.8.0 and connection_notifier ^2.0.1 →
^4.1.0 (dependency freshness, closes Pub Points "up-to-date dependencies"
gap). No API surface used by this package (ConnectionNotifierTools .initialize()/.isConnected/.onStatusChange) changed across
connection_notifier's 3.x/4.x majors — those breaking changes only
affected its widget/UI layer, which this SDK doesn't use.Older entries (1.1.0 and earlier) moved to CHANGELOG_ARCHIVE.md because pub.dev rejects a CHANGELOG.md over 256 KB.
New AdSlotType.native + AdScreen.buildNative(). AdMob renders via Google's NativeAd/NativeTemplateStyle(templateType: TemplateType.medium) (same prelo
buildNative())AdSlotType.native + AdScreen.buildNative(). AdMob renders via
Google's NativeAd/NativeTemplateStyle(templateType: TemplateType.medium)
(same preload-then-AdWidget pattern as banner/MREC; the template
self-draws its own "Ad"/AdChoices label). AppLovin renders via a
self-contained MaxNativeAdView with a custom Dart child layout
(MaxNativeAdIconView/TitleView/MediaView/BodyView/
CallToActionView), for which the package self-draws its own "Ad"
compliance badge (mirrors MREC's _MrecContainer badge). v1 ships one
fixed layout — not a customizable editor. See README § "Native Ad (v1)".buildMrec())AdSlotType.mrec), same lifecycle shell
as banner (RouteAware pause/resume, VIP suppression, offline collapse,
auto-refresh gate).monetization_arbitrator.dart: opt-in per-slot provider arbitration with a
guardrail against flapping between providers. fill_rate_monitor.dart:
tracks per-slot fill rate over a rolling window for arbitration decisions
and diagnostics.AdEvent stream for host-app-side analytics.ad_diagnostics.dart / integration_self_check.dart gained checks that
catch common misconfiguration (missing ad unit IDs, mismatched provider
config) before the SDK starts requesting ads.AppLovinAdapter.preloadMrec() crashed the host app when MREC wasn't configuredAdManager.initialize() (and the VIP-loss handler) unconditionally
preload the MREC slot alongside banner, regardless of whether the host
app actually uses buildMrec(). For AppLovin, an unconfigured MREC
resolves AppLovinConfig.mrecId to its default empty string, and
AppLovin's native MaxAdViewImpl.loadAd() throws
IllegalArgumentException: No Ad Unit ID specified synchronously inside
an Android Handler callback — outside Dart's platform-channel
try/catch, so it crashed the whole process instead of surfacing as a
catchable Dart error. Any AppLovin-provider host app that doesn't
configure MREC (i.e. virtually all apps, since MREC only shipped this
release) would crash on every SDK init. preloadMrec() now skips the
native preload entirely when cfg.mrecId is empty.AppOpenTrigger.splashOnly/resumeOnly only gated the SHOW path, not LOADshowAppOpenAd/showAppOpenAdOnResume respected appOpenTrigger, but
loadAppOpenAd() (init/VIP-change/retry-refill) never checked it — under
splashOnly/resumeOnly the App Open slot kept getting refilled and could
sit ready indefinitely (AppLovin has no AdMob-style 4h TTL), wasting
network requests/fill quota. Default both was unaffected (both gates are
no-ops there). Now gated behind the same appOpenTrigger check as the show
path.redeemVip() demo mode (validator == null) no longer accepts any key in release buildsredeemVip() accepts any key when AdConfig.vipKeyValidator is
null, intended as a zero-config demo mode. A host app that forgot to wire
a validator would ship this silently — any user typing any string got free
VIP. _runValidator now refuses (return false) when validator == null
and kReleaseMode is true; debug/profile builds keep the original
demo-mode passthrough so wiring the integration still works without a
validator during development. Does not affect redeemSignedKey()
(Ed25519-verified, the path production code actually uses).> Published in two commits the same version: 2026-07-10 (consent-on-init +
Published in two commits the same version: 2026-07-10 (consent-on-init + ATT/UMP timeout fixes below) then 2026-07-16 (privacy-options timeout + CCPA toggle + SKAdNetwork expansion + doc fixes). Both are live on pub.dev under
1.0.24— the split below is historical, not two releases.
requestPrivacyOptionsFlow() could hang forever on a served-but-never-dismissed form (T44)ConsentForm.showPrivacyOptionsForm()'s own platform call resolves; awaiting
that call directly (as the code did) meant a stuck/never-dismissed form hung
the whole call with no way out — bypassing an already-added completer
timeout that could never be reached. Fixed by not awaiting
showPrivacyOptionsForm() directly (matching the existing fire-and-forget
shape already used for requestUmpConsentFlow()'s form show/dismiss) and
applying the 20s timeout to the dismiss Completer that its callback feeds.
Test: test/ump_consent_test.dart.VipRedeemScreendoNotSellValue/onDoNotSellChanged params render a switch in
the privacy footer (next to Privacy Policy/Privacy Options), letting a host
app wire it straight to AdManager().setConsent(AdConsent(doNotSell: ...)).
Opt-in only — omitting onDoNotSellChanged (the default) renders the same
footer as before.applovin_adapter.dart) all
refill ads directly from their own onAdHidden/onAdDisplayFailed native
callbacks, bypassing AdManager.loadX() and therefore its gates entirely.
A user who just redeemed VIP, went offline, or revoked consent could still
trigger an outbound ad request from a stale in-flight callback. Fixed by
adding a canReload() check (AdManager wires it to
!_isVipMember && !AdSafetyConfig.dailyCapReached() && _canRequestAds && isConnected)
immediately before every such reload call site.initialize()AdManager.setConsent() called before initialize() (the real app startup
order: requestUmpConsent() → initialize()) used to only mutate an
in-memory field and return early, because ConsentManager wasn't bootstrapped
yet. initialize()'s subsequent ConsentManager.bootstrap() then
unconditionally reloaded the previous session's stale persisted consent
and overwrote it — silently discarding the fresh UMP result on every app
launch. Fixed by buffering the pending ConsentSettings in a new
_pendingConsentSettings field and re-applying it right after bootstrap, so
it wins over the just-loaded stale data; the buffer is cleared on
destroy() so it never leaks into an unrelated future initialize(). Test:
test/consent_persistence_on_init_test.dart.initialize() forever (T43)requestAttIfNeeded() and requestUmpConsentFlow() each awaited a native
modal-dismiss (or network) callback with no timeout. If the OS/native
side never resolved it (ATT prompt throttled by rapid repeated launches;
a UMP form served but never tapped through; a dead network on
requestConsentInfoUpdate), the whole initialize() chain never ran —
the ad SDK stayed silently uninitialized for that app session. All three
awaits are now wrapped in Future.timeout(Duration(seconds: 20), onTimeout: () => <safe fallback>), mirroring the existing App-Open watchdog pattern.
requestPrivacyOptionsFlow()'s dismiss await is deliberately not part of
this fix — it's a user-initiated re-consent action outside the app-boot
gating chain. Tests: test/att_consent_test.dart, test/ump_consent_test.dart
(fakeAsync + never-completing Completer, mocking the real
google_mobile_ads UMP method channel with its custom
StandardMethodCodec(UserMessagingCodec())).ssvUserId/ssvCustomData on AdScreenState.showRewardedAd()AdManager.showRewardedAd() already accepted ssvUserId/ssvCustomData for
server-side reward verification, but the AdScreenState.showRewardedAd()
convenience wrapper (lib/src/core/ad_screen.dart) that most host screens
actually call did not expose or forward them — any caller passing those
named args failed to compile. Added both as optional parameters, forwarded
as-is to the underlying AdManager call; no change to the wrapper's
existing safety-check/disclosure-dialog behaviour.RedeemedKeyLedger (lib/src/vip/_redeemed_key_ledger.dart) backs
VipManager.redeemSignedKey's one-time-use check with an iOS Keychain
entry, alongside the existing AdPreferences (SharedPreferences) check.
AdPreferences alone is wiped on uninstall, so a user could
uninstall/reinstall to redeem the same signed key repeatedly; the Keychain
entry survives that. Android intentionally has no durable backstop here,
same reasoning as the existing FirstInstallGuard (no local primitive
survives uninstall without an install-referrer plugin for a narrow
benefit) — AdPreferences remains the sole check there. Fails open: any
Keychain read/write error is swallowed and treated as "not redeemed" so a
storage hiccup never locks out a legitimate key. Test:
test/redeemed_key_ledger_test.dart.VipManager exposes graceNudgeThreshold (default 24h),
graceNudgeDueListenable, and acknowledgeGraceNudge(). Once a VIP
entry's expiresAt comes within the threshold, the nudge notifier flips
true so the host UI can prompt the user to redeem/extend before ads
resume; acknowledging persists the current expiresAt so the same expiry
doesn't re-nudge, but stacking a new expiry (redeem/watch-ad-to-extend)
makes it due again. Inactive/no-VIP state is never due. Test:
test/vip_manager_grace_nudge_test.dart.AdPreferences.getVipEntriesRaw()/setVipEntriesRaw() now store an
FNV-1a checksum alongside the VIP entries JSON, as a single combined
SharedPreferences value ('<checksum>|<json>' written via one
setString call). A mismatched checksum is logged and treated as absent
data, deterring casual on-device editing of the plaintext VIP entries to
self-grant free ad-free time — this is a tamper deterrent, not
root/jailbreak-proof protection (a rooted device can still recompute the
checksum). Pre-upgrade data with no checksum is trusted once and
backfilled into the new format. FNV-1a was chosen over String.hashCode
(not stable across Dart/Flutter versions) and over the existing async
cryptography-package HMAC (would force every VIP-entries caller async).
Note: an earlier two-separate-keys design was replaced with the single
combined key above after it surfaced a real race — a concurrent
fire-and-forget VipManager._save() write could be observed mid-flight
with one key updated and the other still stale, causing a false
"tampered" read. Test: test/ad_preferences_test.dart.applovin_max/gma_mediation_applovin to the latest
upstream versions (4.6.4/2.6.1) to see whether the CocoaPods
version-pin conflict documented in the host pubspec.yaml
dependency_overrides had been resolved. It has not: 2.6.1 now
requires meta ^1.17.0, while flutter_test from the CI-pinned Flutter
SDK (3.35.1) forces meta 1.16.0 — a Dart-level version-solve conflict,
never even reaching the CocoaPods layer. No SDK code change; the pins
stay at applovin_max 4.6.0 / google_mobile_ads 6.0.0 /
gma_mediation_applovin 2.5.1 in the host app. See
doc/audit/audit_partner_lead_20260710.md findings #2/#3.VipRedeemScreen gained onPrivacyOptionsTap (VoidCallback?) and
VipRedeemStrings.privacyOptions, mirroring the existing
onPrivacyPolicyTap/privacyPolicy pair. The footer now renders whichever
of the two buttons has a non-null callback (previously only the privacy
policy button existed). Closes the gap where AdManager().showPrivacyOptions()
(T06) had no host call site — GDPR requires a durable re-consent entry
point, not just a one-time policy link. Test: test/vip_redeem_screen_test.dart
(footer hidden/shown/tap cases for onPrivacyOptionsTap).AdScreenState.showRewardedAd (T22)showRewardedAd gained optional disclosureTitle/disclosureSubtitle/
disclosureButtonLabel/disclosureCancelLabel params. When
disclosureTitle is set, a confirm dialog naming the reward is shown right
before the ad plays; declining calls onEarnedReward(false) and never
reaches the ad. Omitted (default): behaviour is unchanged — return type
changed void → Future<void>, non-breaking via Dart's void-return
covariance. Test: test/ad_screen_test.dart (rewarded disclosure hook
group — confirm/cancel paths).AdSafetyConfig.dailyCapReached() is a new pure read-only check (no
CTR-anomaly side effects, unlike canShowFullscreenAd()). loadAppOpenAd/
loadInterstitial/loadRewardedAd and the periodic _retryRefillAds scan
now skip preloading once the daily fullscreen-ad cap is hit — previously
the cap was only enforced at show time, so a capped-out user kept
burning ad-network load requests that could never convert. VIP members are
unaffected (the existing VIP guard already returns before this check runs
in every call site). Test: test/daily_cap_load_gate_test.dart,
test/ad_safety_config_test.dart (dailyCapReached group).VipEntry.isActive/remaining now also check now.isBefore(grantedAt) —
previously only now.isBefore(expiresAt) was checked, so rolling the
device clock backwards past a grant's expiresAt made an
already-expired-by-real-time entry "come back to life". A rolled-back
clock is now treated as the entry having already been consumed
(fail-safe), not as extra time granted. VipManager's purge/active/
stacking logic needed no change — everything already routes through
VipEntry.isActive. Test: test/vip_entry_test.dart (anti clock-rollback (T17) group).AdManager.releaseFootgunWarnings now also warns (release builds only,
same log-ERROR + assert(false, ...) treatment) when
AdConfig.firstInstallVipGrace is .disabled — previously a partner
could silently ship with no ad-free first-install trial. Test:
test/ad_manager_core_test.dart (firstInstallVipGrace cases in the
releaseFootgunWarnings group).AdManager.releaseFootgunWarnings now also warns (release builds only,
same log-ERROR + assert(false, ...) treatment as the existing dryRun/
Google-test-id guards) when: any resolved bannerId/interstitialId/
appOpenId/rewardedId is empty, or (AdMob provider only) an id doesn't
match AdMob's ca-app-pub-<16 digits>/<ad-unit id> format — the classic
"pasted an AppLovin id into the AdMob config" mistake. Test:
test/ad_manager_core_test.dart (releaseFootgunWarnings group).AdMobConfig/AppLovinConfig gained optional android*Id/ios*Id
overrides for bannerId/interstitialId/appOpenId/rewardedId (e.g.
androidBannerId, iosBannerId). Resolved via Platform.isAndroid/
Platform.isIOS at read time, falling back to the existing single id when
no override is set — fully backward compatible. Test:
test/ad_config_platform_test.dart.AdManager().isPrivacyOptionsRequired() and AdManager().showPrivacyOptions()
(wrapping ConsentInformation.getPrivacyOptionsRequirementStatus +
ConsentForm.showPrivacyOptionsForm) are now documented in the README as the
required durable re-consent entry point Google's UMP policy mandates
(a permanent "Privacy Settings" button). showPrivacyOptions() safely no-ops
(no native UI) when Google doesn't require it for the current user, and
re-applies the resulting consent to the active ad provider (npa/RDP) when it
does. Test: test/privacy_options_test.dart — required→opens form,
notRequired→no-op, re-consent re-applies to the active adapter.VipRedeemScreen widgetVipRedeemScreen + VipRedeemStrings (localizable, mirrors the
ConsentDialogStrings pattern). The host and the SDK example now render the
identical screen — host injects Vietnamese strings, the example uses the
English defaults. Privacy-policy opening is a callback (onPrivacyPolicyTap)
so the SDK needs no url_launcher dependency; confetti is added.redeemSignedKey now claims the key id atomically (synchronous
check + in-flight set) so a concurrent double-tap of the same signed key can't
slip past the one-time-use check and grant twice. Enforced in the SDK, not
just the host UI. Test: concurrent double-redeem grants exactly once.initialize() logs a loud runtime warning when AppLovin's CMP is
disabled AND autoRequestUmpConsent is false AND requestUmpConsent() was
never called before init — the "no consent form anywhere" footgun. Runtime,
not config-static, so it never false-alarms hosts that gather consent in
their splash.initRevision). Added a widget test.isConnected now falls back to the last-known connectivity state
(from the T08 watch) with a warning log instead of a silent true when the
detector is unavailable. Kept optimistic on purpose — a broken detector must
not permanently block ads; genuine offline loads just fail and back off, and
the watch refills on reconnect (network-error fast-retry is subsumed by T08).AdLoadingDialog.resetState() (called by AdManager.destroy()) now pops
a still-showing dialog before clearing its flags, so a mid-dialog destroy /
re-init can't strand a non-dismissable loading dialog on the navigator.
(_eventStream is intentionally left open — it's a process-lifetime singleton
broadcast exposed publicly; closing it would break host subscribers and it is
bounded to one instance, so it is not a leak.)isReady + atomic beginShow + null-on-dismiss), a disposed ad is never
re-shown, and dispose happens exactly once. (No code change needed; the guard
already existed — the tests lock it down.)BannerAdWidget now guards against stacking multiple post-frame
_initBanner callbacks (_initScheduled) when build runs repeatedly, so a
banner loads exactly once across rebuilds. (loadBannerIfNeeded already
bailed on a cached ad; this removes the wasteful callback pile-up.)
(dispose-before-recreate was already handled by that early-return.)AdManager.canRequestAds consent gate: every load path (app-open,
interstitial, rewarded, banner) AND every show path now skips when consent
hasn't been granted, mirroring Google UMP's ConsentInformation .canRequestAds(). requestUmpConsent stores the result and, when the gate
opens (blocked→allowed), refills the held slots. Google policy: never request
or show an ad while canRequestAds is false. Defaults true so non-UMP /
non-EEA hosts are unaffected.AdConfig.autoRequestUmpConsent (default false): when true,
initialize() runs UMP before the first ad request and gates on the result —
the SDK owns the whole consent flow. umpTagForUnderAgeOfConsent forwards the
under-age flag.AdConfig.disableAppLovinCmpFlow (default true): the AppLovin adapter
disables AppLovin's own Terms & Privacy (CMP) flow so UMP is the single
consent prompt — no double prompt. UMP's result is still forwarded to AppLovin
via setHasUserConsent.bypassSafety: true) no longer shows an
impression before consent is resolved; the show gate also prevents a
previously-loaded ad from showing after consent is revoked.verifySignedVipKey + VipManager.redeemSignedKey verify Ed25519-signed
keys offline against an embedded public key. Only the public key ships, so
a decompiler cannot forge new keys (the old local base64 map could be extracted
and reused infinitely). VIP duration is encoded in the key.AdPreferences redeemed-id store). Global one-time-use still needs a
server — documented as a known offline limitation.cryptography (pure-Dart Ed25519). Tooling: tool/vip_keygen.dart
(generate a key pair) and tool/vip_mint.dart (mint signed keys with the
private key — never shipped). See README → "Signed VIP keys".vip_keys.dart now holds only the public key + demo keys; vip_screen
redeems via redeemSignedKey.ConnectionNotifierTools (nobody did before, so
isConnected silently always returned true and the offline guards never
fired) and subscribes to onStatusChange.initRevision so banner widgets re-init
— within ~1s (debounced) instead of waiting up to 5 min for the poll timer.
Suppressed for VIP members and while uninitialised. Subscription cancelled on
destroy. Test seams: debugConnectivityChanged, debugReconnectDebounce.npa) now actually applied (T02)applyConsentToProviders only set AdMob's global
RequestConfiguration (COPPA/age tags) and never attached the per-request
non-personalized flag, so a user who declined consent could still be served
personalized AdMob ads. The doc comment claimed an npa extra was
forwarded, but no code did so.AdProviderAdapter gains applyConsent(AdConsent). AdMobAdapter maps
!hasUserConsent → AdRequest(nonPersonalizedAds: true) on every load
(banner, interstitial, rewarded, app open); it defaults to non-personalized
until consent is applied and resets to that on dispose. AppLovinAdapter's
implementation is a no-op (it forwards consent via static AppLovinMAX APIs).AdManager calls applyConsent on the adapter at init, from setConsent,
and on any ConsentManager change (auto dialog / set / reset / privacy
screen), so personalization tracks consent across every path.AdScreenRouteLogger now tracks how many PopupRoutes (dialogs, bottom sheets, Cupertino popups) are on the navigation stack and exposes AdScreenRouteLo
AdScreenRouteLogger now tracks how many PopupRoutes (dialogs, bottom
sheets, Cupertino popups) are on the navigation stack and exposes
AdScreenRouteLogger.isDialogOnTop. showAppOpenAdOnResume consults it (plus
AdLoadingDialog.isShowing) and skips the App Open ad while any dialog is
presented — e.g. the consent dialog or a VIP redeem confirmation. Showing a
fullscreen ad over a modal is bad UX and an AdMob policy risk. The counter is
reset by AdManager.destroy() so a mid-dialog teardown can't wedge it._retryRefillAds now returns immediately when the user is a VIP member.
Each load*() already guarded on VIP, so behaviour is unchanged, but this is
a defense-in-depth backstop and avoids a pointless periodic scan/log.The bundled example (example/lib/main.dart) now demonstrates the recommended consent ordering in its splash: AdManager().requestAtt() → AdManager().re
example/lib/main.dart) now demonstrates the recommended
consent ordering in its splash: AdManager().requestAtt() →
AdManager().requestUmpConsent() → AdManager().initialize(). No library /
public-API change vs 1.0.19 — upgrading requires nothing.`AdManager().requestAtt()` / `requestAttIfNeeded()` — show the iOS ATT prompt when needed and return a structured AttResult { status, idfa, allowsTrac
AdManager().requestAtt() / requestAttIfNeeded() — show the iOS ATT
prompt when needed and return a structured AttResult { status, idfa, allowsTracking } (AttStatus enum). No-op on Android; never throws (degrades
to denied). Call it in the splash before requestUmpConsent. Requires
NSUserTrackingUsageDescription in Info.plist. Decoupled from the GDPR
consent flag — the native SDKs read ATT directly for IDFA.resumed. The "foreground = hung" heuristic is now Android-only; iOS relies on
the native hidden/displayFailed callbacks plus the 90 s hard cap.AdSlot.beginReload() (genuine load failures still back off).loading before
the native BannerAd is created (fixes a synchronous-fill race).AppLovinBridge /
GmaBridge) for full behavioural unit-test coverage. No public-API change.Upgrading from 1.0.18 requires no code changes for existing integrations. To use
ATT, add NSUserTrackingUsageDescription and call AdManager().requestAtt().
Version bump only. Runtime behaviour, public API surface, and bundled assets are identical to 1.0.17. Upgrading from 1.0.17 to 1.0.18 requires no code
pubspec.yaml version bump and
flutter pub get.`FirstInstallGuard` (internal, lib/src/vip/_first_install_guard.dart) — protects the firstInstallVipGrace feature against the trivial bypass of "unins
FirstInstallGuard (internal, lib/src/vip/_first_install_guard.dart) —
protects the firstInstallVipGrace feature against the trivial bypass
of "uninstall + reinstall to claim a fresh 24-hour grace window."
Wired automatically inside AdManager.initialize; host apps need no
code changes.kSecAttrAccessibleAfterFirstUnlock, no synchronizable, no
kSecAttrAccessGroup). Keychain entries persist across app uninstall
by default on iOS, so a reinstall on the same device finds the flag
and the guard skips re-granting. Deliberately uses a constant flag
rather than identifierForVendor (IDFV) — Apple resets IDFV when the
user deletes all of a vendor's apps and reinstalls, which would let
a standalone-app reinstall silently bypass the guard.FlutterSharedPreferences.xml (which contains the
prefs.isFirstInstallGraceApplied() flag) on Play Store reinstall,
short-circuiting the outer grace block before the guard runs. The
guard itself returns false (allow grace) on Android — anti-bypass
is performed entirely by the host's AndroidManifest.xml /
<data-extraction-rules> + Google Cloud Backup.AdManager writes the Keychain
anti-bypass flag before the prefs.markFirstInstallGraceApplied()
flag, so a process kill between the two writes leaves the persistent
marker set and the next install on the same device is still blocked.kDebugMode builds skip both hasAlreadyGranted
and markGranted, so QA can iterate on flutter run without the
Keychain signal locking them out of the grace UX. Anti-bypass
validation must happen on signed release builds (TestFlight / Play
Store internal track).false (allow grace) so a transient Keychain
hiccup never denies grace to a legitimate first-time user.markGranted
no-op on Android, idempotency, and fail-open error swallowing.flutter_secure_storage: ^9.2.4 — iOS Keychain wrapper.android/app/src/main/AndroidManifest.xml:<application
android:allowBackup="true"
android:dataExtractionRules="@xml/data_extraction_rules"
android:fullBackupContent="@xml/full_backup_content">
Create android/app/src/main/res/xml/data_extraction_rules.xml
(Android 12+) and full_backup_content.xml (Android 6-11) including
FlutterSharedPreferences.xml so Google Auto Backup restores the
grace flag on Play Store reinstall.
Without these, Android anti-bypass does not work — uninstall +
reinstall always re-grants the grace window. (Acceptable for many
apps; configure Auto Backup only if you want to block this bypass.)play_install_referrer dependency — initially included for an
Android conservative-skip path, removed after research confirmed
Install Referrer cannot detect Play Store reinstall (timestamps
reset per Google's documented behaviour). Real Android anti-bypass
comes from Auto Backup, not Install Referrer.Full English rewrite of `MIGRATION.md` — clear 1.0.14 → 1.0.15 upgrade path (no breaking changes), plus legacy 1.x → 2.x path with auto-migration deta…
README.md — restructured into 13 sections
with table of contents. Quick start expanded into 6 copy-paste steps
any Flutter developer can follow without prior AdMob/AppLovin knowledge.
Added complete public API reference, FAQ, and dedicated Pitfalls section
covering the android:taskAffinity="" issue (the most common cause of
perceived crashes during background → foreground ad cycles).MIGRATION.md — clear 1.0.14 → 1.0.15
upgrade path (no breaking changes), plus legacy 1.x → 2.x path with
auto-migration details. Added Common issues and FAQ sections.doc/architecture.md — deep-dive for
contributors and advanced integrators. Added detailed sections on the
Smart App-Open timeout, Slot-state dismiss watcher, Consent flow
sequence, Memory management contract, and Manifest pitfalls.pubspec.yaml
version bump and flutter pub get.AppLovin App-Open timeout false-positive — old fixed 10 s timeout fired while user was still interacting with the ad (click → browser → return), marki
false and arming the resume guard prematurely.
Replaced with lifecycle-aware polling: re-arms every 5 s while app is
paused (= ad still showing), force-dismisses only when app is foreground
for 2 consecutive ticks without onAdHiddenCallback (hard cap 90 s).BannerAd extends AdWithView which
has no onPaidEvent setter; previous dynamic dispatch silently failed.
Banner revenue is now correctly emitted via BannerAdListener.onPaidEvent
constructor parameter._lastFullscreenDismissAt
was recorded inside the rewarded onDone callback which fires on
reward-earned (mid-video), not on actual dismiss. Replaced with slot-state
watchers that fire on showing → !showing transition for all 3 fullscreen
slots — authoritative dismiss timestamp regardless of adapter quirks.Timer in VipManager
scheduled for the soonest expiresAt. Fires _purgeExpired + _refreshActive
when an entry expires, so the SDK reflects VIP loss without requiring a
full re-init. Especially relevant for short debug grace windows.VipManager.activeListenable; on true → false flip,
triggers loadAppOpenAd + loadInterstitial + loadRewardedAd + preloadBanner
so the user doesn't see "ad not ready" on first show after losing VIP.canShowFullscreenAd / canShowAppOpenOnResume reported "wait 0s" —
sub-second waits truncated to 0. New _fmtWait(ms) helper renders ms when
< 1 s ("wait 645ms") and 1 decimal seconds otherwise ("wait 1.5s")._armSplashBudget now detects appOpenSlot.isShowing on first elapse
and re-arms a 30 s hard cap instead of force-firing markSplashInactive.canShowAppOpenOnResume returned bool — refactored to return
AdSafetyResult (canShow + reason), aligning with canShowFullscreenAd.
Callers can log the specific block reason + remaining wait time.ConsentManager — standalone helper class owning the Cupertino consent
dialog UI, persistence (SharedPreferences), and provider apply pipeline.
Accessible via AdManager().consentManager or ConsentManager.instance.ConsentSettings — persistent user-choice record with hasBeenAsked,
askedAt, JSON serialisation.ConsentDialogStrings — localisation, includes ConsentDialogStrings.vi
for Vietnamese.AdConfig.autoShowConsentDialog (default true) — SDK auto-presents the
dialog ~1 s after markSplashInactive (post-splash, on home), not
during splash flow. Skipped for VIP users.AdConfig.consentDialogPostSplashDelay (default 1 s) — tunable.AdConfig.consentBarrierDismissible (default false).requestUmpConsentFlow(testMode, debugGeography, testIdentifiers, …) —
wraps Google's built-in ConsentInformation + ConsentForm (no extra
dependency, available since google_mobile_ads 6.x).AdManager().requestUmpConsent(…) — auto-applies UMP result to providers.ConsentStatus and DebugGeography from google_mobile_ads
so callers don't need a direct import.AdConfig.firstInstallVipGrace: FirstInstallVipGrace (default auto =
30 s in debug, 24 h in release) — auto-grants a one-time VIP entry on the
very first SDK init for this install. Improves D1 retention by giving
the freshly-installed user an ad-free first session.FirstInstallVipGrace class with auto / disabled / day /
debugShort presets and custom Duration constructor.AdConfig.firstInstallVipKey (default __FIRST_INSTALL__) — VIP entry
key for analytics discrimination.AdPreferences — new keys _keyFirstInstallApplied (one-shot guard)
and _keyFirstInstallAt (epoch-ms install timestamp for analytics).🚀 AdManager singleton CREATED marker fires once per process on cold
start. Two markers in the same logcat session = Android killed and
restarted the process.🚨 lifecycle DETACHED warning when Flutter engine tears down._safeLifecycleLog
so a closure-evaluation throw cannot abort the observer.⏭️ skipped — <reason> logs for
every gate (adapter null, VIP, no network, slot showing, safety reason)
instead of returning silently.onAdDisplayedCallback extended with network, creativeId,
placement, latencyMillis for revenue diagnosis.DebugAdOverlay — new enabled constructor flag plus static
globallyVisible ValueNotifier for runtime toggle (e.g., from a
shake-menu or dev console).AdConfig.autoShowConsentDialog skip path also covers the case where
the user redeems a VIP key during the 1 s post-splash schedule window
(re-checked at fire time).AdManager.processStartedAtMs getter.loadInterstitial / loadRewardedAd / loadAppOpenAd / showInterstitial
/ showRewardedAd / showAppOpenAd skip-path logs now name the specific
reason (adapter null vs VIP vs no network vs already showing vs safety).android:taskAffinity="" on your
MainActivity when using AppLovin. With empty affinity, AppLovin's
AppLovinFullscreenActivity lands in a different Android task; after
user backgrounds + foregrounds and dismisses the ad, the task may be
empty and the user is dropped to launcher. Default affinity (= package
name, by simply omitting the attribute) is safe.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version