@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 X-code 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 Gene:

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

Sadly this is kind of a deal breaker. Managed workflow doesn't have much of a point without IAP... Purchases are the lifeblood of any app. I'll keep an eye on Expo and come back when this is supported. Thanks for all your work on this.

@ide: Really wanted to be on managed workflow, this is a bummer. But thanks Expo team :)

@ide: Is it possible to see the steps in Canny as 'In progress' or 'planned' once you have it? This way we can see the small progresses, instead of waiting every few months for an update, which ultimately seems no progress is ever reported?

@Walsh Costigan: blog.expo.io is the best place to see progress announcements on this front. This is a many-months effort we’re working on every day and as new services are ready, we’ll announce them on the blog.

@Henrique Bruno: i don't understand, the bare workflow is default react-native

@Brent Vatne: Expo's main sell is the managed workflow though. If you take that away, then Expo becomes just another library vendor on npm.

As far as I can tell the managed workflow is a mirage since you'll have to eject sooner or later (to implement IAP, etc). Better to get used to bare React Native from the get go.

I think it was a missed opportunity not to have fully focused on the IAP refactor when this was filed in 2017. Getting everyone on board on a semi-managed workflow (Where Expo would be bundled to a separate app, a bit like Chromium w/ Electron) would have provided Expo with excellent monetization avenues. In short, IAP support is a big deal because it's the reason most apps are created in the first place.

That being said, thank you for all the work you've invested in the RN ecosystem over these years.

@Francisco Hodge: you'll be able to get some better insight into what we're working on in the coming months, and maybe then this will make more sense :) we are planning on supporting iap without ejecting, it just takes time to build the infrastructure and tooling to support this because it requires fundamental changes, eg: the build service will support bare react-native apps in the near future, and the next step is for it to also support custom native modules for managed apps. i've explained this in the topic of the issue, i assure that we are aware that many folks would like iap and we are planning on supporting it.