expo-iap 3.0.7 → 3.1.0

package/CLAUDE.md

@@ -8,6 +8,11 @@
 - Subject must be imperative, lowercase, without a trailing period, and roughly 50 characters
 - Wrap commit body lines near 72 characters and include footers such as `BREAKING CHANGE:` or `Closes #123` when needed
 
+## Tooling & Package Management
+
+- **Use Bun exclusively.** Run installs with `bun install`, scripts with `bun run <script>`, add deps via `bun add` / `bun add -d`.
+- Do **not** suggest or create `package-lock.json` or `yarn.lock`; `bun.lock` is the single source of truth.
+
 ## Expo-Specific Guidelines
 
 ### iOS Pod Configuration
@@ -38,6 +43,11 @@ Before committing any changes:
 
 ### Platform-Specific Naming Conventions
 
+#### Function Naming
+
+- Functions that only operate on one platform must carry the suffix: `nameIOS` or `nameAndroid` (e.g. `getStorefrontIOS`, `deepLinkToSubscriptionsAndroid`).
+- Cross-platform helpers should expose a single name and branch internally via `Platform.select` or equivalent.
+
 #### Field Naming
 
 - **iOS-related fields**: Use `IOS` suffix (e.g., `displayNameIOS`, `discountsIOS`, `introductoryPriceIOS`)
@@ -72,6 +82,8 @@ The library follows the OpenIAP type specifications with platform-specific exten
 
 > **Important:** `src/types.ts` is generated from the OpenIAP schema. Never edit this file manually or commit hand-written changes. After updating any `*.graphql` schema, run `bun run generate:types` (or the equivalent script in your package manager) to refresh the file.
 
+- Whenever you need Request/Params/Result types in the JS API surface (`src/index.ts`, hooks, modules, examples), import them directly from the generated `src/types.ts` (e.g., `MutationRequestPurchaseArgs`, `QueryFetchProductsArgs`). Bind exported functions with the generated `QueryField` / `MutationField` helpers so their signatures stay in lockstep with `types.ts` instead of redefining ad-hoc unions like `ProductTypeInput`.
+
 ### React/JSX Conventions
 
 - **Conditional Rendering**: Use ternary operator with null instead of logical AND
@@ -81,7 +93,7 @@ The library follows the OpenIAP type specifications with platform-specific exten
 ### Hook API Semantics (useIAP)
 
 - Inside the `useIAP` hook, most methods return `Promise<void>` and update internal state. Do not design examples or implementations that expect data from these methods.
-  - Examples: `fetchProducts`, `requestProducts`, `getProducts`/`getSubscriptions` (deprecated helpers), `requestPurchase`, `getAvailablePurchases`.
+  - Examples: `fetchProducts`, `requestPurchase`, `getAvailablePurchases`.
   - After calling, consume state from the hook: `products`, `subscriptions`, `availablePurchases`, etc.
 - Defined exceptions that DO return values in the hook:
   - `getActiveSubscriptions(subscriptionIds?) => Promise<ActiveSubscription[]>` (also updates `activeSubscriptions` state)
@@ -90,7 +102,7 @@ The library follows the OpenIAP type specifications with platform-specific exten
 
 ### API Method Naming
 
-- Functions that depend on event results should use `request` prefix (e.g., `requestPurchase`, `requestSubscription`)
+- Functions that depend on event results should use `request` prefix (e.g., `requestPurchase`)
 - Follow OpenIAP terminology: <https://www.openiap.dev/docs/apis#terminology>
 - Do not use generic prefixes like `get`, `find` - refer to the official terminology
 

package/CONTRIBUTING.md

@@ -8,6 +8,7 @@ Thank you for your interest in contributing to expo-iap! This guide will help yo
 - [Package Manager](#-package-manager)
 - [Running the Example App](#-running-the-example-app)
 - [Development Guidelines](#-development-guidelines)
+- [OpenIAP Version Management](#-openiap-version-management)
 - [Testing](#-testing)
 - [Code Style](#-code-style)
 - [Submitting Changes](#-submitting-changes)
@@ -223,6 +224,24 @@ The generated TypeScript definitions in `src/types.ts` come from the [`openiap-g
 
 Always ensure the repository builds and tests succeed after regenerating the types.
 
+## 🔢 OpenIAP Version Management
+
+All native and type-generation version numbers are sourced from `openiap-versions.json` at the repository root:
+
+- `apple` → iOS Pod dependency (`ios/ExpoIap.podspec`).
+- `google` → Android artifact (`android/build.gradle`, Expo config plugin).
+- `gql` → GraphQL type generator (`scripts/update-types.mjs`).
+
+When bumping dependencies:
+
+1. Update the relevant fields in `openiap-versions.json`.
+2. For iOS changes, run `cd ios && pod install` (and commit the Pod.lock if required by the workflow).
+3. For Android, re-run Gradle (`bun run android`) so the new artifact is pulled down.
+4. When the `gql` value changes, run `bun run generate:types` to refresh `src/types.ts`.
+5. Commit the updated JSON, regenerated files, and any resulting lockfile changes together.
+
+If the JSON file is missing or malformed, build scripts (Gradle, Podspec, the type generator) will fail fast — fix the JSON rather than hard-coding version strings in multiple locations.
+
 ### Development Workflow
 
 1. **Before starting work**:

package/README.md

@@ -5,9 +5,12 @@
   
   [![Version](http://img.shields.io/npm/v/expo-iap.svg?style=flat-square)](https://npmjs.org/package/expo-iap) [![Download](http://img.shields.io/npm/dm/expo-iap.svg?style=flat-square)](https://npmjs.org/package/expo-iap) [![CI](https://github.com/hyochan/expo-iap/actions/workflows/ci.yml/badge.svg)](https://github.com/hyochan/expo-iap/actions/workflows/ci.yml) [![codecov](https://codecov.io/gh/hyochan/expo-iap/graph/badge.svg?token=47VMTY5NyM)](https://codecov.io/gh/hyochan/expo-iap) [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhyochan%2Fexpo-iap.svg?type=shield&issueType=license)](https://app.fossa.com/projects/git%2Bgithub.com%2Fhyochan%2Fexpo-iap?ref=badge_shield&issueType=license)
   
-  In app purchase module in [Expo](https://docs.expo.dev/guides/in-app-purchases) that conforms to the [Open IAP specification](https://openiap.dev)
-  
-  <a href="https://openiap.dev"><img src="https://openiap.dev/logo.png" alt="Open IAP" height="40" /></a>
+Expo IAP is a powerful in-app purchase solution for Expo and React Native applications that conforms to the Open IAP specification. It provides a unified API for handling in-app purchases across iOS and Android platforms with comprehensive error handling and modern TypeScript support.
+
+If you're shipping an app with expo-iap, we’d love to hear about it—please share your product and feedback in [Who's using Expo IAP?](https://github.com/hyochan/expo-iap/discussions/143). Community stories help us keep improving the ecosystem.
+
+<a href="https://openiap.dev"><img src="https://openiap.dev/logo.png" alt="Open IAP" height="40" /></a>
+
 </div>
 
 ## 📚 Documentation
@@ -44,7 +47,7 @@ npx expo install expo-iap
         "expo-build-properties",
         {
           "android": {
-            "kotlinVersion": "2.0.21"
+            "kotlinVersion": "2.1.20"
           }
         }
       ]
@@ -53,6 +56,8 @@ npx expo install expo-iap
 }
 ```
 
+If you're targeting Expo SDK 54 or newer, please confirm whether this manual override is still required and share findings with the community at [github.com/hyochan/expo-iap/discussions](https://github.com/hyochan/expo-iap/discussions).
+
 ## Contributing
 
 We welcome contributions! Please see our [Contributing Guide](./CONTRIBUTING.md) for details on:
@@ -67,14 +72,21 @@ For detailed usage examples and error handling, see the [documentation](https://
 
 > Sharing your thoughts—any feedback would be greatly appreciated!
 
-## Sponsors
+## Our Sponsors
 
 💼 **[View Our Sponsors](https://openiap.dev/sponsors)**
 
+We're building the OpenIAP ecosystem—defining the spec at [openiap.dev](https://www.openiap.dev), maintaining [openiap-gql](https://github.com/hyodotdev/openiap-gql) for the shared type system, and shipping platform SDKs like [openiap-apple](https://github.com/hyodotdev/openiap-apple) and [openiap-google](https://github.com/hyodotdev/openiap-google) that power [expo-iap](https://github.com/hyochan/expo-iap), [flutter_inapp_purchase](https://github.com/hyochan/flutter_inapp_purchase), React Native, and [kmp-iap](https://github.com/hyochan/kmp-iap). The work so far has focused on untangling fragmented APIs; the next milestone is a streamlined purchase flow: `initConnection → fetchProducts → requestPurchase → (server receipt validation) → finishTransaction`.
+
+Your sponsorship helps ensure developers across platforms, OS, and frameworks can implement in-app purchases without headaches. It also fuels new plugins, payment systems, and partner integrations already being explored in the OpenIAP community. Sponsors receive shout-outs in every release and can request tailored support depending on tier. If you’re interested—or have rollout feedback to share—you can view sponsorship options at [openiap.dev/sponsors](https://openiap.dev/sponsors).
+
 ### <p style="color: rgb(255, 182, 193);">Angel</p>
 
 <a href="https://meta.com">
-    <img width="600" alt="courier_dot_com" src="https://static.xx.fbcdn.net/rsrc.php/y3/r/y6QsbGgc866.svg" />
+    <div style="display: inline-flex; flex-direction: column; align-items: center; gap: 0.25rem; padding: 0.75rem 1rem; border-radius: 12px; background: rgba(212, 165, 116, 0.12);">
+      <img alt="Meta" src="https://www.openiap.dev/meta.svg" style="width: 120px;" />
+      <span style="font-size: 0.85rem; font-weight: 600; color: rgb(107, 78, 61); text-align: center; width: 100%;">Meta</span>
+    </div>
 </a>
 
 ## Past Supporters

package/android/build.gradle

@@ -1,3 +1,5 @@
+import groovy.json.JsonSlurper
+
 apply plugin: 'com.android.library'
 apply plugin: 'kotlin-android'
 
@@ -10,6 +12,27 @@ applyKotlinExpoModulesCorePlugin()
 useCoreDependencies()
 useExpoPublishing()
 
+def resolveOpenIapVersionsFile() {
+  def candidates = [
+    new File(projectDir.parentFile, 'openiap-versions.json'),
+    new File(rootDir.parentFile ?: rootDir, 'openiap-versions.json'),
+    new File(rootProject.projectDir.parentFile ?: rootProject.projectDir, 'openiap-versions.json')
+  ]
+  return candidates.find { it.exists() }
+}
+
+def openiapVersionsFile = resolveOpenIapVersionsFile()
+if (openiapVersionsFile == null) {
+  throw new GradleException("expo-iap: Unable to locate openiap-versions.json")
+}
+
+def openiapVersions = new JsonSlurper().parse(openiapVersionsFile)
+def googleVersion = (openiapVersions instanceof Map) ? openiapVersions.google : null
+if (!(googleVersion instanceof String) || !googleVersion.trim()) {
+  throw new GradleException("expo-iap: 'google' version missing or invalid in openiap-versions.json")
+}
+def googleVersionString = googleVersion.trim()
+
 // If you want to use the managed Android SDK versions from expo-modules-core, set this to true.
 // The Android SDK versions will be bumped from time to time in SDK releases and may introduce breaking changes in your module code.
 // Most of the time, you may like to manage the Android SDK versions yourself.
@@ -58,6 +81,6 @@ dependencies {
       implementation project(":openiap-google")
     } else {
       // Fallback to published artifact when local project isn't linked
-      implementation "io.github.hyochan.openiap:openiap-google:1.1.11"
+      implementation "io.github.hyochan.openiap:openiap-google:${googleVersionString}"
     }
 }

package/android/src/main/java/expo/modules/iap/ExpoIapLog.kt

@@ -0,0 +1,69 @@
+package expo.modules.iap
+
+import android.util.Log
+import org.json.JSONArray
+import org.json.JSONObject
+
+internal object ExpoIapLog {
+    private const val TAG = "ExpoIap"
+
+    fun payload(
+        name: String,
+        payload: Any?,
+    ) {
+        debug("$name payload: ${stringify(payload)}")
+    }
+
+    fun result(
+        name: String,
+        value: Any?,
+    ) {
+        debug("$name result: ${stringify(value)}")
+    }
+
+    fun failure(
+        name: String,
+        error: Throwable,
+    ) {
+        Log.e(TAG, "$name failed: ${error.localizedMessage}", error)
+    }
+
+    fun debug(message: String) {
+        Log.d(TAG, message)
+    }
+
+    private fun stringify(value: Any?): String {
+        val sanitized = sanitize(value) ?: return "null"
+        return when (sanitized) {
+            is String -> sanitized
+            is Number, is Boolean -> sanitized.toString()
+            is Map<*, *> -> JSONObject(sanitized).toString()
+            is List<*> -> JSONArray(sanitized).toString()
+            else -> sanitized.toString()
+        }
+    }
+
+    private fun sanitize(value: Any?): Any? {
+        if (value == null) return null
+
+        return when (value) {
+            is Map<*, *> -> sanitizeMap(value)
+            is List<*> -> value.mapNotNull { sanitize(it) }
+            is Array<*> -> value.mapNotNull { sanitize(it) }
+            else -> value
+        }
+    }
+
+    private fun sanitizeMap(source: Map<*, *>): Map<String, Any?> {
+        val sanitized = linkedMapOf<String, Any?>()
+        for ((rawKey, rawValue) in source) {
+            val key = rawKey as? String ?: continue
+            if (key.lowercase().contains("token")) {
+                sanitized[key] = "hidden"
+                continue
+            }
+            sanitized[key] = sanitize(rawValue)
+        }
+        return sanitized
+    }
+}