react-native-iap VS react-native-screens

I did not find any examples on this, but Apple does not seem to have a javascript SDK for In app purchases(like google does) so this needs to be done natively, I guess you are more familiar with javascript than swift so you can start with a basic React Native project, add a webview component and use it to display your PWA, then use the react-native-iap package to handle apple in app payments and trigger this flow from your PWA like this

The first thing I did was clone the Github repository for react-native-iap as it contained all the working examples for Amazon Appstore, Google Play, and Apple Appstore.

What is your purpose with the action of opening the payment window? Do you just want to show the cards, or is the user buying a product, or is it for something in the app? The react-native-payment has not seen any updates the past 2 years… I would skip this package for usage. You could use something like https://github.com/stripe/stripe-react-native if you like to use stripe as a payment provider. Or for in app purchases I use https://github.com/dooboolab/react-native-iap So it depends on want you want to accomplish and what kind of payment provider you want to use. Good luck 💪🏽

I've been working on this side project using react-native & firebase and I wanted to add In-App payments to it so users can buy "coins" inside the app, seems like the best way to do so is to use react-native-iap. I read through the documentation and it's clear to me how it works, but I still have some doubts.

a lot easier and faster to implement. https://github.com/dooboolab/react-native-iap

Great, the more research into it the more I am leaning towards using https://github.com/dooboolab/react-native-iap. Good to hear that you've had no issues with that library.

Dunno if it's the "standard", but when I was implementing IAP, this was the only one I could find that actually 1/2 way worked. https://github.com/dooboolab/react-native-iap

You have to use in-app purchases directly from Apple (but given our size we are well within the new 15% bracket) . There is a great library for react-native to handle in-app purchases. Our current implementation is serverless, but we'll move to something more structured if the app gains enough momentum.

react-native-url-router (a single navigation system, using React Router + react-native-screens for stacks + react-native-pager-viewfor tabs).

Sure. Here is an example of what I'm talking about on github.

FATAL EXCEPTION: main Process: web.tradenewton.com, PID: 13063 java.lang.RuntimeException: Unable to start activity ComponentInfo{web.tradenewton.com/web.tradenewton.com.MainActivity}: androidx.fragment.app.Fragment$InstantiationException: Unable to instantiate fragment com.swmansion.rnscreens.ScreenStackFragment: calling Fragment constructor caused an exception at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3616) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3780) at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85) at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135) at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2251) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:233) at android.app.ActivityThread.main(ActivityThread.java:8063) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:631) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978) Caused by: androidx.fragment.app.Fragment$InstantiationException: Unable to instantiate fragment com.swmansion.rnscreens.ScreenStackFragment: calling Fragment constructor caused an exception at androidx.fragment.app.Fragment.instantiate(Fragment.java:631) at androidx.fragment.app.FragmentContainer.instantiate(FragmentContainer.java:57) at androidx.fragment.app.FragmentManager$3.instantiate(FragmentManager.java:483) at androidx.fragment.app.FragmentStateManager.(FragmentStateManager.java:85) at androidx.fragment.app.FragmentManager.restoreSaveState(FragmentManager.java:2728) at androidx.fragment.app.FragmentController.restoreSaveState(FragmentController.java:198) at androidx.fragment.app.FragmentActivity$2.onContextAvailable(FragmentActivity.java:149) at androidx.activity.contextaware.ContextAwareHelper.dispatchOnContextAvailable(ContextAwareHelper.java:99) at androidx.activity.ComponentActivity.onCreate(ComponentActivity.java:297) at androidx.fragment.app.FragmentActivity.onCreate(FragmentActivity.java:273) at androidx.appcompat.app.AppCompatActivity.onCreate(AppCompatActivity.java:115) at com.facebook.react.ReactActivity.onCreate(ReactActivity.java:44) at android.app.Activity.performCreate(Activity.java:8006) at android.app.Activity.performCreate(Activity.java:7990) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1329) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3589) ... 11 more Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Constructor.newInstance0(Native Method) at java.lang.reflect.Constructor.newInstance(Constructor.java:343) at androidx.fragment.app.Fragment.instantiate(Fragment.java:613) ... 26 more Caused by: java.lang.IllegalStateException: Screen fragments should never be restored. Follow instructions from https://github.com/software-mansion/react-native-screens/issues/17#issuecomment-424704067 to properly configure your main activity. at com.swmansion.rnscreens.ScreenFragment.(ScreenFragment.kt:41) at com.swmansion.rnscreens.ScreenStackFragment.(ScreenStackFragment.kt:30) ... 29 more

It´s very likely you are using react-native-screens and you forgot to updat the onCreate method. Just make sure you're onCreate method looks like this

Not yet, you can open an issue in react-native-screens repo and follow these issues: https://github.com/software-mansion/react-native-screens/issues/561 https://github.com/software-mansion/react-native-screens/issues/317

I LOVE the large title header behavior of the native-stack on iOS. I really wish the folks at RNav would implement something like that in a future release (I had rebuilt the large header from the ground up on our first app using Animated). As it stands, I am 90% sure I want to implement it on Words – but other features / fixes come first!