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?

Apps Genie: See Jonathan Payet's blog post below.

Ajay Thakur: Ajay, did you have to create a config plugin? If so, would you mind sharing it with us? Thank you.

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.

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

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 is not required, but I think it is desirable.

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 .

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 seems to be a bit problematic in a config plugin.)

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.

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.

Michael Wood: Sorry for late reply. The story like this.

Nam Anh: Hi. You do not have to 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 and then install the APK on your phone or emulator and run . Similar for iOS.

See this if you want to revert the changes.

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.

Nam Anh: If you followed his instructions exactly you should 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 :)

Sorry forgot to mention Brent Vatne and Evan Bacon

Andy: + also guide around it... I'm completely in shallow

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/

and: https://www.youtube.com/watch?v=DZlAET7Tgx4

EDIT: I've been informed that the Stripe support won't help with IAP.

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: 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

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?

Apps Genie: +1

Apps Genie: Hi. The migration guide is here

I haven't tried this myself, but it should be something similar to Brent's post here where he marked that feature request as Completed.

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?

Evan Bacon: "I'll leave the canny open for now because we plan on improving this even more in the coming months!" - I hope this doesn't mean it's not being added to managed workflow.

Walsh Costigan: we cannot add IAP to the client that you download from the store, do to App Store restrictions. Also IAP must be setup before building the native binary, because of this, we're working on a system to download a client with arbitrary native code added to it though. This will effectively be managed workflow as you won't need to write native code or use a mac to get a client with IAP support enabled.

Evan Bacon: EAS is not the real solution related to this feature request. It's like we can build our own native code with IAP, even without EAS. We need support for Managed workflow.

Kuriel i: as far as I understand it, it will be available in a workflow that is basically the same as the managed workflow except that people will not get access to IAP in the current Expo app. They will need to build a customised Expo app for you with IAP built-in and configured. As Evan says, you will not need to have Xcode installed, or even have a Mac. So it will be pretty much the same as the managed workflow.

Michael Wood: sounds reasonable.

Evan Bacon: Evan that's great news!!

We're using Expo managed workflow & Expo cloud build service, can you guys come with some IAP integration tutorial/guide for managed workflow for EAS!

Thank for such a piece of great new year news!

Ajay Thakur: For now, EAS is only available in the bare workflow, but it brings the bare workflow closer to the managed workflow.

According to the blog post, the plan is for EAS to be made available in the managed workflow some time in 2021.

Evan Bacon: Any idea (or inside info) whether this has a chance to make it into managed workflow in 2021?

Michael Wood: Will we have to eject for this planned design? Or can use current manage workflow setup to, in essence, add IAP to the existing app(s)?

Apps Genie:

> when

a preview version for managed EAS build will be released with SDK 41. This is something that Brent and I are working full time on. Not directly related to IAP, but we also have some stripe related announcements coming in the next few months.

> will we have to eject

No, eas will handle all of the code generation automatically in SDK 41-42+

Evan Bacon: Thanks for your awesome work with Expo and also your extensive replies here ❤️

Evan Bacon: Evan upgraded to SDK 41, how soon we can add custom native code to support In-app purchase? < 1 month or > 3 month. TIA

Evan Bacon ide Brent Vatne: From what I understood the recently released SDK 41 should allow us to integrate InAppPurchases into our managed workflow, however, I cannot find any documentation or tutorial that explains how to do so. The page https://docs.expo.io/versions/latest/sdk/in-app-purchases/ still says "This module is currently only available in the bare workflow.". Would you be able to refer us to some sort of documentation explaining how to integrate InAppPurchases?

Andy: hello, this is not true yet, please refer to https://blog.expo.io/expo-managed-workflow-in-2021-d1c9b68aa10 for more info

Brent Vatne ide Evan Bacon: If I have deciphered the article correctly, I understand that my previous message is actually true if we sign up for the Priority plan? It says: “Sign up for the EAS Priority Plan to try EAS Build with your managed apps today!” Can we customize the runtime of our managed projects in development if we sign up for Priority plan? Sorry the article is not too clear to me.

Andy: scroll down to the summary bit and let me know which part of it is unclear and i am happy to clarify!

Brent Vatne: With all due respect, I have done both, I read the summary and asked for clarifications in my previous message. I just find that the article could be a bit more direct answering what so many users have been waiting for years, like in big red bold font a on the top saying something like: “You can’t yet implement InAppPurchases, ... with managed workflow, it’s coming in June!”. I see time-saving potential at least for users who are not so involved with the technicalities described, but still need to understand whether the InAppPurchases feature can be finally implemented for managed workflows.

Here we go:

Can we customize the runtime of our managed projects in development as per today so that we can add InAppPurchases in any possible manner even if it is through a paid plan?

Not trying to be rude, it’s just been a long wait.

Andy: hi again!

> "Can we customize the runtime of our managed projects in development as per today so that we can add InAppPurchases in any possible manner even if it is through a paid plan?"

this will be possible later in 2021, we're working on it right now. i tried to make this clear with the following bit in the summary: "Later in 2021, the Expo Development Client (a React Native library installable in any project that gives you the same experience as Expo Go) will enable developers to customize the runtime of their managed projects in development too. This will open up the possibility to install any React Native library in your Expo managed project."

currently, we only have good ergonomics around removing libraries from standalone apps - we don't have Expo Development Client ready yet, and this is what will make it possible to customize the runtime in development.

sorry for just referring you to the summary yesterday, i was not at a computer and it was difficult for me to respond fully from my phone.

i understand that it has been a long wait, trust me that as someone who works on this every day it has felt like an eternity to me. we're trying to come up with a solution that removes expo as a bottleneck for developers adding feature to their apps, as described in that post. hopefully it will address your needs, but if you need something now you should just go ahead and convert to a bare project :) we can't promise any firm timelines for this stuff, that's why we just say "later in 2021" in the post.

Evan Bacon: I noticed the new blog article about Expo Run Commands. Looks pretty great! Hard work with results. But in terms of IAP, we still need to wait on the Expo Dev Client before we can consider some work here, correct? Just wanted to make sure my understanding was right.

Apps Genie: As stated a bit earlier in the thread, we're still working on dev clients, which will provide an E2E experience for getting a reusable client app with any custom native code added to it.

The new run commands, to a degree, let you simulate this locally. You can install an IAP package in your project, and use or to build the app with custom native code.

Prebuilding, config plugins, run commands, and managed EAS Build are all important parts of making the entire experience work. We just need dev clients and a bit of finesse to make the experience smooth and complete.

Evan Bacon: Got it! Thanks for the explanation. Will eagerly keep an eye out for those.