#gran-p_code
rapid tideBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1415619285115601027
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
glossy hemlock
Thanks, let me take a look
pearl gazelle
Sorry first screenshot was of other test data than from the example, here is the same test data as in the example:
glossy hemlock
I think we expect the date formatted (hyphenated) like this: 2023-11-17
Uses Moment.js under the hood from what I can see: https://momentjs.com/docs/#/parsing/string/
pearl gazelle
Tried that now but still getting the same error:
The error says interval OR currency. Could this be a currency issue?
Stripe's documentation uses "new Date(2023, 11, 17)" format, so I don't think that is the issue, unless the documentation is wrong
glossy hemlock
I still think it's Date object, just hyphenated: new Date(2023-11-17)
glossy hemlock
Stripe's documentation uses "new Date(2023, 11, 17)" format, so I don't think th...
Docs are often wrong haha. I'm looking at the source code and trying to interpret how it actually works
pearl gazelle
hehe okey, I'll try this one: "new Date(2023-11-17)"
glossy hemlock
I don't uunderstand how currency can even be invalid when there's no currency prop?
(not really familiar with this component)
Can you try and pass a currency prop? Seems like it is supported, just not documented (we fallback to the report default if not provided)
pearl gazelle
Yeah I couldn't find a currnecy prop as well, but I tried passing in "SEK", but still the same error
Tried this one now but still same error
glossy hemlock
Ugh, this error message is the worst
pearl gazelle
Maybe I'm on the wrong version, because I don't have a currency prop in my sdk?
glossy hemlock
Yeah I don't think it's actually exposed in types (for a reason)
I'm looking at internal tests and new Date('2022-01-01') is the correct format
So I'm stumped
pearl gazelle
We're using the following versions in our package.json:
"@stripe/connect-js-preview": "npm:@stripe/connect-js@^3.3.22-preview-2",
"@stripe/react-connect-js-preview": "npm:@stripe/react-connect-js@^3.3.25-preview-1",
For the preview components
rapid tideBOT
glossy hemlock
currency is meant to be inferred from a network call for the report type somewhere. Is there anything in your network tab that looks like that? The component would invoke this call automatically
glossy hemlock
Yes, that all_currencies_filter I think
Is there a default_currency property in the response?
pearl gazelle
{
"id": "acct_1PGk2d4I9HgPkFWn",
"currencies": [
"eur",
"sek"
],
"default_currency": "sek"
}
bold dune
Hey! Taking over for my colleague. Let me catch up.
This issue will require an in-depth investigation from our team in order to figure out the root cause. Can we ask that you write in to us via https://support.stripe.com/contact, providing as much detail and context as possible (you can also reference this thread).
This is still a private feature and we need to debug it further. If you could export the network record during the component initialization (.har) that would be very helpfull too.
pearl gazelle
Okey, sure I'll do that. Thanks!