[Failed to initialize a component [a is undefined]]

[AlfDev1996]

Hi @clifford-fra

I have been using your component for some time and it has always worked perfectly. But from 4/5 days the component stopped working with the following message:

This page has an error. You might just need to refresh it. Error during LWC component connect phase: [Failed to initialize a component [a is undefined]] Failing descriptor: {markup://flowruntime:auraField}

Can you help me ?

[clifford-fra]

Hey @AlfDev1996

I'm sorry to here that the component has started to fail.

Did you activate some Release Updates 4/5 days ago or has the Salesforce Winter Release '23 been rolled out on your Org?

[AlfDev1996]

I think that salesforce has forcibly updated with all the news of winter 23 (domains etc)

@clifford-fra Thanks for the quick reply, do you have any idea how I could fix the problem?

[clifford-fra]

It might be connected to the Enhanced Domains Release Update or the more restrictive handling of the guest user.

Where's your flow deployed? On a community, somewhere else by lightning out?

[AlfDev1996]

Advanced domains release update I haven't enabled in salesforce yet. The captcha has always worked smoothly and is inserted into a Flow which is exposed externally. I have a guest user that I've always used by enabling all permissions, I don't know if Salesforce has updated something for a few days now

[clifford-fra]

Has your Guest User the "Google Recaptcha Flow Component" Permission Set assigned?

[AlfDev1996]

yes from 23/05/22 and it worked up to 4/5 days ago

[clifford-fra]

I will properly check the component, but my time is limited so I can do it earliest on Saturday.

Until then, you have to remove the component.

[AlfDev1996]

thank you very much, hope you can check the component as soon as possible

[AlfDev1996]

Hi @clifford-fra a few days ago the captcha has magically started working again. Do you know if anything has changed? As I would not like any surprises in PROD

[clifford-fra]

Hey @AlfDev1996 ,

I debugged the component at the weekend and everything seemed to work fine, but I couldn't test it on a public experience cloud site, because I had troubles setting up any flow running on the site... (Thanks salesforce for always changing permission structure etc....)

My suggestion is, that the Callout to Google with the Server Side Verification had some issues (either on Google or on Salesforce side) and that's why the Apex method returned you some error.

I reviewed the changes of the winter release '23 and only found some minor things, which shouldn't impact the component.