#blocher_upcoming-customeraddress
turbid craneBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1246188010060644412
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
worldly lance
Hi, I'm not aware of any recent changes that might affect this. Can you share an example for when it worked?
wise matrix
req_8GuzR2WoTp8Gn3
worldly lance
Can you share the responses please?
We don't save responses from GET requests so I can't see what you're seeing
wise matrix
This is the failed attempt today (customer_addres is null). I do not have a succesful attempt, because we also do not store responses
worldly lance
Let me test this on my end
wise matrix
Thank you
worldly lance
Hmm, I made a similar request and I do get the address in the response.
wise matrix
Are you using the Python sdk?
Can i see from the logs which API version is being used, in case that changed?
I do see this difference
worldly lance
This is from my test using Python
Ah, good call out. Let me change my API version
No, I still see it
Setting the API stripe.api_version = "2024-04-10" did not make a difference
wise matrix
Ok
worldly lance
Can you try this on a different customer?
wise matrix
Yes, trying a few configurations
crisp shell
@wise matrix can you try https://docs.stripe.com/api/invoices/create_preview just quickly to see if you get the same result?
Okay we can reproduce and it looks like a bug. It's because of the Coupon id you pass in discounts, it's causing something to fail internally. We're investigating but I'd recommend reaching out to our support team for further help as they can follow up with you on what's causing this: https://support.stripe.com/contact
blocher_upcoming-customeraddress
crisp shell
@wise matrix okay I think the team found the issue
wise matrix
great!
crisp shell
@wise matrix okay if you try again it should work
crisp shell
Thanks for noticing quickly, could have been bad if it went out the whole week end but it was a Test mode only rollout so you helped catch it quickly