Tychobra / polishedpayments

Other
30 stars 11 forks source link

'stripe_user' not found #13

Open data-scimon opened 1 year ago

data-scimon commented 1 year ago

I am getting an issue when running your subscription_and_payment example's app:

Warning: Error in is_subscription_valid: object 'stripe_user' not found

I manage to see my user authenticated and subscribing to the product on Stripe, but the app exits with this warning.

gioneves commented 1 year ago

I'm facing the same problem, can you solve it? I signed up for Stripe and sent all my company documents, but the Warning persists.

Graham-McCracken commented 1 year ago

Similar issue.

The UI states: "Redirecting to payments page"

App exits with the error: "Warning: Error in is_subscription_valid: object 'stripe_user' not found"

danmalter commented 1 year ago

I have confirmed this error as well. @data-scimon, any updates from your end?

Warning: Error in is_subscription_valid: object 'stripe_user' not found

Graham-McCracken commented 1 year ago

This issue remains. Is there any update on the bug fix? Thanks

danmalter commented 1 year ago

I think the error is related to the subscription ID as I've found it goes away if you take out the subscription ID in the below line or set it to NULL. However, that does you no good as you need to link the subscription ID to the checkout.

subscription_prices = NULL

HugoGit39 commented 1 year ago

Same issue here..and indeed with subscription_prices = NULL without an error.

So I tried to read the source code of the functions and it seems it got to do with payments_ui.R see: https://rdrr.io/github/Tychobra/polishedpayments/src/R/payments_ui.R ..at the function get_stripe see: https://rdrr.io/github/Tychobra/polishedpayments/man/get_stripe.html ....does that make sense?

Graham-McCracken commented 1 year ago

Thanks, @HugoGit39. Were you able to progress with this further?

ctm82 commented 7 months ago

Was this ever solved? I'm running into the same issue.

ethan-project94 commented 5 months ago

Also running into this issue, was this solved?