You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was getting a Paddle Customer already exists in the database error which didn't make sense to me. In my case the user was archived in Paddle. With the current code logic it seems that if a user cancels their account and their Paddle status becomes archived then that user can't return to the "service" as user again with the same email address?
Why is a LogicException thrown in ManagesCustomer@createAsCustomer? The doc blocks for createAsCustomer don't indicate that an exception will be thrown. Shouldn't the $customer object just be returned if one is found matching the Paddle ID? Then make an API PUT request to update the user status to 'active' if they are archived?
Cashier Paddle Version
2.5.2
Laravel Version
11.23.5
PHP Version
8.3.11
Database Driver & Version
SingleStore
Description
Related to #274
I was getting a
Paddle Customer already exists in the database
error which didn't make sense to me. In my case the user was archived in Paddle. With the current code logic it seems that if a user cancels their account and their Paddle status becomes archived then that user can't return to the "service" as user again with the same email address?Why is a LogicException thrown in
ManagesCustomer@createAsCustomer
? The doc blocks for createAsCustomer don't indicate that an exception will be thrown. Shouldn't the$customer
object just be returned if one is found matching the Paddle ID? Then make an API PUT request to update the user status to 'active' if they are archived?Steps To Reproduce
I would be happy to submit a PR if this is acceptable.
The text was updated successfully, but these errors were encountered: