3.1.0

Author: hyochan

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

docs/blog/2025-07-21-v2.6.md docs/blog/2025-07-21-2.6.0.mddocs/blog/2025-07-21-v2.6.md renamed to docs/blog/2025-07-21-2.6.0.md

@@ -1,14 +1,14 @@
 ---
-slug: v2.6
-title: 2.6 - Major iOS Improvements
+slug: 2.6.0
+title: 2.6.0 - Major iOS Improvements
 authors: [hyochan]
 tags: [release, ios, typescript, breaking-changes]
 date: 2025-07-21
 ---
 
-# 2.6 - Major iOS Improvements
+# 2.6.0 - Major iOS Improvements
 
-We're excited to announce the release of expo-iap v2.6.0! This release brings significant improvements to iOS functionality, better TypeScript support, and enhanced developer experience.
+We're excited to announce the release of expo-iap 2.6.0! This release brings significant improvements to iOS functionality, better TypeScript support, and enhanced developer experience.
 
 <!-- truncate -->
 
@@ -22,14 +22,14 @@ import AdFitTopFixed from "@site/src/uis/AdFitTopFixed";
 
 The biggest improvement in this release is the proper serialization of iOS subscription data. Previously, the `subscription` field would return undefined for subscription products. Now, all subscription information is properly serialized and accessible.
 
-#### Before (v2.5.x)
+#### Before (2.5.x)
 
 ```typescript
 const subscriptions = await getSubscriptions(['com.example.premium']);
 console.log(subscriptions[0].subscription); // undefined 😢
 ```
 
-#### After (v2.6.0)
+#### After (2.6.0)
 
 ```typescript
 const subscriptions = await getSubscriptions(['com.example.premium']);
@@ -40,15 +40,15 @@ console.log(subscriptions[0].subscription); // ✅ Full subscription data!
 
 We've restructured how period information is returned to be more consistent and useful. The `period` and `subscriptionPeriod` properties now return objects with `unit` and `value` properties instead of just the unit string.
 
-**Before (v2.5.x):**
+**Before (2.5.x):**
 
 ```typescript
 type SubscriptionInfo = {
   subscriptionPeriod: SubscriptionIosPeriod; // 'DAY' | 'WEEK' | 'MONTH' | 'YEAR'
 };
 ```
 
-**After (v2.6.0):**
+**After (2.6.0):**
 
 ```typescript
 type SubscriptionInfo = {

docs/blog/2025-07-23-v2.7.md docs/blog/2025-07-23-2.7.0.mddocs/blog/2025-07-23-v2.7.md renamed to docs/blog/2025-07-23-2.7.0.md

@@ -1,14 +1,14 @@
 ---
-slug: v2.7
-title: 2.7 - New Platform API & Google Play Billing v8
+slug: 2.7.0
+title: 2.7.0 - New Platform API & Google Play Billing v8
 authors: [hyochan]
 tags: [release, api, breaking-changes, android, google-play-billing]
 date: 2025-07-23
 ---
 
 # 2.7.0 - New Platform API & Google Play Billing v8
 
-We're excited to announce expo-iap v2.7.0! This release includes a cleaner platform-specific API for handling purchases and full support for Google Play Billing Library v8.0.0.
+We're excited to announce expo-iap 2.7.0! This release includes a cleaner platform-specific API for handling purchases and full support for Google Play Billing Library v8.0.0.
 
 <!-- truncate -->
 
@@ -199,7 +199,7 @@ const buySubscription = async (subId: string) => {
 
 ## 🔄 Deprecation Notice: requestSubscription
 
-Starting from v2.7.0, `requestSubscription` is deprecated in favor of using `requestPurchase` with `type: 'subs'`. This unifies our API and makes the codebase cleaner.
+Starting from 2.7.0, `requestSubscription` is deprecated in favor of using `requestPurchase` with `type: 'subs'`. This unifies our API and makes the codebase cleaner.
 
 **Migration example:**
 

…/blog/2025-08-18-v2.8-migration-guide.md …blog/2025-08-18-2.8.0-migration-guide.mddocs/blog/2025-08-18-v2.8-migration-guide.md renamed to docs/blog/2025-08-18-2.8.0-migration-guide.md docs/blog/2025-08-18-v2.8-migration-guide.md renamed to docs/blog/2025-08-18-2.8.0-migration-guide.md

@@ -1,16 +1,16 @@
 ---
-slug: v2-8-migration-guide
-title: v2.8 Migration Guide - iOS Field Naming Convention Update
+slug: 2.8.0-migration-guide
+title: 2.8.0 Migration Guide - iOS Field Naming Convention Update
 authors: [hyochan]
 tags: [release, breaking-change, migration]
 date: 2025-08-18
 ---
 
-# Migrating to expo-iap v2.8
+# Migrating to expo-iap 2.8.0
 
 ## Breaking Changes
 
-Version 2.8 introduces naming convention changes:
+Version 2.8.0 introduces naming convention changes:
 
 1. **iOS suffix convention**: Fields with iOS suffixes now use uppercase `IOS` instead of `Ios`
 2. **ID suffix convention**: All fields ending with `ID` now use `Id` instead for consistency (e.g., `subscriptionGroupID` → `subscriptionGroupId`, `bundleID` → `bundleId`)
@@ -149,14 +149,14 @@ import AdFitTopFixed from "@site/src/uis/AdFitTopFixed";
 Search your codebase for any references to the old field names and update them:
 
 ```typescript
-// Before (v2.7.x)
+// Before (2.7.x)
 const purchase = await requestPurchase({sku: 'product-id'});
 if (purchase.expirationDateIos) {
   console.log('Expires:', purchase.expirationDateIos);
 }
 
-// After (v2.8.0)
-// Note: requestPurchase API signature has also changed in v2.8.0
+// After (2.8.0)
+// Note: requestPurchase API signature has also changed in 2.8.0
 const purchase = await requestPurchase({
   request: {
     ios: {sku: 'product-id'},
@@ -174,15 +174,15 @@ if (purchase.expirationDateIOS) {
 Type names have also been updated to use uppercase `IOS`:
 
 ```typescript
-// Before (v2.7.x)
+// Before (2.7.x)
 import {
   ProductIOS,
   ProductPurchaseIos,
   ProductSubscriptionIOS,
   ProductStatusIos,
 } from 'expo-iap';
 
-// After (v2.8.0)
+// After (2.8.0)
 import {
   ProductIOS,
   ProductPurchaseIOS,
@@ -198,12 +198,12 @@ import {
 If you're using TypeScript and checking for iOS-specific fields:
 
 ```typescript
-// Before (v2.7.x)
+// Before (2.7.x)
 if ('expirationDateIos' in purchase) {
   // Handle subscription
 }
 
-// After (v2.8.0)
+// After (2.8.0)
 if ('expirationDateIOS' in purchase) {
   // Handle subscription
 }
@@ -214,12 +214,12 @@ if ('expirationDateIOS' in purchase) {
 Update all ID field references to use `Id` instead:
 
 ```typescript
-// Before (v2.7.x)
+// Before (2.7.x)
 const appTransaction = await getAppTransactionIOS();
 console.log(appTransaction.bundleID);
 console.log(appTransaction.appID);
 
-// After (v2.8.0)
+// After (2.8.0)
 const appTransaction = await getAppTransactionIOS();
 console.log(appTransaction.bundleId);
 console.log(appTransaction.appId);
@@ -230,13 +230,13 @@ console.log(appTransaction.appId);
 If you're using the subscription helper functions:
 
 ```typescript
-// Before (v2.7.x)
+// Before (2.7.x)
 const subscription = {
   expirationDateIos: purchase.expirationDateIos,
   environmentIos: purchase.environmentIos,
 };
 
-// After (v2.8.0)
+// After (2.8.0)
 const subscription = {
   expirationDateIOS: purchase.expirationDateIOS,
   environmentIOS: purchase.environmentIOS,

docs/blog/2025-09-05-v2.9.md docs/blog/2025-09-05-2.9.0.mddocs/blog/2025-09-05-v2.9.md renamed to docs/blog/2025-09-05-2.9.0.md

@@ -1,14 +1,14 @@
 ---
-slug: v2.9
-title: v2.9 - OpenIAP Apple Integration
+slug: 2.9.0
+title: 2.9.0 - OpenIAP Apple Integration
 authors: [hyochan]
 tags: [release, openiap, ios, architecture, performance]
 date: 2025-09-05
 ---
 
-# v2.9 Release Notes
+# 2.9.0 Release Notes
 
-We're excited to announce v2.9, featuring full integration with OpenIAP Apple that reduces our Swift codebase by **~1,180 lines (73% reduction)**!
+We're excited to announce 2.9.0, featuring full integration with OpenIAP Apple that reduces our Swift codebase by **~1,180 lines (73% reduction)**!
 
 <!-- truncate -->
 
@@ -28,14 +28,14 @@ The core achievement of this release is integrating [OpenIAP Apple](https://gith
 
 ## 🏗️ Architecture Evolution
 
-### Before (v2.8.x)
+### Before (2.8.x)
 
 ```txt
 Expo IAP → Custom Swift Implementation → StoreKit 2
          (1,620 lines of complex logic)
 ```
 
-### After (v2.9.0)
+### After (2.9.0)
 
 ```txt
 Expo IAP → OpenIAP Apple → StoreKit 2
@@ -89,9 +89,9 @@ import {OpenIapEvent} from 'expo-iap';
 purchaseUpdatedListener((purchase) => {}, OpenIapEvent.PurchaseUpdated);
 ```
 
-## 🚀 Looking Ahead: v3.0.0
+## 🚀 Looking Ahead: 3.0.0
 
-This release sets the foundation for v3.0.0:
+This release sets the foundation for 3.0.0:
 
 - **Android**: OpenIAP Android integration (Google Play Billing)
 - **Bundle Size**: Further optimizations through shared native libraries
@@ -141,7 +141,7 @@ bun add expo-iap@2.9.0
 
 ### Note
 
-- Android native module integration with OpenIAP Android planned for v3.0.0
+- Android native module integration with OpenIAP Android planned for 3.0.0
 
 ## 🙏 Acknowledgments
 

docs/blog/2025-09-13-v3.0.md docs/blog/2025-09-13-3.0.0.mddocs/blog/2025-09-13-v3.0.md renamed to docs/blog/2025-09-13-3.0.0.md

@@ -1,12 +1,12 @@
 ---
-slug: v3.0
-title: Expo IAP 3.0 — OpenIAP Integration, Unified Core, Leaner API
+slug: 3.0.0
+title: 3.0.0 — OpenIAP Integration, Unified Core, Leaner API
 tags: [release, breaking-change, android, ios]
 authors: [hyochan]
 date: 2025-09-13
 ---
 
-Expo IAP 3.0 is a major release that fully integrates [OpenIAP](https://openiap.dev)’s Android and iOS modules. Expo IAP is no longer just a framework bridge — it now leverages a centralized [OpenIAP](https://openiap.dev) core for shared logic across platforms and SDKs. The result is a leaner, more maintainable codebase with faster iteration and greater stability.
+Expo IAP 3.0.0 is a major release that fully integrates [OpenIAP](https://openiap.dev)’s Android and iOS modules. Expo IAP is no longer just a framework bridge — it now leverages a centralized [OpenIAP](https://openiap.dev) core for shared logic across platforms and SDKs. The result is a leaner, more maintainable codebase with faster iteration and greater stability.
 
 <!-- truncate -->
 

docs/blog/2025-09-21-3.1.0.md

@@ -0,0 +1,73 @@
+---
+slug: 3.1.0
+title: 3.1.0 - Full OpenIAP Ecosystem Adoption
+authors: [hyochan]
+tags: [release, openiap, ios, android, tooling]
+date: 2025-09-21
+---
+
+# 3.1.0 Release Notes
+
+Expo IAP 3.1.0 graduates the project into the full **OpenIAP ecosystem**. The release ships with three dedicated native stacks:
+
+- **[openiap-apple](https://github.com/hyodotdev/openiap-apple)** — StoreKit 2 implementation for Apple platforms
+- **[openiap-google](https://github.com/hyodotdev/openiap-google)** — Google Play Billing integration for Android
+- **[openiap-gql](https://github.com/hyodotdev/openiap-gql)** — GraphQL helpers that drive types and tooling
+
+From 3.1.0 onward, Expo IAP stays in lockstep with these modules: Apple **v1.2.2**, Google **v1.2.6**, and GQL **v1.0.8**. That shared version alignment gives Expo IAP stable native compatibility and a unified type system straight from the OpenIAP schema.
+
+<!-- truncate -->
+
+## 🚀 Highlights
+
+- Adopted the full OpenIAP core stack—[openiap-gql](https://github.com/hyodotdev/openiap-gql), [openiap-apple](https://github.com/hyodotdev/openiap-apple) v1.2.2, and [openiap-google](https://github.com/hyodotdev/openiap-google) v1.2.6)—bringing Expo IAP into alignment with the shared ecosystem used across Flutter, React Native, and KMP.
+- Trimmed roughly **two thirds** of our custom native bridge code by delegating logic to the OpenIAP modules.
+- Expanded automated coverage to about **98%**, spanning purchase flows, native bridge entry points, and error mapping utilities.
+
+## 🔁 OpenIAP Upgrades
+
+- Normalized purchase payloads on both platforms so every bridge call sanitizes platform casing and forwards the complete OpenIAP record.
+- Migrated Android to the new `RequestPurchaseProps` / `PurchaseResult` / `ErrorCode` contracts, achieving parity with the Apple module.
+- Centralized native dependency versions via [`openiap-versions.json`](https://github.com/hyochan/expo-iap/blob/main/openiap-versions.json); Gradle now fails fast if the Google artifact version is missing and scripts/migrations read from one source of truth.
+
+## 🐞 Bug Fixes
+
+- `fix(android): honor subscription offerToken` ([#214](https://github.com/hyochan/expo-iap/pull/214)) restores proper handling of `subscriptionOfferDetailsAndroid` so Google Play discounts apply reliably.
+
+## 🛡️ Safer Purchases & Better Errors
+
+- `requestPurchase` on iOS explicitly rejects unsupported product types instead of silently treating `all` as `in-app`.
+- Error handling now consistently routes through the shared `ErrorCode` table so promise rejections, platform conversions, and predicates remain aligned.
+- Additional coverage for `createPurchaseError`, `ErrorCodeUtils`, and the user-friendly error helper keeps error copy in sync with OpenIAP terminology.
+
+## 🛠️ Tooling & Workflow
+
+- Contributor docs clarify how to bump OpenIAP packages, regenerate types, and keep `openiap-versions.json` synchronized for Android and iOS builds.
+
+## ⚠️ Important Changes
+
+- **Transaction identifiers**: `transactionId` is reinstated as the primary store reference (`orderId` on Android, StoreKit transaction ID on iOS). Android’s generic `id` is no longer repurposed for orders; when Google Play omits an `orderId` (typical for consumables), `transactionId` becomes `null` and clients should rely on the unified `purchaseToken` (Android purchase token / iOS JWS). This value is the canonical receipt for server validation. See the related [react-native-iap discussion](https://github.com/hyochan/react-native-iap/discussions/3016).
+- **iOS request types**: purchase requests must specify either `in-app` or `subs`. Passing `all` (or any other type) throws an explicit error.
+- **Promoted products**: events now emit the full sanitized product payload; downstream listeners should expect the entire object instead of just `productId`.
+- **Deprecated helpers removed**: `getProducts`, `requestSubscription`, and `requestProducts` are removed. Use `fetchProducts` with the unified purchase flow.
+
+## Minor Updates
+
+- Removed the legacy `useIAP` state shims (`currentPurchase`, `currentPurchaseError`, and their `clear*` helpers) in favour of the hook’s `onPurchaseSuccess` / `onPurchaseError` callbacks ([#213](https://github.com/hyochan/expo-iap/pull/213)).
+
+## 📦 Installation
+
+```bash
+bun add expo-iap@3.1.0
+# or
+npm install expo-iap@3.1.0
+# or
+yarn add expo-iap@3.1.0
+```
+
+## 🔗 References
+
+- Recent work: [Closed pull requests](https://github.com/hyochan/expo-iap/pulls?q=is%3Apr+is%3Aclosed)
+- Release builds on the OpenIAP ecosystem: [openiap.dev](https://openiap.dev)
+
+Enjoy the smoother upgrade path and richer diagnostics shipped in 3.1.0! Let us know how it goes via [GitHub issues](https://github.com/hyochan/expo-iap/issues).