#morteza_react-native-terminal-sdk
shrewd bloomBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1375134523268005948
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
obtuse sparrow
Hi
hope you are doing well
we have a tap to pay app and we have used stripe-react-native-terminal, I want to know if we can publish our app or not, it seems to be in beta version!
severe dust
As described here, this is still in public preview: https://docs.stripe.com/terminal/payments/setup-integration?terminal-sdk-platform=react-native
Caution
Terminal’s React Native library is in public preview and in active development. Please report any issues you encounter to our github project.
Whether that meets your needs to use in production is up to you
shrewd bloomBOT
obtuse sparrow
the package is working properly right now
I wanna know if something can change or what
severe dust
Yea, there may be breaking changes there accompanying a new release after the beta, but this should be documented in the changelog for you to upgrade safely
obtuse sparrow
I have a question, react native package actually is using native sdk under the hood, so we are using native sdk technically right ?
so if we chase the changes before hand, we can avoid crashes ?
red remnant
Hello 👋
I'm stepping in as my colleague needs to go.
The React Native SDK maps components to their native iOS or Android SDK implementations, that's how React Native works in general.
But the React Native SDK manages the dependencies and what components are available.
As for this question
so if we chase the changes before hand, we can avoid crashes ?
I"m not sure what you mean. We provide the Changelog for each SDK version so you can review them prior to making any updates
obtuse sparrow
I wanna know if we lock to a specific version of sdk that we have tested compelety, are we ok ?
red remnant
If you have a specific version set and you have tested your flow end-to-end, you should be reasonably certain that the existing functionality with continue to work.
obtuse sparrow
you mean even if we are locked to a specific evrsion of sdk, something still can change on the stripe side ? like backend code ??
or you mean there mihgt be hidden bugs in the sdk ??
red remnant
I mean that, most likely nothing will change and you will be fine.
If we need to make changes that impact you, e.g. we have to modify how Payment Intents behave for security reasions, we will proactively communicate this coming change to allow you time to modify your integration.
obtuse sparrow
so you are saying that it's fine to use with a thoroughly tested with a specific version
red remnant
I'm saying you are unlikely to run into issues. As long as the RN SDK does everything you need it to do.
obtuse sparrow
ook, thanks, so public preview means that if there is a new version and you upgrade to that version there might be breaking changes other than that if you are using specific version everything is fine , fright ?
red remnant
Public preview means we might still make significant changes to how this SDK behaves in future releases. If you pin to a specific version and everything works, end-to-end, you should be okay.