#benkass
1 messages · Page 1 of 1 (latest)
Hello again! As far as I know there's no way to make this work and still use Expo.
Aside from waiting for the next Expo update.
You know, it's strange. I looked at the dependencies of v29 vs v.28 and I don't see any dependency changes. I don't get why it returns "Invariant Violation" errors...
I can't speak to that. 😅
Is there perhaps another solution for the thing we discussed yesterday (showing the customer a payment sheet with the price, and then create a setupintent, clone to a connected account and with that generate a payment intent)?
We already discussed the other options earlier. The best approach for your use case, by far, is the flow where you show the PaymentSheet first before the Intent. The other approaches all have significant drawbacks.
you mean showing a paymentsheet with no price on it?
Yes.
What is the drawback in what you suggested yesterday, other than the issue I mentioned where I cannot install the new version on expo?
Can you be more specific? Not sure exactly what you're referring to.
You just wrote "The other approaches all have significant drawbacks" - what drawbacks are there in what you suggested yesterday (other than me not being able to use it because of Expo)?
Ah, I was referring to the alternatives that did not require you to abandon Expo. They have the drawback of a PaymentSheet with no amount, or showing the PaymentSheet multiple times, or things of that nature. Every alternative I proposed seemed like it was a dealbreaker for you.
Oh yes, of course. Abandoning Expo is not an option
Then you'll need to decide which of the alternatives is the least bad option.