#nier_docs

1 messages · Page 1 of 1 (latest)

zinc copperBOT
#

👋 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/1421156167698223184

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

hardy warren
#

Hi there, looking at this now

#

Is there a request ID that you can share?

novel fog
#

@hardy warren this is a client side error so I don't think so, please correct me if I am wrong

hardy warren
#

According to the changelog you shared, you'll need to be using the Node.js SDK 18.5.0 • Basil

#

That component won't exist in 18.4.0 or below

#

Can you share the account ID you used to make this request?

zinc copperBOT
novel fog
#

@hardy warren the account id is "acct_1QPqMbAeBrbCOVTG"

hardy warren
#

At a glance it looks like you're using Stripe/v1 NodeBindings/8.222.0, can you double check?

novel fog
#

I am actually using ^18.5.0, is this the wrong version?

#

"stripe": "^18.5.0",

hardy warren
novel fog
#

@hardy warren sorry the account is actually "acct_1JwDnBJQIXbrDAWa"
I can't open the log you sent me

#

this is my request

image.png
#

My guess is that the problem is on the front-end libraries maybe

#

@hardy warren are those the correct versions?
"@stripe/connect-js": "^3.3.30",
"@stripe/react-connect-js": "^3.3.30",

foggy bridge
#

👋 changing of the guard here, i'll be taking over for nobs. Looking into this.

novel fog
#

@foggy bridge yes that's also where I found it, but this is only the backend doc, which seems to be working fine, the problem is client side

#

no I don't have a test page to show

#

connect.esm.js:208 Uncaught (in promise) Error: Element balance_report was not transformed into a custom element. Are you using a documented component? See https://docs.stripe.com/connect/supported-embedded-components for a list of supported components
at connect.esm.js:208:1

the client error points me to the connect doc where it isn't mentioned

#

in then npm libraries I also see no mention of this component

foggy bridge
#

Digging into this, it might just be an omission in our doc's...obviously that makes it harder troubleshoot. Still digging into this.

novel fog
#

Ok! Thanks a lot

#

for some extra context, other embedded components are working fine, the only problem is on the balance_report one

foggy bridge
#

Ok, so it looks like these were inadvertently listed as available but the components aren't actually ready yet.

#

I think an attempt was made to remove references in our doc's but it looks like it's still in the change log.

novel fog
#

@foggy bridge so this component isn't available right now, correct?

foggy bridge
#

Correct.

#

I'm seeing if we can do anything to make this more clear in our documentation, as obviously the change log is a little misleading here and understandably frustrating.

#

I'm going to add this conversation to an open ticket regarding this.
For now i'd recommend writing in to our support and requesting access to this feature.

foggy bridge
#

if you successfully file a case please provide the case number here so I can also attach it to our internal ticket.