Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Linking Tipsi with "react-native link tipsi-stripe" adds deprecated "React" to project

See original GitHub issue

Before I have submitted the issue

[✓] I have read an installation guide
[✓] I know that for an iOS I need to install pods because I’ve read the installation guide
[✓] I have read a linking guide and checked that everything is OK like in manual linking guide
[✓] I know that before using tipsi-stripe I need to set options for my app as described in usage guide

The problem

Currently, linking tipsi-stripe with the command “react-native link tipsi-stripe” does link tipsi, but it also adds “react” to the podfile. When it is installs “react” through the podfile, a status update in terminal mentions that it is deprecated, but now when you try to run your project there will be a lot of conflicting files and just really makes a mess. I’ve tried removing react manually at this point but something else down the line always breaks. I then attempted to start over and link it manually to evade this, but when linking manually I am stopped at the part where you must add “libTPSStripe.a” to your iOS build phases. There is an issue related to this but it came about for them because they were not using pods, I on the other hand am using pods and have Stripe in my podfile. It’s weird that this is all happening because the project was actually working great with tipsi without even having linked it, but then all of a sudden an error: "undefined is not an object (evalutating ‘StripeModule.init’).

The Tipsi library is great aside from this, happy to describe this in more detail if needed, thanks!

Environment

tipsi-stripe version: 5.6.0
Last tipsi-stripe version where the issue was not reproduced (if applicable): NA
iOS or Android: iOS (haven’t tested Android yet but I’m sure the same issue would persist)
OS version: 9.0
React-Native version: 0.55.3