[ECUK][In-App 3DS] Investigate why importing AuthorizeTransaction in useNavigateTo3DSAuthorizationChallenge crashes the browser

[chuckdries]

If you import src/components/MultifactorAuthentication/config/scenarios/AuthorizeTransaction in src/libs/Navigation/useNavigateTo3DSAuthorizationChallenge at all, the browser gets stuck in an infinite reload loop. We want to replace the hard-coded allowedAuthenticationMethods list in the effect with the list from the scenario config, but we cannot until we figure this out.

[DylanDylann]

@chuckdries I'm not sure what's happening on your side, but it worked well for me.

import AuthorizeTransaction from '@components/MultifactorAuthentication/config/scenarios/AuthorizeTransaction';

 .................

        const doesDeviceSupportAnAllowedAuthenticationMethod = AuthorizeTransaction.allowedAuthenticationMethods.some((method) => {

[rafecolton]

Marked this as part of release 4, since it's a functional pre-requisite to implementing passkey for transaction authorization

[rafecolton]

Thanks @DylanDylann - maybe the failure is an artifact of code in #82704 that has since been changed. Hopefully it will be a quick fix after #82704 is merged 🤞

[chuckdries]

I'll look tomorrow

[chuckdries]

Yeah, I couldn't repro the issue. Raised a PR to use the scenario config directly in that file

[rafecolton]

Nice, looks like this is all done! It's in production, so I'm closing it out.