#subandi

1 messages · Page 1 of 1 (latest)

mellow kayakBOT
nimble bough
#

Can you share more where you see the api version was reverted? Sharing an example request ID (req_xxx) will be helpful

hollow spindle
#

sure, one sec. I see it because I get a StripeInvalidRequestError (search is not supported on api version 2019)

#

but for that reason I do set the version to 2020 as per above

nimble bough
#

Can you share the stripe-ruby version that your server uses, and the code snippet which you set the API version?

hollow spindle
#

I don't have the request ids, but I have the (attempted) pm ids, would those help too?

nimble bough
#

Yup, that helps too for me to check the api version sent from your server

hollow spindle
#

stripe version 8.1

#

pm_0N6RDBOWj7lpTW512VvyYIQl and pm_0N6RAmOWj7lpTW51BFCVtx7i

nimble bough
#

Can you share the full error message when you tried to perform Customer Search?

hollow spindle
#

yes exactly / also what I expected and see locally. But still we got one "Search is not supported on api version 2019-05-16. Update your API version, or set the API Version of this request to 2020-08-27 or greater." back

#

the linked request is not a "search" request though, so it's not literally the one that returned that error, right

#

the one that cause the error is the the Stripe::Customer.search(...)

nimble bough
#

Can you share the code which you perform the Customer Search?

#

Did you set API version before you perform the Customer Search?

hollow spindle
#

it's in above screenshot

#

ahhh oooh

mellow kayakBOT
hollow spindle
#

yeah sorry 😅

#

above find_or_create_customer method can be called from one different context than the one I linked, and there we don't set the api version

#

so yeah makes 100% sense, thanks for your patience

nimble bough
#

Yup! I'd recommend setting API version prior performing Customer Search

hollow spindle
#

it "worked" because locally, the version sticked around... refactoring gone wrong. again, thanks and sorry heh