feat(billing): auto-wire native Play/StoreKit client — commonMain-only consumer integration

[therajanmaurya]

Auto-wire native billing — consumers integrate in commonMain only

Makes the native in-app-purchase client resolve per platform automatically, so a consumer gets real Google Play Billing on Android with ZERO androidMain wiring — just PayCraft.initialize(apiKey) from commonMain. Previously consumers had to load paycraftPlayBillingModule + supply an activityProvider in their Application (a platform-specific bootstrap leak that defeats the KMP one-line-setup goal, and that left web checkout as the Android default → the anti-steering Play-policy violation that flagged com.sensei.social).

How

• platformDefaultNativeBillingClient() — new expect (commonMain) + actual per platform:
  • Android → the real PlayBillingNativeClient (Play Billing v8), auto-wired from the Application context + foreground Activity.
  • iOS / JVM / JS / WasmJS → null → web checkout (iOS StoreKit2 stays an explicit opt-in since it needs the app's Swift bridge).
• PayCraftModule now binds single<NativeBillingClient> { platformDefaultNativeBillingClient() ?: WebCheckoutNativeBillingClient() } (was hard-coded WebCheckout).
• PayCraftInitializer (the existing androidx-startup Initializer that already captures the Application context) now ALSO registers foreground-Activity tracking, so launchBillingFlow resolves the resumed Activity with no consumer plumbing.
• PayCraftPlatform.android gains applicationContextOrNull() + WeakReference-based currentActivityOrNull() / startActivityTracking().

paycraftPlayBillingModule / paycraftStoreKit2BillingModule remain as explicit overrides (custom activityProvider, or a consumer who disabled the Initializer).

Verified

BUILD SUCCESSFUL compiling androidMain + iosSimulatorArm64 + jvm + js + wasmJs, and a new jvmTest asserts the web-platform fallback (platformDefaultNativeBillingClient() == null → WebCheckout).

Follow-up (separate)

Publish as 2.3.0, then reels-downloader drops its explicit AndroidApp.kt wiring and just bumps the version.

Summary by CodeRabbit

• New Features

  • Android now automatically detects the active foreground screen for billing flows.
  • Android uses native in-app billing by default when available.
  • Added platform-aware billing selection across Android, iOS, web, desktop, and JVM.

• Bug Fixes

  • Web, desktop, and iOS environments now reliably fall back to web checkout when native billing is unavailable.

• Tests

  • Added coverage confirming JVM environments use web checkout fallback.

[vercel]

@therajanmaurya is attempting to deploy a commit to the MobileByteLabs' projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 07f0e40f-7804-4bc4-b906-b1ea008ac7ce

📥 Commits

Reviewing files that changed from the base of the PR and between 590170f and e8f3fc0.

📒 Files selected for processing (10)

• cmp-paycraft/src/androidMain/kotlin/com/mobilebytelabs/paycraft/PayCraftInitializer.kt
• cmp-paycraft/src/androidMain/kotlin/com/mobilebytelabs/paycraft/PayCraftPlatform.android.kt
• cmp-paycraft/src/androidMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.android.kt
• cmp-paycraft/src/commonMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.kt
• cmp-paycraft/src/commonMain/kotlin/com/mobilebytelabs/paycraft/di/PayCraftModule.kt
• cmp-paycraft/src/iosMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.ios.kt
• cmp-paycraft/src/jsMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.js.kt
• cmp-paycraft/src/jvmMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.jvm.kt
• cmp-paycraft/src/jvmTest/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClientJvmTest.kt
• cmp-paycraft/src/wasmJsMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.wasmJs.kt

---

📝 Walkthrough

Walkthrough

Changes

Native billing auto-wiring

Layer / File(s)	Summary
Platform billing contract cmp-paycraft/src/commonMain/..., cmp-paycraft/src/iosMain/..., cmp-paycraft/src/jsMain/..., cmp-paycraft/src/jvmMain/..., cmp-paycraft/src/wasmJsMain/...	Defines a nullable platform billing factory; non-Android targets return null.
Android activity-aware billing cmp-paycraft/src/androidMain/kotlin/com/mobilebytelabs/paycraft/PayCraftInitializer.kt, cmp-paycraft/src/androidMain/kotlin/com/mobilebytelabs/paycraft/PayCraftPlatform.android.kt, cmp-paycraft/src/androidMain/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClient.android.kt	Tracks the resumed Android Activity through lifecycle callbacks and constructs Play Billing with the application context and current Activity provider.
Billing DI resolution cmp-paycraft/src/commonMain/kotlin/com/mobilebytelabs/paycraft/di/PayCraftModule.kt, cmp-paycraft/src/jvmTest/kotlin/com/mobilebytelabs/paycraft/billing/PlatformNativeBillingClientJvmTest.kt	Selects the platform billing client when available, otherwise uses web checkout; tests the JVM null default.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Startup as PayCraftInitializer
  participant Platform as PayCraftPlatform
  participant Billing as PlayBillingNativeClient
  Startup->>Platform: Start Activity lifecycle tracking
  Platform->>Platform: Store resumed Activity weak reference
  Billing->>Platform: Request application context and Activity
  Platform-->>Billing: Provide Android billing inputs

Loading

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}