Hi,
I saw several reports here about react-native-poolakey not working well with Expo (e.g. #26 – currentActivity in Expo Dev Build, #23 – package not linked).
For Expo projects, I maintain an Expo module that wraps the same Poolakey SDK and works with Expo’s native build (including dev client):
It supports:
- One-time in-app products and subscriptions (same Cafe Bazaar / Poolakey backend)
- React hooks:
useBillingProduct and useBillingSubscription
- Imperative API if you prefer
- No extra native config; it plugs into Expo’s module system
If you’re on Expo and hitting linking or currentActivity issues with react-native-poolakey, you can try this as an alternative. Docs and examples are in the README.
Hi,
I saw several reports here about react-native-poolakey not working well with Expo (e.g. #26 – currentActivity in Expo Dev Build, #23 – package not linked).
For Expo projects, I maintain an Expo module that wraps the same Poolakey SDK and works with Expo’s native build (including dev client):
It supports:
useBillingProductanduseBillingSubscriptionIf you’re on Expo and hitting linking or
currentActivityissues with react-native-poolakey, you can try this as an alternative. Docs and examples are in the README.