@chipmobilesdk/rn-ads 0.6.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,56 @@
 # @chipmobilesdk/rn-ads
 
+## 0.7.0
+
+### Minor Changes
+
+- The ads instance is split by responsibility, and the banner host's wiring is off the
+  public type. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - `AdsInstance` no longer has an `internals` field. It was undocumented, but any
+    consumer could use it to emit `impression` or `reward_earned` into the event stream
+    used for revenue reconciliation. `AdsBanner` now reaches an instance's wiring through
+    a private registry, so a banner given an instance the app wrote by hand renders
+    nothing instead of throwing.
+  - Banner events carry the instance's clock (`createAds({ now })`), like full-screen
+    events, and resolving a banner during render no longer mints a correlation id.
+  - `allTestAdUnits()` moved from the engine module to `@chipmobilesdk/rn-ads/testing`.
+  - Rewards from AdMob go through the one `normalizeReward`; an unused consent port guard
+    and the throttle's unused `reset`/`lastRequestAt` are gone.
+  - Internally, `createAds` is now a 142-line composition root over `core/instance/`
+    (gate, init, load, show, consent, internals), down from one 1,899-line closure. Every
+    path that closes the request gate goes through one teardown.
+
+- Four fixes to how ads behave around throttling, retries and show timeouts. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - A banner refused by the request throttle now tries again by itself once the window
+    passes. Before, it stayed empty until it was remounted, so a banner on a screen the
+    user returned to within a minute never filled.
+  - A load retry waits at least as long as the placement's `minRequestIntervalMs`
+    requires, so a retry policy cannot request faster than the floor allows. The
+    `retry_scheduled` event reports the wait actually used.
+  - A request AdMob refuses outright (an invalid request or ad unit, a missing app id)
+    is the new non-retryable `provider_rejected` code instead of a retryable
+    `provider_error`, so a retry policy no longer spends billable requests on it. Engines
+    may classify a failure with the new optional `kind` on the `failed` event.
+  - A show that times out and then opens anyway is reported once, not twice. The late
+    ad holds the full-screen lock until it is dismissed, and its reward and dismissal
+    still reach the app.
+
+- The banner renders through the engine port. `AdsEngine` has an optional `banner`
+  capability (`isAvailable()` and a `Component` with neutral props: `adUnitId`,
+  `personalizedAds`, `onLoaded`, `onFailed`, `onImpression`, `onClicked`), and the AdMob
+  adapter supplies the adaptive `BannerAd` there. `AdsBanner` no longer loads the AdMob
+  bridge itself, so a custom or future iOS engine provides its own banner, and the fake
+  engine from `./testing` renders one in tests without a mocked native module. An engine
+  without `banner` keeps working; its banners report `unavailable`. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+### Patch Changes
+
+- Internal: no module in these packages is over 500 lines any more. The camera controller's session I/O moved to `sessionRuntime` and its contract to `contract.ts`; the Play adapter's shape translation to `iapShapes`; the purchase flow's failure mapping and its receipt-validation hook to modules of their own; the AI client's quota request to `quotaRequest`; the in-memory adapter's attachments and the fake ads engine's clock likewise. Behaviour is unchanged — the splits are by responsibility, and every package's suite passes as it stood. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  The repository also measures what it promised: `npm run perf` prints the median of nine runs of the deterministic hot paths against written budgets (recurrence expansion, theme construction, translation lookup, chart geometry, filter compilation), the demo app has a Performance screen reporting startup phases, time to interactive and the same benchmarks on Hermes, and `npm run check:file-size` keeps the limit from drifting. The budgets and the measured figures are recorded in `docs/standards.md` §VI.
+
 ## 0.6.0
 
 ### Minor Changes

package/README.md

@@ -273,7 +273,9 @@ ads.subscribeEvents(event => {
 A config value outside its band names its own field and code: a timeout or validity window is `timeout_out_of_bounds`, a retry policy `retry_out_of_bounds`, a placement's `minRequestIntervalMs` `invalid_config`.
 
 Retryable: `no_fill` `network_error` `load_timeout` `show_timeout` `ad_expired` `not_ready` `busy` `consumed` `app_inactive` `provider_error`
-Not retryable: `invalid_config` `duplicate_placement_key` `missing_ad_unit_id` `format_mismatch` `placement_not_found` `production_in_dev_build` `timeout_out_of_bounds` `retry_out_of_bounds` `unsupported_platform` `provider_missing` `disabled` `consent_required` `consent_undetermined` `requires_reinitialization` `internal_error`
+Not retryable: `invalid_config` `duplicate_placement_key` `missing_ad_unit_id` `format_mismatch` `placement_not_found` `production_in_dev_build` `timeout_out_of_bounds` `retry_out_of_bounds` `unsupported_platform` `provider_missing` `disabled` `consent_required` `consent_undetermined` `requires_reinitialization` `provider_rejected` `internal_error`
+
+`provider_rejected` (0.7.0) means AdMob refused the request itself — an invalid request or ad unit, a missing app id — so a retry policy does not spend more requests on it. Before, those were `provider_error` and were retried.
 
 Attach any logger or analytics you already use. The package depends on none:
 
@@ -804,7 +806,7 @@ On device, verify with Google's official test ads only. `npm run android`, then
 Adding iOS contributes exactly three things and changes **nothing** you have already written:
 
 1. **`PlacementDefinition.iosAdUnitId`** — the optional field already exists in v1's type, so existing Android-only catalogs stay valid.
-2. **A second engine adapter** behind the existing `AdsEngine` port. The port names no platform and no provider; that is what makes this additive.
+2. **A second engine adapter** behind the existing `AdsEngine` port. The port names no platform and no provider; that is what makes this additive. The banner is part of the port too (`AdsEngine.banner`, since 0.7.0): an adapter supplies its own banner component, which receives neutral props (`adUnitId`, `personalizedAds`, `onLoaded`, `onFailed`, `onImpression`, `onClicked`), and `AdsBanner` renders whatever the engine offers.
 3. **iOS entries in the private test-ad-unit table.**
 
 Your `createAds`, `initialize`, `load`, `show`, `AdsBanner`, and every subscription keep their current signatures. The exported state, event, and error models do not change.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@chipmobilesdk/rn-ads",
-	"version": "0.6.0",
+	"version": "0.7.0",
 	"private": false,
 	"license": "UNLICENSED",
 	"main": "src/index.ts",

package/skills/sdk-rn-ads/SKILL.md

@@ -174,7 +174,8 @@ policy; everything else returns a typed result rather than throwing) · `AdsProv
 `UNDECIDED_WARNING_BOUNDS`, `DEFAULT_BANNER_MIN_REQUEST_INTERVAL_MS`,
 `DEFAULT_FULL_SCREEN_MIN_REQUEST_INTERVAL_MS`, `MIN_REQUEST_INTERVAL_BOUNDS`,
 `defaultMinRequestIntervalMs` · `createFakeAdsEngine`, `createTestClock`,
-`runAdsEngineConformance` from `@chipmobilesdk/rn-ads/testing` (test doubles only).
+`runAdsEngineConformance`, `allTestAdUnits` from `@chipmobilesdk/rn-ads/testing` (test
+doubles only).
 
 Instance: `initialize`, `updatePrivacy`, `setEnabled`, `setEnablement`, `setAppActive`,
 `consent`, `getStatus`, `subscribeStatus`, `load`, `show`, `getPlacementState`,