1.7k
In App Purchases
planned
Brent Vatne
Moved from: https://github.com/expo/expo/issues/11
Add support for in app purchases to standalone apps on iOS and Android in the managed workflow
Status as of May 3, 2021:
We are working on supporting native plugins in Expo managed apps, you can read about it here: https://blog.expo.io/expo-managed-workflow-in-2021-d1c9b68aa10 - but it's not ready yet.
------------------------------
Status as of July 21, 2020:
The same as the previous status update applies here. We are still building the infrastructure that we need to be able to support IAPs in the managed workflow. If you need them, I recommend ejecting to the bare workflow. You can continue to use all of the Expo SDK packages after ejecting, including OTA updates and Notifications. https://docs.expo.io/workflow/customizing/
------------------------------
Status as of April 14, 2020:
IAP APIs in the managed workflow will not be available until we have completed support for native plugins in the managed workflow, which is part of our rewrite of the build service. You may want to consider using bare workflow for now! You can continue to use Updates and Notifications in bare React Native apps now as of SDK 37: https://blog.expo.io/expo-sdk-37-is-now-available-dd5770f066a6.
------------------------------
Status as of November 7, 2019:
This feature is definitely important for us in the medium to long-term but we need to build some more infrastructure before it's possible. We're currently rewriting our build service to make it capable of handling adding In-App Purchase support to apps but it's not there yet.
ide
In-App Purchases are technically incompatible with today's managed workflow. That is, it's not a question of priorities or time investment; the way IAPs work on mobile requires a unique app for each project.
The way IAPs will come to Expo is by superseding the managed workflow with a new main workflow that supports native code (like IAPs) but also lets developers continue to use Expo and pick & choose what to manage with Expo Application Services (EAS) instead of bare React Native. Since this is a fundamental rehaul of the Expo platform, EAS, and the Expo workflow, this work is slated for 2021+.
More information here: https://blog.expo.io/expo-managed-workflow-in-2021-d1c9b68aa10
Activity
Newest
Oldest
MyCloudVIP com
LOVE TO SEE THIS HAPPEN SOON....
Any update on this highly needed request? Doing this on the bare workflow takes away the magic and beauty of EXPO. Please consider speeding up or prioritizing this essential feature. I need to start managing subscriptions on both platforms and trial to monthly / annual conversions. Please allow this to go through! Best regards.
Rachel Lau
Hey all! I am pretty new to Expo. Since the EAS is launch and seems to have built-in Eject (being called "Pre-Build'). does it mean that now we can use EAS with In-App Purchase plug-in? I know this modification is not completely done, but wonder if it is possible to use In-App Purchase without eject into bare workflow?? Cheers!
Ajay Thakur
With Expo EAS Build + Custom dev client, we have been using https://docs.expo.dev/versions/latest/sdk/in-app-purchases/ for more than one month in the production. Thanks, Brent for guiding me through.
- No custom configs or linking, EAS handles everything for you! and the Custom dev client allows you to code and test Expo in-app purchases.
- Expo managed, Push notification Service, publish and everything is working smoothly and sales are coming 💥
Apps Genie
Ajay Thakur: those are some great news! Do you happen to know of a guide we can look at to add IAP as first time add-in to an existing managed flow app?
Michael Wood
Apps Genie: See Jonathan Payet's blog post below.
Lisa Lee
Ajay Thakur: Ajay, did you have to create a config plugin? If so, would you mind sharing it with us? Thank you.
Apps Genie
Michael Wood: maybe it's my misunderstanding but in Jonathan 's blog post, we have to use expo-dev-client. But I've seen online somewhere that it's not required and that if you do the custom client you are effectively ejecting. So I wanted to double check before I do that. And also have the config plugin question as below.
Michael Wood
Apps Genie: No, that's not quite right.
When you install native code like RevenueCat's react-native-purchases you can no longer use the Expo Go app during development (except if you avoid calling the native code when you're in development mode).
expo-dev-client
is basically like a custom version of Expo Go that has your native dependencies built-in. So you can still use the dev client instead of Expo Go when you're developing the app.Using
expo-dev-client
is not required, but I think it is desirable.expo-dev-client
can
be used in an ejected app, but it can also be used in a managed app. There is definitely no need to eject to use expo-dev-client
.Since EAS Build, custom dev clients, config plugins etc. are still new, most information out there will tell you that you cannot use certain native libraries without ejecting. But these days it's definitely possible. Sometimes it might still be hard, though, because you might need to write a config plugin, or it might not be easy to do certain things in a config plugin (e.g. editing
MainApplication.java
seems to be a bit problematic in a config plugin.)N
Nam Anh
WARNING:
I had follow this instruction. I end up with IAP integrated successfully. However, my Application changed to Bare Workflow.
Please have consideration because we can not roll it back.
Michael Wood
Nam Anh: Hi. Which instructions did you follow exactly? You can definitely switch back to the managed workflow if you want to. This might be easy or hard depending on what changes you made while in the bare workflow.
N
Nam Anh
Michael Wood: Sorry for late reply. The story like this.
- In order to run use react-native-purchase, we need to run the application onexpo-dev-client.
- To use expo-dev-client, we need to run expo run:ios/android instead of expo start.
- When you run expo run:ios/android, it create ios and android fodlers and install react-native-unimodules. Now it comes to bare flow.
Michael Wood
Nam Anh: Hi. You do not have to run
expo run:*
. That is one way to do things. I am not sure why the documentation seems to recommend that. I would rather suggest to build with eas build --profile development --platform android --local
and then install the APK on your phone or emulator and run expo start --dev-client
. Similar for iOS.See this if you want to revert the
expo run:*
changes.Jonathan Payet
I made a little guide of how I made this possible using EAS / custom dev-client and react-native-purchases :
N
Nam Anh
WARNING:
I had follow this instruction. I end up with IAP integrated successfully. However, my Application changed to Bare Workflow.
Please have consideration because we can not roll it back.
Michael Wood
Nam Anh: If you followed his instructions exactly you should
not
have ended up with a bare workflow app. Also, it is definitely possible to roll back to the managed workflow again. But perhaps you should post on forums.expo.dev if you're having problems :)Jake Beauchamp
Michael Wood: When you run 'expo start --dev-client' it says "Option --dev-client can only be used in bare workflow apps. Run expo eject and try again."
Michael Wood
Jake Beauchamp: Please make sure you're running the latest version of
expo-cli
and post about any problems on forums.expo.devA
Andy
Hi! Do expo-dev-client + EAS Build finally allows us to implement In-App-Purchases to our Managed workflows? (The expo-dev-client release post doesn’t seem to mention IAP)
A
Andy
Sorry forgot to mention Brent Vatne and Evan Bacon
A
Ajay Thakur
Andy: + also guide around it... I'm completely in shallow
Michael Wood
Andy: I don't know enough about IAP to know if Stripe is relevant. If it is, see the following: https://docs.expo.io/versions/latest/sdk/stripe/
EDIT: I've been informed that the Stripe support won't help with IAP.
Apps Genie
Michael Wood: yea Stripe is for services outside what your app offers, right? and the Stores don't allow it for IAPs according to their terms.
William Guinaudie
Any news on when the functionality will be compatible with managed workflows?
Michael Wood
William Guinaudie: I think expo-dev-client (https://blog.expo.io/introducing-custom-development-clients-5a2c79a9ddf8) and EAS Build (https://docs.expo.io/build/introduction/) are the way forward
Apps Genie
Michael Wood: Any guide on how to migrate from traditional managed workflow (expo build) to the new eas build, and how would custom native modules like IAP be implemented there?
A
Ajay Thakur
Apps Genie: +1
Michael Wood
Apps Genie
Michael Wood: thank you. this is a good start. I will read it more thoroughly, but a bit afraid not to break my current app in both stores in this migrations. So maybe will try a test app and migrating to the latest SDK until I see some more examples for existing managed workflow apps already published on both mobile platforms. But also specifically to IAP, that part is more involved than just adding native library like the date picker, no?
F
Farhan Aslam
appreciate on such good updates looking forward about its release thank you
Apps Genie
Hello. Any updates here on being able to use IAP with managed workflow? really would put us a step forward being able to do this!
Mike
Looking forward to seeing this in 2021!
Onur Eker
Any news on this? Thanks
Load More
→