5 posts tagged with "Breaking Change"

This release simplifies field naming in Android input types (RequestPurchaseAndroidProps and RequestSubscriptionAndroidProps). Since these types are already Android-specific, their fields no longer need the Android suffix.

Breaking Changes​

Simplified Field Names in Android Input Types​

Fields inside platform-specific input types no longer require the platform suffix. The parent type name already indicates the platform context.

Why this change?

When you write google: { offerToken: "..." }, the google key already tells you this is Android-specific. Adding Android suffix to fields inside is redundant:

// Redundant - we know it's Android from the parent
google: { offerTokenAndroid: "..." }

// Cleaner - parent context is sufficient
google: { offerToken: "..." }

Migration Guide​

Before (v3.4.3):

await requestPurchase({
  request: {
    google: {
      skus: ['product_id'],
      offerTokenAndroid: discountOffer.offerTokenAndroid,
      isOfferPersonalizedAndroid: true,
      obfuscatedAccountIdAndroid: 'user_123',
    },
  },
  type: 'in-app',
});

After (v3.4.4):

await requestPurchase({
  request: {
    google: {
      skus: ['product_id'],
      offerToken: discountOffer.offerTokenAndroid,  // Note: response field keeps suffix
      isOfferPersonalized: true,
      obfuscatedAccountId: 'user_123',
    },
  },
  type: 'in-app',
});

Important: Response Types Keep Suffixes​

The suffix removal only applies to input types (request parameters). Response types still use suffixes because they're cross-platform:

// Response fields KEEP the Android suffix
const product = products[0] as ProductAndroid;
const discountOffer = product.discountOffers?.[0];

// These response fields still have Android suffix
console.log(discountOffer?.offerTokenAndroid);           // ✓ Keep suffix
console.log(discountOffer?.percentageDiscountAndroid);   // ✓ Keep suffix

// But input fields don't need it anymore
await requestPurchase({
  request: {
    google: {
      skus: [product.id],
      offerToken: discountOffer?.offerTokenAndroid,      // Input: no suffix
    },
  },
  type: 'in-app',
});

One-Time Purchase Discount Offers (Android 7.0+)​

This release also adds support for discount offers on one-time (in-app) purchases:

import {fetchProducts, requestPurchase} from 'expo-iap';
import type {ProductAndroid} from 'expo-iap';

// 1. Fetch products with discount offers
const products = await fetchProducts({
  skus: ['premium_upgrade'],
  type: 'in-app',
});

const product = products[0] as ProductAndroid;

// 2. Get the discount offer
const discountOffer = product.discountOffers?.[0];

// 3. Purchase with the discount
if (discountOffer?.offerTokenAndroid) {
  await requestPurchase({
    request: {
      google: {
        skus: [product.id],
        offerToken: discountOffer.offerTokenAndroid,  // Use simplified input field
      },
    },
    type: 'in-app',
  });
}

Naming Convention Summary​

Closes​

• #307 - Support offerToken for in-app products (one-time purchases)

OpenIAP Versions​

For detailed changes, see the OpenIAP Release Notes.

This release reflects OpenIAP v1.3.11 updates, simplifying the PurchaseState enum and consolidating the Android billing API.

Breaking Changes​

• PurchaseState: Removed failed, restored, deferred (now only pending, purchased, unknown)
• AlternativeBillingModeAndroid: Deprecated in favor of BillingProgramAndroid
• useAlternativeBilling: Deprecated (only logged debug info, had no effect on purchase flow)

Migration Guide​

// Before
const {connected} = useIAP({
  alternativeBillingModeAndroid: 'user-choice',
});

// After
const {connected} = useIAP({
  enableBillingProgramAndroid: 'user-choice-billing',
});

OpenIAP Versions​

For detailed changes, see the OpenIAP Release Notes.

Expo IAP 3.3.0 brings Google Play Billing Library 8.2.0 features including the new Billing Programs API for external billing and one-time product discount support from Billing Library 7.0+.

Expo IAP 3.0.0 is a major release that fully integrates OpenIAP’s Android and iOS modules. Expo IAP is no longer just a framework bridge — it now leverages a centralized OpenIAP core for shared logic across platforms and SDKs. The result is a leaner, more maintainable codebase with faster iteration and greater stability.

Breaking 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)

Note: Android field names remain unchanged as they already follow the correct convention (e.g., autoRenewingAndroid, purchaseTokenAndroid).