admanagekit-mcp-server 1.2.3 → 1.2.5

package/content/README.md

@@ -5,9 +5,13 @@
 
 AdManageKit is a comprehensive Android library designed to simplify the integration and management of Google AdMob ads, Google Play Billing, and User Messaging Platform (UMP) consent.
 
-**Latest Version `4.4.4`** is a **critical billing hotfix**. No API changed. It repairs a regression introduced in 4.4.3, where the Play Billing connection was never started at all: `connectToGooglePlayBilling()` guarded on `billingClient.isReady()`, which reports `true` the instant a client is built, so `startConnection(...)` was skipped on every fresh client. Setup never ran, no product details or entitlement were ever fetched, and there was **no failure callback and no error log** to explain it. **If you ship the billing module on 4.4.3, upgrade.** Also fixes a long-standing bug where a timed-out setup reported itself as initialized — permanently suppressing the host app's `if (!initBillingFinish) initBilling()` retry — and adds `DEBUG` logging across the billing connection lifecycle. See [Release Notes v4.4.4](docs/release-notes/RELEASE_NOTES_v4.4.4.md).
+**Latest Version `4.4.6`** is a **maintenance release**. No API changed and no library source file changed — the whole diff is dependencies and docs. It **downgrades** `androidx.work:work-runtime` **2.11.2 → 2.9.1**: WorkManager **2.10 and 2.11** call `JobScheduler.forNamespace` whenever `SDK_INT >= 34`, and modified or spoofed ROMs that report API 34 over an older framework have no such method — the `NoSuchMethodError` then kills the **whole process during bind** (`Unable to get provider androidx.startup.InitializationProvider`), because `androidx.startup` builds WorkManager in a `ContentProvider` installed before `Application.onCreate` runs. 2.9.1 is the last release without that call. AdManageKit has no WorkManager code of its own; the pin only steers the version the ads SDK pulls in, and since Gradle resolves the **highest** version in the graph, an app that declares 2.10/2.11 itself keeps the crash — pin `androidx.work:work-runtime:2.9.1` in your app too. Also picks up AGP **9.4.0**, Firebase BOM **34.19.0**, Compose BOM **2026.09.00** and Yandex Mobile Ads **8.4.0**. See [Release Notes v4.4.6](docs/release-notes/RELEASE_NOTES_v4.4.6.md).
 
-> ⚠️ **4.4.3 is superseded.** Its billing regression makes purchases unusable; use 4.4.4.
+**Version `4.4.5`** is a **patch release**. No API changed. It fixes a `BannerAdView` bug that renders a **blank banner slot inside Jetpack Compose**: swapping the shimmer placeholder for the loaded `AdView` raises an ordinary `requestLayout()`, which cannot cross Compose's `AndroidView` interop boundary once any ancestor already carries a pending layout flag — so Compose never re-measured the subtree and the freshly attached `AdView` was left at 0×0. The ad loaded, `onAdLoaded`/`onAdImpression` fired and the impression was **logged and billed**, but the slot stayed blank until a rotation or resize forced a full traversal. Both the AdMob and `BannerWaterfall` success paths now force the measure/layout pass themselves. Also picks up the Next-Gen GMA SDK **1.4.0**, AGP **9.3.2** and Firebase BOM **34.18.0**. See [Release Notes v4.4.5](docs/release-notes/RELEASE_NOTES_v4.4.5.md).
+
+**Version `4.4.4`** is a **critical billing hotfix**. No API changed. It repairs a regression introduced in 4.4.3, where the Play Billing connection was never started at all: `connectToGooglePlayBilling()` guarded on `billingClient.isReady()`, which reports `true` the instant a client is built, so `startConnection(...)` was skipped on every fresh client. Setup never ran, no product details or entitlement were ever fetched, and there was **no failure callback and no error log** to explain it. **If you ship the billing module on 4.4.3, upgrade.** Also fixes a long-standing bug where a timed-out setup reported itself as initialized — permanently suppressing the host app's `if (!initBillingFinish) initBilling()` retry — and adds `DEBUG` logging across the billing connection lifecycle. See [Release Notes v4.4.4](docs/release-notes/RELEASE_NOTES_v4.4.4.md).
+
+> ⚠️ **4.4.3 is superseded.** Its billing regression makes purchases unusable; use 4.4.4 or newer.
 
 **Version `4.4.3`** is a bug-fix and dependency release. No API changed. Two silent-failure bugs are fixed, both of which cost money: a **rewarded load the manager had given up on could sabotage the load that replaced it** — discarding an ad a newer load had just delivered, and clearing the "loading" flag out from under a request still in flight — and **billing could stop acknowledging purchases for the rest of the process**, which lets Play auto-refund a completed purchase on day 3. Acknowledgment also no longer requires the purchase to match a configured product id. Picks up the Next-Gen GMA SDK **1.3.1**, Yandex Mobile Ads **8.3.0**, and refreshed AndroidX/Firebase/Compose BOMs. See [Release Notes v4.4.3](docs/release-notes/RELEASE_NOTES_v4.4.3.md).
 
@@ -35,7 +39,7 @@ Since **4.2.0** the library runs on the Google Mobile Ads **Next-Gen SDK** (`ads
 
 ## Next-Gen GMA SDK
 
-As of v4.2.0, AdManageKit runs on Google's **Next-Gen Google Mobile Ads SDK** (`com.google.android.libraries.ads.mobile.sdk`, stable `1.3.1` as of 4.4.3) instead of the legacy `com.google.android.gms:play-services-ads`. This isn't a branch or an opt-in — it's the only version of AdManageKit going forward.
+As of v4.2.0, AdManageKit runs on Google's **Next-Gen Google Mobile Ads SDK** (`com.google.android.libraries.ads.mobile.sdk`, stable `1.4.0` as of 4.4.6) instead of the legacy `com.google.android.gms:play-services-ads`. This isn't a branch or an opt-in — it's the only version of AdManageKit going forward.
 
 ### Why the move
 
@@ -199,15 +203,15 @@ dependencyResolutionManagement {
 **Step 2:** Add dependencies to your app's `build.gradle`:
 
 ```groovy
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.4'
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.6'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.6'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.6'
 
 // For Jetpack Compose support
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.6'
 
 // For Yandex Ads multi-provider support
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.6'
 ```
 
 **Step 3:** Ensure your app's `compileSdk` is **37 or higher** (required transitively as of 4.2.0).
@@ -781,6 +785,8 @@ Register it **before** `initBilling`. Products land in `unfetched` when the id i
 - [Multi-Provider Waterfall](docs/MULTI_PROVIDER_WATERFALL.md)
 - [Yandex Integration](docs/YANDEX_INTEGRATION.md)
 - [Billing Integration Guide](docs/APP_PURCHASE_GUIDE.md)
+- [Release Notes v4.4.6](docs/release-notes/RELEASE_NOTES_v4.4.6.md)
+- [Release Notes v4.4.5](docs/release-notes/RELEASE_NOTES_v4.4.5.md)
 - [Release Notes v4.4.4](docs/release-notes/RELEASE_NOTES_v4.4.4.md)
 - [Release Notes v4.4.3](docs/release-notes/RELEASE_NOTES_v4.4.3.md)
 - [Release Notes v4.4.2](docs/release-notes/RELEASE_NOTES_v4.4.2.md)

package/content/docs/release-notes/RELEASE_NOTES_v4.4.5.md

@@ -0,0 +1,63 @@
+# Release Notes — v4.4.5
+
+**Release Date:** 2026-08-27
+
+## Overview
+
+v4.4.5 is a **patch release**. No API was added, removed or changed.
+
+It fixes a `BannerAdView` bug that renders a **blank banner slot inside Jetpack Compose**: the ad loads, reports success, logs its impression — and nothing is drawn, because the freshly attached `AdView` is left measured at 0×0. It also picks up the Google Mobile Ads Next-Gen SDK **1.4.0**, AGP **9.3.2** and Firebase BOM **34.18.0**.
+
+Upgrading is a drop-in from 4.4.x.
+
+---
+
+## Fixed
+
+### Banner ad loaded but rendered blank under Compose interop
+
+`BannerAdView` builds its slot as a shimmer placeholder, then swaps in the real `AdView` when the load succeeds — `layBannerAd.removeAllViews()`, `addView(adView, ...)`, hide the shimmer. Swapping the children of a `ViewGroup` raises an ordinary `requestLayout()`, and in a plain View hierarchy that is enough.
+
+Inside Compose's `AndroidView` interop it is not. `View.requestLayout()` only walks up while each ancestor reports `isLayoutRequested == false`; the moment one already carries a pending layout flag, propagation stops there. For an interop subtree the request has to reach `AndroidViewsHandler` — the **only** place that turns a View layout request into a `LayoutNode.requestRemeasure()`. If any ancestor on the way up (the `ViewFactoryHolder` included) is already flagged, the request dies below that point and Compose never re-measures the subtree.
+
+The consequence is that the banner keeps the measurement it had while the shimmer was mounted, and the `AdView` attached after that pass is never measured at all:
+
+- the ad loads successfully, `onAdLoaded` and `onAdImpression` both fire
+- the impression is logged and billed
+- the slot renders **blank** — the container is still sized for the shimmer, the ad view is 0×0
+- it stays blank until something unrelated forces a full traversal (a rotation, a keyboard, a resize)
+
+Recomposition does not rescue it either: a semantics or `testTag` change does not invalidate measurement.
+
+Both success paths — the AdMob path (`handleAdLoadSuccess`) and the multi-provider `BannerWaterfall` path (`onBannerLoaded`) — now call a new private `forceRelayoutAfterAdSwap()` after the swap. It walks up from the banner flagging each ancestor with `forceLayout()` (which makes `View.measure()` re-run even when the `MeasureSpec`s are unchanged — exactly what a swapped-in child needs), stopping at Compose's interop holder when there is one, and then requests the layout from **above** that holder, where `AndroidViewsHandler.requestLayout()` sees `child.isLayoutRequested == true` and schedules the remeasure. With no Compose holder in the chain, normal propagation works once the chain is flagged and a plain `requestLayout()` is issued.
+
+Because a request raised while a layout pass is already running can still be dropped (`ViewRootImpl.requestLayoutDuringLayout`), the pass is repeated once on the next frame via `post { ... }`, which also logs the resulting container and ad-view dimensions through `AdDebugUtils` for diagnosis.
+
+There is no behavior change for banners hosted in XML — the extra pass is a no-op when the layout is already correct.
+
+## Changed
+
+- **Dependency updates:** Google Mobile Ads Next-Gen SDK **1.3.1 → 1.4.0**, Android Gradle Plugin **9.3.0 → 9.3.2**, Firebase BOM **34.17.0 → 34.18.0**, org.json (test only) **20260719 → 20260814**. Play Billing stays at **9.1.0**, Kotlin at **2.2.10**, Yandex Mobile Ads at **8.3.0**, Compose BOM at **2026.08.00**
+
+## Notes
+
+- The fix is not test-covered: it depends on a real Compose interop measure/layout traversal, which the Robolectric harness cannot drive faithfully. It was verified on-device against a Compose-hosted banner slot. The existing 176 tests are unaffected
+- No billing changes in this release
+
+---
+
+## Upgrading
+
+```gradle
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.5'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
+
+// For Jetpack Compose support
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.5'
+
+// For Yandex Ads multi-provider support
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.5'
+```
+
+No code changes are required.

package/content/docs/release-notes/RELEASE_NOTES_v4.4.6.md

@@ -0,0 +1,110 @@
+# Release Notes — v4.4.6
+
+**Release Date:** 2026-09-14
+
+## Overview
+
+v4.4.6 is a **maintenance release**. No API was added, removed or changed, and **no library source file changed** — the entire diff is `gradle/libs.versions.toml`, the five publication blocks, and documentation.
+
+The one change worth reading is a deliberate **downgrade** of WorkManager to **2.9.1**. WorkManager 2.10 and 2.11 call `JobScheduler.forNamespace` on any device reporting `SDK_INT >= 34`; on modified or spoofed ROMs that report API 34 over an older framework the method is absent, and the resulting `NoSuchMethodError` kills the process at startup via `androidx.startup`'s `WorkManagerInitializer`. 2.9.1 is the last release without that call. It also picks up AGP **9.4.0**, Firebase BOM **34.19.0**, Compose BOM **2026.09.00** and Yandex Mobile Ads **8.4.0**.
+
+Upgrading is a drop-in from 4.4.x.
+
+---
+
+## Changed
+
+### WorkManager pinned back to 2.9.1 (a downgrade, on purpose)
+
+`androidx.work:work-runtime` moves **2.11.2 → 2.9.1**. This is the only dependency in the catalog moving backwards, and it is intentional.
+
+**The defect.** WorkManager **2.10 and 2.11** call `android.app.job.JobScheduler.forNamespace` whenever `Build.VERSION.SDK_INT >= 34`. That method genuinely exists on API 34 — but modified and spoofed ROMs that *report* API 34 while running an older framework underneath do not have it. Constructing the WorkManager singleton on such a device throws `NoSuchMethodError`.
+
+That throw is fatal rather than merely inconvenient because `androidx.startup` auto-initializes WorkManager through `WorkManagerInitializer`, which runs from `InitializationProvider` — a `ContentProvider`. `ActivityThread.handleBindApplication` installs content providers **after** `Application.attachBaseContext` but **before** `Application.onCreate`, so there is no user code on the stack to catch it and nothing in the app has run yet. The process dies during bind:
+
+```
+Fatal Exception: java.lang.RuntimeException: Unable to get provider
+androidx.startup.InitializationProvider: java.lang.NoSuchMethodError:
+No virtual method forNamespace(Ljava/lang/String;)Landroid/app/job/JobScheduler;
+in class Landroid/app/job/JobScheduler; or its super classes
+(declaration of 'android.app.job.JobScheduler' appears in /system/framework/framework.jar)
+    at android.app.ActivityThread.installProvider(ActivityThread.java:7467)
+    at android.app.ActivityThread.installContentProviders(ActivityThread.java:6973)
+    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6744)
+```
+
+In a minified build the `StartupException` between the two appears under its obfuscated name (`y40:` or similar), so match on the `InitializationProvider` + `forNamespace` pair rather than on the middle frame. `declaration ... appears in /system/framework/framework.jar` is the confirmation that the device's framework really is older than the API level it advertises.
+
+**2.9.1 is the last release without that call**, which is why the pin lands exactly there rather than at some newer 2.10.x or 2.11.x patch — the call is present throughout both lines.
+
+**This is a host-device problem, not an ads problem.** No source file in any of AdManageKit's five modules references `androidx.work`. The dependency is declared purely to control which version lands in the graph — the Next-Gen GMA SDK asks for `work-runtime:2.7.0` transitively, and this entry is what decides where that resolves. The downgrade changes nothing about the library's behavior, surface, or minimum requirements; it only moves a pin.
+
+**The pin does not override your app.** It is an `implementation` dependency, so it lands in the published POM at `runtime` scope, and Gradle's conflict resolution still picks the **highest** version across the whole graph. If your app declares 2.10 or 2.11 directly, or depends on anything that does, you resolve that version and you keep the crash. Check what you actually resolve:
+
+```bash
+./gradlew :app:dependencies --configuration releaseRuntimeClasspath | grep androidx.work
+```
+
+If that shows 2.10.x or 2.11.x and you are seeing `NoSuchMethodError` on `JobScheduler.forNamespace` in your startup crash reports, pin it in the app as well:
+
+```kotlin
+dependencies {
+    implementation("androidx.work:work-runtime:2.9.1")
+}
+```
+
+**If you need 2.10+ APIs**, do not downgrade your app to match the library. Take the auto-initializer out of the startup path instead, so a failure is catchable rather than fatal — remove `WorkManagerInitializer` in the manifest and initialize WorkManager yourself inside a guard:
+
+```xml
+<provider
+    android:name="androidx.startup.InitializationProvider"
+    android:authorities="${applicationId}.androidx-startup"
+    tools:node="merge">
+    <meta-data
+        android:name="androidx.work.WorkManagerInitializer"
+        android:value="androidx.startup"
+        tools:node="remove" />
+</provider>
+```
+
+Then have your `Application` implement `androidx.work.Configuration.Provider`. WorkManager falls back to on-demand initialization at the first `WorkManager.getInstance(context)` call — which happens on your own thread, in your own code, where a `NoSuchMethodError` can be caught and degrade that one feature instead of killing the process. Nothing in AdManageKit depends on which version resolves, or on WorkManager being initialized at all.
+
+### Other dependency updates
+
+- Android Gradle Plugin **9.3.2 → 9.4.0**
+- Firebase BOM **34.18.0 → 34.19.0**
+- Compose BOM **2026.08.00 → 2026.09.00**
+- Yandex Mobile Ads **8.3.0 → 8.4.0**
+- Robolectric (test only) **4.16.1 → 4.17**
+
+Unchanged: Google Mobile Ads Next-Gen SDK **1.4.0**, Play Billing **9.1.0**, Kotlin **2.2.10**, UMP **4.0.0**, Compose compiler **1.5.8**.
+
+## Fixed
+
+### A stray leading space in the `workRuntime` catalog entry
+
+The downgraded version was written as `" 2.9.1"` — with a leading space. Gradle does not trim version strings, so it treats that as a distinct and unresolvable coordinate rather than 2.9.1. Caught before tagging; the published 4.4.6 resolves `androidx.work:work-runtime:2.9.1` cleanly, verified against `:AdManageKit:dependencies`.
+
+## Notes
+
+- No behavioral change in any ad, billing, consent or waterfall path. The existing 176 tests pass unchanged
+- Robolectric stays pinned to SDK 35 via `robolectric.properties`; the 4.17 bump does not change that
+- There is nothing to migrate — upgrading is a one-line version bump from 4.4.5
+
+---
+
+## Upgrading
+
+```gradle
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.6'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.6'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.6'
+
+// For Jetpack Compose support
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.6'
+
+// For Yandex Ads multi-provider support
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.6'
+```
+
+No code changes are required.

package/content/wiki/Ad-Loading-Strategies.md

@@ -1,4 +1,4 @@
-# Ad Loading Strategies - AdManageKit v4.4.4
+# Ad Loading Strategies - AdManageKit v4.4.5
 
 ## Overview
 

package/content/wiki/App-Open-Ads.md

@@ -1,10 +1,10 @@
-# App Open Ads - AdManageKit v4.4.4
+# App Open Ads - AdManageKit v4.4.5
 
 ## Overview
 
 AdManageKit provides lifecycle-aware app open ad management through `AppOpenManager`. App open ads display when users launch or return to your app, with support for loading strategies, ad freshness enforcement, welcome dialogs, activity/screen exclusion, and the multi-provider waterfall.
 
-**Library Version**: v4.4.4
+**Library Version**: v4.4.5
 
 ## Features
 
@@ -23,9 +23,9 @@ AdManageKit provides lifecycle-aware app open ad management through `AppOpenMana
 
 ```groovy
 dependencies {
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
 }
 ```
 

package/content/wiki/Banner-Ads.md

@@ -1,10 +1,10 @@
-# Banner Ads - AdManageKit v4.4.4
+# Banner Ads - AdManageKit v4.4.5
 
 ## Overview
 
 AdManageKit provides `BannerAdView` for banner ad integration with every standard AdMob size, adaptive banners, collapsible banners, a size-aware loading shimmer, auto-refresh, and smart retry logic.
 
-**Library Version**: v4.4.4
+**Library Version**: v4.4.5
 
 ## Features
 
@@ -23,8 +23,8 @@ AdManageKit provides `BannerAdView` for banner ad integration with every standar
 
 ```groovy
 dependencies {
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
 }
 ```
 

package/content/wiki/Billing-Integration.md

@@ -7,8 +7,8 @@ AdManageKit provides a comprehensive billing integration module (`admanagekit-bi
 ### 1. Add Dependency
 
 ```groovy
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.4'
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.5'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
 ```
 
 ### 2. Define Products

package/content/wiki/Configuration.md

@@ -1,4 +1,4 @@
-# Configuration - AdManageKit v4.4.4
+# Configuration - AdManageKit v4.4.5
 
 ## Overview
 

package/content/wiki/Home.md

@@ -6,7 +6,14 @@
 
 AdManageKit is a comprehensive Android library designed to simplify the integration and management of Google AdMob ads, Google Play Billing, and User Messaging Platform (UMP) consent.
 
-**Latest Version: `4.4.4`**
+**Latest Version: `4.4.5`**
+
+## What's New in 4.4.5
+
+Patch release, no API changes.
+
+- **A banner loaded successfully but rendered blank under Compose** — `BannerAdView` swaps the shimmer placeholder for the loaded `AdView`, which raises an ordinary `requestLayout()`. That request cannot cross Compose's `AndroidView` interop boundary once any ancestor already carries a pending layout flag, so Compose never re-measured the subtree and the freshly attached `AdView` was left at 0×0. The ad loaded, `onAdLoaded`/`onAdImpression` fired and the impression was logged and billed, but the slot stayed blank until a rotation or resize forced a full traversal. Both the AdMob and `BannerWaterfall` success paths now force the measure/layout pass themselves; XML-hosted banners are unaffected
+- **Dependencies** — Next-Gen GMA SDK 1.4.0, Android Gradle Plugin 9.3.2, Firebase BOM 34.18.0
 
 ## What's New in 4.4.4
 
@@ -20,7 +27,7 @@ Critical billing hotfix, no API changes. **If you ship the billing module on 4.4
 
 Bug-fix and dependency release, no API changes. Two silent-failure bugs, both of which cost money.
 
-> ⚠️ 4.4.3's billing regression makes purchases unusable — use 4.4.4.
+> ⚠️ 4.4.3's billing regression makes purchases unusable — use 4.4.4 or newer.
 
 - **A timed-out rewarded load could sabotage the one that replaced it** — a request handed to the SDK cannot be cancelled, and when it finally reported back it could discard an ad a *newer* load had just delivered, clear the loading flag out from under a request still in flight, and fail callers waiting on a load that had not finished. Every load path now carries a generation token, and a late ad is kept for the next show instead of dropped
 - **Billing could stop acknowledging purchases for the rest of the process** — the connection flag could latch `false` after one disconnect while the client was actually ready, disabling every purchase re-query including the acknowledgment retry. Play auto-refunds an unacknowledged purchase after 3 days
@@ -94,15 +101,15 @@ dependencyResolutionManagement {
 **Step 2:** Add dependencies to your app's `build.gradle`:
 
 ```groovy
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.4'
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.5'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
 
 // For Jetpack Compose support
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.5'
 
 // For Yandex Ads multi-provider support
-implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.4'
+implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.5'
 ```
 
 **Step 3:** Ensure your app's `compileSdk` is **37 or higher** (required transitively as of 4.2.0).

package/content/wiki/Interstitial-Ads.md

@@ -1,10 +1,10 @@
-# Interstitial Ads - AdManageKit v4.4.4
+# Interstitial Ads - AdManageKit v4.4.5
 
 ## Overview
 
 AdManageKit provides a complete interstitial ad stack with `AdManager` and the fluent `InterstitialAdBuilder`. Features include loading strategies, automatic retry, frequency controls, splash screen support, and Jetpack Compose utilities.
 
-**Library Version**: v4.4.4
+**Library Version**: v4.4.5
 
 ## What's New
 
@@ -23,11 +23,11 @@ AdManageKit provides a complete interstitial ad stack with `AdManager` and the f
 
 ```groovy
 dependencies {
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.4'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-billing:v4.4.5'
     // Optional - Jetpack Compose
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.4'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.5'
 }
 ```
 

package/content/wiki/Jetpack-Compose.md

@@ -1,18 +1,18 @@
-# Jetpack Compose Integration - AdManageKit v4.4.4
+# Jetpack Compose Integration - AdManageKit v4.4.5
 
 ## Overview
 
 AdManageKit provides first-class Jetpack Compose support with composable functions for all ad types, state management helpers, and programmatic native ad loading.
 
-**Library Version**: v4.4.4
+**Library Version**: v4.4.5
 
 ## Installation
 
 ```groovy
 dependencies {
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.4'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-compose:v4.4.5'
 }
 ```
 

package/content/wiki/Multi-Provider-Waterfall.md

@@ -38,11 +38,11 @@ This is fully backward compatible -- if no provider chains are configured, all e
 
 ```groovy
 dependencies {
-    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4"
-    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4"
+    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5"
+    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5"
 
     // Add Yandex provider
-    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.4"
+    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.5"
 }
 ```
 

package/content/wiki/NativeAdManager.md

@@ -1,10 +1,10 @@
-# Native Ads - AdManageKit v4.4.4
+# Native Ads - AdManageKit v4.4.5
 
 ## Overview
 
 AdManageKit provides comprehensive native ad support with caching, multiple formats, and the new `NativeTemplateView` (v2.6.0+). Native ads blend seamlessly with your app's content while maximizing engagement.
 
-**Library Version**: v4.4.4
+**Library Version**: v4.4.5
 
 ## Features
 
@@ -19,8 +19,8 @@ AdManageKit provides comprehensive native ad support with caching, multiple form
 
 ```groovy
 dependencies {
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4'
-    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5'
+    implementation 'com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5'
 }
 ```
 

package/content/wiki/Yandex-Integration.md

@@ -10,9 +10,9 @@ The `admanagekit-yandex` module provides Yandex Ads SDK providers for the multi-
 
 ```groovy
 dependencies {
-    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.4"
-    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.4"
-    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.4"
+    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit:v4.4.5"
+    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-core:v4.4.5"
+    implementation "com.github.i2hammad.AdManageKit:ad-manage-kit-yandex:v4.4.5"
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "admanagekit-mcp-server",
-  "version": "1.2.3",
+  "version": "1.2.5",
   "description": "MCP server for AdManageKit Android library - documentation lookup and code generation",
   "main": "dist/index.js",
   "bin": {