[anglinb]

Problem

When a paywall is embedded with PaywallComposable in the app's own Activity, trial reminders are never scheduled. A customer hit this on 2.8.4 and 2.8.8 with a custom PurchaseController, and it is still the case in 2.9.0.

Three paths schedule notifications, and all of them go through PaywallNotifications.forPaywall:

• the fallback trial reminder in DependencyContainer.notifyOfTransactionComplete
• the paywall's ScheduleNotification message in Superwall.eventDidOccur
• web checkout reminders in DependencyContainer.scheduleTrialNotifications

forPaywall only knew about SuperwallPaywallActivity and InWindowPaywallHost. For an embedded view it returned null, and the SDK logged No paywall host available to schedule fallback notifications without scheduling anything.

Change

• forPaywall gets a third case: the Activity the view is embedded in, which PaywallBuilder.activity(...) sets on encapsulatingActivity. A finishing or destroyed Activity doesn't count. The current-activity fallback still only stands in for a SuperwallPaywallActivity, so a paywall that isn't embedded anywhere still gets nothing.
• PaywallNotifications.forEmbeddingActivity asks for POST_NOTIFICATIONS through requestPermissionFrom, the helper InWindowPaywallHost already uses. That means the activity result registry on a ComponentActivity (Compose apps) and the headless PermissionRequestActivity on a plain Activity.
• PaywallView holds the instance, so repeated lookups reuse it and only one permission waiter is kept. It is deliberately not released in cleanup(): PaywallComposable releases the view right after a purchase, often while the permission prompt is still on screen, and a grant that comes after that should still schedule the reminders. A pending request is released when a lifecycle-aware host Activity is destroyed, because its answer can no longer arrive.
• An in-window host that is closing returns null as before, rather than falling through to the embedded case.

Tests

The new EmbeddedPaywallNotificationsTest uses Robolectric with a ComponentActivity:

• an embedded paywall's notifications are scheduled, and later lookups reuse the same instance
• the permission is requested through the registry, and a grant that arrives after cleanup() still schedules
• a request still pending when the Activity is destroyed is released, and nothing is scheduled
• a paywall that isn't embedded anywhere gets no notifications from the current-activity fallback

./gradlew :superwall:testDebugUnitTest --tests '*EmbeddedPaywallNotificationsTest' --tests '*InWindowPaywallHostTest' --tests '*InWindowComponentActivityHostTest'
EmbeddedPaywallNotificationsTest   tests=4  failures=0
InWindowComponentActivityHostTest  tests=3  failures=0
InWindowPaywallHostTest            tests=19 failures=0

Not verified

• I haven't checked whether paywallManager.currentView points at an embedded view during web checkout, which the web-checkout path relies on. The other two paths take the view directly.
• I haven't tested on a device with PaywallComposable.

🌸 Shipped with Kanna — an open-source workspace for all your coding agents. Written by claude/opus.

[maple-review-bot]

Maple review

🟢 Confidence 10/10 · safe to merge. The focused change reuses existing permission and scheduling paths, with regression tests covering embedded-host selection and pending-request lifetime.
_{no findings · tests covered · risk medium · 1/1 new units observable}

Adds trial-reminder scheduling for embedded paywalls while preserving pending permission results after view cleanup. The change is safe to merge; no confirmed defects found.

_{b4b39b6 · What was checked, coverage and telemetry details are on the Maple / review check. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.}